PROTOCOL CONVERTER S2000-PP

Transcription

1 PROTOCOL CONVERTER S000-PP USER S MANUAL

2 Table of Content Purpose Specifications Operating 4.. Orion Interface 4.. Modbus/T Interface 5.. S000-PP Operating with a Modbus System 6 4 PCB Layout 9 5 Preparing for Use 0 6 evice Operation 7 Standard elivery 9 Manufacturer Information 9

3 This Manual is intended to help in understanding the principles of operation and using the S000- PP protocol converter of version.4.. Purpose The S000-PP Protocol Converter is designed to integrate a Bolid manufactured fire and intrusion alarm system (Orion system devices) into third vendor equipment by using Modbus-RTU interface. The S000-PP provides: Monitoring events occurred in the Orion system, Switching Orion system relays on / off and arming / disarming Orion system zones and partitions, Receiving numeric values of parameters from Orion system devices.. Specifications.. The S000-PP is to be powered by an external power supply providing 0. V to 5 V dc. It is advised to use Bolid manufactured battery backed power supplies of RIP- series... Current consumption at V: 0 milliamp max;.. RS-45 Orion Working Parameters: Bits per Second: 9600; Start / Stop Bits: ; Parity: None; Maximum Packet Length: 75 bytes..4. Modbus/T Interface Working Parameters:.4. Gateway for the Modbus: Interface Type: RS-45; Protocol Type: Modbus-RTU; Bits per Second: 00, 400, 9600, 900, 400, 57600, 500 bit/s; Parity: None, Even, Odd; Stop Bits: with parity; or without parity; Maximum Packet Length: 56 bytes..4. Transferring events to an RS-0T: Interface Type: RS-45 or RS-TTL; Protocol Type: Contact I; Bits per Second: 9600; Stop Bits: ; Parity: None; Maximum Packet Length: 4 bytes..5. The S000-PPБ atabase provides supporting: Maximum number of relays: 55; Maximum number of zones: 5; Maximum number of partitions: 64; Maximum number of user codes: 64; Maximum number of stored events (circular event log capacity): Pre-operation Time: s max..7. The S000-PP is designed for round-the-clock operating within protected premises... The S000-PP is not supposed to be used in aggressive and dust environment and fire hazardous premises..9. Overall imensions: 55 mm x 6 mm x mm..0. Weight: 0.05 kg max... Operating Temperatures: -0 С to +50 С non-condensing.

4 . OPERATING Table shows operating modes of the S000-PP: Table ORION Interface Modbus/T Interface Operating Mode Master Slave Orion Modbus gateway Slave Slave Master Master Translating events to the RS-0T 4 Slave Master.. Orion Interface... The S000-PP can operate over the Orion Interface either in the Master mode or the Slave mode depending on the position on the jumper XP. efining the mode is performed on starting the program (on applying the power): if the jumper is put on the S000-PP enters the Orion Master mode while, otherwise, if the jumper is put off the S000-PP operates in the Orion Slave mode. The operation mode over the Modbus/T interface and the interface mode (selecting third-vendor equipment) are specified while configuring the device.... In the Orion Master mode the S000-PP polls the devices of the Orion system. Being initialized, the S000-PP sequentially requests for statuses of all zones and relays which are enrolled in its database (the database is created when the S000-PP is programmed). On operating, the S000-PP changes current statuses of zones and partitions in accordance with the events being received from the devices of the Orion system. If a command to turn a relay on/off or to change the status of a zone/partition is received over the Modbus interface, the S000-PP forwards this command to the devices of the Orion system. A single command received by the S000-PP over the Modbus interface can cause, depending on the context, several data calls over the Orion interface with one or several devices of the Orion system.... The Orion Slave mode is designed for: - Configuring the S000-PP by means of the UProg.exe and RS45Setting.exe programs; - Updating S000-PP firmware by means of the Orion_prog.exe program; - S000-PP s operating as a gateway between the Orion system and the Modbus system...4 This mode fundamentally differs in that the S000 or S000M console polls the devices of the Orion system. The S000(M) console must be programmed (by means of the PProg.exe program) to translate events received from the devices to the S000-PP converter. Being initialized, the S000-PP sequentially requests the S000(M) console for the statuses of zones and relays from the S000-PP database. uring operation the S000-PP changes current statuses of zones, partitions, and relays in accordance with messages received from the console. If a command to turn a relay on/off or to change the status of a zone/partition is received over the Modbus interface, the S000-PP forwards this command to the S000(M) console which, in turns, forwards the command to the devices of the Orion system. Notes:. The programs PProg.exe, UProg.exe, RS45Setting.exe, Orion_prog.exe are free and can be downloaded from the site of the Bolid Company at the address of Only the device can be requested for a relay status which can answer for such request: - Signal-0М from the version.0 (device version.0 rev ); - S000-SP from the version.50; - S000-4 from the version.05; - S000-KL from the version.45. 4

5 .. Modbus/T Interface... If the interface is used as a gateway between the Orion system and the Modbus system then the S000-PP operates as a slave in the Modbus Slave mode responding to the Modbus Master. A single Modbus-Master device (third-vendor equipment) can have several Modbus-Slave devices (S000-PP) connected, each of the S000-PP having a unique address from to 47 at the Modbus interface. Figure shows the common packet format. byte byte..5 bytes bytes Modbus ata Fields CRC Field Address Function Code N- N Low byte High byte The minimum packet length is 5 bytes. The maximum packet length is 56 bytes. Figure. Modbus Packet Format A sign of the end of the packet is the delay which is equal or more than the time needed to transmit.5 bytes, according to the selected transmission rate. 5

