FieldServer Metasys N2 FS-8700-19 Release note

A Sierra Monitor Company
APPLICABILITY & EFFECTIVITY
Effective for all systems manufacture after May 1, 2001
Driver Manual
(Supplement to the Fiel Server Instruction Manual)
FS-8700-19 Metasys N2
Driver Version:
1.02
Document Revision: 22

FS-8700-19_Metasys_N2 Driver Manual Table of Contents
Fiel Server Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver. om
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: support@fieldserver. om
TABLE OF CONTENTS
1. Metasys N2 Description ................................................................................................. 3
2. Driver Scope of Supply.................................................................................................. 4
2.1. Supplied by FieldServer Te hnologies for this driver.................................................. 4
2.2. Provided by the Supplier of 3
rd
Party Equipment ........................................................ 4
2.2.1. Hardware................................................................................................................ 4
2.2.2. Required 3
rd
Party Software.................................................................................... 4
2.2.3. Required 3
rd
Party Configuration............................................................................. 4
3. Har ware Connections .................................................................................................. 5
3.1. Hardware Conne tion Tips / Hints.............................................................................. 5
4. Configuring the Fiel Server as a Metasys N2 Client ................................................... 6
4.1. Data Arrays/Des riptors............................................................................................. 6
4.2. Client Side Conne tion Des riptions .......................................................................... 7
4.3. Client Side Node Des riptors ..................................................................................... 8
4.4. Client Side Map Des riptors....................................................................................... 8
4.4.1. FieldServer Related Map De criptor Parameter .................................................... 8
4.4.2. Driver Related Map De criptor Parameter ............................................................. 9
4.4.3. Timing Parameter ................................................................................................13
4.4.4. Map De criptor Example 1 – N2Open....................................................................14
4.4.5. Map De criptor Example 2 - VMA..........................................................................14
4.4.6. Map De criptor Example 3 - DX9100.....................................................................15
5. Configuring the Fiel Server as a Metasys N2 Server .................................................16
5.1. Server Side Conne tion Des riptors .........................................................................16
5.2. Server Side Node Des riptors...................................................................................17
5.3. Server Side Map Des riptors ....................................................................................18
5.3.1. FieldServer Specific Map De criptor Parameter ...................................................18
5.3.2. Driver Specific Map De criptor Parameter ...........................................................18
5.3.3. Map De criptor Example........................................................................................19
Appen ix A. A vance Topics...........................................................................................20
Appendix A.1. Writing to DX9100 Binary Outputs................................................................20
Appendix A.2. Managing Analog Inputs and Outputs for DX9100. ......................................21
Appen ix B. Troubleshooting tips.....................................................................................22
Appendix B.1. Conne tion Tips & Hints...............................................................................22
Appendix B.2. Offline Behavior ...........................................................................................22
Appendix B.3. Tip on Overrides ..........................................................................................22
Appen ix C. Setting up FS-B20 for RS-485.......................................................................23
Appendix C.1. Jumper Settings:..........................................................................................23
Appendix C.2. Hardware onne tions .................................................................................25
Appendix C.3. Configuration Settings..................................................................................25
Appen ix D. Memory Maps ................................................................................................26
Appendix D.1. Metasys DX9100 Memory Map....................................................................26
Appendix D.2. Metasys DC9100 Memory Map....................................................................33
Appendix D.3. Metasys TC9100 Memory Map ....................................................................40
Appen ix E. Error Messages .............................................................................................50

FS-8700-19_Metasys_N2 Driver Manual Page 3 of 51
Fiel Server Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver. om
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: support@fieldserver. om
1. Metasys N2 Description
The Metasys N2 network supports ommuni ations with a diverse range of devi es. Many N2
ompatible devi es use their own version of the proto ol and are must be taken to ensure that
the devi e of interest is overed by the FieldServer implementation.
At present the FieldServer N2 driver will support ommuni ations with the following devi es or
devi e lasses when a ting as a Client:
1. N2Open- ompliant devi es. N2Open is a published N2- ompatible proto ol enabling 3
rd
party devi e vendors to integrate with N2.
2. VMA 1400 series (with restri tions, as des ribed in this do ument)
3. DX9100 and XT9100
When a ting as a Server, the FieldServer N2 driver an emulate an N2Open devi e only.

