How it Works
System Sensor
Loading...
FAAST
User Manual
20 pgs1.03 Mb0
User Manual
4 pgs742.09 Kb0
User Manual
35 pgs2.21 Mb0
User Manual
40 pgs2.39 Mb0

System Sensor FAAST User Manual

FAAST Fire Alarm Aspiration Sensing Technology® Modbus
USER GUIDE
User Guide: FAAST Fire Alarm Aspiration Sensing Technology® Modbus Protocol Schema 1
Table of Contents
Accessible Registers .........................................................................................................................................................................4
Data Format ........................................................................................................................................................................................4
Device Read ........................................................................................................................................................................................5
Device Output and Operating Mode Control ...................................................................................................................................5
Device Conguration .........................................................................................................................................................................5
Device Time ........................................................................................................................................................................................6
Device Smoke Reference ..................................................................................................................................................................6
Modbus Administrator Password .....................................................................................................................................................6
Reading Logs .....................................................................................................................................................................................7
Event Log Read ..................................................................................................................................................................................7
Trend Log Read ..................................................................................................................................................................................7
Message Log Read ............................................................................................................................................................................7
Device Status .....................................................................................................................................................................................9
Sensor Status ................................................................................................................................................................................... 11
Device Logs ......................................................................................................................................................................................13
Factory Conguration ......................................................................................................................................................................14
Device Conguration .......................................................................................................................................................................15
Network Conguration ....................................................................................................................................................................17
Appendix A. Congurable options on FAAST .............................................................................. 18
A.1. Alarm Conguration Variables .................................................................................................................................................18
A.2. Device Conguration Variables ...............................................................................................................................................19
Revision Table
Revision Description of Change Author Date
A0 Initial Release for Review ZK 05/06/2013
22
User Guide: FAAST Fire Alarm Aspiration Sensing Technology® Modbus Protocol Schema 1
Product Description
The FAAST - Fire Alarm Aspiration Sensing Technology® aspirating smoke detector is an advanced particulate detection system designed for use in early warning and very early warning fire detection applications. FAAST draws air from the environment through sampling holes in a pipe network and monitors for smoke particulates. FAAST includes a local display which provides a clear indication of the devices status. Smoke particulate level, alarm level, air flow, and faults can all be discerned with a glance at the user interface.
FAAST is also enabled by built-in Modbus communications capabilities. The Modbus Protocol utilizes the TCP server. They physical connection is Ethernet.
Modbus is a communications protocol allowing for connectivity with several building management solutions. Using Modbus, a FAAST device can be monitored remotely and various device configuration actions and device interactions are facilitated.
PLEASE NOTE: WHILE Modbus CAN BE USED TO SET DEVICE CONFIGURATIONS, THE DESIGN OF ANY NEW FAAST DEVICE MUST BE VERIFIED USING PipeIQ® TO ENSURE THAT SITE SPECIFIC REQUIREMENTS ARE MET. IF Modbus IS USED TO MODIFY AN INSTALLED UNIT, ANY CHANGES TO SENSITIVITY SETTING SHOULD ALSO BE VERIFIED IN PipeIQ® TO ENSURE CONTINUED SYSTEM PERFORMANCE.
3
Rev A0
User Guide: FAAST Fire Alarm Aspiration Sensing Technology® Modbus Protocol Schema 1
Communication Interface
Modbus protocol stack is an application that runs over TCP. The device requires a 10 or 100Mbps Ethernet connection to an existing IP network and a valid network configuration in order to enable Modbus Communications. The FAAST device’s TCP server will listen for Modbus protocol packets on Port 502.
Separate TCP ports allow Modbus, e-mail, PipeIQ and web communications simultaneously. Finally, to transmit and receive data over Modbus, the user requires a client that can generate Modbus packets over TCP.
Client Interface
When a client is connected through Port 502, the FAAST device will act as a Modbus/TCP “server”. This section defines the format of data in Modbus/TCP registers. More information about Modbus/TCP can be obtained from www.Modbus.org.
The entire Modbus map is related to a single device, and the Slave ID parameter is unused by the FAAST device.
Accessible Registers
Input registers for registers listed in Table 1. Holding registers in Tables 2 to 8.
Data Format
To properly transfer data to and from the Modbus registers, the following descriptions specify how data is organized when more than one register is required to read or write a specific piece of data.
1. Long Integer, floating point: Value = 0xaabbccdd Holding Reg1 = 0xaabb Holding Reg2 = 0xccdd
2. String: Value = “test” Holding Reg1 = “et” Holding Reg2 = “ts”
3. IP Address: Value = a.b.c.d Holding Reg1 = dc Holding Reg2 = ba
4. MAC Address: Value = 0x (aa-bb-cc-dd-ee-ff) Holding Reg1 = 0xbbaa Holding Reg2 = 0xddcc Holding Reg3 = 0xffee
4
User Guide: FAAST Fire Alarm Aspiration Sensing Technology® Modbus Protocol Schema 1
Device Sensor Status and Control Operations
Device Read
The Modbus client is able to read the device status data directly via input and holding register reads.
Device Output and Operating Mode Control
The Modbus client is able to initiate different operating modes through the Sensor Input Holding Register.
1. Write the Administrator Password in the Administrator Password holding register (this is the same as the Button Activation Passcode configured through PipeIQ).
2. Read the Sensor API status holding register and verify that the ADMIN_UNLOCK bit is set.
3. Write the value to the Sensor Input Holding Register (40035) that initiates the desired action or mode change:
a. 0x0001 to Isolate b. 0x0002 to Disable c. 0x0004 to initiate Test Mode d. 0x0008 to Silence a Fault or Alarm (when equipped with an audible indicator) e. 0x0010 to Reset the Device f. 0x0020 to Reset the Airflow Baseline g. 0x0040 to Clear the Event Log h. 0x0080 to Clear the Trend Log i. 0x0100 to Clear the Message Log
4. Write 0x0 to the Administrator Password in the Administrator Password holding register if no further changes are desired.
Device Conguration
In order to write a new configuration, the following steps must be followed:
1. Write the Administrator Password in the Administrator Password holding register (this is the same as the Button
Activation Passcode configured through PipeIQ).
2. Read the Sensor API status holding register and verify that the ADMIN_UNLOCK bit is set. If it is set, the Sensor API Command Register is enabled and will process commands issued.
3. The device must be placed in Disable Mode by setting disable bit in Sensor Input Holding register Holding register.
4. Read the Operating Mode holding register.
5. The Modbus client writes the new values for the respective configuration holding registers through Write Multiple Register Command(s).
6. Write the Save Configuration Command value, 0xAA11 in the Modbus Specific configuration Command holding register in order to save any configuration changes.
7. The device stores new configuration.
8. Read the Modbus Specific configuration Command holding register. The value will be 0x0000 when the Command completes successfully.
9. Remove the device from Disable Mode by clearing the disable bit Sensor Input Holding register.
10. The device will reset and the new configuration will be applied.
5
Rev A0
User Guide: FAAST Fire Alarm Aspiration Sensing Technology® Modbus Protocol Schema 1
Device Sensor Status and Control Operations (Cont’d)
Device Time
In order to set the time, the following steps must be followed:
1. Write the Administrator Password in the Administrator Password holding register.
2. Read the Sensor API status holding register and verify that the ADMIN_UNLOCK bit is set. If it is set, the Sensor API Command Register is enabled and will process commands issued.
3. The Modbus client writes the new time value using Epoch/UNIX timestamp formate to the time holding registers through Write Multiple Register Command(s).
4. Write the Save Time Command value, 0xEE22 in the Modbus Specific configuration Command holding register in order to save the new time.
5. The device stores and applies the new device time.
6. Read the Modbus Specific configuration Command holding register. The value will be 0x0000 when the Command completes successfully.
7. Write 0x0 to the Administrator Password in the Administrator Password holding register if no further changes are desired.
Device Smoke Reference
The device may be programmed with a reference in order to compensate for a period of high particulate due to a change in ambient environmental conditions. Use the following steps to modify the Device Reference:
1. Write the Administrator Password in the Administrator Password holding register.
2. Read the Sensor API status holding register and verify that the ADMIN_UNLOCK bit is set. If it is set, the Sensor API Command Register is enabled and will process commands issued.
3. The Modbus client writes the new Reference Value in 32-bit Float format to the Smoke Reference Value register through Write Multiple Register Command.
4. The device applies the new Reference.
5. Read the Sensor Smoke Reference Value to verify it stored correctly.
6. Write 0x0 to the Administrator Password in the Administrator Password holding register if no further changes are desired.
Modbus Administrator Password
The Modbus Administrator Password grants the user the privilege of writing to the Holding Registers. This password is the same as the User Interface Button Lockout Code. It is not readable through the Modbus Interface. It is set to ‘1111’ as the default. The values may range from 1111 to 9999. The user may change the password by performing a Device Configuration Change as described earlier.
A failure to gain administrator privileges due to a forgotten or lost password is a recoverable event by using the PipeIQ software, connecting to the device and updating the device configuration with a known password.
6
Loading...
+ 14 hidden pages
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use