User guide

20 HDMI5 Component Video Switch
When used in combination with the “Read Last IR Code” command, even IR commands can be handled by the controller, outside the HDMI5’s fi rmware. Because of the tight link between this command and the HDMI5’s fi rmware, there are some caveats when using this command. The Zektor fi rmware expects a button press code to always
be followed by a button release code. Sending these codes out of logical order will not harm the HDMI5, but may result in unpredictable behavior (buttons codes ignored, or unexpected state changes).
B b1,bn... Send one or more button codes to the HDMI5. B ? Query for any buffered button presses. B Query for any buffered button presses. Response String: =B b1,bn... Where: b1,bn.. = A variable number of button codes (1 to 16 codes per command).
In the Master / Slave mode, only the last 16 button presses will be logged between queries, after that, new button presses overwrite the old ones in the internal buffer and will be lost to the controller. The maximum number of button codes that can be sent is 16. If more than 16 button codes are sent a “parameter count error” will be returned and only the fi rst 16 button codes will be accepted. The Button Codes for the HDMI5 are defi ned as follows:
Button Press Code Release Code Power Toggle 10 19 Input 1 Select 2 20 Input 2 Select 3 21 Input 3 Select 4 22 Input 4 Select 5 23 Input 5 Select 6 24 ‘Sel’ Button 7 25 ‘A1’ Relay Toggle 8 26 ‘A2’ Relay Toggle 9 27
The “Press Code” is the value returned when a button pressed, and the “Release Code” is the value returned when a button is released. There are also a small number of codes that are unique to this command that cannot be gener-
HDMI5 Command Ref. (Cont’d)
9HDMI5 Component Video Switch
The unsolicited Query Responses were handled internally by the new “Get Response” routine, and fi ltered from the communication fl ow, and only the Acknowledgement (or possible Error) Responses were allowed to pass. When the “=LI 2,13<CR><LF>” response is eventually received, it will be handled like any other unsolicited response. Using K.I.S.S.™ in the Asynchronous mode is nearly as easy as using it in the Master / Slave mode, allowing for the creation of simple to write, but highly effi cient device drivers.
K.I.S.S.™ (Continued)