FS-8700-19_Metasys_N2 Driver Manual Page 4 of 51
Fiel Server Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver. om
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: support@fieldserver. om
2. Driver Scope of Supply
2.1. Supplie by Fiel Server Technologies for this river
Fiel Server Technologies
PART # Description
FS-8915-10 UTP able (7 foot) for Ethernet onne tion
FS-8915-10 UTP able (7 foot) for RS-232 use
FS-8917-02 RJ45 to DB9F onne tor adapter
FS-8917-01 RJ45 to DB25M onne tion adapter
SPA59132 RS-485 onne tion adapter
FS-8700-19 Driver Manual.
2.2. Provi e by the Supplier of 3
r
Party Equipment
2.2.1. Har ware
PART # DESCRIPTION
Metasys NCU or other devi e
2.2.2. Require 3
r
Party Software
Depending on appli ation, JCI software may be ne essary
2.2.3. Require 3
r
Party Configuration
Depending on appli ation, third party devi es may need onfiguration

FS-8700-19_Metasys_N2 Driver Manual Page 5 of 51
Fiel Server Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver. om
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: support@fieldserver. om
3. Har ware Connections
Fiel Server as a Server
NCM, N30 or
other N2 lient
3rd Party
System
FieldServer
N2 bus
N2 devi es
Fiel Server as a Client
FieldServer N2 bus
N2 devi es
3rd Party
System
DATE: 05/31/
06
BY: MC
(408)-262-2299
BASE NAME:
FILE NAME: FS-8700-19
MetasysN2
CONNECTION DIAGRAM
3.1. Har ware Connection Tips / Hints
When using the FS-X40 ensure that the FieldServer is onne ted to the network using one
or both of the RS-485 ports marked R1 and R2. If more ports are required, P1-P8 may be
used in onjun tion with an RS-232-to-RS-485 onverter.
When using the FS-X20, ensure that the serial port is onfigured as an RS-485 port. Refer
to Appendix B.3 for more information.
Only one N2 Client may be onne ted to a N2 network. If the FieldServer is to a t as a
Client, ensure that no other Clients are onne ted to the same N2 network.
Note: Inter eptor mode is no longer supported for this driver.

FS-8700-19_Metasys_N2 Driver Manual Page 6 of 51
Fiel Server Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver. om
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: support@fieldserver. om
4. Configuring the Fiel Server as a Metasys N2 Client
For a detailed dis ussion on FieldServer onfiguration, please refer to the FieldServer
Configuration manual. The information that follows des ribes how to expand upon the fa tory
defaults provided in the onfiguration files in luded with the FieldServer (See “. sv” sample files
provided with the FieldServer).
This se tion do uments and des ribes the parameters ne essary for onfiguring the FieldServer
to ommuni ate with a Metasys N2 Server.
4.1. Data Arrays/Descriptors
The onfiguration file defines the FieldServer interfa es, and the data routing required. In
order to enable the FieldServer for Metasys N2 ommuni ations, the driver independent
FieldServer buffers need to be de lared in the “Data Arrays” se tion, the destination devi e
addresses need to be de lared in the “Client Side Nodes” se tion, and the data required
from the Servers needs to be mapped in the “Client Side Map Des riptors” se tion.
Note that in the tables, * indi ates an optional parameter, with the bol legal value being the
default value. Where only one legal value is given, no other values for that parameter are
allowed.
Section Title
Data_Arrays
Column Title Function Legal Values
Data_Array_Name Provide name for Data Array Up to 15 alphanumeri
hara ters
Data_Array_Format Provide data format. Ea h Data Array
an only take on one format.
Float, Bit, UInt16, SInt16,
Pa ked_Bit, Byte,
Pa ked_Byte,
Swapped_Byte
Data_Array_Length
Number of Data Obje ts. Must be
larger than the data storage area
required by the Map Des riptors for
the data being pla ed in this array.
1-10,000
Example
// Data Arrays
Data_Arrays
Data_Array_Name, Data_Format, Data_Array_Length
DA_AI_01, UInt16, 200
DA_AO_01, UInt16, 200
DA_DI_01, Bit, 200
DA_DO_01, Bit, 200

FS-8700-19_Metasys_N2 Driver Manual Page 7 of 51
Fiel Server Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver. om
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: support@fieldserver. om
4.2. Client Si e Connection Descriptions
Section Title
Conne tions
Column Title Function Legal Values
Port Spe ify whi h port the devi e is
onne ted to the FieldServer P1-P8, R1-R2
1
Proto ol Spe ify proto ol used Metasys_N2
Baud* Spe ify baud rate 9600
Parity* Spe ify parity None
Data_Bits* Spe ify data bits 8
Stop_Bits* Spe ify stop bits 1
Handshaking* Spe ify hardware handshaking None
Poll _Delay* Time between internal polls 0
Line_Drive_On* Duration of RTS assert before
start of transmission 0.001s
Line_Drive_Off* Duration of RTS assert after
end of transmission 0.000s
Example
// Client Side Conne tions
Conne tions
Port, Proto ol
R1, Metasys_N2
1
Not all ports shown are ne essarily supported by the hardware. Consult the appropriate Instru tion
manual for details of the ports available on spe ifi hardware.

FS-8700-19_Metasys_N2 Driver Manual Page 8 of 51
Fiel Server Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver. om
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: support@fieldserver. om
4.3. Client Si e No e Descriptors
Section
Title
Nodes
Column
Title Function Legal Values
Node_Name Provide name for node
Up to 32
alphanumeri
hara ters
Node_ID Station address of physi al Server node 1-255
Proto ol Spe ify proto ol used Metasys_N2
Conne tion Spe ify whi h port the devi e is onne ted to the
FieldServer P1-P8, R1-R2
1
Node_Type
Identify type of devi e
If this parameter is omitted the driver treats the
onfiguration as a N2Open onfiguration and marks
the Node_Type as N2OpenClient when using Ruinet
to he k the Node parameters.
If the Node_Type is spe ified as N2Open then the
driver still a ts as N2 Open onfiguration but some
lega y port expander fun tionality used in some
lega y advan ed onfiguration is enabled.
N2OpenClient,
DX9100, VMA,
N2Open
Example
// Client Side Nodes
Nodes
Node_Name, Node_ID, Proto ol, Conne tion, Node_Type
PLC 1, 1, Metasys_N2, P8, VMA
4.4. Client Si e Map Descriptors
4.4.1. Fiel Server Relate Map Descriptor Parameters
Column Title Function Legal Values
Map_Des riptor_Name Name of this Map
Des riptor
Up to 32 alphanumeri
hara ters
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” se tion
above
Data_Array_Offset Starting lo ation in Data
Array
0 to maximum spe ified in
“Data Array” se tion above
Fun tion Fun tion of Client Map
Des riptor RDBC, WRBC, WRBX

FS-8700-19_Metasys_N2 Driver Manual Page 9 of 51
Fiel Server Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver. om
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: support@fieldserver. om
4.4.2. Driver Relate Map Descriptor Parameters
4.4.2.1. N2Open Map Descriptor Parameters
Column Title Function Legal Values
Node_Name Name of Node to fet h data from
One of the node names
spe ified in “Client Node
Des riptor” above
Data_Type Data type
If the vendor devi e lists a
point as BD then use
Data_Type=Byte.
If the vendor devi e lists a
point as ADI then use
Data_Type=Integer.
If the vendor devi e lists a
point as ADF then use
Data_Type=Float_Reg.
AI, AO, DI, DO,
Float_Reg, Integer, Byte
Length Length of Map Des riptor 1
Address Starting address of read blo k 1-256
MN2_Fun tion*
Used to spe ify an N2-spe ifi
fun tion, e.g. COS. See
des ription below.
COS, Override, Release
MN2_Attribute*
Used to spe ify the attribute if an
attribute other than Current Value
is to be a essed. See attribute
table below
See
N2Open Attribute Table

