ICAS UWI-IQ, Руководство пользователя, Страница: 11 / 12

SPI message structure and instruction set (the same structure and instruction set is used for both ICAS wireless system or OEM system)
SPI message structure:
// CMD // PTYPE // DATA_1 // DATA_2 // DATA_3 // DATA_4 // CRC//
where
CMD
= F0 ..... Data read/write operation code
PTYPE = 84 ..... code for full duplex communication 80+ data block length
DATA_1 = master data - actual chamber value *
/ slave data - source component ID number **
DATA_2 = master data - average chamber value * / slave data - source subloop ID number **
DATA_3 = master data - status byte of the detector* / slave data - source zone ID number **
DATA_4 = master data - detector info (ASCII code upper case ) / slave data - loop info (ASCII code - lower case)
CRC
= ((CMD) xor (PTYPE) xor (DATA_1) xor (DATA_2) xor (DATA_3) xor (DATA_4) xor (5F)) for the master message
CRC = ((PTYPE) xor (DATA_1) xor (DATA_2) xor (DATA_3) xor (DATA_4) xor (5F)) for the slave message
*
these data are not broadcasted by IQRF radio-transceiver
** these data are not evaluated by the detector / serves for control panel operations
The Interface microcontroller serves as the SPI master for a communication between the IQRF radio-module and the in built Interface microcontroller.
The SPI slave (radio-module) is waken up periodically and the message from SPI master to SPI slave and from SPI slave to SPI master are exchanged at the
same time. The SPI message includes 4 data bytes due to compatibility of the protocol with
µ
CU-IQ, but for the Interface is mostly important the last data byte
only, on this data position is sent a code which informs about Interface events and received code with information/instruction from the SLAVE module (loop
info). If instruction code is 'w' , the other bytes are used for UWI-IQ configuration:
- the first byte is interpreted as the new input delay
- the second byte is interpreted as the new output delay
- the third byte is interpreted as a new configuration byte CFG with following meanings of single bits:
CFG Configuration byte structure:
FIN
ALARM INPUT CONFIGURATION - 0: NO - input active if closed /// 1: NC - input active when open
EIN FAULT INPUT CONFIGURATION - 0: NO - input active if closed /// 1: NC- input active when open
REL Outputs response to local events - 0: response only to remote events /// 1: response to local or remote alarm/fault
QRE Q Response - 0: Q response is blocked (default) /// 1: response to Q instruction enabled
RFT special RF communication test - not applied (the compatible standard communication test is solved in the system with uCU-IQ )
HRE H Response - 0: HUSH function is disabled /// 1: HUSH function and response to H enabled
x
x
ICAS instruction set (ASCII code interpretation):
Code set transmitted by UWI-IQ interface (by MASTER)
Code set accepted from SLAVE (from the radio-module) and evaluated by Interface
code detector status code code interpretation
F local fire alarm info f request for remote alarm indication
S stopped local fire alarm info s request for remote fire alarm indication stop
E detector /chamber/ error info e request for remote error indication
C stopped error or low battery info c directive to suppress the remote error , low batt and com. lost indication
Q request to stop all remote events indications q directive to stop all remote evens indication incl. remote alarm)
T test request w instruction before special EEprom update operation
R loop reset request r RESET directive - stop all detector indication of both remote and local events
(the detector in the alarm condition gets into hush first)
N no significant event i request for basic detector status info
k request for communication lost indication
X info about RESTART x for detector RESTART
Z data after w directive was not accepted
Additional codes which are used for communication
L
D
K
Appendix 1
SPI IQRF compatible protocol description
Appendix 2
ICAS IQ wireless system configuration
/ LEARN/ DELETING from the LOOP or sub-loop/ Creating the wireless PEER to PEER loop / Zone configuration/