ethm1 op pl 1.07, Satel, Instrukcje
[ Pobierz całość w formacie PDF ]
//-->SATEL 2014-04-02Short technical description: INT-RS v1.12 2013-11-08, INT-RS v2.12 2013-11-08andETHM-1 v1.07 2013-10-23The INT-RS module is an INTEGRA LCD-bus to RS-232 converter. It is dedicated to work with INTEGRA v1.12 2013-11-08 ornewer.The ETHM-1 module converts INTEGRA LCD-bus to Ethernet network - its protocol is described inFunction 2chapter.INT-RS v2.xx is 100% backward compatible with INT-RS v1.xx.To properly configure INT-RS module with INTEGRA panel, the following steps should be done:1) Set the module address using DIP-switches 3..1 (3-MSB, 1-LSB). Allowed addresses are:- 0..3 - for INTEGRA 24 and 32 (i.e. DIP3='OFF')- 0..7 - for INTEGRA 64, 128, 128-WRL, 64 PLUS, 128 PLUS and 256 PLUSE.g. to set the 6 address = 110bin, the DIP-switches should be moved to: DIP3='ON', DIP2='ON', DIP1='OFF'.2) Set the module function using DIP-switches 8..4 (8-MSB, 4-LSB). Possible values are 0 to 31 = 00000binto 11111bin, butonly the first few functions are present (see description below).3) Connect INT-RS module to INTEGRA LCD bus using 4-wire cable.4) Enter the service mode, go to theStructuremenu ->Hardwaremenu ->Identificationmenu ->LCD keypads id.function.For more details refer to INTEGRA manuals.Function 0- DIP-switches 8..4 = 00000The module RS-232 port acts as INT-KLCD keypad serial port. For details refer toINT-KLCD eng.pdfdocument.Function 1- DIP-switches 8..4 = 00001The module is used by INTEGRA panel for the monitoring purposes. To activate monitoring through INT-RS module, set theMon.ETHM-1option in panel service settings.If the system contains ETHM-1 modules and INT-RS modules with function 1, setting theMon.ETHM-1option will allow to monitorevents only by one of these modules - the one with the lowest address (e.g. the system contains modules: ETHM-1 address 5, INT-RSwith function 0 address 1 and INT-RS with function 1 address 3 modules. Monitoring will be processed only through INT-RS withfunction 1 address 3 module).RS-232 serial port of INT-RS module is configured as 4800/8/1/N. The DB9-male connector on the PCB uses the following lines:- RX (pin 2) - serial input- TX(pin 3) - serial output- DTR (pin 4) - output - active when INT-RS module has communication with INTEGRA- GND (pin 5) - signal ground- DSR (pin 6) - input - the module can use this signal only to generate 'No external device DTR signal' eventThe GND lines between INT-RS module and external device must be tied together.The RX and TX lines should be swapped.The DTR and DSR lines should also be swapped, if they are used.In INTEGRA service mode it can be set that INT-RS module does or does not generate 'No external device DTR signal' event. It canalso be set that INT-RS module does or does not check '?',#13 command (see below). If set, a monitoring trouble arises if externaldevice does not ask INT-RS with '?',#13 question for a time longer that 32 seconds.Communication between INT-RS module and external device is arranged is such a way that external device should ask INT-RSmodule to check if a new event is ready to be send to a monitoring station. All data are ASCII chars ended with CR char (#13 = 0x0Dbyte). Data exchange is no time dependent.Commands that INT-RS module understands:- '?',#13- a question if a new event is ready (2 bytes: 0x3F, 0x0D)- '+',m,#13 - confirmation of sending event with marker m (3 bytes: 0x2B, m, 0x0D)- '-',m,#13 - error sending event with marker m (3 bytes: 0x2D, m, 0x0D)An answer is returned only on '?',#13 question. Possible answers are listed below:- 'OK',#13- no new event to send- 'EN=m,s,iiii,cc'#13- 4/2 event to sent: m - event marker, s - monitoring station number ('1' or '2'),iiii - event identifier, cc - event code- 'EC=m,s,iiii,q,ccc,pp,nnn'#13- Contact ID event to send: s - monitoring station number ('1' or '2'), m - eventmarker, iiii - event identifier, q and ccc - event code, pp - partition number,nnn - source numberEvents format and what events should be sent (4/2 or Contact ID) are to be set in INTEGRA service mode.Event marker m is a char between 'a' and 'z'. The current event and its marker remain unchanged upon successive '?',#13 questions,until the event is confirmed by '+',m,#13 command from the external device or if INTEGRA time-out occurs (75 seconds). The nextevent, if ready, will be submitted by INT-RS module with succeeding value of marker m.-1-SATEL 2014-04-02Function 2- DIP-switches 8..4 = 00010The 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 (sendcommand 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):0xFE0xFEcmdd1d2...dncrc.highcrc.low0xFE0x0DThe 16-bit crc sum is calculated as follows (see Appendix 4):1) Set crc := 0x147A2) 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 0xFFFFc) crc := crc + crc.high + b, e.g. if crc=0xFEDC and b=0xA9 then: 0xFEDC + 0xFE + 0xA9 = 0x0083The 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 receives0xFE, 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 bestill 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 besent 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 notsuitable 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 0DFE FE 1C D7 FE F0 FE 0DPart 1 - Reading INTEGRA state:cmd meaning0x00 zones violation0x010x020x030x040x050x060x070x080x090x0A0x0B0x0C0x0D0x0E0x0F0x100x110x120x130x140x150x160x170x180x19zones tamperzones alarmzones tamper alarmzones alarm memoryzones tamper alarm memoryzones bypasszones 'no violation' troublezones 'long violation' troublearmed partitions (suppressed)armed partitions (really)partitions armed in mode 2partitions armed in mode 3partitions with 1st code enteredpartitions entry timepartitions exit time >10spartitions exit time <10spartitions temporary blockedpartitions blocked for guard roundpartitions alarmpartitions fire alarmpartitions alarm memorypartitions fire alarm memoryoutputs statedoors openeddoors opened longanswer0x00 + 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 + 16/32 bytes (*)0x02 + 16/32 bytes (*)0x03 + 16/32 bytes (*)0x04 + 16/32 bytes (*)0x05 + 16/32 bytes (*)0x06 + 16/32 bytes (*)0x07 + 16/32 bytes (*)0x08 + 16/32 bytes (*)0x09 + 4 bytes0x0A + 4 bytes0x0B + 4 bytes0x0C + 4 bytes0x0D + 4 bytes0x0E + 4 bytes0x0F + 4 bytes0x10 + 4 bytes0x11 + 4 bytes0x12 + 4 bytes0x13 + 4 bytes0x14 + 4 bytes0x15 + 4 bytes0x16 + 4 bytes0x17 + 16/32 bytes (*)0x18 + 8 bytes0x19 + 8 bytes-2-SATEL 2014-04-02cmd0x1A0x1B0x1C0x1D0x1E0x1F0x200x210x220x230x240x250x260x270x280x290x2A0x2B0x2C0x2D0x2E0x2F0x7CmeaningRTC and basic status bitstroubles part 1troubles part 2troubles part 3troubles part 4troubles part 5troubles memory part 1troubles memory part 2troubles memory part 3troubles memory part 4troubles memory part 5partitions with violated zoneszones isolatepartitions with verified alarmszones maskedzones masked memorypartitions armed in mode 1partitions with warning alarmstroubles part 6troubles part 7troubles memory part 6troubles memory part 7INT-RS/ETHM-1 module versionanswer0x1A + 9 bytes (see description below)0x1B + 47 bytes (see description below)0x1C + 26 bytes (see description below)0x1D + 60 bytes (see description below)0x1E + 30 bytes (see description below)0x1F + 31 bytes (see description below)0x20 + 47 bytes (see description below)0x21 + 39 bytes (see description below)0x22 + 60 bytes (see description below)0x23 + 30 bytes (see description below)0x24 + 48 bytes (see description below)0x25 + 4 bytes0x26 + 16/32 bytes (*)0x27 + 4 bytes0x28 + 16/32 bytes (*) (**)0x29 + 16/32 bytes (*) (**)0x2A + 4 bytes (**)0x2B + 4 bytes (**)0x2C + 45 bytes (see description below) (***)0x2D + 47 bytes (see description below) (***)0x2E + 45 bytes (see description below) (***)0x2F + 48 bytes (see description below) (***)0x7C + 12 bytes, e.g. for version 1.23 2012-05-27 (****):11 bytes1 byte- '12320120527'- .0 - 1 = module can serve 32 data bytes for zones/outputs0x7D +1 byte - read zone temperature0x7E INTEGRA version0x7D + 3 bytes (answer can be delayed up to 5s):1 byte- zone number 1..256 (send 0 instead of 256)2 bytes - temperature (high,low):0x0000 = -55.0 °C0x0001 = -54.5 °C0x006E = 00.0 °C...0xFFFF = undeterminedIf requested zone is not temperature zone, answer will not be returned.0x7E + 14 bytes, e.g. for version 1.23 2012-05-27:1 byte- INTEGRA type:0, 1, 2, 3= INTEGRA 24, 32, 64, 1284= INTEGRA 128-WRL SIM300132= INTEGRA 128-WRL LEON66= INTEGRA 64 PLUS67= INTEGRA 128 PLUS72= INTEGRA 256 PLUS- '12320120527'- language version (1 = english, otherwise other language version)- 255 = settings stored in FLASH, otherwise not stored11 bytes1 byte1 byteNote:in INT-RS v2.xx all commands 0x00..0x2F can be sent as 2-bytes (i.e. command byte + 1 additional byte), but those of themthat are not marked with (*) in above list will answer the same way as were sent as 1-byte command.if any command returns data that contains more zones/outputs etc. than INTEGRA connected to INT-RS, the redundancy datareturned will be cleared. E.g. if INT-RS is connected to INTEGRA 24, the command 0x00 will return 16 data bytes in whichonly the first 3 bytes could be non-zero (i.e. zones 1..24) and the remaining 13 bytes should be zeros. Using 0x00 + 1 bytecommand (e.g. 0x00, 0x00 - in INT-RS v2.xx only) will return 32 bytes in which 29 last bytes should be zeros.Note:*In INT-RS v1.xx this command is only 1-byte long and it returns 16 bytes of data.In INT-RS v2.xx this command can be used as 1-byte long (as in v1.xx) or as 2-bytes long - send it with 1 additional byte (no matterof its value) and this command will return 32 bytes of data (i.e. list of 1..256 zones/outputs).2-bytes version of this command is especially usefull in conjuction with INTEGRA 256 PLUS.In INT-RS v1.xx answer can be delayed up to 5s.In INT-RS v2.xx answer is returned immediately.Command available in INT-RS v2.xx only.Modules ealier than 2013-11-08 does not know this command, so they will not reply.-3-*********SATEL 2014-04-02cmd meaning0x7F list of new states of above dataanswer0x7F + 5 bytes(each bit is set when new data is collected in corresponding command,each bit is cleared after reading the corresponding command):1 byte - .0 - 1 = new data in 0x00 command.1 - 1 = new data in 0x01 command.2 - 1 = new data in 0x02 command.3 - 1 = new data in 0x03 command.4 - 1 = new data in 0x04 command.5 - 1 = new data in 0x05 command.6 - 1 = new data in 0x06 command.7 - 1 = new data in 0x07 command1 byte - .0 - 1 = new data in 0x08 command.1 - 1 = new data in 0x09 command.2 - 1 = new data in 0x0A command.3 - 1 = new data in 0x0B command.4 - 1 = new data in 0x0C command.5 - 1 = new data in 0x0D command.6 - 1 = new data in 0x0E command.7 - 1 = new data in 0x0F command1 byte - .0 - 1 = new data in 0x10 command.1 - 1 = new data in 0x11 command.2 - 1 = new data in 0x12 command.3 - 1 = new data in 0x13 command.4 - 1 = new data in 0x14 command.5 - 1 = new data in 0x15 command.6 - 1 = new data in 0x16 command.7 - 1 = new data in 0x17 command1 byte - .0 - 1 = new data in 0x18 command.1 - 1 = new data in 0x19 command.2 - 1 = new data in 0x1A command.3 - 1 = new data in 0x1B command.4 - 1 = new data in 0x1C command.5 - 1 = new data in 0x1D command.6 - 1 = new data in 0x1E command.7 - 1 = new data in 0x1F command1 byte - .0 - 1 = new data in 0x20 command.1 - 1 = new data in 0x21 command.2 - 1 = new data in 0x22 command.3 - 1 = new data in 0x23 command.4 - 1 = new data in 0x24 command.5 - 1 = new data in 0x25 command.6 - 1 = new data in 0x26 command.7 - 1 = new data in 0x27 commandIn INT-RS v2.xx (see below):1 byte - .0 - 1 = new data in 0x28 command.1 - 1 = new data in 0x29 command.2 - 1 = new data in 0x2A command.3 - 1 = new data in 0x2B command.4 - 1 = new data in 0x2C command.5 - 1 = new data in 0x2D command.6 - 1 = new data in 0x2E command.7 - 1 = new data in 0x2F commandNote:in INT-RS v1.xx - 0x7F command returns 0x7F + 5 bytes,in INT-RS v2.xx - 0x7F command returns 0x7F + 5 bytes, but 0x7F command send with 1 additional byte (no matterof its value) returns 0x7F + 6 bytes (see the list above).-4-SATEL 2014-04-02Answers description:RTC and basic status bits- 7 bytes - time: YYYY-MM-DD hh:mm:ss - 0xYY, 0xYY, 0xMM, 0xDD, 0xhh, 0xmm, 0xss1 byte - .210 - day of the week (0 = Monday, 1 = Tuesday, ..., 6 = Sunday).7 - 1 = service mode.6 - 1 = troubles in the system (= flashing TROUBLE LED in keypad)1 byte -.7 - 1 = ACU-100 are present in the system.6 - 1 = INT-RX are present in the system.5 - 1 = troubles memory is set in INTEGRA panel.4 - 1 = Grade2/Grade3 option is set in INTEGRA panel.3210 - INTEGRA type:0 = INTEGRA 241 = INTEGRA 322 = INTEGRA 64 / INTEGRA 64 PLUS3 = INTEGRA 128 / INTEGRA 128 PLUS4 = INTEGRA 128-WRL8 = INTEGRA 256 PLUS(to read detailed type use 0x7E command)- 16 bytes8 bytes8 bytes8 bytes3 bytes1 byte1 byte1 byte1 byte- 8 bytes8 bytes8 bytes2 bytes- 15 bytes15 bytes15 bytes15 bytes- 8 bytes8 bytes1 byte1 byte1 byte8 bytes1 byte1 byte1 byte- 1 byte30 bytes-15 bytes15 bytes15 bytestroubles part 1- troubles - technical zones- expanders AC trouble- expanders BATT trouble- expanders NO BATT trouble- system troubles (see description below)- CA-64 PTSA modules AC trouble- CA-64 PTSA modules BATT trouble- CA-64 PTSA modules NO BATT trouble- ETHM-1 monitoring trouble- proximity card readers head A trouble- proximity card readers head B trouble- expanders supply output overload- addressable zone expanders short circuit or jammed ACU-100 modules- ACU-100 modules jam level- radio devices with low battery- radio devices with no communication- radio outputs with no communication- expanders with no communication- switcherooed expanders- LCD keypads with no communication- switcherooed LCD keypads- ETHM-1 modules with no LAN cable / INT-RS modules with no DSR signal- expanders tamper- LCD keypads tamper- LCD keypad initiation errors- auxiliary STM troubles (in INTEGRA PLUS, in others value of this field is 0)- low battery in masters key fobs- low battery in users key fobs- radio devices with low battery (last 120 ACU-100 devices in INTEGRA 256 PLUS)- radio devices with no communication (last 120 ACU-100 devices in INTEGRA 256 PLUS)- radio outputs with no communication (last 120 ACU-100 devices in INTEGRA 256 PLUS)troubles part 2troubles part 3troubles part 4troubles part 5troubles part 6troubles part 7- 16 bytes16 bytes15 bytes- troubles - technical zones 129..256 in INTEGRA 256 PLUS- memory of troubles - technical zones 129..256 in INTEGRA 256 PLUS- ACU-100 modules jam level (last 15 ACU-100 modules in INTEGRA 256 PLUS)-5-
[ Pobierz całość w formacie PDF ]