-
A Sierra Monitor Company
Driver Manual
(Supplement to the FieldServer Instruction Manual)
FS-8700-101
Setra Digital Pressure Gage Model 370
APPLICABILITY & EFFECTIVITY
Effective for all systems manufactured after May 1, 2001
Driver Version:
1.00
Document Revision: 7
FS-8700-101_Setra Model 370 Digital Pressure Gage Manual
Page 3 of 23
1.
Setra Model 370 Digital Pressure Gage Description
The ‘Setra Model 370 Digital Pressure Gage’ driver allows the FieldServer to transfer data to
and from devices over either RS-232 or RS-485 using the ‘Setra Model 370 Digital Pressure
Gage’ protocol. The FieldServer can emulate either a Server or Client.
The driver implements a subset of the commands and responses that an actual Setra Model
370 Digital Pressure Gage is capable of. Thus the driver permits the transfer of current pressure
information, Gage status information and the processing of Gage verification information.
The driver is capable of providing active Client and passive Server support. An active Client
polls for data and processes responses, it is not capable of processing unsolicited messages
from the remote device. A passive Server can respond to polls but is not capable of sending
unsolicited messages reporting change of state or other information.
When configured as a Client it is important the digital Gage is configured correctly and that it is
left in an operational mode where it can respond easily to the commands sent to it. If a user,
were to operate the Gage from its front panel and leave it in a configuration state, awaiting input
from a user, then the Gage would be incapable of responding to commands from the
FieldServer. The driver cannot write to the digital Gage. Thus alarm set points and other
configuration tasks cannot be performed using a FieldServer.
Max Nodes Supported
FieldServer
Nodes Comments
Mode
This is a nodeless protocol. Only one Server per FieldServer
port.
This is a nodeless protocol. Only one Client per FieldServer port.
Client
1
1
Server
FS-8700-101_Setra Model 370 Digital Pressure Gage Manual
Page 4 of 23
2.
Driver Scope of Supply
2.1. Supplied by FieldServer Technologies for this driver
FieldServer Technologies
PART #
Description
FS-8917-01
FS-8700-101
Connector, 25 pin male: Connects to DCE, RTS/CTS loop
Driver Manual.
2.2.
Provided by the Supplier of 3rd Party Equipment
2.2.1.
Required 3rd Party Hardware
Part #
Description
M370
SETRA DIGITAL PRESSURE GAGE
2.2.2.
Required 3rd Party Configuration
The M370 Gage must be configured using the operator’s manual and the front panel
push buttons so that its serial port settings match the FieldServer settings.
The following notes have been extracted from the operator’s manual.
The Setra Digital Pressure Gage is capable of interfacing with a wide variety of computers or
other devices through the RS-232 serial communications port. Devices which are connected this
way must be set up to communicate at the same rate of speed. To change the baud rate of the
gage (the rate at which the gage sends information out through the port) so it agrees with that of
the device connected to it, use the following procedure.
1. Press CONV until the gage is displaying pressure units (make sure it is not displaying in "ft" or
"meters").
2. Press the "-" key.
3. Enter "5555". This is the baud rate access code.
4. Press SETUP. The display will read "CAL br".
5. Enter the baud rate. Choose either 300, 600, 1200, 1800, 2400, 3600, 4800or 9600.
6. Press SETUP.
The baud rate is factory set to 2400. If you change the baud rate and wish the gage to retain the
new rate after power is removed and restored, repeat steps 2-6 a second time.
FS-8700-101_Setra Model 370 Digital Pressure Gage Manual
Page 5 of 23
3.
Hardware Connections
The FieldServer is connected to the rear side of the Model 370 Digital Pressure Gage as shown
in the following connection drawing.
FS-8700-101_Setra Model 370 Digital Pressure Gage Manual
Page 6 of 23
3.1.
Hardware Connection Tips / Hints
The following notes are extracted from the Setra 370 Operator Manual.
The Setra Digital Pressure Gage implements the majority of the RS-232 communications standard,
but does not provide handshaking lines (such as busy, DSR, or DTR). The four lines which must be
connected are diagrammed below, along with the pin layout of the female connector on the back of
the gage.
13
7
3 2 1
O O O O O O O O O O O O O
O O O O O O O O O O O O
25
Pin
1
14
Desc.
Protective ground
Input to gage (RXD)
2
3
7
Output from gage (TXD)
Signal ground
The Model 370 serial interface is a DCE (Data Communications Equipment) type, with a standard
female DB25S pin connector. This means that it receives data on pin 2 and sends data on pin 3. This
is in contrast to DTE (Data Transmission Equipment) which receives data on pin 3 and sends data on
pin 2. The RS-232 standard describes communications between DTE and DCE devices.
Since many computers have serial ports configured as DTE, the Model 370 conveniently plugs
directly into the standard serial port on most computers, using a standard RS-232 "straight-through"
cable available from SETRA, or from any computer hardware vendor. Some devices, including some
printers and computers, will be equipped with DCE interfaces like that in the Model 370. To connect
the Model 370 to these devices, a "null modem" cable is required. This is simply a cable which
connects pin 2 and 3 of the Model 370 to pin 3 and 2 of the other device respectively by crossing
them in the cable. This kind of cable is also available from SETRA, or from any computer hardware
vendor.
The maximum recommended cable length is 15 meters.
The RS-232 data format used by the Model 370 is:
8 bits, 1 start bit, 1 stop bit, no parity.
FS-8700-101_Setra Model 370 Digital Pressure Gage Manual
Page 7 of 23
4.
Configuring the FieldServer as a Setra Model 370 Digital Pressure Gage
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 Setra Model 370 Digital Pressure Gage.
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 Setra Model 370 Digital Pressure Gage
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
Data_Array_Name Provide name for Data Array
Provide data format. Each Data Array can
Function
Legal Values
Up to 15 alphanumeric
characters
only take on one format.
For this driver, FieldServer recommends Float,
the use of a FLOAT Data Array. This is SInt16,
because the pressure and status settings Byte,
Bit,
UInt16,
Packed_Bit,
Packed_Byte,
Data_Array_Format
are reported as real signed numbers with Swapped_Byte
some significant digits after the decimal
point.
Number of Data Objects. Must be larger
than the data storage area required by the
Map Descriptors for the data being placed
Data_Array_Length
1-10,000
in this array.
Example
// Data Arrays
Data_Arrays
Data_Array_Name,
DA_PRESSURE,
DA_STATUS,
DA_DI_01,
Data_Format,
FLOAT,
FLOAT,
Bit,
Data_Array_Length,
200
200
200
200
DA_DO_01,
Bit,
FS-8700-101_Setra Model 370 Digital Pressure Gage Manual
Page 8 of 23
4.2.
Client Side Connection Descriptors
Section Title
Connections
Column Title
Function
Legal Values
P1-P8, R1-R21
Setra370
110 – 115200, standard baud
rates only, 2400.
Specify which port the device is
connected to the FieldServer
Specify protocol used
Port
Protocol
Baud*
Specify baud rate
Parity*
Specify parity
Even, Odd, None, Mark, Space
Data_Bits*
Stop_Bits*
Specify data bits
Specify stop bits
7, 8
1
Specify hardware handshaking
Handshaking*
RTS, RTS/CTS, None
The Setra Model 370 does not support
handshaking.
Poll _Delay*
Time between internal polls
0-32000 seconds, 1 second
Example
// Client Side Connections
Connections
Port,
P8,
Protocol,
Setra370,
Baud, Parity,
2400, None,
Handshaking,
None,
Poll_Delay
0.100s
4.3.
Client Side Node Descriptors
Section Title
Nodes
Column Title
Function
Provide name for node
Legal Values
Up to 32 alphanumeric
characters
Node_Name
This commonly used parameter has no meaning for this driver and may be
omitted.
Node_ID
Protocol
Specify protocol used
Setra370.
Specify which port the device is connected
to the FieldServer
Connection
P1-P8, R1-R21
Example
// Client Side Nodes
Nodes
Node_Name,
Gage1,
Protocol,
Setra370,
Connection
P8
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-8700-101_Setra Model 370 Digital Pressure Gage Manual
Page 9 of 23
4.4.
4.4.1.
Client Side Map Descriptors
FieldServer Related Map Descriptor Parameters
Column Title
Function
Legal Values
Up to 32 alphanumeric
characters
Map_Descriptor_Name Name of this Map Descriptor
Name of Data Array where One of the Data Array names
data is to be stored in the from “Data Array” section
Data_Array_Name
FieldServer
above
Starting location in Data 0 to maximum specified in
Data_Array_Offset
Function
Array
“Data Array” section above
RDBC
Function of Client Map
Descriptor
4.4.2.
Driver Related Map Descriptor Parameters
Column Title
Function
Legal Values
Name of Node to fetch data One of the node names specified in
Node_Name
Data_Type
from
“Client Node Descriptor” above
This
commonly
used
parameter has no special
meaning to this driver and
may be omitted.
Register, Coil, AI, DI
The driver knows the correct length
for the various Map Descriptors and
will prompt you accordingly if an
invalid length is specified.
Length
Length of Map Descriptor
Pressure : Set Length 5
Status: Set Length 14
Verification Info: Set length 100.
This commonly used parameter has no special meaning to this
driver and may be omitted.
Address
Specifies what data should
be read and stored.
Gage_Function*
4.4.3.
Pressure, Status, Verify
If you omit this parameter
then the driver assumes
you are reading pressure.
Timing Parameters
Column Title
Scan_Interval
Function
Rate at which data is polled
Legal Values
≥0.001s
FS-8700-101_Setra Model 370 Digital Pressure Gage Manual
Page 10 of 23
4.4.4.
Map Descriptor Example #1 – Read Pressure.
In this example a Map Descriptor is defined which controls the task of reading pressure data from the Setra Model 370 Digital
Pressure Gage. The task gets performed every 5.0 seconds. When a response is received the data is stored in the Data Array
called DA_PRESSURE stating at element zero (the offset). Each pressure reading requires the driver store 5 parameters and hence
the length of the Map Descriptor is 5. Refer to Appendix A for further information.
Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, Node_Name, Gage_Function, Length, Scan_Interval
Read_Press,
DA_PRESSURE,
0,
RDBC,
Gage1,
Pressure,
5,
5.0s
Unique names
assist config file
validation
Tells the driver
to schedule this
MD no more
The name of a Node
defined in the CSV file.
The node name connect
the MD to a node which
The 1st location
in the Data
Array which will
be used for
storage.
Tells the driver
to read the
current
pressure
measurement
from the Gage
The name of a
Data Array in
which
the
debugging but
often than
seconds.
5
response data
will be stored.
are
not
in turn points to
a
necessary.
connection Thus the
driver knows what port
and port settings to use
to send the poll..
Reserves
5
elements of the
Data Array to
store response
data.
FS-8700-101_Setra Model 370 Digital Pressure Gage Manual
Page 11 of 23
4.4.5.
Map Descriptor Example #2 – Read Status
In this example a Map Descriptor is defined which controls the task of reading status data from the Setra Model 370 Digital Pressure
Gage. The task gets performed every 5.0 seconds. When a response is received the data is stored in the Data Array called
DA_STATUS stating at element zero (the offset). Each pressure status reading requires the driver store 20 parameters and hence
the length of the Map Descriptor is 20. Refer to Appendix A for further information.
Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, Node_Name, Gage_Function, Length, Scan_Interval
Read_Status,
DA_STATUS,
0,
RDBC,
Gage1,
Status ,
20,
5.0s
Unique names
assist config file
validation
The name of a
Data Array in
The 1st location
Tells the driver
to read the
current status
from the Gage
The name of a Node defined in
the CSV file. The node name
connect the MD to a node which
in turn points to a connection
Thus the driver knows what port
and port settings to use to send
the poll..
Tells the driver
to schedule this
MD no more
in the Data
Array which will
be used for
storage.
debugging but
which
the
are
not
response data
will be stored.
often than
seconds.
5
necessary.
Reserves
20
elements of the
Data Array to
store response
data.
FS-8700-101_Setra Model 370 Digital Pressure Gage Manual
Page 12 of 23
4.4.6.
Map Descriptor Example #3 - Verify.
The verification string contains revision and model information about the Gage. In this example a Map Descriptor is defined which
controls the task of reading verification data from the Setra Model 370 Digital Pressure Gage. The task gets performed every 5.0
seconds. When a response is received the data is stored in the Data Array called DA_VERIFY stating at element zero (the offset).
Each Gage verification reading requires the driver store a string containing two lines of data. The actual length is unknown in
advance and it is recommended that 100 Data Array elements be reserved to store the verification sting. The verification string is
stored by writing each consecutive letter in consecutive Data Array elements. It is recommended that the Data_Array_Format is set
to BYTE in this case. This will enable the use of the “String” display to read the verification string in RuiNet.
Map_Descriptor_Name, Data_Array_Name, Data_Array_Offset, Function, Node_Name, Gage_Function, Length, Scan_Interval
Read_Verify,
DA_VERIFY,
0,
RDBC,
Gage1,
Verify,
100,
5.0s
Unique names
assist config file
validation
The name of a
Data Array in
The 1st location
in the Data
Array which will
be used for
storage.
The name of a Node defined in
the CSV file. The node name
connect the MD to a node
which in turn points to a
connection Thus the driver
knows what port and port
settings to use to send the
poll..
Tells the driver
to read the
verification
string
measurement
from the Gage
Tells the driver
to schedule this
MD no more
which
the
debugging but
response data
will be stored.
often than
seconds.
5
are
not
necessary.
Reserves 100
elements of the
Data Array to
store response
data.
FS-8700-101_Setra Model 370 Digital Pressure Gage Manual
Page 13 of 23
5.
Configuring the FieldServer as a Setra Model 370 Digital Pressure Gage
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.
This section documents and describes the parameters necessary for configuring the FieldServer
to communicate with a Setra Model 370 Digital Pressure Gage Client
The configuration file tells the FieldServer about its interfaces, and the routing of data required.
In order to enable the FieldServer for Setra Model 370 Digital Pressure Gage 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
Specify which port the device is
connected to the FieldServer
Legal Values
P1-P8, R1-R22
Port
Protocol
Specify protocol used
Setra370
110 – 115200, standard
baud rates only
Even, Odd, None, Mark,
Space
Baud*
Parity*
Specify baud rate
Specify parity
Data_Bits*
Specify data bits
Specify stop bits
7, 8
Stop_Bits*
1
Handshaking*
Specify hardware handshaking
Specifies time FieldServer will
reserve Server side connection
RTS, RTS/CTS, None
Server_Hold_Timeout*
while waiting for the Client side to >1.0s
update data in Data_Array (if
necessary)
Example
// Server Side Connections
Connections
Port,
P8,
Protocol,
Setra370,
Baud,
9600,
Parity,
None,
Handshaking,
None,
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-8700-101_Setra Model 370 Digital Pressure Gage Manual
Page 14 of 23
5.2.
Server Side Node Descriptors
Section Title
Nodes
Column Title
Function
Legal Values
Up to 32 alphanumeric
characters
Node_Name
Provide name for node
This commonly used parameter is not used by this driver and
maybe omitted.
Node_ID
Protocol
Specify protocol used
Setra370
Specifies time FieldServer will
reserve Server side connection
Server_Hold_Timeout*
while waiting for the Client side >1.0s
to update data in Data_Array (if
necessary)
Example
// Server Side Nodes
Nodes
Node_Name,
PLC 1,
∗
Protocol
Setra370
∗ Note that no connection information is necessary on Server side.
FS-8700-101_Setra Model 370 Digital Pressure Gage Manual
Page 15 of 23
5.3.
5.3.1.
Server Side Map Descriptors
FieldServer Specific Map Descriptor Parameters
Column Title
Function
of this
Descriptor
Legal Values
Map Up to 32 alphanumeric
characters
Name
Map_Descriptor_Name
Name of Data Array where One of the Data Array
data is to be stored in the names from “Data Array”
Data_Array_Name
FieldServer
section above
Starting location in Data 0 to maximum specified in
Data_Array_Offset
Function
Array
“Data Array” section above
Server
Function of Server Map
Descriptor
Specifies time FieldServer
will reserve Server side
connection while waiting for
the Client side to update
data in Data_Array (if
necessary)
Server_Hold_Timeout*
>1.0s
5.3.2.
Driver Specific Map Descriptor Parameters
Column Title
Function
Legal Values
One of the node names
specified in “Client Node
Descriptor” above
Name of Node to fetch data
from
Node_Name
Data_Type
This
commonly
used
parameter has no special
meaning to this driver and
may be omitted.
Register, Coil, AI, DI
Length
Length of Map Descriptor
1 - 1000
This commonly used parameter has no special meaning to
this driver and may be omitted.
Address
FS-8700-101_Setra Model 370 Digital Pressure Gage Manual
Page 16 of 23
5.3.3.
Server Map Descriptor Example.
This Map Descriptor defines a capability of the FieldServer to respond to a poll for an immediate Pressure Print (Command Code =
‘P’). When the poll is received, the driver inspects 5 consecutive array elements starting at offset 0 in the Data Array named
DA_PRESSURE. The contents of the 5 elements are defined in Appendix A.1.1. The 2nd element is the units index, the 3rd is the
pressure indicating letter. Both of these elements must be set to non-zero values.
Map_Descriptor_Name,
SRV_Pressure,
Data_Array_Name,
DA_PRESSURE
Data_Array_Offset,
0,
Function,
Server
Node_name
Gage1
Gage_Functon
Pressure,
Length
5
This function defines
a capability of the
The Node Name
Defines the capability
of this Map Descriptor.
This Map Descriptor
can only be used to
form responses to a
‘P’ poll.
Data for the
response to a
must be the same
as one of the
nodes defined in
the ‘nodes’ section
of the CSV file.
FieldServer
respond
to
an
‘P’
poll
is
to
extracted from
this Data Array.
incoming poll.
The Map Descriptor
is passive. It does
not
generate
messages but is
used to respond.
FS-8700-101_Setra Model 370 Digital Pressure Gage Manual
Appendix A. Advanced Topics
Page 17 of 23
Appendix A.1. How Data Gets Stored
Appendix A.1.1. Pressure Data
Offset (where x is the offset
Notes
specified in the MD)
X + 0
Gage Pressure. A signed real number.
Gage Pressure Units. A whole number which is used
X + 1
as a lookup into the table provide in section
“Appendix A.2 Gage Pressure Units”
Gage Pressure Indicating Letter
‘A’ = 65
‘G’ = 71
X + 2
‘T’ = 84
Set to 1 If the pressure reading reports the status as
‘OK’
X + 3
Set to 1 If the pressure reading reports the pressure
as a ‘SEA LEVEL’ reading
X + 4
Appendix A.1.2. Status Data
If any fields are absent in the response to a poll for status data then the values are set to
zero for that field.
Offset (where x is the offset
Notes
specified in the MD)
X + 0
X + 1
X + 2
X + 3
X + 4
X + 5
X + 6
X + 7
X + 8
X + 9
X + 10
X + 11
X + 12
X + 13
‘ELEV:’ measurement. A signed real number.
‘ELEV:’ engineering units index. See table
“Appendix A.2 Gage Pressure Units”
‘MAX:’ measurement. A signed real number.
‘MAX:’ engineering units index. See table “Appendix
A.2 Gage Pressure Units”
‘MIN:’ measurement. A signed real number.
‘MIN:’ engineering units index. See table “Appendix
A.2 Gage Pressure Units”
‘HI ALARM:’ measurement. A signed real number.
‘HI ALARM:’ engineering units index. See table
“Appendix A.2 Gage Pressure Units”
‘LO ALARM:’ measurement. A signed real number.
‘LO ALARM:’ engineering units index. See table
“Appendix A.2 Gage Pressure Units”
‘ZERO:’ measurement. A signed real number.
‘ZERO:’ engineering units index. See table
“Appendix A.2 Gage Pressure Units”
‘UNIT:’ measurement. A signed real number.
‘UNIT:’ engineering units index. See table “Appendix
A.2 Gage Pressure Units”
FS-8700-101_Setra Model 370 Digital Pressure Gage Manual
Appendix A.2. Gage Pressure Units
Page 18 of 23
The driver does not report status and pressure reading units as text strings. Rather, the
driver reports and index number. Use the index number and the table below to determine
the units being reported.
Index #
Meaning
0
The Units field could not be interpreted correctly / there were no units reported
/ the units reported were not part of the following list. This may be the case if
the Gage is reporting some custom units that the driver does not recognize.
1
HPA
2
PSI, psi
3
4
5
mbar, MBAR
MmHG, mmHg,
MmH20
6
InH20
7
ft, FT
8
m. M
9
Units
10
inHG, In HG, IN HG
Appendix A.3. Driver Limitations & Exclusions
This driver implements a subset of the commands defined by the protocol. The commands
that have been implemented have been selected to provide relevant real time data transfer
and have omitted configuration/setup functions.
The following table lists the commands that have been implemented.
Command
Immediate Print of Pressure Reading
Status Print
Verification String
All others
Code
P
SP
V
Implemented
Yes
Yes
Yes
No
FS-8700-101_Setra Model 370 Digital Pressure Gage Manual
Page 19 of 23
Appendix B. Troubleshooting tips
Appendix B.1. Connection Tips & Hints
The digital pressure Gage must be left in an operational state, in which it is able to respond
to the commands (polls) sent by the FieldServer. It is possible to enter a configuration mode
using the buttons on the front panel of the Gage and then fail to complete the configuration
sequence. In such cases, the Gage will not be able to respond to polls from the
FieldServer. This problem can be eliminated by ensuring that, after operating the Gage
from the front panel, that it is left in a mode where it is displaying the current measured
pressure.
FS-8700-101_Setra Model 370 Digital Pressure Gage Manual
Appendix C. Driver Error Messages
Page 20 of 23
Message
Notes and Corrective Action
Set370:#1 FYI. Use an
Array called <%s> to
expose diagnostic info.
This message is provided for information and may be ignored. Read
Appendix C.1 for more information.
This message is provided for information and may be ignored. The
Set370:#2a. FYI. MD message is printed when the Map Descriptor length in the
Length=%d assigned by configuration file has not been specified. The driver makes the
driver.
correction by itself. To stop this message being printed, modify the
configuration file to match the length reported in the message.
This Driver cannot be used to write to the Setra device. Remove
any Map Descriptors whose function requires the FieldServer to
write to the Setra device. 3
Set370:#3 Err. No Write
MD's allowed.
This message is provided for information and may be ignored. The
address parameter is ignored by the driver. To stop this message
being printed, remove the address parameter from the configuration
file.
Set370:#4
param=Address has no
meaning. Ignoring.
FYI.
MD
There are a few variations of this message. Note the variation and
Set370:#5
Diagnostic x
Err. report the error to FieldServer tech support. You cannot resolve this
error yourself. The error is printed when the driver executes a
diagnostic function used for QA testing.
The Data Array associated with the reported MD is too short to store
Set370:#6 Err. Array too
short. DA=%s MD=%s
all the data returned by the Setra Gage. Increase the length of the
Data Array and of the Map Descriptor.3
The response to a pressure reading request cannot be parsed by the
Set370:#7 Err. Pressure driver. Use the connection view to check the number of protocol
message
parsed. Abandoned!
can’t
be errors. If they keep rising, then take a log and report the error to
FieldServer Tech Support. If the protocol errors are occasional then
ignore them.4
The response to a status reading request cannot be parsed by the
Set370:#8* Err. Status driver. Use the connection view to check the number of protocol
message
parsed. Abandoned!
can’t
be errors. If they keep rising, then take a log and report the error to
FieldServer Tech Support. If the protocol errors are occasional then
ignore them.
A Map Descriptor is found which does not have the ‘Gage_Function”
Set370:#9 FYI. Default specified. The driver assumes your intention was to read the Gage’s
to reading pressure.
pressure. If you wish stop this message being printed then modify
the configuration file and specify the ‘Gage_Function’ = ‘Pressure’.3
This message is printed when the driver is configured as a Server.
The Data Array associated with the reported MD is too short to store
the message. Modify the MD length and the DA length and try
again.3
Set370:#10 Err. DA=%s
too
short.
Act=%d
Rqd=%d MD=%s
3
Modify the configuration CSV file. Download the modified file to the FieldServer and reset the
FieldServer for the changes to take effect.
Message is printed once and then suppressed. This is to prevent the error log filling with redundant
4
repetition and thus obscuring other important information.
FS-8700-101_Setra Model 370 Digital Pressure Gage Manual
Appendix C.1. Exposing Driver Diagnostic Statistics
Page 21 of 23
In addition to the standard FieldServer communication statistics described in Appendix C.2
and in the FieldServer Instruction Manual, this driver can also expose some driver statistics
by writing data to a data array. A special Data Array name is required. The driver
recognizes the Data Array by its name which must be "Setra370-Stats"
The following example shows how this Data Array can be configured. You can copy this
section of text directly into your CSV file.
Data_Arrays
Data_Array_Name,
setra370-stats,
Data_Format,
UINT32,
Data_Array_Length
1000
The driver stores the following data. The location in the data array is obtained by
multiplying the port number by 100 and then using the location offset indicated in the table
below.
Offset + x
Where x = port_number*100
Physical Port 1 = Port Number 2
Physical Port 2 = Port number 1
Data Array Offset
Contents
0
1
2
3
For FieldServer use only.
For FieldServer use only.
For FieldServer use only.
Increments by 1 each time a Client poll message is sent to a Gage.
Increments each time a Client poll message is sent to a Gage.
Increases by the number of bytes in the message.
Increments by 1 each time the Gage sends a response which is
completely unsuitable for data storage. Includes messages which
report the Gage is in a setup mode and is unable.
Increases each time the Gage receives a response which has some
hope of containing data. Increased by the number of bytes in that
message.
Increases each time the Gage receives a response which has some
hope of containing data. Increased by 1 each time.
Increments by one each time a status response contains a line
which appears not to be a heading but which does no appear to be
suitable for data extraction.
4
5
6
7
8
Increments by 1 each time a status response contains no data
which could be stored.
9
Increments by 1 each time a pressure reading response is not
suitable for data extraction and storage.
10
FS-8700-101_Setra Model 370 Digital Pressure Gage Manual
Appendix C.2. Standard Driver Stats
Page 22 of 23
Driver Statistics Recorded
PLC Read Messages sent
PLC Write Messages sent
PLC Bytes sent
Explanation
Number of message sent to the Gage
Should be zero
Total number of bytes sent by the Client side driver
Total number of messages of all types received (ACK,
NAK, error response, normal response) on the Client side
driver.
Total number of bytes received by all message types on
the Client side driver.
PLC Message received
PLC Bytes received
Protocol errors are incremented when the Client side
cannot correctly parse a response message from the
Protocol
Gage.
This includes responses that are formatted
differently from what the driver expects, or messages that
report the Gage is ‘unable’ or in setup mode.
Incoming message buffer experiences an excessive
delay between incoming bytes
Client side messages that were not responded to by a
Server. Possibly a communications error or a command
was made to a unit that does not exist.
IC_Timeout
Timeout
Message size was too large for the input buffer. This
should never occur.
Increments when a ‘status’ response contains a line with
insufficient information for storage but which may be a
heading.
Streaming
Exception
FS-8700-101_Setra Model 370 Digital Pressure Gage Manual
Page 23 of 23
THIS PAGE INTENTIONALLY LEFT BLANK
|