FS-8700-19_Metasys_N2 Driver Manual Page 10 of 51
Fiel Server Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver. om
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: support@fieldserver. om
N2Open Attribute Table
Data Type Attribute No. Attribute
1 Obje t Configuration
2 Obje t Status
3 Analog Input Value
4 Low Alarm Limit
5 High Alarm Limit
6 Low Warn Limit
7 High Warn Limit
Analog Input
8 Differential
1 Obje t Configuration
Binary Input 2 Obje t Status
1 Obje t Configuration
2 Obje t Status
Analog Output
3 Current Value
1 Obje t Configuration
2 Obje t Status
3 Minimum On-Time
4 Minimum Off-Time
Binary Output
5 Maximum Cy les/Hour
1 Obje t Status
Internal Float 2 Current Value
1 Obje t Status
Internal Integer 2 Current Value
1 Obje t Status
Internal Byte 2 Current Value
Using Change of State (COS) – N2Open
If a large number of points are to be monitored, optimal effi ien y is a hieved by
using the COS me hanism instead of reading ea h individual point dire tly. A
N2Open devi e responds to a COS poll with a hange re ord if a hange has taken
pla e. On startup the devi e will report the state of all its points when it re eives a
COS poll.
Two kinds of Map Des riptors are required for every node that is to be monitored
using COS:
A COS polling Map Des riptor with Function set to COS_Poll.
A COS_Rea (i.e. Function set to COS_Rea ) Map Des riptor for every point
on that node that is to be monitored. Any COS re ords re eived will be stored to
the mat hing Map Des riptor data lo ation.
Note that the COS_Read Map Des riptor has an optional s an_interval. If a value is
set the Map Des riptor will poll at that rate in addition to re eiving COS data. This
an be used if the values are to be refreshed ontinually even if they don’t hange. If
the s an_interval is not onfigured (through omitting the olumn, or by setting the
value to ‘-‘) the COS_Read Map Des riptor will not ause a tive polls on e the value
has been initialized. See 4.4.4 for example.
Important Note on COS Operation in N2Open
Please be aware that N2Open devi es will only report value hanges under the
following onditions:

FS-8700-19_Metasys_N2 Driver Manual Page 11 of 51
Fiel Server Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver. om
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: support@fieldserver. om
Point Type Con itions that will trigger a COS report
AI
point status hange (e.g. override)
hange in alarm or warning status
NB: no value changes within the normal ban are reporte by COS!
AO point status hange (e.g. override)
NB: no value changes within the normal ban are reporte by COS!
BI, BO point status hange (e.g. override); in ludes urrent value (On/Off)
ADI, ADF, BD none; COS annot be used with internal data types.
Using Overri e an Release – N2Open
It is not normally ne essary to use the Override ommand expli itly as the
FieldServer automati ally uses this ommand when the Current Value attribute of a
point is written. For any other attribute it uses the Write ommand. It will sometimes
be ne essary to send a Release ommand to an overridden point, however. To do
this, a Map Des riptor must be onfigured with Function set to wrbx and
MN2_Function set to Release. Then, when any value is stored to the Map
Des riptor data lo ation, the Release ommand will be sent to the N2Open point
spe ified by the Map Des riptor.
4.4.2.2. VMA Map Descriptor Parameters
Column Title Function Legal Values
Node_Name Name of Node to fet h
data from
One of the node names
spe ified in “Client Node
Des riptor” above
Data_Type Data type
AI, AO, DI, DO, Driver
(used for ADF, ADI and
BD)
Length Length of Map Des riptor 1
Address Starting address of read
blo k 1-256
MN2_Type
Data type spe ifier to be
set when Data_Type has
been set to Driver
5-7
ADI, ADF an BD types: using the “Driver” Data_Type an MN2_Type fiel s
The VMA proto ol uses a byte value to spe ify the data types. The standard types
AI, AO, DI and DO orrespond to a byte value of 1 through 4 respe tively. The types
ADF, ADI and BD are believed to orrespond to a byte value of 5 through 7
respe tively. If the user wishes to use any other type value based on knowledge of a
parti ular VMA onfiguration, then that value may also be spe ified here. Refer to
Se tion 4.4.5 for a spe ifi example.

