Data Format ........................................................................................................................................................................................4
Device Sensor Status and Control Operations .............................................................................. 5
Device Output and Operating Mode Control ...................................................................................................................................5
Device Time ........................................................................................................................................................................................6
Device Status .....................................................................................................................................................................................9
Sensor Status ................................................................................................................................................................................... 11
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
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 Conguration
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
User Guide: FAAST Fire Alarm Aspiration Sensing Technology® Modbus Protocol Schema 1
Reading Logs
In order to read the device logs, the following steps must be followed.
Event Log Read
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.
3. Write the Event log index value into corresponding holding register using Write Single Holding Register Command
(0x06). The 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 present
in the memory corresponding to given Index value.
Trend Log Read
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.
3. Write the Trend log index value into corresponding holding register using Write Single Holding Register Command
(0x06). The default shall be 1 which reads the latest one trend log.
4. Read the Trend Log.
Examples:
a. Total no. of trends = 50, Index = 2, then the Trend log read command will read recent but one trend log.
b. Total no. of trends = 80, Index = 80, then the Trend log read command will read last trend log.
c. Total no. of trends = 30, Index >30, then the client shall show Device read failure because there are no trends present
in the memory corresponding to given Index value.
Message Log Read
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.
3. Write the Message log index value into corresponding holding register using Write Single Holding Register Command
(0x06). The default shall be 1 which reads the latest one message log.
4. Read the Message Log.
Examples:
a. Total no. of messages = 50, Index = 2, then the Message log read command will read recent but one message log.
b. Total no. of messages = 20, Index = 20, then the Message log read command will read last message log.
c. Total no. of messages = 30, Index >30, then the client shall show Device read failure because there are no messages
present in the memory corresponding to given Index value.
7
Rev A0
User Guide: FAAST Fire Alarm Aspiration Sensing Technology® Modbus Protocol Schema 1
Modbus Conguration
The device’s Modbus Configuration Structure is READ/WRITE and mapped directly to a set of holding registers. The structure in the
Firmware is defined as follows:
AddressSize
(16-bit
words)
403261∆ Administrator PasswordU16Password to enable Commands through the Command
3271∆ Sensor Command RegisterU16Command Register:
3281∆ Event Log IndexU16Starting Index of Event Log Entry which to read
3291∆ Trend Log IndexU16Starting Index of Trend Log to read
3301∆ Message Log IndexU16Starting Index of Message Log to read
∆ Information - Registers 326-330 can be configured by using Function code 6(single write) or Function 16 (multiple write).
Input Registers
The Modbus Holding Register addresses are indexed for a Honeywell Building Solutions Enterprise Building IntegratorTM client. Other
clients may need to subtract 1 from each address in order to access the desired register.
AddressSize
(16-bit
words)
300011SchemaU16Modbus Firmware Schema for client to determine version of
Parameter NameTypeDescription
register mapping.
Table 2. Modbus Input Registers
8
User Guide: FAAST Fire Alarm Aspiration Sensing Technology® Modbus Protocol Schema 1
Holding Registers
Note: The Modbus Holding Register addresses are indexed for a Honeywell Building Solutions Enterprise Building IntegratorTM client.
Other clients may need to subtract 1 from each address in order to access the desired register.
Device Status
The device’s Device Status Structure is READ ONLY and mapped directly to a set of holding registers. The structure in the Firmware
is defined as follows:
AddressSize
(16-bit
words)
40001-22Universal Time StampU32Read Only - Universal Time Stamp corresponding to the
real-time clock value in UNIX seconds epoch format
For internal use only.
Bit 0: Low Voltage
Bit 1: Low Flow
Bit 2: Configuration
Bit 3: Sensor
Bit 4: External Monitor
Bit 5: Time
Bit 6: Communication
Bit 7: Aspirator
Bit 8: Filter
Bit 9: Isolation
Bit 10: High Flow
Bits 11-15 unused
Bit 0: Low Flow
Bit 1: Configuration
Bit 2: External Monitor Open
Bit 3: External Monitor Short
Bit 4: Time
Bit 5: Filter
Bit 6: High Flow
Bits 7-15 unused
Bit 0: Low Flow
Bit 1: Configuration
Bit 2: Communication
Bit 3: Sensor
Bit 4: Aspirator
Bit 5: Filter
Bit 6: High Flow
Bit 7: Low Voltage
Bits 8-15 unused
19-3012Password Recovery CodeU16Code for recovering the device PipeIQ password.
Parameter NameTypeDescription
Bit 0: Alert
Bit 1: Action1
Bit 2: Action2
Bit 3: Fire1
Bit 4: Fire2
Bit 5: Minor (if equipped)
Bit 6: Urgent/Fault
Bit7: Isolate (if equipped)
Bits 8-15 unused
For internal use only.
For internal use only.
For internal use only.
Bit 0: Alert
Bit 1: Action1
Bit 2: Action2
Bit 3: Fire1
Bit 4: Fire2
Bits 5-15 unused.
User Guide: FAAST Fire Alarm Aspiration Sensing Technology® Modbus Protocol Schema 1
Sensor Status
The device’s Sensor Status Structure is READ ONLY with the exception of the Smoke Reference Value and mapped directly to a set
of holding registers. The structure in the Firmware is defined as follows:
AddressSize
(16-bit
words)
40031-322System TimeU32Device Time in UNIX seconds epoch format, use Universal
33-342∆ Smoke Reference ValueF32Smoke reference value used to increase noise floor of
351∆ Sensor Action InputsU16All bits are self-clearing and will read ‘0’ after bit has been
36½Ch 1 Air TemperatureS8Real-time sampled air temperature in Channel 1
37½Ch 1 Air Velocity ChangeS8Percentage change from baseline air velocity in Channel 1
38-392Ch 1 Air Velocity BaselineF32Average velocity during baselining in Channel 1
40-412Ch 1 Air Velocity Daily MinF32Daily minimum air velocity realized on Channel 1
42-432Ch 1 Air Velocity Daily MaxF32Daily maximum air velocity realized on Channel 1
44½Ch 2 Air TemperatureS8Real-time sampled air temperature in Channel 2
45½Ch 2 Air Velocity ChangeS8Percentage change from baseline air velocity in Channel 2
46-472Ch 2 Air Velocity BaselineF32Average velocity during baselining in Channel 2
48-492Ch 2 Air Velocity Daily MinF32Daily minimum air velocity realized on Channel 2
50-512Ch 2 Air Velocity Daily MaxF32Daily maximum air velocity realized on Channel 2
Parameter NameTypeDescription
Time Stamp instead.
detector.
US Standard Units Max: 0.10 (%/ft)
Metric Units Max: 0.328 (%/m)
read and processed
Bit 0: 1 Isolate – Toggles Isolate Mode
Bit1: 1 Disable – Toggles Disable Mode
Bit2: 1 Test – Place the device in Test Mode
Bit3: 1 Silence Sounder (if enabled / equipped)
Note: Sounder Silence is effective for a single alarm or fault
occurrence. If an alarm recurs, another alarm is initiated or
another fault occurs, the sounder will re-energize.
Bit4: Reset Device
Bit5: Reset Airflow Baselines
Current baseline cleared, and device will set a new
baseline. New baseline established within 15 minutes.
Bit6: Clear Event Log Note: Allow this action up to 10
seconds to complete. Erases all Event Log entries
Bit7: Clear Trend Log Note: Allow this action up to 5
seconds to complete. Erases all Trend Log entries
Bit8: Clear Message Log Note: Allow this action up to 5
seconds to complete. Erases all Message Log entries
Bit9-15: Unused
(multichannel device only)
(multichannel device only)
(multichannel device only)
(multichannel device only)
(multichannel device only)
11
Rev A0
User Guide: FAAST Fire Alarm Aspiration Sensing Technology® Modbus Protocol Schema 1
Sensor Status (Cont’d)
AddressSize
(16-bit
words)
52½Ch 3 Air TemperatureS8Real-time sampled air temperature in Channel 3
53½Ch 3 Air Velocity ChangeS8Percentage change from baseline air velocity in Channel 3
54-552Ch 3 Air Velocity BaselineF32Average velocity during baselining in Channel 3
56-572Ch 3 Air Velocity Daily MinF32Daily minimum air velocity realized on Channel 3
58-592Ch 3 Air Velocity Daily MaxF32Daily maximum air velocity realized on Channel 3
60½Ch 4 Air TemperatureS8Real-time sampled air temperature in Channel 4
61½Ch 4 Air Velocity ChangeS8Percentage change from baseline air velocity in Channel 4
62-632Ch 4 Air Velocity BaselineF32Average velocity during baselining in Channel 4
64-652Ch 4 Air Velocity Daily MinF32Daily minimum air velocity realized on Channel 4
66-672Ch 4 Air Velocity Daily MaxF32Daily maximum air velocity realized on Channel 4
69-702Smoke Current ObsF32Current Obscuration Level the Smoke Sensor is Detecting
71-722Smoke Daily Max ObsF32Maximum Obscuration Level the Smoke Sensor Detected
73-742Smoke Daily Min ObsF32Minimum Obscuration Level the Smoke Sensor Detected
75-762Alert ThresholdF32Current Active Alert Threshold ( %/ft if US Standard or %/m
77-782Action1 ThresholdF32Current Active Action1 Threshold ( %/ft if US Standard or
79-802Action2 ThresholdF32Current Active Action2 Threshold ( %/ft if US Standard or
81-822Fire1 ThresholdF32Current Active Fire1 Threshold ( %/ft if US Standard or %/m
83-842Fire2 ThresholdF32Current Active Fire2 Threshold ( %/ft if US Standard or %/m
851Sensor StatusU16Bit 0 – Admin Unlock
Parameter NameTypeDescription
(multichannel device only)
(multichannel device only)
(multichannel device only)
(multichannel device only)
(multichannel device only)
(multichannel device only)
(multichannel device only)
(multichannel device only)
(multichannel device only)
(multichannel device only)
since 12am
since 12am
if metric)
%/m if metric)
%/m if metric)
if metric)
if metric)
1 = Unlocked, 0 = Locked
Bit 1 –Baselining
1 = set (configured from sensor action inputs)
Table 4. Sensor Status Modbus Holding Registers
∆ Information - Registers 35 can be configured by using Function code 6(single write) or Function 16 (multiple write).
∆ Warning!! Device threshold configuration variables should be set by the user to values scaled based on the Units configuration
setting. The detector will interpret the value differently for different Units settings. E.g. The device will interpret a 0.01 threshold
setting as 0.01 %/ft when Units setting is US Standard. The device will interpret a 0.01 threshold setting as 0.01 %/m when Units
setting is Metric.
12
User Guide: FAAST Fire Alarm Aspiration Sensing Technology® Modbus Protocol Schema 1
Device Logs
The device’s Log Structure is READ ONLY and mapped directly to a set of holding registers. The structure in the Firmware is defined
as follows:
AddressSize
(16-bit
words)
400861Event Log EntriesU16Number of Event Log Entries
871Trend Log EntriesU16Number of Trend Log Entries
881Message Log EntriesU16Number of Message Log Entries
89-2083 x 40Read Event LogU32
209-23224Read Trend LogU32
233-29866Message LogU32
Parameter NameTypeDescription
U16
F32 [11]
U16 [64]
Reads 40 log entries starting with the entry in the Index register.
Each entry contains a 32-bit Epoch time stamp and 16-bit Event number
The events numbers represent the following events:
Test 0
Normal 1
Isolate 2
POR 3
Reset 4
UI Passcode Entry Failure 5
UI Passcode Entry Success 6
UI Button Autolock 7
Filter Cover Open 8
Filter Cover Closed 9
Configuration Change Success 10
User Login 11
User Logout 12
Flow Fault High 13
Flow Fault Low 14
Configuration Fault 15
Configuration Fault Urgent 16
Sensor Fault 17
External Device Fault 18
External Device Fault Clear 19
Communication Fault 20
Aspiration Fault 21
Aspiration Fault Urgent 22
Filter Fault 23
Filter Fault Urgent 24
Time Fault 25
Low Voltage Fault 26
Low Voltage Fault Clear 27
Alarm Alert 28
Alarm Action1 29
Alarm Action2 30
Alarm Fire1 31
Alarm Fire2 32
Operating Mode Disable 33
Reads log entry specified by the Index register.
Each entry contains a 32-bit time stamp and daily air velocity and smoke
detection logs including:
Float : Daily Alert Threshold
Float : Daily Action1 Threshold
Float : Daily Action2 Threshold
Float : Daily Fire1 Threshold
Float : Daily Fire2 Threshold
Float : Trend Max
Float : Trend Min
Float : Trend Avg
Float : Air Velocity Max
Float : Air Velocity Min
Float : Air Velocity Avg
Reads the log entry specified by the Index register.
Each entry contains a 32-bit time stamp and a UTF-16 64 character string.
Table 5. Device Log Modbus Holding Registers
13
Rev A0
User Guide: FAAST Fire Alarm Aspiration Sensing Technology® Modbus Protocol Schema 1
Factory Conguration
AddressSize
(16-bit
words)
40299½SLC Interface PresentboolDesignates the presence of an SLC interface
3001SLC_PROTOCOL_TYPEU16Defines the supported SLC protocol.
3011OEMID_TYPEU16Defines Device OEM.
302-3043MAC AddrU8[6]Device’s MAC Address
305½Sensor TypeU8Smoke 1
306½Firmware Main Board RevU8Main Board Microcontroller Firmware Image Revision
∆ Warning!! Device threshold configuration variables should be set by the user to values scaled based on the Units configuration
setting. The detector will interpret the value differently for different Units settings. E.g. The device will interpret a 0.01 threshold
setting as 0.01 %/ft when Units setting is US Standard. The device will interpret a 0.01 threshold setting as 0.01 %/m when Units
setting is Metric.
16
User Guide: FAAST Fire Alarm Aspiration Sensing Technology® Modbus Protocol Schema 1
TimeReal time clock time in hours/minutes/secondsMidnight
DateReal time clock dateCurrent date
YearReal time clock yearCurrent year
Log SettingConfigures the method of Event logging for either
FIFO (first in first out) or LIFO (last in first out) setting
Password UserPassword for Web Access User entryMonitor
Latching/Non-LatchingLatching
Latching/Non-LatchingLatching
Latching/Non-LatchingLatching
Latching/Non-LatchingLatching
Latching/Non-LatchingLatching
0 - 60 seconds0
0 - 60 seconds0
0 - 60 seconds0
0 - 60 seconds0
0 - 60 seconds0
Locked / Unlocked For the lock
function to work the passcode
must be any value other than
0000
0-255
1-99
1-159
1-255
FIFO / LIFOFIFO
Locked
Locked
Locked
1
Table 10. Device Configuration Variable Ranges.
19
Rev A0
User Guide: FAAST Fire Alarm Aspiration Sensing Technology® Modbus Protocol Schema 1
Technical Support
System Sensor strives to provide our customers with outstanding support for the FAAST Fire Alarm Aspiration Sensing Technology®
and all our products. For more information, contact us using one of the methods below: