Table 2: Milliamp Logic Chart
Priority State Load Current mA
1 Fire 20 ± 0.2
2 Fire IR Warning 16 ± 0.2
3 Ref IR Warning 15 ± 0.2
4 Fire Relay Coil Fault 3 ± 0.2
5 Calibration not complete /
EEPROM Corrupted Fault
2 ± 0.2
6 Exceedance Fault 1.5 ± 0.2
7 Block Fault 2.5 ± 0.2
8 Self-Test Fault 1 ± 0.2
9 Current Loop Fault 0 ± 0.2
10 Normal 4 ± 0.2
RS485 MODBUS RTU
The Series 760 Flame Detector is equipped with a two wire, half-
duplex, serial communication interface which supports the MODBUS
RTU protocol. The RS485 MODBUS RTU will allow up to 31 detectors
to be networked to a controller (i.e., customized re panel or personal
computer). The network controller will perform the master duties.
Due to the network being in half-duplex mode, it will only allow one
transmitter to be broadcasting on the network at one time.
The RS485 MODBUS RTU Option
The RS485 MODBUS RTU is enabled when switch 8 is in the “ON”
position. The Flame Detector has to be programmed to a unique
detector number from 1 through 247. The detector number will give
the Flame Detector an address on the network.
Programming the Detector Address Number
This option is activated when switch position 9 is toggled“ON”. The
option is deactivated when the switch is in the “OFF”position. This
option provides the user with a method of programming the unit
number into the non-volatile memory of the microprocessor.
To program the detector address number, rst remove power from
the detector. Then toggle the program option“ON” and use the
remaining eight switches on the User Selectable Interface (USI) to set
the detector address number.
In program mode, the USI becomes a binary programmer as illustrated
in Table 3. When a switch is toggled“ON”, it will equal the binary
weighted number. These binary weighted numbers are added
together when a multiple number of switches are switched“ON” (i.e.,
if SW2 and SW3 were toggled“ON”, then the detector number would
equal a 6)
Table 3: Binary Weight for Switch States “ON”
SW1 SW2 SW3 SW4 SW5 SW6 SW7 SW8
1 2 4 8 16 32 64 128
When power is applied to the detector, the detector will sense that it is
in program mode and read the eight switch positions. From the switch
setting, it will determine the detector number. Once the number
has been determined, the detector will enter it into the non-volatile
memory of the microprocessor. Next, the amber LED will ash “ON”a
certain number of times equaling the detector address number in the
following manner: the detector will ash the hundreds digit, pause 2
seconds, ash the tens digit, pause 2 seconds, and then ash the ones
digit. Then it will hold the amber LED “ON”constantly for about 10
seconds. Next, the detector will repeat this sequence. This process will
continue for up to 5 minutes.
Once you are sure that the proper number is programmed, then shut
the power“OFF”and reset the USI options to suit your application.
Reference the section on the USI if you are not sure which option is
best for your application or call a Vibro-Meter, Inc application engineer.
Note: In the case that the program option switch is left“ON”and the
detector is installed on network, the detector will go through the same
process as explained previously, but after 5 minutes the detector will
reset and use the last USI setting that it had prior to going into the
program mode.
MODBUS RTU Protocol
A typical MODBUS message or Application Data Unit (ADU), which
is also referred to as a MODBUS RTU Message Frame, as illustrated in
Table 4 consists of a Slave Address byte, a Protocol Data Unit and two
CRC error checking bytes in accordance with the MODBUS standard.
A Slave Address of 0 is used when a message is directed to “ALL” Slave
Devices (MODBUS Broadcast Mode). A Slave address of 1 to 247 is
used when directing a message to a single Slave Device (MODBUS
Unicast Mode).
Table 4: MODBUS Application Data Unit Format
Slave Address Protocol Data Unit CRC Low CRC High
The Protocol Data Unit (PDU) shown in Table 5 consists of a function
code byte and a data eld. The data eld supported by this application
may be empty (no bytes) or it may contain up to two address and two
data bytes.
Table 5: MODBUS Protocol Data Unit Format
Function
Code
Address
High
Address
Low
Data
High
Data
Low
MODBUS RTU Supported Commands
In normal operating mode, the Flame Detector will receive and
respond to the following MODBUS commands listed in Table 6.
Table 6: PDU Supported MODBUS Commands
Supported Commands Function
codes
Addr
high
Addr
low
Data
high
Data
low
Fire & Fault relay status 0x01 0x00 0x00 0x00 0x08
USI Status 0x02 0x00 0x01 0x00 0x08
Fire Delay (EEPROM) 0x03 0x00 0x02 0x00 0x01
Warning Delay
(EEPROM)
0x03 0x00 0x03 0x00 0x01
Fire Occurrences 0x03 0x00 0x04 0x00 0x01
Fault Occurrences 0x03 0x00 0x05 0x00 0x01
Fire Delay (Measured) 0x03 0x00 0x06 0x00 0x01
Warning Delay
(Measured)
0x03 0x00 0x07 0x00 0x01
MODBUS ID# 0x06 0x00 0x08 0x00 0x00
to
0xFF
Clear Fire Occurrences 0x06 0x00 0x09 0x00 0x00
Clear Fault
Occurrences
0x06 0x00 0x0A 0x00 0x00
Software Reset 0x06 0x00 0x0C 0x00 0x06