6 Configuring the FieldServer as a Secutron Modul-R driver Server ................................................................ 10
6.1Server Side Connection Parameters ............................................................................................................ 10
6.2Server Side Node Parameters ...................................................................................................................... 10
6.3Server Side Map Descriptors........................................................................................................................ 11
6.3.1 FieldServer Specific Map Descriptor Parameters ................................................................................. 11
6.3.2 Driver Specific Map Descriptor Parameters ......................................................................................... 11
Appendix A. Troubleshooting .............................................................................................................................. 13
Appendix B. Reference ........................................................................................................................................ 14
Appendix B.1. Event Function or Condition Codes .................................................................................................. 14
Appendix B.2. Panel Circuit or Zone numbers ......................................................................................................... 15
Appendix B.3. Panel Power-up, Restarts and Resets ............................................................................................... 16
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Polls the Secutron Modul-R at the configured scan interval.
Device
Stores alarm (Device) statuses.
Function
Stores the function or type of alarm that was triggered or restored.
Secutron_type
Map Descriptor Function
Device
Stores alarm (Device) statuses.
Function
Stores the function or type of alarm that was triggered or restored.
Fieldserver
Mode
Nodes
Comments
Client
Up to 1000 per
port
Only one panel can be connected per port, but the driver supports up to
1000 networked panels.
Server
10
Max of 10 panels supported due to memory limitations.
1 SECUTRON MODUL -R DRIVER DESCRIPTION
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. The Client Drive supports up to 1000 networked panels per port, but the Server
driver only supports 10 panels due to memory limitations. A Server panel can consist of up to 100 circuits.
When 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.
Each circuit’s alarms are represented by 32 unsigned quantities, which hold 1,024 bits. Only bits 0 to 999 may be
used. The last 25 bits are reserved.
There are 3200 unsigned quantities per panel to represent the 100 circuits with 1000 devices per circuit. Each bit
of the 32-bits in an unsigned quantity represents an alarm state (1 = alarm, 0 = normal).
A set bit indicates an alarm and the clearing of a bit indicates the reset of an alarm. A panel number is identified
by the Node Id in the configuration files.
Panel, circuit and device numbers range from 0 in messages e.g.
Panel numbers – 0 to 999
Circuit numbers – 0 to 99
Device numbers – 0 to 999
The Client driver is configured with three Map Descriptors. Each Map Descriptor must be of a certain
“Secutron_Type”. The following types and their functions are defined:
The Server driver emulates a Secutron Modul-R panel and is configured through the use of two Map Descriptors:
The Server driver will respond with alarm statuses from the Device Map Descriptor. The Function Map Descriptor
will return the type or function of the corresponding alarm reported by the Device Map Descriptor.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
5 CONFIGURING THE FIEL DSERVER 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.
5.1 Client Side Connectio n Paramete rs
Example
1
Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction manual for details of the ports available
on specific hardware.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Any unique
name. Name
will appear in
Bridge Map
Descriptor
status
information
screens.
The rate at which the
driver polls the panel.
A Data Array name
must be one found
under Data_Arrays.
Data from a circuit
event will be stored in
the array at
Data_Array_Offset.
The Poller Data Array
will contain non-zero
data when
communications with
the panel is OK
Function must be
read for pollers and
all others
Passive_Client.
A name given
to the device to
which the
FieldServer is
connected.
The type of data the
Map Descriptor
points to. Device
data contains alarm
statuses. Function
data contains
condition codes.
Refer to Appendix
B.1 for more
information.
The circuit or
zone number
used to trap
incoming events
into the Map
Descriptor. See
Driver notes.
The number of devices
on the circuit this Map
Descriptor can detect
for incoming events.
5.3.4 Map Descripto r Example.
.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Generic Node ID unique to port. Also used as panel number.
0-9
Protocol
Specify protocol used
Secutron
Port
Port to which node belongs
P1-P8
6 CONFIGURING THE FIEL DSERVER 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.
6.1 Server Side Connectio n Parameters
Example
6.2 Server Side Node Pa rame te rs
2
Not all ports shown are necessarily supported by the hardware. Consult the appropriate Instruction manual for details of the ports available
on specific hardware.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Any unique
name. Name
will appear in
Bridge Map
Descriptor
status
information
screens.
The rate at which the
driver polls the panel.
A Data Array name
must be one found
under Data_Arrays.
Data from a circuit
event will be stored in
the array at
Data_Array_Offset.
Function may not be
read or write since
it implements a
Server. Function
may only be Passive.
A name given
to the device to
which the
FieldServer is
connected.
The type of data the
Map Descriptor
points to. Device
data contains alarm
statuses. Function
data contains
condition codes.
Refer to Appendix
B.1 for more
information.
The circuit or
zone number
used to trap
incoming events
into the Map
Descriptor. See
Driver notes.
The number of devices
on the circuit this Map
Descriptor can detect
for incoming events.
6.3.3 Map Descripto r Exam pl e.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com
Appendix A.1. 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
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 following table lists the full list of event function codes
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:
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com