Chipkin Mircom PRO2000 FS-8705-17 User manual

ffffnbjjjjjj
[e-mail]
Tel: [phone]
© 2021 CHIPKIN AUTOMATION SYSTEMS
Driver Version: 1.00a
Document Revision: 1

FS-8705-17 Mircom Pro2000 Serial Driver Page 2 of 32
© 2021 CHIPKIN AUTOMATION SYSTEMS
TABLE OF CONTENTS
1MIRCOM PRO2000 FIRE ALARM PANEL SERIAL DRIVER DESCRIPTION.......................................................................................3
2DRIVER SCOPE OF SUPPLY.........................................................................................................................................................5
2.1 SUPPLIED BY FIELDSERVER TECHNOLOGIES FOR THIS DRIVER...................................................................................................................5
2.2 PROVIDED BY THE SUPPLIER OF 3RD PARTY EQUIPMENT........................................................................................................................5
Required 3rd Party Hardware................................................................................................................................................5
Required 3rd Party Software .................................................................................................................................................5
Required 3rd Party Configuration..........................................................................................................................................5
3HARDWARE CONNECTIONS.......................................................................................................................................................6
3.1 HARDWARE CONNECTION TIPS /HINTS .............................................................................................................................................7
4CONFIGURING THE FIELDSERVER AS A PRO2000 FIRE ALARM PANEL ACTIVE CLIENT ..............................................................10
4.1 DATA ARRAYS/DESCRIPTORS .........................................................................................................................................................10
4.2 CLIENT SIDE CONNECTION DESCRIPTIONS.........................................................................................................................................12
4.3 CLIENT SIDE NODE DESCRIPTORS....................................................................................................................................................14
4.4 CLIENT SIDE MAP DESCRIPTORS .....................................................................................................................................................15
FieldServer Related Map Descriptor Parameters ...............................................................................................................15
Driver Related Map Descriptor Parameters .......................................................................................................................16
Timing Parameters .............................................................................................................................................................16
Map Descriptor Example 1 .................................................................................................................................................17
4.5 HOW POINT DATA IS STORED ........................................................................................................................................................18
4.6 HOW MOST RECENT EVENT DATA IS STORED....................................................................................................................................18
4.7 DRIVER LIMITATIONS AND EVENT PROCESSING..................................................................................................................................20
How to use the tool ............................................................................................................................................................23
4.8 DRIVER LIMITATIONS....................................................................................................................................................................25
5CONFIGURING THE FIELDSERVER AS A PRO2000 SERVER ........................................................................................................26
6REVISION HISTORY..................................................................................................................................................................27
ADVANCED TOPICS.................................................................................................................................................28
DRIVER ERROR MESSAGES ...............................................................................................................................................28
DRIVER STATISTICS .........................................................................................................................................................30
Exposing Driver Stats .....................................................................................................................................................30
THE CLIENT SIDE OF THE CONFIGURATION ...........................................................................................................................31

FS-8705-17 Mircom Pro2000 Serial Driver Page 3 of 32
© 2021 CHIPKIN AUTOMATION SYSTEMS
1Mircom PRO2000 Fire Alarm Panel Serial Driver Description
The driver provides an interface to monitor a Mircom Pro2000 Fire Alarm Panel. It is able to read status data from the
panel –when combined with another protocol driver this data can be served using another protocol such as BACnet,
Lonworks, Johnson Controls N2, Rockwell, XML etc. A block diagram showing potential connectivity is provided below.
To avoid manual configuration the driver is provided with a utility that is used to aid in the creation of the FieldServer
configuration. This utility reads the PRO2000 Modbus CSV and uses this to make BACnet objects, for each device
connected to the system. One set of objects for each device is created –reporting the alarm, trouble and other status
info of the device. The Modbus CSV file is created when the panel is configured and is provided by the engineer who
configures the fire alarm panel.
This is an active client driver –it sends commands and polls and the panel responds with data.
The driver supports a small subset of the command/query functions and assumes the devices have been configured
correctly and appropriately to achieve the control required.
The driver can only be used as a client. Minimal server functionality is provided only to support our ongoing quality
assurance program by facilitating automated testing of the driver. It is not documented or supported.
Synchronization
No special steps are required for synchronization. On startup the driver will looked for new flagged events, thereafter it
will read the status of every device thus providing an automatic synch.
Driver Functionality
The driver continuously polls the panel reading a set of change flags. These flags are set by the panel when a device’s
status changes. Actually each flag may represent more than one device. The Pro200 refers to these groups of devices as
blocks. When a change flag is seen, the driver reads the set of data associated with the device that the change flag
represents. This can range from 1 to 100 devices. The quantity (block size) is determined by the panel configuration
engineer. When data associated with a change flag is read, the panel unsets the flag.
If more than one change flag is set this is how the driver operates. It reads, the data associated with the 1st one set. In
the next cycle, when it reads the change flags again, it will look for a change flag for a higher block number and then
read that block’s data. It only returns to look at the start of the change flags again when all the change flags have been
processed.
If no change flags are set, the driver will read the data for each device by reading the blocks of data associated with each
flag. In this mode, with no change flags set, the driver sequences through each block in turn and starts at the beginning
again.
Each device has 16 bits allocated to it. These bits report the status of the device. They are documented in this manual
but you should check with the manufacturer’s documentation in case there have been changes. This data can be
mapped onto any other FieldServer protocol such as BACnet or Modbus/TCP.

FS-8705-17 Mircom Pro2000 Serial Driver Page 4 of 32
© 2021 CHIPKIN AUTOMATION SYSTEMS
Configuration Tool
CAS has developed a configuration tool to assist in the automation of the production of the configuration file. To obtain
a copy of the tool send an email to [email protected] and ask for the ‘Mircom Pro2000 configuration tool’.
Use of this tool eliminates the need to create the 16 potential objects for each device, eliminates the need to retype the
device labels etc. .. ie use it for productivity and accuracy.
The tool uses the data in the Modbus file to produce a portion of a FieldServer configuration. This is then added to the
base configuration file and the result is a complete configuration to map the panel data onto BACnet/IP objects.
Max Nodes Supported
FIELDSERVER MODE
NODES
COMMENTS
Active Client
1
Only one panel can be connected to a single FieldServer . If
this LIMITATION has significant impact for your project,
contact us, we might be able to change this limitation.
Active Server
(Simulate a PRO2000
Panel)
0
Not supported or documented.

FS-8705-17 Mircom Pro2000 Serial Driver Page 5 of 32
© 2021 CHIPKIN AUTOMATION SYSTEMS
2Driver Scope of Supply
2.1 Supplied by FieldServer Technologies for this driver
FIELDSERVER
TECHNOLOGIES
PART #
DESCRIPTION
-
No specific cables are shipped with this driver.
A generic RJ45 Ethernet cable must be shipped with this driver.
-
A generic male and Female connector kit must be shipped with
this driver.
FS-8705-17
Driver Manual.
2.2 Provided by the Supplier of 3rd Party Equipment
Required 3rd Party Hardware
PART #
DESCRIPTION
Required 3rd Party Software
Required 3rd Party Configuration
None known.

FS-8705-17 Mircom Pro2000 Serial Driver Page 6 of 32
© 2021 CHIPKIN AUTOMATION SYSTEMS
3Hardware Connections
Multiple upstream protocols and connection supported. See list of FieldServer Drivers.
Ethernet Network
Connection via std
networking interfaces
such as hubs, switches,
routers.
Lonworks
Device
RS232/RS485 Network
(Units with 1-8ports
available)
Lonworks Network
FS30 Series
Modbus
TCP
BACnet
IP BACnet
Ethernet
Rockwell
Ethernet/IP
or
CSP
HTTP
and other web
protocols
XML
Omron
Fins
GE-SRTP
or
GE-EGD
Other serial protocols
such as
Rockwell DF1
GE-SNP
JCI Metasys N2
Bacnet MSTP
Free BACnet test software with purchase*
Confidently test the BACnet interface.
Discover devices and their objects. Test
and document them. Arm yourself with a
powerful field tool. Full license.
We are always adding to
the library of protocols
and can add yours.
Monitor and Control Mircom PRO2000 FIre Panels using BACnet, Lonworks or a PLC system
MIRCOM
PRO2000 Series
Fire and Gas
Panels

