Innotech Systems SpitFIRE II - Manual (Page 13)

SpitFIRE Innotech Systems Inc. Page 13
It is not strictly necessary to issue a Key Release
command during the programming sequence. The
SpitFIRE will respond to any scancode changes
in the command. The SpitFIRE will operate
properly if you issue:
Button function Scancode Status returned
SOURCE1 press C1 1 flash
PROGRAM press C0 2 flashes
#0 press 80 1 flash
#4 press 84 1 flash
#5 press 85 1 flash
PROGRAM press C0 3 flashes
However, in the absence of a Key Release
command, the SpitFIRE cannot distinguish two
identical consecutive scancodes. For example, if
the ISI number were 113, the first two “ones”
could not be distinguished without a button
release between them.
Once programmed, the SpitFIRE will remember
the ISI numbers of all the programmed sources
until the engine is reset or until it is
reprogrammed. You may have up to six different
devices programmed and quickly scan between
them by issuing a Source # scancode.
The SpitFIRE will respond to programming
codes rapidly. At the end of the programming
sequence it will provide a status byte that
indicates if the engine accepted the ISI number. (3
flashes)
While infrared is actually being transmitted, the
status response to the next button may take
significantly longer. If an undefined scancode is
issued, the device will respond with an error
scancode. In addition, if a button is pressed that
is defined, but is not implemented for the
particular device programmed, the device will
respond with a different error response.
Status Byte From Spit
FIRE
You will get one and only one status change per command that you send to the SpitFIRE .
Status Byte from SpitFIRE
7 6 5 4 3 2 1 0
Button press Tx IR MOD1 MOD0 DAT3 DAT2 DAT1 DAT0
DB7 ScanKey Up/Down feedback bit
DB6 Transmitting IR message bit (if continuous)
DB5-4 MOD bits determine the interpretation of the DAT bits.
0 X Software revision level (5 bits DAT0-3 and MOD0)