Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Girr 2.0": Make Girr useful for more than proper sense IR #2

Open
bengtmartensson opened this issue Nov 9, 2017 · 0 comments
Open

Comments

@bengtmartensson
Copy link
Owner

Although the applicationData allows for adding all sort of data, it would be desirable to make Girr more explicitly in inviting to use for other kind of remote control than IR in the proper sense, i.e. either raw signals or protocol/parameter form of signals. For this, in the commandSet element. there should be a parameter kind taking values like "ir", "serial", "tcp", "udp", "http", code" etc. (Default to "ir" for backwards compatibility). (Let's make it "text", and not an ennumeration, to be able to have it user extendable). It using this parameter, it may be necessary to complement it with some application parameter (appParameter), like code requires (e.g.) a lirc driver. both to make sense of the codes and to send them.

For example, the atilibusb.lircd.conf may be turned into

<remote vendor="ATI" name="ATI_Remote_Wonder_II">
    <commandSet type="code">
          <applicationData application="lirc">
                 <appParameter name="driver" value="atilibusb"/>
                  <appParameter name="gap" value="203970"/>
            </applicationData>
            <command name="KEY_STOP" code="0x000231"/>
             ...
      </commandSet>
</remote>

Similarly, a Sony Projector can be controlled serially and over IR by

<remote id="sony_vlp_hw50es" name="Sony VLP HW50ES" vendor="Sony" model="VLP HW50ES" type="projector">
<commandSet kind="serial">
       <applicationData application="serial">
            <applicationParameter name="protocol" value="rs232"/>
             <applicationParameter name="baud" value="38400"/>
              <applicationParameter name="dataBits="8"/>
              <applicationParameter name="parity" value="even"/>
               <applicationParameter name="stopBits" value="1"/>
               <applicationParameter name="commandFormatter" value="org.harctoolbox.harchardware.misc.SonySerialCommand"/>
        </applicationData>
        <command name="power_toggle" code="set,23,21"/>
         ...
    </commandSet>
    <commandSet name="sony15" protocol="sony15" deviceno="84">
           <command name="video_mute_toggle" code="36"/>
           ....
    </commandSet>     
     ....
</remote>

Here, the attribute F in command has been renamed to code.

Remains to define syntax and semantic for

  • input arguments,
  • output arguments.

Note that:

  1. This does not concern IrScrutinizer proper,
  2. The changes are all to girr[_ns].xsd.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant