FAAST XT Fire Alarm Aspiration Sensing Technology Modbus .

FAAST XT Fire Alarm Aspiration SensingTechnology Modbus Protocol Schema 10USER GUIDE

User Guide: FAAST XT Fire Alarm Aspiration Sensing Technology Modbus Protocol Schema 102

User Guide: FAAST XT Fire Alarm Aspiration Sensing Technology Modbus Protocol Schema 10Table of ContentsProduct Description.4Communication Interface.4Ethernet.4RS-485.4Modbus Resources.5Client Interface.5Accessible Registers.5Data Format.5Device Sensor Status and Control Operations.6Modbus Administration Password.6Device Read.6Device Output and Operating Mode Control.6Device Configuration.6Device Time.7Device Smoke Reference.7Reading Logs.7Trend Log Read.8Message Log Read.8Input Registers.9Holding Registers.9Sensor Status. 10Device Status. 13Device Logs. 14Factory Configuration. 15Modbus Configuration. 16Device Functions and Sensor Inputs. 17Device Configuration. 17General Configuration.20Network Configuration.21User Interface Configuration.22Appendix A. Configuration Options on FAAST.23A.1. Alarm Configuration Variables.23A.2. Device Configuration Variables.25Revision TableRevisionDescription of ChangeAuthorDateAInitial ReleaseZK10/30/1432Rev A

User Guide: FAAST XT Fire Alarm Aspiration Sensing Technology Modbus Protocol Schema 10Product DescriptionThe FAAST Fire Alarm Aspiration Sensing Technology aspirating smoke detector is an advanced particulate detection systemdesigned for use in early warning and very early warning fire detection applications. FAAST draws air from the environment throughsampling holes in a pipe network and monitors for smoke particulates. FAAST includes a local display that provides a clear indicationof the device status. Smoke particulate level, alarm level, air flow and faults can all be discerned with a glance at the user interface.One MODBUS Protocol interface comprises of the MODBUS over TCP server. The physical interface is Ethernet. A TCP server listenson Port 502. Separate ports provide connections to the PipeIQ protocol server and a web server. This enables access to all serverssimultaneously through individual TCP sockets.FAAST also supports MODBUS over RS-485 full or half duplex. Either MODBUS/TCP or MODBUS/RS-485 can be used at any onetime. The MODBUS configuration settings can be set with Pipe IQ tool.FAAST product variants function differently from model to model. Please refer to the installation instructions of the relevant productsfor which the MODBUS Protocol interface will be implemented. i.e. Verify the configuration methods available for the product underconsideration and the behavior in response to each operating mode.MODBUS is a communications protocol allowing for connectivity with several building management solutions. Using MODBUS, aFAAST 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 DEVICEMUST BE VERIFIED USING PipeIQ TO ENSURE THAT SITE SPECIFIC REQUIREMENTS ARE MET. IF MODBUS IS USED TOMODIFY AN INSTALLED UNIT, ANY CHANGES TO SENSITIVITY SETTING MUST ALSO BE VERIFIED IN PipeIQTM TO ENSURECONTINUED SYSTEM PERFORMANCE.Communication InterfaceEthernetThe MODBUS protocol stack is an application that runs over TCP. The device requires a 10 or 100Mbps Ethernet connection to anexisting IP network and a valid network configuration in order to enable MODBUS Communications. The FAAST device’s TCP serverwill listen for MODBUS protocol packets on Port 502. Separate TCP ports allow MODBUS, e-mail, PipeIQ and web communicationssimultaneously. Finally, to transmit and receive data over MODBUS, the user requires a client that can generate MODBUS packetsover TCP. The Device Identifier is the only configuration option. The valid range is 1-247. This is independent of any other addresssetting associated with the unit (i.e. SLC address/Device Identifier, IP address, etc).RS-485The FAAST detector supports MODBUS over RS-485 (as defined in MODBUS over Serial Line Specification and ImplementationGuide V1.02) in both RTU and ASCII formats. The table below lists the configuration options.The RS-485 terminals are biased such that the ‘B’ terminals can be considered ‘ ’ and the ‘A’ terminals are considered ‘-‘.CriteriaRTUASCIIDevice Identifier1-2471-247Baud rate (bps)1200, 9600, 14400, 19200, 28800, 57600, 1152001200, 9600, 14400, 19200, 28800, 57600, 115200Data bits87,8Stop bits1,21,2ParityNone, Even, OddNone, Even, OddTable 1. Modbus Over RS-485 Configuration4

User Guide: FAAST XT Fire Alarm Aspiration Sensing Technology Modbus Protocol Schema 10Modbus Resources1.Modbus Application Protocol Specification, Version 1.1b3, Modbus Organization, Hopkinton, MA, 20122.Modbus over Serial Line Specification and Implementation Guide, Version 1.02, Modbus Organization, Hopkinton, MA, 20063.Modbus Messaging on TCP/IP Implementation Guide, Version 1.0b, Modbus Organization, Hopkinton, MA, 20064.T. Kugelstadt, “The RS-485 Design Guide”, Texas Instruments, Dallas, TX, Application Report SLA272B, May 20085.User Guide: FAAST Networking, System Sensor, Saint Charles, IL, 2012Client InterfaceAccessible RegistersInput registers for registers listed in Table 1. Holding registers in tables following.Data FormatTo transfer data to and from the MODBUS registers, the following descriptions specify how data is organized when more than oneregister is required to read or write a specific piece of data.1. Long Integer, floating point:Value 0xaabbccddHolding Reg1 0xaabbHolding Reg2 0xccdd2. String:Value “test”Holding Reg1 “et”Holding Reg2 “ts”3. IP Address:Value a.b.c.dHolding Reg1 dcHolding Reg2 ba4. MAC Address:Value 0x (aa-bb-cc-dd-ee-ff)Holding Reg1 0xbbaaHolding Reg2 0xddccHolding Reg3 0xffee5Rev A

User Guide: FAAST XT Fire Alarm Aspiration Sensing Technology Modbus Protocol Schema 10Device Sensor Status and Control OperationsModbus Administration PasswordThe Mobus Administrator Password grants the user the privilege of writing to the Holding Registers. This password is set in theModbus Configuration using PipeIQ. It is not readable through the Modbus Interface. It is set to ‘1111’ as the default. The values mayrange from 0001 to 9999.A failure to gain administrator privileges due to a forgotten or lost password is recoverable by using the PipeIQTM software, connectingto the device and updating the device configuration with a known password.Device ReadThe Modbus client is able to read the device status data directly via input and holding register reads.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.Device Output and Operating Mode ControlThe MODBUS client is able to initiate different operating modes through the Sensor Input Holding Register.1. rite the Administrator Password in the Administrator Password holding registerW(this is can be 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.b.c.d.e.f.g.h.i.4.0x0001 to Isolate0x0002 to Disable0x0004 to Reset the Device0x0008 to Initiate Test0x0010 to Reset the Airflow Baseline0x0020 to Silence a Fault or Alarm (when equipped with an audible indicator)0x0040 to Reset the Network Settings to Factory Default0x0080 to Clear the Event Log0x0100 to Clear the Message LogWrite 0x0 to the Administrator Password in the Administrator Password holding register if no further changes are desired.Device ConfigurationIn order to write a new configuration, the following steps must be followed:1.Write the Administrator Password in the Administrator Password holding register.2. ead the Sensor API status holding register and verify that the ADMIN UNLOCK bit is set. If it is set, the Sensor APIRCommand 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.4.Read the Operating Mode holding register to verify the device is in Disable Mode.5. he MODBUS client writes the new values for the respective configuration holding registers through Write Multiple RegisterTCommand(s).6. rite the Save Configuration Command value, 0xAA11 in the MODBUS Specific configuration Command holding register inWorder to save any configuration changes.7.The device stores new configuration. The current RTC value will be stored into time of last configuration registers.8. ead the MODBUS Specific configuration Command holding register. The value will be 0x0000 when the CommandRcompletes successfully.9.The device will reset if the configuration is valid.10. Remove the device from Disable Mode by clearing the disable bit in Sensor Input Holding register.11. The device will reset and the new configuration will be applied.6

User Guide: FAAST XT Fire Alarm Aspiration Sensing Technology Modbus Protocol Schema 10Device TimeIn order to set the time, the following steps must be followed:1.Write the Administrator Password in the Administrator Password holding register2. ead the Sensor API status holding register and verify that the ADMIN UNLOCK bit is set. If it is set, the Sensor APIRCommand Register is enabled and will process commands issued.3. he MODBUS client writes the new time value using Epoch/UNIX timestamp format to the time holding registers throughTWrite Multiple Register Command(s).4. rite the Save Time Command value, 0xEE22 in the MODBUS Specific configuration Command holding register in order toWsave the new time.5.The device stores and applies the new time.6. ead the MODBUS Specific configuration Command holding register. The value will be 0x0000 when the CommandRcompletes successfully.7.Write 0x0 to the Administrator Password in the Administrator Password holding register if no further changes are desired.Device Smoke ReferenceThe device may be programmed with a reference in order to compensate for a period of high particulate due to a change in ambientenvironmental conditions. Use the following steps to modify the Device Reference:1.Write the Administrator Password in the Administrator Password holding register2. ead the Sensor API status holding register and verify that the ADMIN UNLOCK bit is set. If it is set, the Sensor APIRCommand Register is enabled and will process commands issued.3. he MODBUS client writes the new Reference Value in 32-bit Float format to the Smoke Reference Value register throughTWrite 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.Reading LogsIn order to read the device logs, the following steps must be followed.Event Log Read1.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.3. rite the Event log index value into corresponding holding register using Write Single Holding Register Command (0x06).WThe default shall be 1 which reads the latest 40 events.4.Read Event Logs.Examples:a. Total no. of events 50, Index 2, then the Event log read command will read last 10 events.b. Total no. of events 80, Index 2, then the Event log read command will read last 40 events.c. Total no. of events 80, Index 3, then the client shall show Device read failure because there are no events presentin the memory corresponding to given Index value.7Rev A