Satel ETHM-1 - Manual (Page 2)

SATEL 2014-04-02
Function 2 - DIP-switches 8..4 = 00010
The module is used by INTEGRA panel for integration purposes. The same protocol is used by ETHM-1 module - see it below.
INT-RS v2.xx can be used with any INTEGRA model, INT-RS v1.xx can be use with any INTEGRA except 256 PLUS.
Using INT-RS v1.xx with INTEGRA 256 PLUS results in limitations on zones, outputs and troubles.
RS-232 serial port of INT-RS module is configured as 19200/8/1/N. The DB9 connector uses the same lines as in Function 1.
Communication between INT-RS module and external device is arranged is such a way that external device should ask (send
command to) INT-RS module, and the module will answer immediately, if it is not marked otherwise.
Data exchange is no time dependent. The protocol uses the following frame structure (both ways - from and to INT-RS):
0xFE 0xFE cmd d1 d2 ... dn crc.high crc.low 0xFE 0x0D
The 16-bit crc sum is calculated as follows (see Appendix 4):
1) Set crc := 0x147A
2) For all successive bytes b = cmd, d1, d2, ..., dn perform the crc update steps:
a) crc := rl(crc) - rotate crc 1 bit left (msb=bit.15 shifts into lsb=bit.0 position)
b) crc := crc xor 0xFFFF
c)
crc := crc + crc.high + b, e.g. if crc=0xFEDC and b=0xA9 then: 0xFEDC + 0xFE + 0xA9 = 0x0083
The 0xFE byte is special value:
1) Two (or more) successive 0xFE mean frame synchronization - i.e. if device waits for any data-frame byte and it receives
0xFE, 0xFE - it should interrupt collecting the current frame and start waiting for cmd.
2) If device is waiting for the 1st byte of a frame (i.e. waiting for cmd), receiving 0xFE should not change it - device should be
still waiting for cmd. So, cmd can not be 0xFE.
3) If any byte of the frame (i.e. cmd, d1, d2, ..., dn, crc.high, crc.low) to be sent is equal 0xFE, the following two bytes must be
sent instead of single 0xFE byte: 0xFE, 0xF0. In such case only single 0xFE should be used to update crc.
4) If 0xFE, 0x0D are received, it means the frame is completed and it can be processed - i.e. check crc and analyze.
5) If other value after 0xFE is received - treat it as 0xFE, 0xFE (i.e. treat it as synchronization sequence).
If frame is corrupted (i.e. wrong crc sum or interrupted by 0xFE, 0xFE before completed) or cmd is not know or data length is not
suitable for cmd - it is dropped and no answer is given back. External device should act the same way.
Exemplary frames:
FE FE 09 D7 EB FE 0D FE FE 1C D7 FE F0 FE 0D
Part 1 - Reading INTEGRA state:
cmd meaning answer
0x00 zones violation 0x00 + 16/32 bytes (*)
(e.g. 04 20 00 00 00 00 00 00 00 00 00 00 00 00 00 80 - zones 3, 14 and 128)
0x01 zones tamper 0x01 + 16/32 bytes (*)
0x02 zones alarm 0x02 + 16/32 bytes (*)
0x03 zones tamper alarm 0x03 + 16/32 bytes (*)
0x04 zones alarm memory 0x04 + 16/32 bytes (*)
0x05 zones tamper alarm memory 0x05 + 16/32 bytes (*)
0x06 zones bypass 0x06 + 16/32 bytes (*)
0x07 zones 'no violation' trouble 0x07 + 16/32 bytes (*)
0x08 zones 'long violation' trouble 0x08 + 16/32 bytes (*)
0x09 armed partitions (suppressed) 0x09 + 4 bytes
0x0A armed partitions (really) 0x0A + 4 bytes
0x0B partitions armed in mode 2 0x0B + 4 bytes
0x0C partitions armed in mode 3 0x0C + 4 bytes
0x0D partitions with 1st code entered 0x0D + 4 bytes
0x0E partitions entry time 0x0E + 4 bytes
0x0F partitions exit time >10s 0x0F + 4 bytes
0x10 partitions exit time <10s 0x10 + 4 bytes
0x11 partitions temporary blocked 0x11 + 4 bytes
0x12 partitions blocked for guard round 0x12 + 4 bytes
0x13 partitions alarm 0x13 + 4 bytes
0x14 partitions fire alarm 0x14 + 4 bytes
0x15 partitions alarm memory 0x15 + 4 bytes
0x16 partitions fire alarm memory 0x16 + 4 bytes
0x17 outputs state 0x17 + 16/32 bytes (*)
0x18 doors opened 0x18 + 8 bytes
0x19 doors opened long 0x19 + 8 bytes
- 2 -