
2
Copyright © 2009 ILLUMRA. All rights reserved.
Contact ILLUMRA:
T: (80) 349-200 | F: (80) 653-4257 | [email protected] | www.ILLUMRA.com
AHD0239B
LENGTH (5 bit) Number of octets following the header octet ( dec)
ORG (8 bit) Type of telegram (see detail description)
DATA_BYTE 0..3 (8 bit each) Data bytes 0..3 (see detail description)
ID_BYTE 0..3 (8 bit each) 32-bit transmitter ID
STATUS (8 bit) Status field (see detail description)
CHECKSUM (8 bit) Checksum (Last LSB from addition of all octets except
sync bytes and checksum)
Table C: Detailed Description of ORG Field
ORG field value
(decimal)
Acronym
Description
5
RPS
Telegram from a PTM switch module received (e.g. PTM 100 or PTM 200)
6
1BS
1 byte data telegram from a STM sensor module (e.g. STM 250)
7
4BS
4 byte data telegram from a STM sensor module (e.g. STM 100)
8
HRC
Telegram from a CTM module received
0-47, 9-255
--
Reserved
Operation
Verify Serial Port – Connect to terminal program, like “HyperTerminal” or “Portmon” and monitor activity on serial port. Each time
another ILLUMRA device transmits, a few copies of the data packet should flow through to the serial port.
The data received from the modules contains non-printable characters. In order to see the exact contents of the received packets, set
up a text capture with Transfer->Capture Text. An alternative to the text capture method is to run a serial port monitoring program
(use Google to search for “portmon” which is available as a free download from microsoft.com, and can display the hexadecimal values
during serial operation).
Save the file in a convenient location.
Serial Data Structure
The structure of the serial data is as follows:
Table A: Serial Data Structure
Bit 7
Bit 0
SYNC_BYTE1 (A5 Hex)
SYNC_BYTE0 (5A Hex)
H_SEQ (3 bits)
LENGTH (5 bits)
ORG
DATA_BYTE3
DATA_BYTE2
DATA_BYTE1
DATA_BYTE0
ID_BYTE3
ID_BYTE2
ID_BYTE1
ID_BYTE0
STATUS
CHECKSUM
SYNC_BYTE 0.. (8 bit each) Synchronization Bytes
H_SEQ (3 bit) Header Identification [refer to table below]
Table B: Header Identification
H_SEQ
Meaning
Mode
0b 000
Unknown transmitter ID received
(serial telegram only if no ID has been learned so far!)
For RPS also:
-- Known transmitter ID and unknown rocker
-- U-message from known transmitter ID received
For HRC also:
-- Known transmitter ID and unknown rocker
-- Scene switch command (last three bits of ID 0b111) from known
transmitter ID (only first 29 bits are compared!)
Operating
Mode
0b 001
For 1BS and 4BS: Known transmitter ID received
For RPS: Known transmitter ID and at least 1 known rocker (1 or 2 rockers
operated)
For HRC: Known transmitter ID and known rocker
Operating
Mode
0b 010
New transmitter learned (If a switch telegram is received (RPS or HRC),
the rocker code (RID) is stored together with the ID.)
• Mode 3: a telegram with this header information will be sent also when
in LRN mode a transmitter which is already learned is operated again
Learn Mode
0b 110
Mode 0: Transmitter just deleted (If a switch telegram is received (RPS
or HRC), the rocker code (RID) and module ID are checked. The entry is
only deleted if module ID and rocker are known.)
Learn Mode