FS-8705-17 Mircom Pro2000 Serial Driver Page 7 of 32
© 2021 CHIPKIN AUTOMATION SYSTEMS
3.1 Hardware Connection Tips / Hints
Jack J4 Pinout

FS-8705-17 Mircom Pro2000 Serial Driver Page 8 of 32
© 2021 CHIPKIN AUTOMATION SYSTEMS
MPU Switch Positions
Led’s for RS232
1
2
3
4
5
8
7
6
5
5
Mircom
Jack J4
(RJ11
Telephone
Jack)
FieldServer
RJ45
6 4
2
1
GE-TLC Direct Connect
to RJ111 to RJ45 Cable
Blue
Yellow
Green
Red
Black
White
Orange-White
Blue-White
Brown
Assembly Instructions
1. Cut one end off a
RJ45 Patch cable.
2.
Jumper between 1,3 and 6.
Rx
Tx
Gnd
Cable Assembly –This cable is not provided.

FS-8705-17 Mircom Pro2000 Serial Driver Page 9 of 32
© 2021 CHIPKIN AUTOMATION SYSTEMS
1
2
3
4
59
8
7
6
1
2
3
4
59
8
7
6
1
2
3
4
5
Mircom
Jack J4
(RJ11
Telephone
Jack)
6
Blue
Yellow
Green
Red
Black
White
Jumper between 1,3 and 6.
Rx
Tx
Gnd
DB9
Female
Cable Assembly –This cable is not provided.

FS-8705-17 Mircom Pro2000 Serial Driver Page 10 of 32
© 2021 CHIPKIN AUTOMATION SYSTEMS
4Configuring the FieldServer as a PRO2000 Fire Alarm Panel Active 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” sample files provided with the FS).
This section documents and describes the parameters necessary for configuring the FieldServer to communicate with a
PRO2000 Panel.
4.1 Data Arrays/Descriptors
The configuration file tells the FieldServer about its interfaces, and the routing of data required. In order to enable the
FieldServer for FSC - Electronic Siren Controllers Serial 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.
SECTION TITLE
Data_Arrays
COLUMN TITLE
FUNCTION
LEGAL VALUES
Data_Array_Name
Provide name for Data Array
Up to 15 alphanumeric
characters
Data_Array_Format
Provide data format. Each Data Array
can only take on one format.
Float, Bit, UInt16, Uint32,
SInt16, Packed_Bit, Byte,
Packed_Byte,
Swapped_Byte
Data_Array_Length
Number of Data Objects. Must be
larger than the data storage area
required by the Map Descriptors for
the data being placed in this array.
1-10,000

FS-8705-17 Mircom Pro2000 Serial Driver Page 11 of 32
© 2021 CHIPKIN AUTOMATION SYSTEMS
Example
// Data Arrays
Data_Arrays
Data_Array_Name,
Data_Format,
Data_Array_Length,
PRO2k_DATA,
Packed_Bit,
16000
PRO2k_FLAGS,
Packed_Bit,
1600
pro2000-stats,
UNT16,
200
REQUIRED:
These 3 Data arrays are required in
all Pro2000 configurations.

FS-8705-17 Mircom Pro2000 Serial Driver Page 12 of 32
© 2021 CHIPKIN AUTOMATION SYSTEMS
4.2 Client Side Connection Descriptions
Create one connection for each PRO2000 port. Each connection can only be used to connect to a single PRO2000
interface/port.
SECTION TITLE
Connections
COLUMN TITLE
FUNCTION
LEGAL VALUES
Port
Specify which port the device is
connected to the FieldServer
P1-P8, R1-R21
Protocol
Specify protocol used
Mircom_PRO2000
Baud*
Specify baud rate
Driver Supports : 110; 300; 600;
1200; 2400; 4800; 9600; 19200;
28800; 38400; 57600 Baud
PRO2000 supports:
2400,4800,9600,91200
Parity*
Specify parity
Driver Supports : 7,8
PRO2000 supports: 8
Data_Bits*
Specify data bits
Driver Supports : 1,2
PRO2000 supports: 1
Stop_Bits*
Specify stop bits
Driver Supports : Odd, Even, None
PRO2000 supports: none
Handshaking*
Specify hardware handshaking
None
Poll _Delay*
This parameter is not used.
Example
// Client Side Connections
Connections
Port,
Baud,
Parity,
Protocol,
P1,
9600,
None,
Mircom_PRO2000,
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.