FS-8700-19_Metasys_N2 Driver Manual Page 12 of 51
Fiel Server Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver. om
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: support@fieldserver. om
Driver Data_Type
MN2_Type values
Point Type Known Value
2
Suggeste Value
3
AI 1
AO 2
BI 3
BO 4
ADF 5
ADI 6
BD 7
If a large number of points are to be monitored, optimal effi ien y is a hieved by
using the COS me hanism instead of reading ea h individual point dire tly. An
N2Open devi e responds to a COS poll with a hange re ord if a hange has taken
pla e. On startup the devi e will report the state of all its points when it re eives a
COS poll.
Three kinds of Map Des riptors are required for every node that is to be monitored
using COS:
• A COS initialization Map Des riptor with Function set to ARS and
MN2_Function set to COS_Enable. This Map Des riptor enables COS polling
of those points on the VMA for whi h Passive Map Des riptors exist.
• A COS polling Map Des riptor with Function set to r bc and MN2_Function set
to COS.
• A Passive (i.e. Function set to Passive) Map Des riptor for every point on that
node that is to be monitored. Any COS re ords re eived will be stored to the
mat hing Map Des riptor data lo ation.
See example in Se tion 4.4.5
Using Overri e an Release - VMA
It is normally not ne essary to use the Override ommand expli itly as the
FieldServer automati ally uses this ommand when the Current Value attribute of a
point is written. For any other attribute it uses the Write ommand. It will sometimes
be ne essary to send a Release ommand to an overridden point, however. To do
this, a Map Des riptor must be onfigured with Function set to wrbx and
MN2_Function set to Release. Then, when any value is stored to the Map
Des riptor data lo ation, the Release ommand will be sent to the VMA point
spe ified by the Map Des riptor.
Note: The VMA Release fun tion only works for analog and binary inputs (AI and
BI). Outputs may be restored to their original value using an expli it write ommand.
2
For information only. Do not use Driver type for these, but spe ify AI, AO, BI or BO dire tly in the Data_Type field.
3
These values are believed to be orre t for the orresponding point types, but no guarantee an be given at this time.

FS-8700-19_Metasys_N2 Driver Manual Page 13 of 51
Fiel Server Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver. om
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: support@fieldserver. om
4.4.2.3. DX9100 Map Descriptor Parameters
Column Title Function Legal Values
Node_Name Name of Node to fet h
data from
One of the node names
spe ified in “Client Node
Des riptor” above
Length Length of Map Des riptor 1
Address Starting address of read
blo k 0 - 2397
For DX9100 addresses please refer to the DX9100 user do umentation. This lists
the name, fun tion (read/write) and data format of all available points. Alternatively,
obtain assistan e from FieldServer Te hni al Support.
4.4.3. Timing Parameters
Column Title Function Legal Values
S an_Interval Rate at whi h data is polled ≥0.001s

FS-8700-19_Metasys_N2 Driver Manual Page 14 of 51
Fiel Server Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver. om
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: support@fieldserver. om
4.4.4. Map Descriptor Example 1 – N2Open
// Client Side Map Des riptors Map_Des riptors Map_Des riptor_Name, DA_Name, DA_Offset, Fun tion, MN2_Fun tion
, Node_name Address Data_Type S an_Interval
AI_READ, DA_AI3, 0, RDBC, -, Node_A, 1, Ana_Input 5s
COS_POLLER, DA_COS, 0, COS_Poller, -, Node_A, -, -, 30s
AI_BY_COS, DA_AI3, 1, COS_Read, -, Node_A, 1, Ana_Input, -
BI_BY_COS, DA_BI, 3, COS_Read, -, Node_A, 2, Dig_Input, 10
AI_1_Release, DA_Release, 0, WRBX, Release, Node_A, 1, Ana_Input, -
Note:
To get hange of state (COS) reports from an analog port, the warning/alarm levels need to be onfigured. If the alarm/warning values are not known, then it would be better to onfigure an RDBC Map Des riptor whi h reads the analog input dire tly. Limits will then not be required.
4.4.5. Map Descriptor Example 2 - VMA
// Client Side Map Des riptors Map_Des riptors Map_Des riptor_Name, DA_Name, DA_Offset, Fun tion, MN2_Fun tion, Node_name, Address, Data_Type, MN2_Type, S an_Interval
AI_READ, DA_AI3, 0, RDBC, -, Node_VMA, 1, Ana_Input -, 5s AO_WRITE, DA_AO, 0, WRBX, -, Node_VMA, 3, Ana_Output, -, 30s AO_Release, DA_AO, 0, WRBX, Release, Node_VMA, 3, Ana_Output, -, -
Spe ial_type, DA_DRV, 10, RDBC, -, Node_VMA, 23, Driver, 5, 10s
Normal read Map Des riptor. Note RDBC fun tion, Data_Type and Address spe ifi ation.
COS_Poller Map Des riptor. This only spe ifies the Fun tion, Node and S an_Interval.
COS_Read Map Des riptor sets point type the same as normal read Map Des riptor. Optional s an_interval.
Release fun tion used in onjun tion with wrbx. If the Data Array value spe ified in this Map Des riptor is hanged, then a Release ommand is sent to the spe ified point.
Override release fun tion onfigured as wrbx. Driver type 5 (ADF) onfigured here.

