The Metasys N2 network supports communications with a diverse range of devices. Many N2
compatible devices use their own version of the protocol and care must be taken to ensure that
the device of interest is covered by the FieldServer implementation.
At present the FieldServer N2 driver will support communications with the following devices or
device classes when acting as a Client:
1. N2Open-compliant devices. N2Open is a published N2-compatible protocol enabling 3rd
party device vendors to integrate with N2.
2. VMA 1400 series (with restrictions, as described in this document)
3. DX9100 and XT9100
When acting as a Server, the FieldServer N2 driver can emulate an N2Open device only.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
When using the FS-X40 ensure that the FieldServer is connected 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 conjunction with an RS-232-to-RS-485 converter.
When using the FS-X20, ensure that the serial port is configured as an RS-485 port. Refer
to Appendix B.3 for more information.
Only one N2 Client may be connected to a N2 network. If the FieldServer is to act as a
Client, ensure that no other Clients are connected to the same N2 network.
Note: Interceptor mode is no longer supported for this driver.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
4. Configuring the FieldServer as a Metasys N2 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 FieldServer).
This section documents and describes the parameters necessary for configuring the FieldServer
to communicate with a Metasys N2 Server.
4.1. Data Arrays/Descriptors
The configuration file defines the FieldServer interfaces, and the data routing required. In
order to enable the FieldServer for Metasys N2 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.
Note that in the tables, * indicates an optional parameter, with the bold 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
Data_Array_Format
Provide data format. Each Data Array
can only take on one format.
Number of Data Objects. Must be
Data_Array_Length
larger than the data storage area
required by the Map Descriptors for
the data being placed in this array.
Node_ID Station address of physical Server node 1-255
Protocol Specify protocol used Metasys_N2
Connection
Specify which port the device is connected to the
FieldServer
Identify type of device
If this parameter is omitted the driver treats the
configuration as a N2Open configuration and marks
the Node_Type as N2OpenClient when using Ruinet
Node_Type
to check the Node parameters.
If the Node_Type is specified as N2Open then the
driver still acts as N2 Open configuration but some
legacy port expander functionality used in some
legacy advanced configuration is enabled.
Low Alarm Limit
High Alarm Limit
Low Warn Limit
High Warn Limit
Differential
Object Configuration
Object Status
Object Configuration
Object Status
Current Value
Object Configuration
Object Status
Minimum On-Time
Minimum Off-Time
Maximum Cycles/Hour
Object Status
Current Value
Object Status
Current Value
Object Status
Current Value
Using Change of State (COS) – N2Open
If a large number of points are to be monitored, optimal efficiency is achieved by
using the COS mechanism instead of reading each individual point directly. A
N2Open device responds to a COS poll with a change record if a change has taken
place. On startup the device will report the state of all its points when it receives a
COS poll.
Two kinds of Map Descriptors are required for every node that is to be monitored
using COS:
A COS polling Map Descriptor with Function set to COS_Poll.
A COS_Read (i.e. Function set to COS_Read) Map Descriptor for every point
on that node that is to be monitored. Any COS records received will be stored to
the matching Map Descriptor data location.
Note that the COS_Read Map Descriptor has an optional scan_interval. If a value is
set the Map Descriptor will poll at that rate in addition to receiving COS data. This
can be used if the values are to be refreshed continually even if they don’t change. If
the scan_interval is not configured (through omitting the column, or by setting the
value to ‘-‘) the COS_Read Map Descriptor will not cause active polls once the value
has been initialized. See 4.4.4 for example.
Important Note on COS Operation in N2Open
Please be aware that N2Open devices will only report value changes under the
following conditions:
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Point Type Conditions that will trigger a COS report
point status change (e.g. override)
AI
AO
BI, BO
ADI, ADF, BD
change in alarm or warning status
NB: no value changes within the normal band are reported by COS!
point status change (e.g. override)
NB: no value changes within the normal band are reported by COS!
point status change (e.g. override); includes current value (On/Off)
none; COS cannot be used with internal data types.
Using Override and Release – N2Open
It is not normally necessary to use the Override command explicitly as the
FieldServer automatically uses this command when the Current Value attribute of a
point is written. For any other attribute it uses the Write command. It will sometimes
be necessary to send a Release command to an overridden point, however. To do
this, a Map Descriptor must be configured with Function set to wrbx and
MN2_Function set to Release. Then, when any value is stored to the Map
Descriptor data location, the Release command will be sent to the N2Open point
specified by the Map Descriptor.
4.4.2.2. VMA Map Descriptor Parameters
Column Title Function Legal Values
One of the node names
specified in “Client Node
Descriptor” above
Node_Name
Name of Node to fetch
data from
AI, AO, DI, DO, Driver
Data_Type Data type
(used for ADF, ADI and
BD)
Length Length of Map Descriptor 1
Address
Starting address of read
block
1-256
Data type specifier to be
MN2_Type
set when Data_Type has
5-7
been set to Driver
ADI, ADF and BD types: using the “Driver” Data_Type and MN2_Type fields
The VMA protocol uses a byte value to specify the data types. The standard types
AI, AO, DI and DO correspond to a byte value of 1 through 4 respectively. The types
ADF, ADI and BD are believed to correspond to a byte value of 5 through 7
respectively. If the user wishes to use any other type value based on knowledge of a
particular VMA configuration, then that value may also be specified here. Refer to
Section 4.4.5 for a specific example.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Driver Data_Type
MN2_Type values
Point Type Known Value
2
Suggested 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 efficiency is achieved by
using the COS mechanism instead of reading each individual point directly. An
N2Open device responds to a COS poll with a change record if a change has taken
place. On startup the device will report the state of all its points when it receives a
COS poll.
Three kinds of Map Descriptors are required for every node that is to be monitored
using COS:
• A COS initialization Map Descriptor with Function set to ARS and
MN2_Function set to COS_Enable. This Map Descriptor enables COS polling
of those points on the VMA for which Passive Map Descriptors exist.
• A COS polling Map Descriptor with Function set to rdbc and MN2_Function set
to COS.
• A Passive (i.e. Function set to Passive) Map Descriptor for every point on that
node that is to be monitored. Any COS records received will be stored to the
matching Map Descriptor data location.
See example in Section 4.4.5
Using Override and Release - VMA
It is normally not necessary to use the Override command explicitly as the
FieldServer automatically uses this command when the Current Value attribute of a
point is written. For any other attribute it uses the Write command. It will sometimes
be necessary to send a Release command to an overridden point, however. To do
this, a Map Descriptor must be configured with Function set to wrbx and
MN2_Function set to Release. Then, when any value is stored to the Map
Descriptor data location, the Release command will be sent to the VMA point
specified by the Map Descriptor.
Note: The VMA Release function only works for analog and binary inputs (AI and
BI). Outputs may be restored to their original value using an explicit write command.
2
For information only. Do not use Driver type for these, but specify AI, AO, BI or BO directly in the Data_Type field.
3
These values are believed to be correct for the corresponding point types, but no guarantee can be given at this time.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
One of the node names
specified in “Client Node
Descriptor” above
Node_Name
Name of Node to fetch
data from
Length Length of Map Descriptor 1
Address
Starting address of read
block
0 - 2397
For DX9100 addresses please refer to the DX9100 user documentation. This lists
the name, function (read/write) and data format of all available points. Alternatively,
obtain assistance from FieldServer Technical Support.
4.4.3. Timing Parameters
Column Title Function Legal Values
Scan_Interval Rate at which data is polled ≥0.001s
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
5. Configuring the FieldServer as a Metasys N2 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 on the
driver diskette).
This section documents and describes the parameters necessary for configuring the FieldServer
to communicate with a Metasys N2Open Client. Note that only the N2Open variation of the N2 protocol may be used when configuring the FieldServer as a Server.
The configuration file tells the FieldServer about its interfaces, and the routing of data required.
In order to enable the FieldServer for Metasys N2 communications, the driver independent
FieldServer buffers need to be declared in the “Data Arrays” section, the FieldServer virtual
node(s) needs to be declared in the “Server Side Nodes” section, and the data to be provided to
the Clients 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.
5.1. Server Side Connection Descriptors
Section Title
Connections
Column Title Function Legal Values
Port
Specify which port the device is
connected to the FieldServer
P1-P8, R1-R24
Protocol Specify protocol used Metasys_N2
Baud* Specify baud rate
Parity* Specify parity
Data_Bits* Specify data bits
Stop_Bits* Specify stop bits
Handshaking* Specify hardware handshaking
Poll _Delay* Time between internal polls
Line_Drive_On*
Line_Drive_Off*
Duration of RTS assert before
start of transmission
Duration of RTS assert after
end of transmission
9600
None
8
1
None
0
0.001s
0.000s
Example
// Server Side Connections
Connections
Port, Protocol
P8, Metasys_N2
4
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
5.3.1. FieldServer Specific Map Descriptor Parameters
Column Title Function Legal Values
Map_Descriptor_Name
Data_Array_Name
Data_Array_Offset
Function
Name of this Map
Descriptor
Name of Data Array where
data is to be stored in the
FieldServer
Starting location in Data
Array
Function of Server Map
Descriptor
Up to 32 alphanumeric
characters
One of the Data Array
names from “Data Array”
section above
0 to maximum specified in
“Data Array” section above
Server
5.3.2. Driver Specific Map Descriptor Parameters
Column
Title
Node_Name
Data_Type Data type
Length
Address
Function Legal Values
Name of Node to
fetch data from
Length of Map
Descriptor
Starting address of
read block
One of the node names specified in “Client
Node Descriptor” above
If the vendor device lists a point as BD then
use Data_Type=Byte.
If the vendor device lists a point as ADI then
use Data_Type=Integer.
If the vendor device lists a point as ADF then
use Data_Type=Float_Reg.
AI, AO, DI, DO, Float_Reg, Integer, Byte
1 - 256
1 - 256
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
When using the FieldServer as an N2 Client, make very sure that it is the only Client /
master on the N2 network. If there is another Client on the network there will be
communication conflicts. These will be reflected on the FieldServer as protocol errors.
Appendix B.2. Offline Behavior
When the Client node on the FieldServer goes offline, the corresponding data objects on the
FieldServer are also marked offline. If a client polls a virtual FieldServer node for this
particular data, therefore, an offline response will be returned by the FieldServer. A request
from an master device for a FieldServer to identify itself would be met by a valid response,
however. This could lead to confusion and status toggling. This can be addressed using
Responsible Map Descriptors and by configuring the virtual FieldServer using the
Offline_Method option. Please refer to the Configuration Manual for further information.
Appendix B.3. Tip on Overrides
It is important that there be only one device (including the slave device itself) updating a
point which is in overridden mode. The reason for this is that the value of the point could be
changed by an update from a non-Metasys Server before the override is released by the
Metasys Master. In this case, the FieldServer would respond to a poll from the Master with
this changed data.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Jumpers jp16, jp17, and jp18 need to be transferred from pins 1-2 to pins 2-3 in order to
enable RS-485. These jumpers can be found just behind the RJ45 ports inside the box
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Relative Item Signal Condition Read/Write Johnson Tag Description
0 Word Write AIT Analog inout type
1 FP Write HR High range input
2 FP Write LR Low range input
3 FP Write HIA High alarm limit
4 FP Write LOA Low alarm limit
5 FP Write FTC Filter constant
6 FP Write ADF Differential on alarm limit (units)
7 FP Read AI Analog input value
8 FP Read AI% Analog input %
9 FP Read ADC Analog input in counts
10 Byte Read AIST Analog input status
Analog Output Modules
Relative Item Signal Condition Read/Write Johnson Tag Description
0 Byte Write AOT Analog output type
1 Word Write AO@ Source of analog output module
2 Word Write AOF@ Output forcing logic connection
3 FP Write HRO Output high range
4 FP Write LRO Output low range
5 FP Write OFL Output % value in forcing mode
6 FP Write OUT Output module output value %
7 Byte Write AOC Analog output control and status
8 FP Write HLO Output high limit
9 FP Write LLO Output low limit
10 Word Write INC@ DDC increase logic connection
11 Word Write DEC@ DDC decrease logic connection
12 Word Write ENL@ Limit function enable logic connection
Digital Output Modules
Relative Item Signal Condition Read/Write Johnson Tag Description
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Relative Item Signal Condition Read/Write Johnson Tag Description
0 Byte Write DOT Digital output options
1 Word Write DO@ Source of digital output module
2 Word Write FB@ Source of feedback signal
3 Word Write DOF@ Output forcing logic connection
4 FP Write HRO Output high range
5 FP Write LRO Output low range
6 FP Write FST PAT output full stroke time/DAT cycle
7 FP Write DB PAT deadband
8 FP Write HLO Output high limit
9 FP Write LLO Output low limit
10 FP Write OFL Output % value in forcing mode
11 FP Write OUT Output module output value %
12 Byte Write DOC Logic output control and status
13 Word Write INC@ DDC increase logic connection
14 Word Write DEC@ DDC decrease logic connection
15 Word Write ENL@ Limit function enable logic connection
Extension Modules
Relative Item Signal Condition Read/Write Johnson Tag Description
0 Word Write XTIOMAP Extension module I/O map
1 Word Write XTIOTYP Extension module I/O type
2 Word Write XTIOMOD Extension module I/O mode
3 Byte Write XTADX Extension module address 0-255
4 Word Write XTI1@ Point connection - I1
5 Word Write XTI2@ Point connection - I2
6 Word Write XTI3@ Point connection - I3
7 Word Write XTI4@ Point connection - I4
8 Word Write XTI5@ Point connection - I5
9 Word Write XTI6@ Point connection - I6
10 Word Write XTI7@ Point connection - I7
11 Word Write XTI8@ Point connection - I8
12 FP Write XTHR01 High output range point 1
13 FP Write XTLR01 Low output range point 1
14 FP Write XTHR02 High output range point 2
15 FP Write XTLR02 Low output range point 2
16 FP Write XTHR03 High output range point 3
17 FP Write XTLR03 Low output range point 3
18 FP Write XTHR04 High output range point 4
19 FP Write XTLR04 Low output range point 4
20 FP Write XTHR05 High output range point 5
21 FP Write XTLR05 Low output range point 5
22 FP Write XTHR06 High output range point 6
23 FP Write XTLR06 Low output range point 6
24 FP Write XTHR07 High output range point 7
25 FP Write XTLR07 Low output range point 7
26 FP Write XTHR08 High output range point 8
27 FP Write XTLR08 Low output range point 8
28 FP Write XTHIA1 High alarm limit point 1
29 FP Write XTLOA1 Low alarm limit point 1
30 FP Write XTHIA2 High alarm limit point 2
31 FP Write XTLOA2 Low alarm limit point 2
32 FP Write XTHIA3 High alarm limit point 3
33 FP Write XTLOA3 Low alarm limit point 3
34 FP Write XTHIA4 High alarm limit point 4
35 FP Write XTLOA4 Low alarm limit point 4
36 FP Write XTHIA5 High alarm limit point 5
37 FP Write XTLOA5 Low alarm limit point 5
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Relative Item Signal Condition Read/Write Johnson Tag Description
38 FP Write XTHIA6 High alarm limit point 6
39 FP Write XTLOA6 Low alarm limit point 6
40 FP Write XTHIA7 High alarm limit point 7
41 FP Write XTLOA7 Low alarm limit point 7
42 FP Write XTHIA8 High alarm limit point 8
43 FP Write XTLOA8 Low alarm limit point 8
44 Word Read XTAIS Extension module alarms
45 FP Read XTAI1 Analog input value 1
46 FP Read XTAI2 Analog input value 2
47 FP Read XTAI3 Analog input value 3
48 FP Read XTAI4 Analog input value 4
49 FP Read XTAI5 Analog input value 5
50 FP Read XTAI6 Analog input value 6
51 FP Read XTAI7 Analog input value 7
52 FP Read XTAI8 Analog input value 8
53 FP Write XTAO1 Analog output value 1
54 FP Write XTAO2 Analog output value 2
55 FP Write XTAO3 Analog output value 3
56 FP Write XTAO4 Analog output value 4
57 FP Write XTAO5 Analog output value 5
58 FP Write XTAO6 Analog output value 6
59 FP Write XTAO7 Analog output value 7
60 FP Write XTAO8 Analog output value 8
61 LONG Write XTDIC1 Digital input 1 pulse count
62 LONG Write XTDIC2 Digital input 2 pulse count
63 LONG Write XTDIC3 Digital input 3 pulse count
64 LONG Write XTDIC4 Digital input 4 pulse count
65 LONG Write XTDIC5 Digital input 5 pulse count
66 LONG Write XTDIC6 Digital input 6 pulse count
67 LONG Write XTDIC7 Digital input 7 pulse count
68 LONG Write XTDIC8 Digital input 8 pulse count
69 Byte Write XTCNT Extension module hold control
70 Byte Write XTDO Logic outputs control and status
71 Byte Read XTDI Logic inputs status
72 Byte Read XTSTC Extension module local status
Time schedule modules
Relative Item Signal Condition Read/Write Johnson Tag Description
0 Word Write TSOPT Time schedule options LSB
1 Word Write TSEX@ External extension logical connection
2 Word Write TSON@ On forcing logical connection
3 Word Write TSOF@ Off forcing logical connection
4 FP Write TSXTM Extension time (min)
5 FP Write TSTIM Time to next event (min)
6 Byte Write TSSTA Time schedule status
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Byte Write RA1@ Reverse action logic control connection
Byte Write EF1@
External forcing logic control
connection
Byte Write TYPE1 Controller type
FP Write LS1 Local setpoint
FP Write PB1 Proportional band
FP Write TI1 Reset action
58 3A FP Write TD1 Rate action
59 3B FP Write HL1 Upper limit of the control output
60 3C FP Write LL1 Lower limit of the control output
61 3D FP Write BS1 Change of setpoint during STAND-BY
62 3E FP Write BO1 Change of setpoint during OFF
63 3F FP Write AD1 Deviation alarm
64
65
66
67
68
69
70
71
72
73
Byte Write PV2@ Process variable connection
Byte Write RS2@ Remote setpoint connection
Byte Write RV2@ Reference variable connection
Byte Write PB2@ Proportional band connection
Byte Write OF2@ OFF mode logic control connection
Byte Write SB2@
STAND-BY mode logic control
connection
Byte Write RA2@ Reverse action logic control connection
Byte Write EF2@
External forcing logic control
connection
Byte Write TYPE2 Controller type
FP Write LS2 Local setpoint
74 4A FP Write PB2 Proportional band
75 4B FP Write TI2 Reset action
76 4C FP Write TD2 Rate action
77 4D FP Write HL2 Upper limit of the control output
78 4E FP Write LL2 Lower limit of the control output
78 4E FP Write LL2 Lower limit of the control output
79 4F FP Write BS2 Change of setpoint during STAND-BY
80
81
82
83
84
85
86
87
88
FP Write BO2 Change of setpoint during OFF
FP Write AD2 Deviation alarm
Byte Write PV3@ Process variable connection
Byte Write RS3@ Remote setpoint connection
Byte Write RV3@ Reference variable connection
Byte Write PB3@ Proportional band connection
Byte Write OF3@ OFF mode logic control connection
Byte Write SB3@
STAND-BY mode logic control
connection
Byte Write RA3@ Reverse action logic control connection
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
connection
126 7E Byte Write TYPE5 Controller type
127 7F FP Write LS5 Local setpoint
128
129
130
131
132
133
134
FP Write PB5 Proportional band
FP Write TI5 Reset action
FP Write TD5 Rate action
FP Write HL5 Upper limit of the control output
FP Write LL5 Lower limit of the control output
FP Write BS5 Change of setpoint during STAND-BY
FP Write BO5 Change of setpoint during OFF
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
138 8A Byte Write RV6@ Reference variable connection
139 8B Byte Write PB6@ Proportional band connection
140 8C Byte Write OF6@ OFF mode logic control connection
141 8D Byte Write SB6@
STAND-BY mode logic control
connection
142 8E Byte Write RA6@ Reverse action logic control connection
143 8F Byte Write EF6@
144
145
146
147
148
149
150
151
152
153
Byte Write TYPE6 Controller type
FP Write LS6 Local setpoint
FP Write PB6 Proportional band
FP Write TI6 Reset action
FP Write TD6 Rate action
FP Write HL6 Upper limit of the control output
FP Write LL6 Lower limit of the control output
FP Write BS6 Change of setpoint during STAND-BY
FP Write BO6 Change of setpoint during OFF
FP Write AD6 Deviation alarm
External forcing logic control
connection
154 9A Byte Write PV7@ Process variable connection
155 9B Byte Write RS7@ Remote setpoint connection
156 9C Byte Write RV7@ Reference variable connection
157 9D Byte Write PB7@ Proportional band connection
158 9E Byte Write OF7@ OFF mode logic control connection
231 E7 Byte Write OMS4 Source of logic output module OUTB
232 E8 Byte Write OMTY1 Output module type
233 E9 FP Write FST1 PAT/DAT output 1 timing
234 EA FP Write DB1 Dead band PAT output 1
235 EB FP Write OH5 Output OUTA2 high range
236 EC FP Write OL5 Output OUTA2 low range
237 ED Byte Write OMS5 Source of logic output module OUTA
238 EE Byte Write OMS6 Source of logic output module OUTB
239 EF Byte Write OMTY2 Output module type
240 F0 FP Write FST2 PAT/DAT output 2 timing
241 F1 FP Write DB2 Dead band PAT output 2
242 F2 FP Write OH7 Output OUTA3 high range
243 F3 FP Write OL7 Output OUTA3 low range
244 F4 Byte Write OMS7 Source of logic output module OUTA
245 F5 Byte Write OMS8 Source of logic output module OUTB
246 F6 Byte Write OMty3 Output module type
247 F7 FP Write FST3 PAT/DAT output 3 timing
248 F8 FP Write DB3 Dead band PAT output 3
249 F9 FP Write SB1 Symmetry band controller module 5
250 FA FP Write SB2 Symmetry band controller module 6
251 FB Byte Write ALDIS Alarm disable condition source
252 FC Byte Write RCTY1 DC type settings
253 FD Byte Write ALGT Standard algorithm type
254 FE FP Write COS1 Spare constant
255 FF FP Write COS2 Spare constant
PAGE 1
Relative Item Signal Condition Read/Write Johnson Tag Description Relative Item
0
1
2
3
4
5
6
7
8
9
10 A FP Write HR6 High range analog input 6
11 B FP Write LR6 Low range analog input 6
12 C FP Write HR7 High range analog input 7
13 D FP Write LR7 Low range analog input 7
14 E FP Write HR8 High range analog input 8
15 F FP Write LR8 Low range analog input 8
16
17
18
19
20
21
22
23
FP Write HR1 High range analog input 1
FP Write LR1 Low range analog input 1
FP Write HR2 High range analog input 2
FP Write LR2 Low range analog input 2
FP Write HR3 High range analog input 3
FP Write LR3 Low range analog input 3
FP Write HR4 High range analog input 4
FP Write LR4 Low range analog input 4
FP Write HR5 High range analog input 5
FP Write LR5 Low range analog input 5
Relative Item Signal Condition Read/Write Johnson Tag Description
0 Byte Write OSOPT Module options
1 Word Write OSZT@ Zone temperature connection
2 Word Write OSOT@ Outdoor temperature connection
3 Word Write OSSP@ Zone temperature setpoint connection
4 Word Write OSOB@ Off setpoint bias connection
5 Word Write OSDI@ Disable module connection
6 Word Write OSDA@ Disable adaptive action connection
7 Word Write OSTS@ Connection at time schedule output
8 Word Write OSNX@ Connection at next output
9 Word Write OSTIM@ Connection at time to next output
10 FP Write OSPURGE Minimum cool / heat time (min)
11 FP Write OSMAXST Maximum start up time (min)
12 FP Write OSMAXSO Maximum shut down time (min)
13 FP Write OSBHK Start mode building heating factor
14 FP Write OSBCK Start mode building cooling factor
15 FP Write OSSBHK Stop mode building heating factor
16 FP Write OSSBCK Stop mode building cooling factor
17 FP Write OSFW Percentage adaptive control (filter weight)
18 FP Write OSHTD Outdoor heating design temperature
19 FP Write OSCTD Outdoor cooling design temperature
20 FP Write OSCRNG Control range
21 FP Write OSSP Zone temperature on setpoint
22 FP Write OSOB Zone temperature off setpoint
23 FP Write OSTIM Remaining time to next event
24 Byte Write OSSTA Operating status
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Note: The TC9100 is not currently supported by the FieldServer MetasysN2 Driver.
The information below is for interest and future use only.
General dynamic Parameters
Relative Item Signal Condition Read/Write Johnson Tag Description
0 Byte Read UNIT Device model. For TC-9100 always 06h
1 FP Write AI1 Process Temperature
2 FP Write AI2 Remote Temperature Set Point Bias
3 FP Write AI3 Pressure
4 FP Write AI4 Override Input
5 Spare
6 Spare
7 Spare
8 Spare
9 Word Read ADC Selected Analog Input ADC counter
10 FP Write OCM1 Output Programmable Module #1
11 FP Write OCM2 Output Programmable Module #2
12 FP Write OCM3 Output Programmable Module #3
13 FP Write OCM4 Output Programmable Module #4
14 FP Write OCM5 Output Programmable Module #5
15 FP Write OCM6 Output Programmable Module #6
16 FP Write WSP1 Working Set Point Control Module 1
17 FP Write WSP2 Working Set Point Control Module 2
18 FP Write WSP3 Working Set Point Control Module 3
19 FP Write WSP4 Working Set Point Control Module 4
20 FP Write WSP5 Working Set Point Control Module 5
21 FP Write WSP6 Working Set Point Control Module 6
22 FP Write XAI1 External Analog Input 1
23 FP Write XAI2 External Analog Input 2
24 FP Write XAI3 External Analog Input 3
25 FP Write XAI4 External Analog Input 4
26 FP Write ACO5 Analog Constant 5
27 FP Write ACO6 Analog Constant 6
28 FP Read WAC Winter Authority Correction
29 FP Read SAC Summer Authority Correction
30 Word Read ALR Analog Inputs Alarm Status
W(1) AIH1 Analog Input 1 High alarm
W(2) AIL1 Analog Input 1 High alarm
W(3) AIH2 Analog Input 2 High alarm
W(4) AIL2 Analog Input 2 Low alarm
W(5) AIH3 Analog Input 3 High alarm
W(6) AIL3 Analog Input 3 Low alarm
W(7) AIH4 Analog Input 4 High alarm
W(8) AIL4 Analog Input 4 Low alarm
W(9) Not used
W(10) Not used
W(11) Not used
W(12) Not used
W(13) Not used
W(14) Not used
W(15) Not used
W(16) Not used
31 Byte Read LOS Logic Output Status
B(1) DO3 TRIAC 3 ON
B(2) DO4 TRIAC 4 ON
B(3) DO5 TRIAC 5 ON
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Relative Item Signal Condition Read/Write Johnson Tag Description
W(14) Read Reset Cycle indication
W(15) Read 00 = Power Up Reset
01 = External Reset
10 = Oscillator Failure
W(16) Read 11 = Watchdog Reset
133 Word R/W TCS2 TC9100 Controller Options
W(1) 00 Select Analog Input 1 ADC
to
W(2) 11 Select Analog Input 4 ADC
W(3) TM9100 does not overrd the proc Variable
W(4) Half Alternate Mode Timing
W(5) 0 = Celsius 1 = Fahrenheit
W(6) 0 = 50 Hz 1 = 60 Hz Power Line
W(7) Enable Facilitator Mode
W(8) TRIAC7 is ON if mode is Comfort
W(9) Digital Input #1 Mode
000 = Not used
001 = Window Open
010 = Occupancy Sensor
011 = Air Quality Sensor
100 = Reverse Action
W(11) 101 = Intrusion Alarm
W(12) Negate Digital Input #1
W(13) Digital Input #2 Mode
000 = Not used
001 = Window Open
010 = Occupancy Sensor
011 = Air Quality Sensor
100 = Reverse Action
W(15) 101 = Intrusion Alarm
W(16) Negate Digital Input #2
134 Word R/W TCS3 Enable Jumper Options
W(1) Enable Integral Zeroing Loop #1
W(2) Enable Integral Zeroing Loop #2
W(3) Enable Integral Zeroing Loop #3
W(4) Enable Integral Zeroing Loop #4
W(5) Enable Integral Zeroing Loop #5
W(6) Enable Integral Zeroing Loop #6
W(7) Not used
W(8) Not used
W(9) Enable Gain Doubling Loop #1
W(10) Enable Gain Doubling Loop #2
W(11) Enable Gain Doubling Loop #3
W(12) Enable Gain Doubling Loop #4
W(13) Enable Gain Doubling Loop #5
W(14) Enable Gain Doubling Loop #6
135 Byte Write TCS1 Controller Options
B(1) Not used
B(2) Not used
B(3) Not used
B(4) Not used
B(5) Not used
B(6) Not used
B(7) Not used
B(8) Default Action 1=Reverse
136 Word R/W HDW1 Hardware Configuration
137 FP R/W HRI1 High Range AI1
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
Relative Item Signal Condition Read/Write Johnson Tag Description
162 FP Write WA Winter Authority Slope
163 FP Write SA Summer Authority Slope
164 Byte R/W FT@ Freeze Temperature connection
165 FP Write FSP Freeze set point
166 FP R/W FDIF Freeze Differential
167 Word Write LOO Input/Output Override Control
W(1) Read Three Speed Fan Actual Speed
00 = Output OFF
01 = Speed #1
10 = Speed #2
W(2) Read 11 = Speed #3
W(3) Not used
W(4) Read FOS Three spd Fan Overrd Reqst by Hardware
W(5) Write Fan Speed Reqst by Command Module
00 = Output OFF
01 = Speed #1
10 = Speed #2
W(6) 11 = Speed #3
W(7) TM9100 Real Time Clk Refresh Request
W(8) FOR Three speed Fan Overrd Reqst Cmd Mod
W(9) AIO1 Analog Input #1 Override
W(10) AIO2 Analog Input #2 Override
W(11) AIO3 Analog Input #3 Override
W(12) AIO4 Analog Input #4 Override
168 Word Write CLACT Control Loops Activity Mode
W(1) Read Loop #1 Heating
W(2) Read Loop #2 Heating
W(3) Read Loop #3 Heating
W(4) Read Loop #4 Heating
W(5) Read Loop #5 Heating
W(6) Read Loop #6 Heating
W(7) Not used
W(8) Not used
W(9) Write Loop #1 Active
W(10) Write Loop #2 Active
W(11) Write Loop #3 Active
W(12) Write Loop #4 Active
W(13) Write Loop #5 Active
W(14) Write Loop #6 Active
169 Word R/W ALG2 Configuration Index 2
170 FP R/W WAL Winter Authority Limit
171 FP R/W SAL Summer Authority Limit
Items Stored in the TM91xx External Database
Relative Item Signal Condition Read/Write Johnson Tag Description
256 Byte Read UNIT Device Model : xxH
257 FP Read TEMP Room Temperature
258 FP Read RSP Remote Temperature Set Point
259 Word Read LOO Copy of TC9100 Item LOO
260 Byte Read JMP TM9100 Jumper Configuration & status
B(1) JMP1 Clock Setting Disable
B(2) JMP2 Fan Setting Disable
B(3) JMP3 Time Schedule Setting Disable
B(4) JMP4 Model with Time Schedule
B(5) JMP5 Time Schedule Configuration Changed
261 Word Write TIME Real Time
W(1) RTC Minutes 0..59
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
MN2:#01 WARN.
Server_Hold_Timeout is
%0.3fs
For N2Open Slave
typical value is %0.3fs
Typically N2open Clients are configured to timeout after 200ms. If a
FieldServer is configured as a Server the Server_Hold_Timeout time
should be set to 0.175s or less otherwise the response will be suppressed.
This message is printed if the Server_Hold_Timeout is set for >0.175s.
If the Client’s timeout is >200ms this message may be ignored.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com