FS-8705-17 Mircom Pro2000 Serial Driver Page 13 of 32
© 2021 CHIPKIN AUTOMATION SYSTEMS

FS-8705-17 Mircom Pro2000 Serial Driver Page 14 of 32
© 2021 CHIPKIN AUTOMATION SYSTEMS
4.3 Client Side Node Descriptors
Create one Node per connection only.
SECTION TITLE
Nodes
COLUMN TITLE
FUNCTION
LEGAL VALUES
Node_Name
Provide name for node
Up to 32 alphanumeric characters
Node_ID
Station address of physical
server node
This parameter is not used
directly by the driver. We
recommend that a unique Node
ID’s be given to each node.
1-258
Protocol
Specify protocol used
PRO2000
Connection
Specify which port the device is
connected to the FieldServer
P1-P8, R1-R22
Pro2000_Max_Blocks
When there are no change flags
set the driver sequences through
each block of device information.
However, the driver doesn’t
know how many block there are
being used so it could read more
information than necessary. Use
this parameter to make sure the
driver does not read data blocks
that do not correspond to
installed devices.
16 , Any whole number Max=32
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.

FS-8705-17 Mircom Pro2000 Serial Driver Page 15 of 32
© 2021 CHIPKIN AUTOMATION SYSTEMS
Example
// Client Side Nodes
Nodes
Node_Name,
Node_ID,
Protocol,
Connection
Pro2kPanel,
1,
Mircom_PRO2000,
P1
4.4 Client Side Map Descriptors
Think of a Map Descriptor as a task. Normally each task read or writes different items of data. For this driver is there is
only one map descriptor required –its precense is mandatory.
FieldServer Related Map Descriptor Parameters
COLUMN TITLE
FUNCTION
LEGAL VALUES
Map_Descriptor_Name
Name of this Map
Descriptor
Up to 32 alphanumeric
characters
Data_Array_Name
Name of Data Array
where data is to be stored
in the FieldServer
One of the Data Array names
from “Data Array” section
above
Data_Array_Offset
Starting location in Data
Array
0 to maximum specified in
“Data Array” section above
Function
Function of Client Map
Descriptor
RDBC, WRBC, WRBX

FS-8705-17 Mircom Pro2000 Serial Driver Page 16 of 32
© 2021 CHIPKIN AUTOMATION SYSTEMS
Driver Related Map Descriptor Parameters
COLUMN TITLE
FUNCTION
LEGAL VALUES
Node_Name
Name of Node to fetch data
from
One of the node names
specified in “Client Node
Descriptor” above
Data_Type
Data type
This commonly used
parameter is not used by
this driver.
Length
Length of Map Descriptor
This commonly used
parameter is not used by
this driver. However, it
must be specified with a
value of 1.
1
Address
This commonly used
FieldServer parameter is
not used by this protocol.
Timing Parameters
COLUMN TITLE
FUNCTION
LEGAL VALUES
Scan_Interval
Rate at which data is polled
≥0.001s

FS-8705-17 Mircom Pro2000 Serial Driver Page 17 of 32
© 2021 CHIPKIN AUTOMATION SYSTEMS
Map Descriptor Example 1
Only one Map Descriptor is required to process all messages from the panel. The MD is mandatory. This task is used to drive the automatic reading of change
flags and device status data.
Read section 4.5 How Point Data is Stored
Map_Descriptors
Map_Descriptor_Name ,Scan_Interval ,Data_Array_Name ,Data_Array_Offset ,Node_Name ,Function ,Address ,Length
Read_Inputs ,0.0s ,DA_CONTROL ,0 ,Panel01 ,Rdbc ,1 ,1
Set this to zero to have the
gateway process this task
as often as possible.
No data get stored here. It
must be specified because all
Map Descriptors require a
Data Array to be specified.
Essentially a dummy
No data get stored here. It
must be specified because all
Map Descriptors require a
Data Array to be specified.
Essentially a dummy