FS-8700-19_Metasys_N2 Driver Manual Page 15 of 51
Fiel Server Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver. om
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: support@fieldserver. om
4.4.6. Map Descriptor Example 3 - DX9100
// Client side Map Des riptors Map_Des riptors Map_Des riptor_Name, DA_Name, DA_Offset, Fun tion, Node_name, Address, S an_Interval D191_ZN1-T, DA_AI3, 0, RDBC, Node_DX, 1223, 5s D191_ZN1-S, DA_AO3, 0, WRBX, Node_DX, 1225, -
The address alone is suffi ient to spe ify DX9100 point. The Data Type is determined by the devi e.

FS-8700-19_Metasys_N2 Driver Manual Page 16 of 51
Fiel Server Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver. om
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: support@fieldserver. om
5. Configuring the Fiel Server as a Metasys N2 Server
For a detailed dis ussion on FieldServer onfiguration, please refer to the FieldServer
Configuration Manual. The information that follows des ribes how to expand upon the fa tory
defaults provided in the onfiguration files in luded with the FieldServer (See “. sv” files on the
driver diskette).
This se tion do uments and des ribes the parameters ne essary for onfiguring the FieldServer
to ommuni ate with a Metasys N2Open Client. Note that only the N2Open variation of the
N2 protocol may be use when configuring the Fiel Server as a Server.
The onfiguration file tells the FieldServer about its interfa es, and the routing of data required.
In order to enable the FieldServer for Metasys N2 ommuni ations, the driver independent
FieldServer buffers need to be de lared in the “Data Arrays” se tion, the FieldServer virtual
node(s) needs to be de lared in the “Server Side Nodes” se tion, and the data to be provided to
the Clients needs to be mapped in the “Server Side Map Des riptors” se tion. Details on how to
do this an be found below.
Note that in the tables, * indi ates an optional parameter, with the bold legal value being the
default.
5.1. Server Si e Connection Descriptors
Section Title
Conne tions
Column Title Function Legal Values
Port Spe ify whi h port the devi e is
onne ted to the FieldServer P1-P8, R1-R2
4
Proto ol Spe ify proto ol used Metasys_N2
Baud* Spe ify baud rate 9600
Parity* Spe ify parity None
Data_Bits* Spe ify data bits 8
Stop_Bits* Spe ify stop bits 1
Handshaking* Spe ify hardware handshaking None
Poll _Delay* Time between internal polls 0
Line_Drive_On* Duration of RTS assert before
start of transmission 0.001s
Line_Drive_Off* Duration of RTS assert after
end of transmission 0.000s
Example
// Server Side Conne tions
Conne tions
Port, Proto ol
P8, Metasys_N2
4
Not all ports shown are ne essarily supported by the hardware. Consult the appropriate Instru tion
manual for details of the ports available on spe ifi hardware.

FS-8700-19_Metasys_N2 Driver Manual Page 17 of 51
Fiel Server Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver. om
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: support@fieldserver. om
5.2. Server Si e No e Descriptors
Section Title
Nodes
Column Title Function Legal Values
Node_Name Provide name for node
Up to 32
alphanumeri
hara ters
Node_ID MetasysN2 station address of physi al
Server node 1-255
Proto ol Spe ify proto ol used Metasys_N2
Server_Hold_Timeout*
Spe ifies time FieldServer will reserve
Server side onne tion while waiting for the
Client side to update data in Data_Array
< 0.175s
5
Node_Type*
Identify type of devi e
This parameter need not be spe ified. The
Server side of the driver an only operate
as an N2 Server and the option for setting it
to N2Open is purely for ba kward
ompatibility.
N2OpenServer,
N2Open
Example
// Server Side Nodes
Nodes
Node_Name, Node_ID, Proto ol
PLC 1, 1, Metasys_N2
5
Can be set to >0.175s if the Client has bee set to timeout after >200ms. Refer to Appendix E for more
information.