6 .. S000-PP Operating with a Modbus System... Table shows a list of the functions of the Modbus protocol supported by the S000-PP. Table. Modbus Function Code Modbus Function supported by the S000-PP escription (0x0) Reading values from several flag registers (Read Coil Status) (0x0) Reading values from several holding registers (Read Holding Registers) 5 (0x05) Writing the value of a single flag (Force Single Coil) 6 (0x06) Writing a value into a single holding register (Preset Single Register) 5 (0x0F) Writing values to several flag registers (Force Multiple Coils) 6 (0x0) Writing values to several holding registers (Preset Multiple Registers) A command having been fulfilled successfully, the S000-PP returns a response with the same Function Code as in the query and the requested data in the ata Fields. If the command fails, the S000- PP returns the response with the same Function Code but with the high bit being set on. In the ata Fields of the response in such case the Error Code is transmitted. Modbus Error Codes, generated by the S000- PP are shown in Table. Table. Supported Modbus Error Codes Error Code escription The received Function Code cannot be processed by the slave The address of data specified in the request is not available for the slave The value in the data field of the request is not a valid value for the slave 6 The slave is busy processing the command. The request should be retransmitted when the slave is free 5 The data have not yet been received. For example, the S000-PP has not yet known the status of the requested zone because it has not yet received from the device (Orion-Master mode) or from the S000М console (Orion-Slave mode) the status of this particular zone. The request should be repeated later. Modbus-Master can send a broadcast instruction. In such case the estination Address is equal to zero. No response for a broadcast instruction is to be sent... Receiving ata from the S000-PP epending on the data the Modbus-Master would like to receive it can be necessary one or two request-response transactions. The data the S000-PP has already had in its configuration are to be received by the Modbus-Master in a single session. Such data includes: The maximum quantity of relays, zones, and partitions; The maximum number of states of zones and partitions; The capacity of the circular event buffer; The maximum event description length; The type and the version of the S000-PP; The states of zones, partitions, and relays; escription of events; The number of non-read events; The number of the newest event and the number of the latest event; The current data and time. 6

7 Two request-response sessions are to be used: To receive an extended zone status: during the first session Modbus Master writes the zone number into the S000-PP while during the second session it performs reading. The register address (the address of the first register of a sequence of registers) for reading extended zone status is the same for all the zones 469; To receive an extended partition status: during the first session Modbus Master writes the partition number into the S000-PP while during the second session it performs reading. The register address (the address of the first register of a sequence of registers) for reading extended partition status is the same for all the partitions 4600; To read an event by its known number: during the first session Modbus Master writes into the S000-PP the number of the event while during the second session it performs reading. The register address (the address of the first register of a sequence of registers) for reading an event in accordance with its known number is the same for all the event numbers 4696; To receive a numeric parameter value: during the first session Modbus Master writes into the S000-PP the zone number while during the second session it performs reading. If Modbus Master generates requests frequently, then to receive data it can be necessary more than two request-response sessions (especially the W000-PPoperate as Slave in the Orion system). If, during a second session, at the moment of receiving a request for sending data the S000-PP has not yet had them, the S000-PP generates an error packet with the code 5. In this case it is recommended for the Modbus Master to repeat the data request after a time. Getting a zone number to request the temperature ata Request Yes Error Code 5? No ata has been received By means of the S000-PP the Modbus Master can get numerical values of the following parameters:.. Numerical Parameter Values Temperature (for such devices as S000-IP and S000-VT); Humidity (for an S000-VT); Number of pulses (for an S000-ASR); Voltage and current (for RIP-V-A-7Ah RS and RIP- RS). Because of a special request must be sent in order to get a numerical parameter value from an Orion system device, the relevant zone type for this alarm loop must be specified in the configuration table of zones and partitions of the S000-PP. Please read more about configuring the S000-PP in Section 5 of this Manual. 7

8 ... Table 4 includes the list of Modbus Functions supported by the S000-PP. Table 4. Modbus Functions Supported by the S000-PP Purpose Request for maximum number of relays (R) Maximum number of relays Request for maximum number of zones (R) Maximum number of zones Modbus Function Register Address 4644 Modbus ata Hi Lo Hi =0 Lo = Count = Maximum number of relays Register Address 4645 Hi Lo Hi Lo Hi =0 Lo = Count = Maximum number of zones Hi Lo Packet Length 7 7 Comment Request for maximum number of partitions (R) Maximum number of partitions Register Address 4646 Hi Lo Hi =0 Lo = Maximum number of partitions Count = Hi Lo 7 Request for maximum number of zone statuses (R) Maximum number of zone statuses Register Address 4647 Hi Lo Hi =0 Lo = Count = Maximum number of zone statuses Hi Lo 7 Request for max number of partition statuses (R) Maximum number of partition statuses Register Address 464 Hi Lo Hi =0 Lo = Count = Maximum number of partition statuses Hi Lo 7 Request for maximum number of events (R) Register Address 4649 Hi Lo Hi =0 Lo = Maximum number of events Count = Maximum number of events Hi Lo 7 Request for max length of event description (R) Max length of event description Register Address 4650 Hi Lo Hi =0 Lo = Count = Max length of event description Hi Lo 7 Request for type and version of the device (R) Register Address 465 Hi Lo Hi =0 Lo = Type and Version of the device Count = evice Type evice Version 9