FS-8705-17 Mircom Pro2000 Serial Driver Page 18 of 32
© 2021 CHIPKIN AUTOMATION SYSTEMS
4.5 How Point Data is Stored
Data is always stored in two Data Arrays. The names of the Data Arrays is fixed. Please follow our recommendation of
data type.
Data_Arrays
Data_Array_Name ,Data_Format ,Data_Array_Length
PRO2k_DATA ,Packed_Bit ,16000
PRO2k_FLAGS ,Packed_Bit ,1600
Each time change flags are read, they are stored in the Data Array named PRO2k_FLAGS.
Each time a block of device status data is read, it is stored in the Data Array named PRO2k_DATA. One word (16 bits) are
used for each device.
Device data starts at offset 21 in the Data Array.
There is no obvious relationship between the position and the device number. Ie. You cannot tell which device stores its
status data at offset 21, 22, 23….. The allocation of storage positions is done by the Pro2000 panel configuration
software and documented in the Pro2000 Modbus File. Only when you have that file in your possession can you allocate
meaning to the data.
4.6 How Most Recent Event Data is Stored
Input Device
BIT #
STATE=0
STATE=1
0
No Trouble
Trouble
1
No Alarm
Alarm
2
Service Mode OFF
Service Mode ON
3
Isolate Mode OFF
Isolate Mode ON
4
NA
NA
5
Not Used
Not Used
6
Not Used
Not Used
7
Reserved bit 3
Reserved bit 3
8
Reserved bit 2
Reserved bit 2
9
Reserved bit 1
Reserved bit 1
10
UA bit 1
UA bit 1
11
Device not present in
database
Device present in
database

FS-8705-17 Mircom Pro2000 Serial Driver Page 19 of 32
© 2021 CHIPKIN AUTOMATION SYSTEMS
12
Alarm not cleared
Alarm cleared
13
Trouble not cleared
Trouble cleared
14
Alarm not acknowledged
Alarm acknowledged
15
Trouble not acknowledged
Trouble acknowledged
Output Device
BIT #
STATE=0
STATE=1
0
No Trouble
Trouble
1
Normal
Off Normal(Supervisory)
2
Service Mode OFF
Service Mode ON
3
Isolate Mode OFF
Isolate Mode ON
4
Automatic
Manual
5
Not Used
Not Used
6
Not Used
Not Used
7
Reserved bit 3
Reserved bit 3
8
Reserved bit 2
Reserved bit 2
9
Reserved bit 1
Reserved bit 1
10
UA bit 1
UA bit 1
11
Device not present in
database
Device present in
database
12
NA
NA
13
Trouble not cleared
Trouble cleared
14
NA
NA
15
Trouble not acknowledged
Trouble acknowledged

FS-8705-17 Mircom Pro2000 Serial Driver Page 20 of 32
© 2021 CHIPKIN AUTOMATION SYSTEMS
4.7 Driver Limitations and Event Processing
To obtain a copy of the tool send an email to [e-mail] and ask for the ‘Mircom Pro2000 configuration tool’
(Download from this link: https://www.filesanywhere.com/fs/v.aspx?v=8a696588616173b771a0 )
The tool is used to form the server portion of a FieldServer configuration file. The client side portion of the configuration
file is usually standard. A copy and notes are provided in another section of this manual.
The PRO-2000 Configurator will generate a Text file to cross-reference a device ID to a MODBUS register. Each device
will have a MODBUS register in the MODBUS database. The MODBUS register will be assigned automatically and
sequentially by the PRO-2000 Configurator
At the time of writing the Modbus text file contains the following columns
Column 1 (1st Column) Modbus Holding Register Number.
Column 4 Device ID
Column 5 LCD Message
The tool does not use the contents of any other columns. The tool looks for a line that begins :MODBUS. It processes all
the lines starting on the next line, until it finds a line that begins :Local. It then ends processing. The ‘finds’ are case
sensitive.
(You could construct any CSV file that has this format. This would give you an opportunity to use different labels than
allocated for the DeviceID and LCD Message)
The tool takes the following parameters
PARAM
1
InputFileName
The name of the Modbus Text file produced by the pro2000 configurator. . You
can specify the full path.
2
OutputFileName
The output from this tool is saved in a file. Specify the name of the file here.
You can specify the full path.
3
NameOption
Valid options are 1,2,3