FS-8700-19_Metasys_N2 Driver Manual Page 18 of 51
Fiel Server Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver. om
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: support@fieldserver. om
5.3. Server Si e Map Descriptors
5.3.1. Fiel Server Specific Map Descriptor Parameters
Column Title Function Legal Values
Map_Des riptor_Name Name of this Map
Des riptor
Up to 32 alphanumeri
hara ters
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”
se tion above
Data_Array_Offset Starting lo ation in Data
Array
0 to maximum spe ified in
“Data Array” se tion above
Fun tion Fun tion of Server Map
Des riptor Server
5.3.2. Driver Specific Map Descriptor Parameters
Column
Title Function Legal Values
Node_Name Name of Node to
fet h data from
One of the node names spe ified in “Client
Node Des riptor” above
Data_Type Data type
If the vendor devi e lists a point as BD then
use Data_Type=Byte.
If the vendor devi e lists a point as ADI then
use Data_Type=Integer.
If the vendor devi e lists a point as ADF then
use Data_Type=Float_Reg.
AI, AO, DI, DO, Float_Reg, Integer, Byte
Length Length of Map
Des riptor 1 - 256
Address Starting address of
read blo k 1 - 256

FS-8700-19_Metasys_N2 Driver Manual Page 19 of 51
Fiel Server Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver. om
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: support@fieldserver. om
5.3.3. Map Descriptor Example.
// Server Side Map Des riptors Map_Des riptors Map_Des riptor_Name, Data_Array_Name, Data_Array_Offset, Data_Type, Fun tion, Node_name, Address, Length
A1, DA_AI3, 10, Ana_Input, Server, Node_A, 1, 256
The Server fun tion tells the FieldServer that this Map Des riptor makes data available to a Client sending polls to the FieldServer.
Note that a single Server Map Des riptor of length 256 an represent all possible points of one type (e.g. AI).
The Data_Array_Offset sets the start of the data range overed by the Server Map Des riptor. The number of points in luded is determined by the Length field.

FS-8700-19_Metasys_N2 Driver Manual Page 20 of 51
Fiel Server Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver. om
Tel: [phone] Fax: [phone] Toll_Free: 888-509-1970 email: support@fieldserver. om
Appen ix A. A vance Topics
Appendix A.1. Writing to DX9100 Binary Outputs
When writing to DX9100 Binary Outputs, it is important to understand that ea h binary output has three bits asso iated with it as des ribed in the table below: Bit Description A ress
6
Output status bit
The status bit will indi ate the a tual status of the output in the field. This bit annot be modified by the FieldServer as it is read only, and is meant for a tual status display. Address 5
Output ontrol bit
The ontrol bit will allow the FieldServer to write a ommand to the DX9100 for the asso iated output. This ommand will only exe ute if the override is enabled by the override bit.
Low byte of
Address 1
Override bit The override bit must be set to enable an output to be written to by the FieldServer. If this is
not set, then the ontrol bit will be ignored.
High byte of
Address 1
Example
The example below better illustrates the mapping that is typi ally needed to deal with DX9100 Binary Outputs. Note that sin e all 6 outputs are pa ked into word format when transmitted, a Pa ked_Bit Array is typi ally required to a ess the bits individually. In this Example, the status for BO3-BO8 an be found in offsets 0-5 of DA_PO1_02, the ontrol bits an be found in offsets 0-5 of DA_PO1_01, and the override bits an be found in offsets 8-13 of DA_PO1_01.
Data_Arrays Data_Array_Name, Data_Format, Data_Array_Length DA_PO1_01 , Pa ked_Bit , 100 DA_PO1_02 , Pa ked_Bit , 100 Map_Des riptors Map_Des riptor_Name, Data_Array_Name, Data_Array_Offset, Fun tion, Node_Name, Address, S an_Interval CMD_DO1_05 , DA_PO1_01 , 0 , Rdb , Dev_30 , 0001 , 1.0s // DO3 -
DO8 Set and Enable
CMD_DO1_06 , DA_PO1_02 , 0 , Rdb , Dev_30 , 0005 , 1.0s // DO3 - DO8 Status
6
Binary Outputs start at address 3, so the first bit of ea h of these addresses will represent B03