The Secutron Modul-R driver allows the FieldServer to transfer data to and from a Client and a Server
panel on a single point to point network over RS-232 using Secutron Modul-R protocol.
The protocol is strictly command/response with the Client polling a Server device. A Server device can
report the generation and clearing of alarms to the polling Client. One panel can be connected per
FieldServer port. The driver supports networked panels connected to a single port. The server driver
only supports 10 panels due to memory limitations. A Server panel can consist of up to 100 circuits.
Whan an alarm is generated, a bit is set and when the alarm is cleared, the bit is cleared. The panel
number is identified by the Node_ID in the configuration file.
2. Driver Scope of Supply
2.1. Supplied by FieldServer Technologies for this driver
FieldServer Technologies PART # Description
FS-8917-16 Pigtail cable for RJ45 Port
FS-8700-72 Driver Manual.
.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
4. Configuring the FieldServer as a Secutron Modul-R driver Client
For a detailed discussion on FieldServer configuration, please refer to the FieldServer Configuration
Manual. The information that follows describes how to expand upon the factory defaults provided in the
configuration files included with the FieldServer (See “.csv” files on the provided with the FieldServer).
This section documents and describes the parameters necessary for configuring the FieldServer to
communicate with Secutron Modul-R panels.
The configuration file tells the FieldServer about its interfaces, and the routing of data required. In order
to enable the FieldServer for Secutron Modul-R driver communications, the driver independent
FieldServer buffers need to be declared in the “Data Arrays” section, the destination device addresses
need to be declared in the “Client Side Nodes” section, and the data required from the Servers needs to
be mapped in the “Client Side Map Descriptors” section. Details on how to do this can be found below.
Note that in the tables, * indicates an optional parameter, with the bold legal value being the default.
The Poller Data Array will contain non-zero data when communications with the panel is OK.
Provide data format. Each Data Array can only take
on one format.
Number of Data Objects. Must be larger than the data
storage area required for the data being placed in this
array.
5. Configuring the FieldServer as a Secutron Modul-R driver Server
For a detailed discussion on FieldServer configuration, please refer to the FieldServer Configuration
Manual. The information that follows describes how to expand upon the factory defaults provided in the
configuration files included with the FieldServer (See “.csv” files provided with the FieldServer).
The configuration file tells the FieldServer about its interfaces, and the routing of data required. In order
to enable the FieldServer for Secutron Modul-R driver communications, the driver independent
FieldServer buffers need to be declared in the “Data Arrays” section, the FieldServer virtual node(s) need
to be declared in the “Server Side Nodes” section, and the data to be provided to the Client needs to be
mapped in the “Server Side Map Descriptors” section. Details on how to do this can be found below.
Note that in the tables, * indicates an optional parameter, with the bold legal value being the default.
Provide data format. Each Data Array
can only take on one format.
Number of Data Objects. Must be larger
than the data storage area required for
the data being placed in this array.
Up to 15 alphanumeric
characters
Bit, Packed_Bit, Byte,
Uint16
1-10,000
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
5.4.1. FieldServer Specific Map Descriptor Parameters
Column Title Function Legal Values
Map_Descriptor_Name Name of this Map Descriptor Up to 32 alphanumeric characters
Name of the Data Array where
Data_Array_Name
Data_Array_Offset Starting location in Data Array
Function
Node_Name
Length
Block_Type*
data is to be stored in the
FieldServer
Function of Client Map
Descriptor
The name of the Node the Map
Descriptor is attached to
The number of devices on the
circuit the Map Descriptor must
represent
Used to enable packed bit when
using a Packed_Bit Data Array
on the Map Descriptor
One of the Data Array names from
“Data Array” section above
0 to (Data_Array_Length-1) as
specified in “Data_Array” section
Server
One of the Node Names specified
in “Server Node Descriptor” above
0-999
Flag, -
5.4.2. Driver Specific Map Descriptor Parameters
Column Title Function Legal Values
Secutron_Type Identifies the type of data the Map Descriptor points to Device, Function
Secutron_Circuit Identifies the circuit or panel zone 0-99
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
When the Client driver receives an event from the panel, it stores the event’s function or condition
code in the Secutron_Type=function Map Descriptor’s Data Array at the device number’s offset,
Example:
Device=3 on Circuit=1 goes into alarm – the Panel reports an event with function code A (Decimal 65)
The Map Descriptor Secutron_Type=device, Secutron_Circuit=1 will set a bit and store the event
function code A (Decimal 65) at offset 3 in the Map Descriptors’ Data Array.
The Secutron_Type=device Map Descriptors will set a bit if any of the events listed below occur on
that circuit or zone. The bit will be cleared if the panel reports the event as cleared.
The full list of event function codes are:
ASCII value Decimal Meaning
A
B 66 Bypass
C 67 Comlink
D 68 Duplicate Addressable Device
E 69 Maintenance Alert
G 71 Ground Fault
H 72 Hot Key Pressed
I 73 Illegal Addressable Device
J 74 Switch
M 77 Missing Addressable Device
N 78 Non-Fire/Non-Reporting
P 80 Pull Station Alarm
Q 81 Releaser Abort
R 82 Releaser Halt
S 83 Supervisory
T 84 Trouble or Parameter Change
U 85 Wrong Device Type
W 87 Waterflow Alarm
65 Alarm
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
The panel groups events under circuit or zone numbers. When setting up a Client configuration it is
necessary to create Map Descriptors to trap the events from the zones or circuits you want to see
data from.
If an event is received that has no corresponding Map Descriptor defined, this will be reported on the
RuiNet E screen. This is a useful configuration tool to ensure that all required data is stored.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
When the panel powers up or is restarted it will send an event on zone/circuit 69 device 0.
When the panel is reset from the Hot Keys on the front panel, it will send an event on zone/circuit 90,
device 9.
The Client driver will clear all the Secutron_Type=device and Secutron_Type=function Data Arrays
when it traps any of these 2 events, provided the circuit 69 and 90 Map Descriptors have been set up
as per the example Map Descriptors under the Client Side configuration instructions.
Other events for Circuits 69 and 90 are shown below for which a bit will be set in the
Secutron_Type=device Map Descriptor’s Data Array at the device offset values shown below:
001 – Fire Drill 026– Switch 11 On
002 - Lamp Test 027 – Switch 12 On
003 – Releaser Disconnect 028 – Switch 13 On
004 – Relay disconnect 029 – Switch 14 On
005 – Test mode 030 – Switch 15 On
006 – Signal Disconnect 031 – Switch16 On
007 - Acknowledge 032 – Switch 1 Off
008 – Signal Silence 033 – Switch 2 Off
009 - Reset 034 – Switch 3 Off
010 – Common Disconnect 035 – Switch 4 Off
011 – General Alarm 036 – Switch 5 Off
012 - Halt 037 – Switch 6 Off
013 - Abort 038– Switch 7 Off
013 – 2nd Stage Inhibit 039– Switch 8 Off
016 – Switch 1 On 040– Switch 9 Off
017 – Switch 2 On 041– Switch 10 Off
018 – Switch 3 On 042– Switch 11 Off
019 – Switch 4 On 043 – Switch 12 Off
020 – Switch 5 On 044 – Switch 13 Off
021 – Switch 6 On 045 – Switch 14 Off
022– Switch 7 On 046 – Switch 15 Off
023– Switch 8 On 047 – Switch16 Off
024– Switch 9 On 051 – Manual Restart
025– Switch 10 On
Appendix A.4. Driver Messages, Error Messages and Optional Map Descriptors
The Client driver will report all events it receives from the panel on the RuiNet F screen.
If an event is received that has no corresponding Map Descriptor defined, this will be reported on the
RuiNet E screen. This is a useful configuration tool to ensure that all required data is stored.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com