9 Continuation of Table 4 Purpose Modbus Function Modbus ata Packet Length Comment Request Status and Set Status Functions Request for status of the relay group (R) Status of the relay group Start Relay Address М, where М is (No of the first relay ) Quantity of Relays Hi Lo Hi = 0 Lo Count = N Relay Status s byte N 5+N Status bytes: bit is for a single relay Control status of a relay group (W) 5 Start Relay Address М, where М is (the number of the first relay ) Quantity of Relays Count N ata to set the relay status Hi Lo Hi Lo N 9 + N Status bytes: bit is for a single relay Confirmation for controlling a relay group Start Relay Address М, where М is (the number of the first relay ) Quantity of Relays Hi Lo Hi = 0 Lo Control a single relay (W) Confirmation for controlling a single relay 5 Register Address М, where М is (relay No - ) Relay Status: 0xFFFF Switch On 0x0000 Switch Off Register Address М, where М is (relay No - ) Relay Status: 0xFFFF Switch On 0x Switch Off The response is the same as the request Zone Status Request (R) Register Address М, where M is (zone No ) Hi Lo Hi = 0 Lo = Zone Status Response Count = Zone Status s 7 Priority zone Hi (Table 5) Мл.байт (Table 5) statuses 9

10 Continuation of Table` 4 Purpose Modbus Function Modbus ata Packet Length Comment Set a zone status (W) 6 Register Address М, where М is (zone No ) Zone status: 09: alarm loop disarmed; 4: alarm loop armed; 4: auto extinguishing off; 4: auto extinguishing on; 4: abort discharging; 46: discharge Hi Lo Hi = 0 Lo Confirmation for changing the zone status Register Address М, where М is (zone No ) Zone status: 09: alarm loop disarmed; 4: alarm loop armed; 4: auto extinguishing off; 4: auto extinguishing on; 4: abort discharging; 46: discharge The response is the same as the request Hi Lo Hi =0 Lo Set the number of the zone to request extended zone status (W) Confirmation for setting zone number 6 Register Address 4676 Zone Number Register Address 4676 Zone Number Request for extended status of the zone by the set number (R) Register Address 469 = Number of Status s / Hi Lo Hi = 0 Lo Extended zone status Count Zone Number Hi Lo Number of Status s Zone Status s N +N St.s in priority descending order Partition Status Request (R) Register Address М, where М is (Part.No ) Hi Lo Hi = 0 Lo Status of the partition Count = Status bytes 7 Priority partition statuses Hi (Table 5) Lo (Table 5) Set the partition status (W) Register address М, where М is (Part.No ) Partition statuses: 09 loop armed; 4 loop disarmed Hi Lo Hi = 0 Lo Confirmation for setting the partition status 6 Register Address М, where М is (Part.No ) Partition statuses: 09 loop armed; 4 loop disarmed Hi Lo Hi = 0 Lo Response = request 0

11 Continuation of Table 4 Purpose Modbus Function Modbus ata Packet Length Comment Set the number of the partition to request extended partition status Register Address 4677 Partition Number Hi Lo Hi = 0 Lo Confirmation for setting the partition number 6 Register Address 4677 Partition Number Hi Lo Hi = 0 Lo Response = request Request for the extended partition status by the set number Extended partition status Register Address 4600 = Number of Status s / Hi Lo Hi = 0 Lo Count Partition Number Number of Status s Hi Lo Functions to Work with Event Log Partition Status s N +N Status s in priority descending order Request for number of the most recent event (R) Number of the most recent event Register Address 4660 Hi Lo Hi = 0 Lo = Count = Event Number Hi Lo 7 Request for number of the oldest event (R) Number of the oldest event Register Address 466 Hi Lo Hi = 0 Lo = Count = Hi Event Number Lo 7 Request for number of non-read events (R) Register Address 466 Hi Lo Hi = 0 Lo = Number of nonread events Count = Quantity of Events 7 Hi = 0 Lo Set the Event Read flag (W) Confirmation for setting the flag 6 Register Address 466 Event Number Register Address 466 Event Number Response = request

12 Continuation of Table 4 Purpose Modbus Function Modbus ata P.Len gth Comment Clear Event Log Register Address Clear Event Log Confirmation (W) 6 Hi Lo Register Address Hi Lo Response = request Request for event (R) The oldest nonread event Setting the event number for request by number (W) 6 Request for event by the number (R) Response to the request for the event by the number Register Address 4664 = Number of event bytes / Hi Lo Hi = 0 Lo Count Event Number Hi Lo Register Address 467 Длина описания Code Event Number Fields: field type, field length, data Register Address 467 Event Number Register Address N = Number of Event s / Hi Lo Hi = 0 Lo Count Event Number Hi Lo Length of description Code Fields: field type, field length, data 5+N N = Quantity of Registers * Confirmation for setting the number Response = request N = Quantity of Registers * Functions for Reading Numerical Values of Parameters Setting the number of the zone to request temperature/humidity (W) 6 Register Address 4679 Zone Number Register Address 4679 Zone Number Confirmation of setting the number Response = request

13 Continuation of Table 4 Purpose Request for the numerical value of the temperature/humidity (R) The numerical value of the temperature/ humidity Setting the zone number to request for the counter (W) Request for the number (R) The number (counter reading) Modbus Function Setting the number of zone to request for voltage or current (W) 6 Confirm setting the number Request for the numerical value of voltage or current (R) Numerical value of voltage or current 6 Register Address 46 Modbus ata = Number of bytes / Hi Lo Hi = 0 Lo = Count = Register Address 460 P.Len gth The numerical value is signed two s complement fixed point 7 Hi Zone Number Lo Register Address 460 Zone Number = Register Address 46 Number of bytes / Hi Lo Hi = 0 Lo = Count = 6 (high) Register Address Zone Number Register Address 46 Zone Number Register Address 46 = Number of bytes / Hi Lo Hi = 0 Lo = Count = 6 (low) The numerical value is signed two s complement fixed point 7 Hi Lo Comment Confirmation for setting the number Response = request Response = request

14 End of Table 4 Other Functions Synchronization (W) 6 Register Address 4665 Quantity of Registers Count = 6 6 bytes of data Hi Lo 0 H М S М Y 5 Only for the Orion- Master mode Confirmation of synchronization Register Address 4665 Hi Lo Hi = 0 Lo = Request for time and date (R) Time and date of the device Register Address 4665 Hi Lo Hi = 0 Lo = Count = 6 Time and ate H M S M Y Notes: W Writing; R Reading; evice Type: 6 is for S000-PP; evice Version: version. is transmitted as ( Hi = 0, Lo = ), version.0 is transmitted as 0 (Hi =, Lo = 45)...4. The S000-PP supports priority of statuses of zones and partitions. In responses for status requests the states of the highest priority are transmitted by first. Table 5 shows the list of events (states of alarm loops) of the Orion system along with priorities of those events which have an effect on states of zones and partitions. The most priority status has the priority index of. Priority decreases with increasing the index. The event which doesn t affect status of a zone or partition has an empty field in the Priority column in Table 5. Table 5. The List of Events of the Orion System Event Code Event The list of fields for this event (see Table 6) Event escription Priority ( is the highest) AC Power Restored (),, Mains power 0 V has restored 6 AC Power Failed (),, Mains power 0 V has failed 4 Intrusion Alarm (),, The armed alarm loop has been broken 7 Arming Failed (), (),, While being armed, the alarm loop was 5 broken or faulty 9 Test (),, The smoke detector IP-4A has responded after a special test action such as (moving a magnet close the detector or pressing test button, the Test Mode being off 0 Test Begins (),, The alarm loop is switched to the Test Mode Test Ends (),, The alarm loop is switched off the Test Mode Monitoring Restored (), (),, Monitoring of the Programmable Auxiliary alarm loop has restored (switched on) Arming elay (), (),, The exit delay or delay before arming is 9 being counted 4 Alarm Loop Armed (), (),, The alarm loop has just been armed 0 4 User s Code Entered, The user has entered his code (for example, for arming or disarming) 4

15 Event Code Event The list of fields for this event (see Table 6) Event escription Priority ( is the highest) 5 Auxiliary Zone Restored (),, 55 6 Auxiliary Zone Alarm (),, 40 7 Fire Alarm (),, Two threshold detectors have responded in a single alarm loop, or Arming elay after a response of a threshold detector has not yet been expired, or the measured value (temperature or smoke content) has exceeded the Fire threshold in the analog addressable zone Auxiliary Zone Alarm (),, Another breaking of the auxiliary alarm loop 9 Восстановление нормы (),, 56 пожарного оборудования 4 Fire Trouble (),, This is either an internal malfunction of 9 the addressable detector (optical system trouble of the IP-4A) or breaking a monitored circuit of mass and pressure of the S000-KPB 4 Unknown evice (),, 44 Fire Prealarm (),, A response from the heat detector, or 9 confirmed response of the smoke detector, or measured value s (temperature s or smoke content s) exceeding the Prealarm threshold in the analog addressable zone 45 Loop Open Failure (),, An open circuit failure of the alarm loop or monitored circuit of the addressable input module 47 Polling Loop Restored (),, The Polling Loop of the S000-KL 64 has been restored after a short/open failure 5 Panic Alarm (),, The Panic alarm loop is broken 0 7 Low Level (),, The water or pressure level has decreased 49 (for the Potok-N) 7 Normal Level (),, The water or pressure level is normal 59 (for the Potok-N) 74 High Level (),, The water or pressure level has increased 4 (for the Potok-N) 75 Too High Level (),, The pressure or water level has increased 46 the emergency threshold (for the Potok-N) 76 High Temperature (),, The temperature value has exceeded a 50 threshold value 77 Too Low Level (),, The pressure or water level has decreased 47 the emergency threshold (for the Potok-N) 7 Normal Temperature (),, The temperature value is within the given 5 range (The thermostatic zone of the S000-KL) Heat Sensor Failed (),, A failure of the heat sensor (The thermostatic 0 zone of the S000-KL) Heat Sensor Restored (),, The heat sensor has been restored after a failure( The thermostatic zone of the S000-KL) 4 Local Programming 09 Alarm Loop isarmed (), (),, The alarm loop has just been disarmed 7 0 Alarm Reset (),, The alarm has been cancelled 5

16 Event Code Event The list of fields for this event (see Table 6) Event escription Priority ( is the highest) 7 Ready to Arm (),, The disarmed alarm loop is in norm Entrance Alarm (),, An alarm in the entrance zone 9 Not Ready to Arm (),, Breaking of the disarmed alarm loop 6 Relay Open Failure 5, An open circuit failure of the relay output load circuit has been detected 4 Relay Short Failure 5, A short circuit failure of the relay output load circuit has been detected 4 Relay Restored 5, The relay output load circuit is restored 60 6 Relay isconnected 5, The output (relay) cannot be controlled due to loss of communication with it: either the S000-KL controller has lost its S000-SP module or the 4 S000-ASPT has lost the connected S000-KPB 7 Relay Connected 5, The output (relay) can be controlled again: the S000-KL has found its relay module S000-SP lost before or 6 the S000-ASPT has found the connected S000-KPB Relay Status Change 5, A change in status of the relay: switching on, switching off, or switching on and off alternately 0 The pump is on (),, 7 The pump is off (),, 5 Auto Test Error An equipment malfunction has detected 7 Start Circuit Activation 5, 9 Launch Fault (),, The fire extinguishing equipment was not successfully started: the discharge command was given out but no agent outflow has been detected 40 Manual Testing Panel diagnostic mode has been started 4 Launching elay (),, A condition to release extinguishing agent has been occurred and the Pre- 5 ischarge elay is being counted 4 Manual ischarge (),, Automatic mode of starting extinguishing equipment is off 6 4 Launch Cancel (),, Starting the fire extinguishing equipment was cancelled (for example, due to pressing RESET button of the S000- ASPT during Pre-discharge elay or 7 due to Cancel Extinguishing command received from the S000M console) 44 Extinguishing (),, Fire extinguishing is in process (the launch pulse was given out and outflow of fire extinguishing agent has been detected) The fire extinguishing equipment was launched in emergency mode (the 45 Emergency Launch (),, launch pulse was not given out but outflow of fire extinguishing detector has been detected) 46 Launching (),, The pulse to discharge extinguishing agent was given out 47 Launch Blocked (),, Releasing extinguishing agent has is blocked (for example, due to opening the door to the protected premises dur- 6 6

17 Event Code Event The list of fields for this event (see Table 6) Event escription Priority ( is the highest) ing the Pre-discharge elay time) 4 Auto ischarge (),, Automatic mode of starting extinguishing equipment is on 9 49 Tamper Alarm (),, The device enclosure has been open 50 Starting Voice Announcement 5, 5 Cancelling Voice Announcement Start 5, 5 Tamper restored (),, The device enclosure has been closed 66 5 amper Activated 5, entered the active status amper Restored 5, The ventilation or smoke removal damper has entered the initial status 5 55 amper Failure 5, The damper has entered neither active nor initial status amper Error 5, Incorrect status of damper monitoring circuits 44 5 Internal Zone Restored (),, Loop Parameter Error (),, The alarm loop cannot operate due to configuration errors 7 isconnected (),, The alarm loop is disconnected: communications between the S000- KL and the addressable device (or 5 between the S000-ASPT and connected S000-KPB) has been lost Connected (),, Communications between the S000-KL and the addressable device (or between the S000-ASPT 65 and S000-KPB) has been restored 9 Polling Loop Lost (),, Communications with the detector and the PL terminal of the controller has been lost 90 Polling Loop Lost (),, Communications with the detector and the PL terminal of the controller has been lost 9 Polling Loop Restored (),, Communications with one or several addressable devices and the PL terminal of the controller has been restored 9 RIP Power Off (),, RIP output voltage has been shut off (a shut off command has been executed) 9 RIP Power On (),, RIP output voltage has been turned on (a turn on command has been executed) 94 RIP Overcurrent (),, The RIP output current has exceeded a threshold value 95 RIP Current Restored (),, RIP overcurrent has been eliminated RIP Charger Failed (),, The power charger of the RIP power supply has failed 97 RIP Charger Restored (),, A trouble of the RIP power charger has been eliminated 5 9 Power Failed (),, Power supply voltage is out of normal range 5 99 Power Restored (),, 00 Battery Restored (),, Power supply voltage has returned to normal after a failure The voltage of the system battery has returned to normal 6 6 7

18 Event Code Event The list of fields for this event (see Table 6) Event escription Priority ( is the highest) 0 Polling Loop Restored (),, Communications with one or several addressable devices and the PL terminal of the controller has been restored 0 Battery Failed (),, No battery or a battery trouble 0 evice Restart The device was restarted Service Required (),, The zone requires some service (for example, the smoke chamber of the IP-4A is contaminated) 05 Battery Test Error (),, The battery fails the test and is found to be unsuitable for use 06 Low Temperature (),, The temperature value has dropped below a threshold value 5 Low Battery Voltage (),, Warning about imminent battery discharge 4 Loop Short Failure (),, A short circuit failure of the alarm loop or monitored circuit of the addressable 4 input module 5 Polling Loop Short (),, A short circuit failure within the Polling Loop of the S000-KL 6 6 etector Response (),, An unconfirmed response from the fire detector has been received 7 RS-45 Branch The device has lost one branch of the isconnected RS-45 ring interface RS-45 Branch Connected 0 Gas Pressure Signal (),, Gas Pressure Failure (),, Polling Loop Trouble (),, Communication with the device over the branch of the RS-45 interface has been restored The pressure detector detects rising in pressure There is no expected pressure increase after giving the discharge command The Polling Loop of the S000-KL has failed (usually the voltage is too high) Patrol Check The Patrol Check circuit has activated 4 Partition Armed (),,, (4) The partition has been armed 4 Partition isarmed (),,, (4) The partition has been disarmed 50 Communications with the device is lost (), (), 4 5 Communications with the device is repaired (), (), 70 Note: The fields in parentheses can be absent..5. The S000-PP generates an event description packet which contains additional fields identifying this event. Types and codes of additional event fields are shown in Table 6. Table 6. Types of Additional Fields of Events Code escription Length (bytes) The number of the user in the S000-PP database Partition: the number of the partition Zone: the number of the zone 7

19 Code escription Length (bytes) 5 Relay: the number of the relay Time and date: hours, minutes, seconds, day, month, year 6 4 I of the partition: the partition identifier in the Orion system Both for Master and Slave modes the S000-PP use its own database to assign events to zones and partitions. The only difference is that in the Slave mode the S000-PP receives the evice Address and Loop Number from the S000(M) console...6. Address space of the Modbus registers of the S000-PP is shown in Figure Reserved Relay Numbers Reserved Zone Numbers Reserved Partition Numbers Reserved Parameters Reserved Figure. Modbus Registers 9

20 ..6. Table 7 represents the summary of Modbus addresses for various parameters of the S000-PP. Table 7 Modbus Address estination 4644 The maximum number of relays 4645 The maximum number of zones 4646 The maximum number of partitions 4647 The maximum number of zone statuses 464 The maximum number of partition statuses 4649 The maximum number of events 4650 The maximum event length 465 Type and version of the device 4660 The number of the most recent event 466 The number of the oldest event 466 The number of non-read events 466 Setting Event Read attribute 4664 Clearing event log 4665 Time and ate 4676 Setting the number of zone for request 4677 Setting the number of partition for request 467 Setting the number of event for request Setting the number of zone to request for values of temperature or humidity Setting the number of zone to request for values of S000- ASR counter Setting the number of zone to request for values of current or voltage of RIP- RS 469 Request for extended zone status 4600 Request for extended partition status 4664 Request for event 4696 Request for event by its number 46 Request for the value of temperature/humidity/current/voltage 46 Request for the value of S000-ASR counter 0

21 4. PCB Layout 4.. Figure schematically shows the location and designation of terminals and jumpers of the S000-PP. Block ХТ Jumper ХР4 Jumper ХР Block ХТ Power RS-45 Orion +V 0V А B TTL OUT TTL IN 0V B А RS-45 Modbus/T Jumper ХР Tamper S LE HL Figure. S000-PP Printed Circuit Board The jumper ХP is designed to switch over S000-PP modes at the ORION interface: If the jumper is closed (put on) the mode is ORION Master; If the jumper is open (put off) the mode is ORION Slave. The jumper ХP4 is designed to connect/disconnect the EOL resistor to the Orion interface line. The jumper ХP is designed to connect/disconnect the EOL resistor to the Modbus interface. Tamper switch S detects opening and closing of the device enclosure. The light indicator HL is designed to indicate S000-PP operation modes. After applying (or resetting) power the LE light with red for a short time, then with green for short time, and then switches off. Then the LE operates depending on S000-PP operation mode. In the Orion Slave mode the LE switches on/off in green every two seconds in state of no communications and turns on for 5 seconds after each transmission. In the Orion Master mode the LE flashes in green at the beginning of each cycle of polling the Orion system devices. LE s flashing in read with duty cycle about 0. indicates an S000-PP malfunction. In such case try to update the S000-PP firmware using the program Orion_prog.exe. The ХТ., ХТ.4, ХТ.5 are designed only for work with an RS-0T transmitter over the RS- interface.

22 5. Preparing for Use 5.. Before using the S000-PP, it should be programmed: ) Orion interface in the Master mode is configured by the program RS45Setting.exe: The pause before a response over RS-45: ms; The pause before a new session without changing the direction of transmission: 6.0 ms; The pause before a new session with changing the direction of transmission: 6.0 ms; The pause between repeating of a common command: 6 ms; Timeout of the response to a request for new events while polling: 0 ms; Timeout of the response to an address command: 600 ms; Timeout of the response to a request for new events while searching: 6 ms; The number of attempts to link while polling: 6; The number of attempts to send an address command: 5; The number of times to send a common command:. The parameter values specified in this clause have already been programmed during manufacturing (factory values) and provide correct operation of the S000-PP with devices of the Orion system. These values should not be changed unless absolutely necessary. ) Orion interface in the Slave mode is configured by the program UProg.exe: The pause before a response over RS-45: ms; The address of the S000-PP within the Orion interface: to 7; The maximum time without requests from Master: 5 to 6 s. This parameter is used to monitor lack of Master requests and to generate communication lost messages. ) The Modbus interface is programmed using the UProg.exe program: S000-PP Address for the Modbus interface: to 47; Bits per Second: 00, 400, 9600, 900, 400, 57600, 500; Parity (none, even, odd); Stop Bits with parity NONE: or ; Interface Type: Modbus RS-45. 4) The S000-PP database is programmed using the UProg.exe program: The S000-PP database consists of four tables: Zone and Partition Table; Relay Table; Partition I Table; User I Table Figure 4 shows an excerpt of Zone and Partition Table of the S000-PP database. Zone Number evice Address Loop Number Partition Number Zone Type Figure 4. Zone and Partition Table Columns of the table: Zone Number: The sequential number of the zone. The zone No has the address of the register within the address space of Modbus; evice Address: The address of the device within the Orion system;

23 Loop Number: The number of the alarm loop monitored the zone in question or the number of the relay which circuits are monitored. The alarm loop or relay belongs to the device which address is specified in the string; Partition Number: The number of the Modbus partition the zone belongs to; the range of available number is to 64; Zone Type: The code of the zone type: is for an alarm loop, is for monitored circuits of a relay, is for a device as a whole (in this case the Loop Number must be 0), 4 is for switching on/off auto mode of releasing extinguishing agent, 5 is for releasing or cancelling releasing extinguishing agent (S000-ASPT); 6 is for the temperature [degrees C] / the humidity [%]; 7 is for pulse counter; is for the voltage / current of a RIP. Requests to the following alarm loops are supported: No.: Output voltage [V]; No.: Load current [A]; No.: Battery voltage [V]; No.4: Current battery charge [%]; No.5: Mains voltage [V]. The S000-PP uses data from this table to: - poll the devices of the Orion system; - assign the events generated by the devices to zones and partitions defined by users; - verify compatibility between a command for changing zone status and the type of the zone; - check the match between the request for the numerical parameter value and the type of the zone and to generate a correct request to an Orion system device for receiving the numerical parameter value. For zones with code types 6, 7, and you can request not only numerical parameter values but also send regular alarm loop status requests. Figure 4 shows second zone s having the zone type code equal to 6. A request for status of this zone is a request of the Modbus register with the address But the same zone can be requested as a numerical parameter value by writing the zone number ( in our case) into the Modbus register with the address of 46. An attempt to set a zone number for requesting for numerical parameter value with non-relevant zone type code will cause receiving an error packet with code from the S000-PP. In the Orion Master mode, to identify events generated by the S000-PP itself and to read its status, a zone with the following attributes is to be used: evice Address = 0; Loop Number = 0; Zone Type =, the numbers of zone and partition can be any of the allowable range of numbers. You can add such zone into the Zone Table by doing the following: right click on the zone number you wish assign for the S000-PP and select Assign the Zone for the Pollster in the pop-up menu. In the Orion Slave mode, to identify events generated by the S000M console, a zone with the following attributes is to be used: evice Address = 0; Loop Number = 0; Zone Type =, the numbers of zone and partition can be any ones of the allowable range of numbers. To identify events from the S000- PP itself, one of the zones is used as for any other slave devices within the Orion interface: the evice Address is the S000-PP address in the Orion Interface, Loop Number = 0, Zone Type =. The Partition Number can be any one within the available range of numbers.

24 5... Figure 5 shows an excerpt of the relay table of the S000-PP database. Relay Number (Modbus) evice Address Relay Number Figure 5. Zone and Partition Table Columns of the table: Relay Number (Modbus): The sequential number of the relay. The relay No has the Register Address of 0000 within the address space of Modbus; evice Address: The address of the device within the Orion system; Relay Number: The number of the relay for the device which address is specified in the string. For the devices which have no alarm loop inputs (for example, an S000-SP) you should make an entry in the table of zones for a zone to identify the device itself. Otherwise, events from these devices will be impersonal, without zone and partition fields Figure 6 shows an excerpt of the table of the Partition I of the S000-PP database. Partition Number (Modbus) Partition I Figure 6. Partition I Table Columns of the table: Partition Number (Modbus): The sequential number of the partition; Partition I: Any number ranged from to 6554; If you are going to use Bolid manufactured Orion-ModBus OPC server, each Modbus partition should be assigned to a numerical partition I Figure 7 shows an excerpt of the table of user I of the S000-PP database. No User I Figure 7. User I Table Columns of the table: No: The sequential number of the I; User I: The User I in the Orion system (a credential code). Reading a credentials and writing it into the S000-PP database is performed by means of any other device which can read credentials such as S000-, S000-4, S000-KL etc. 4

25 5.. To write (load) configuration parameters to the S000-PP: - wire it as shown in Figure, - remove the jumper ХP, - switch on the power supply, and - run the UProg.exe. PC Power Supply V Interface Converter S000-PP ХТ +V 0 V А 4 В Figure. The Schematic for Configuring the S000-PP Following is to be made in the UProg.exe window: Read the current configuration of the S000-PP; Revise the configuration as necessary; Write the new configuration to the S000-PP. Then close the UProg.exe, switch the power supply off, and put on the jumper ХP if the S000-PP is used in Master mode. 5.. The S000-PP can be mounted on a wall, behind a suspended ceiling, or on other structures of the premises at places protected against atmospheric fallouts, mechanical damage, and unauthorized access. The drilling pattern for hanging the S000-PP by means of woodscrews is shown in Figure 9. Figure 9. rilling Pattern 5

26 6. evice Operation 6.. Figure 0 shows the schematic for connecting the S000-PP in the Орион Master mode to integrate a fire & intrusion alarm system from the Bolid Company (Orion system devices) into a SCAA system of the user. SCAA System Modbus RTU ХТ А В ХТ +V 0V Power Supply V А В 4 S000-PP A device of the Orion system RS45 Orion A device of the Orion system A device of the Orion system Figure 0. Connecting the S000-PP in the Orion Master Mode The jumper ХP of the S000-PP must be put on because the S000-PP is the Master in the Orion RS-45 interface. Orion system devices must be pre-configured in accordance with their manuals and requirements of the system Project. 6.. Figure shows the schematic for connecting the S000-PP in the Orion Slave mode to integrate a fire & intrusion alarm system from the Bolid Company (Orion system devices) into a SCAA system of the user. 6

27 ORION SOFTWARE S000М Console SCAA System Modbus RTU ХТ А В ХТ +V 0V Power Supply V А В 4 S000-PP A device of the Orion system RS45 Orion A device of the Orion system A device of the Orion system Figure. Connecting the S000-PP in the Orion Slave Mode The jumper ХP of the S000-PP must be removed because the S000-PP is the Slave in the Orion RS45 interface. Orion system devices must be pre-configured in accordance with their manuals and requirements of the system Project. 6.. Figure shows a schematic for connecting the transmitter to the S000-PP in accordance with TTL interface scheme. S000-PP RS-0T GN ХТ A B 0 V ХТ В A 0V 4 RS45 To Orion ISS devices Rx 4 Out +V Tx 5 In Figure. Connecting the Transmitter to the S000-PP 7

28 6.4. Guidelines for Connecting the S000-PP and evices over the RS-45 Interface The RS-45 interface uses connections between the devices as a bus when all the devices are connected to the interface by a pair of wires (lines A and B). This interface bus should be matched at the two ends by termination resistors which are to be installed at the first and the last devices in the line. Most devices have built-in termination resistance, which can be included to the line by putting on the special jumper. Upon delivering the devices jumpers are put on, so the jumpers should be removed for all the devices except the first and the last devices in the RS-45 line. The S000-PP can be connected at any place of the RS-45 line. If it is the first or the last device in the line, its jumper XP(4)must be put on, otherwise this one must be removed. Branches on the RS-45 line are undesirable because they increase the signal distortion in the line, but practically they are acceptable with a small length of the branches (not more than 0 meters). No termination resistors should be connected to the branches. To make long branches, use S000-PI repeaters. In a scattered system where the S000-PP and devices connected to a single RS-45 line are powered by various power supplies, the circuits 0 V of all the devices and the S000-PP must be coupled in order to equalize their potentials. Otherwise, communications between the S000-PP and the devices can be unstable. If a cable with several twisted pairs of wires is in use, a free pair can be used to equalize potential. For this purpose also the shield of a shielded twisted pair can be used provided that the shield is NOT grounded. It should also be taken into account the possibility of linking 0 V with a protective earth circuit in the equipment used in the OPS and SCAA system. Figure shows a schematic for connecting the devices and the S000-PP to the RS-45 interface line. RS-45 Line (no more than 000 m) A B 0V A B 0V A B 0V 60 evice evice 60 evice RS-45 signal line (twisted pair); equipotential bonding conductor; shield (if a shielded cable is in use). Figure. The Schematic for Connecting evices to the RS-45 Interface 6.5. Receiving information from Orion system devices SCAA can receive information from Orion system devices by two ways: Requesting for status of the zone or relay; Requesting for event. Request for status of zones (or relays) is reasonable on system startup, in order to find out current statuses of zones. This way is inefficient in relation to traffic usage because you request and receive statuses of all the zones, including the ones which statuses have not changed. Requests for events allow optimizing the traffic and fast receiving changes in zone statuses. The S00-PP supports two ways to request for events: Request for the oldest event; Request for the event which number was given preliminary. The S000-PP dispatches the events by the following rules:

29 - After filling the circular event log (the event log capacity is 56) the S000-PP writes a current event to the place of the oldest event; - Receiving a request for event (Modbus Address = 4664) the S000-PP returns the oldest nonread event; - An event is considered to be read only after the Event Read flag (Modbus Address = 466) is set on for this event; - If the S000-PP has no non-read events, it returns an event with all bytes equal to zero as a response to a request for event. 9

30 6.6. Examples of Modbus requests and responses from the S000-PP Requesting for status of the zone No 9 from the S000-PP with the address of 5: ata Slave Modbus Register Address = Address Function x0F 0x0 0x9C 0x4 0x0 0x0 CRC6 The response from the S000-PP is: the alarm loop is disarmed, the polling loop is repaired: Slave Modbus ata Address Function Count s of Status 0x0F 0x0 0x6 0xF CRC Requesting for extended status of the partition No from the S000-PP with the address of 5: Step. Setting the partition number (No ): ata Slave Modbus Register Address = Address Function 4677 Partition Number 0x0F 0x06 0xВ4 0x6 0x0 0x0 The confirmation from the S000-PP: ata Slave Modbus Register Address = Address Function 4677 Partition Number 0x0F 0x06 0xВ4 0x6 0x0 0x0 CRC6 CRC6 Step. Request for extended status of the partition with the length of 6 bytes: ata Slave Modbus Register Address = Address Function x0F 0x0 0xВ4 0x7 0x0 0x0 CRC6 The response from the S000-PP: the bytes of extended status of the partition: Slave Address Modbus Function Count = 6 Partition Number 0x0F 0x0 Hi=0 Lo= Number of Status s = s of Status,,, CRC6 0

31 6.6.. Reading an event ( bytes) from the S000-PP with the address of 5: ata = Slave Modbus Register Address = Number of the Event Address Function 4664 s/ 0x0F 0x0 0xВ4 0xВ 0x0 0x0Е CRC6 The response of the S000-PP: the bytes of the event No: Slave Address Modbus Function Count = 0хС Event Number = 0x0F 0x0 0 0х0 escription Length = 0х9 Event Code = 0x6 Event Fields 4 CRC6 Event Fields: В 6 С В Zone Partition Partition I User Time and ate Event No : The Zone No which is included to the Partition No (I=6) is disarmed by the User No on the 5 th of May at :: Reading an event ( bytes) from the S000-PP with the address of 5: ata = Slave Modbus Register Address = Number of the Event Address Function 4664 s/ 0x0F 0x0 0xВ4 0xВ 0x0 0x0Е CRC6 The response of the S000-PP: the bytes of the event No: Slave Address Modbus Function Count = 0хС Event Number = 0x0F 0x0 0 0х escription Length = 0х Event Code = 0x0 Event Fields 4 CRC6 Event Fields: C 7 0 B 6 C E Relay Relay Status Time and ate

32 Event No : Status of the Relay No has been changed, now the relay is ON, the 7 th of April, 04 at :4: Setting the relays No and No to the status ON, and the relay No to the status OFF. The address of the S000-PP is. ata Slave Modbus Register Address = 0000 Relays Number of ata for Address Function Setting the Count Hi Lo Hi LO Relay 0x0 0x0F 0x7 0x0 0 0x05 CRC6 The response from the S000-PP confirming setting the relay status Slave Address Modbus Function Register Address = 0000 Number of Relays 0x0 0x0F 0х7 0х0 0 CRC Request for the numerical number of temperature from the S000-PP with the address : Step. Setting the number of the zone to request for temperature (the zone No.7): ata Slave Modbus Register Address = Address Function 4679 Zone Number 0x0 0x06 0xВ4 0x6 0x0 0x5 The response of the S000-PP: confirmation: ata Slave Modbus Register Address = Address Function 4679 Zone Number 0x0 0x06 0xВ4 0x6 0x0 0x5 CRC6 CRC6 Step. Request for the numeric value of the temperature: ata Slave Modbus Register Address = Address Function 46 0x0 0x0 0xВ4 0xF 0x0 0x CRC6 Variant. The response of the S000-PP is a numeric value of temperature higher than 0. Slave Address Modbus Function Count 0x0 0x0 ata Temperature Value Hi (integral part) 0xA Lo (fractional part) 0x70 CRC6 The temperature value is in signed two s complement fixed point data format: the high byte contains the integral part of the value while the low byte contains the fractional part of the value. The sign of the value is stored in the high bit (b7) of the high byte: 0 for a positive value and for a negative value. How to decode the received value: