FieldServer Dart FS-8700-78 Driver Manual

A Sierra Monitor Company

Driver Manual

(Supplement to the FieldServer Instruction Manual)

FS -8700-78 Dart

APPLICABILITY & EFFECTIVITY

Effective for all systems manufactured after January 18, 1999

Instruction Manual Part Number FS-8700-78

2/20/2003

Driver Manual

TABLE OF CONTENTS

1 Dart Driver Description................................................................................................................1

1.1 Performance Issues ................................................................................................................1

2 Driver Scope of Supply ................................................................................................................2

2.1 Supplied by Sierra Monitor for this driver...............................................................................2

2.2 Provided by user....................................................................................................................2

3 Hardware Connections .................................................................................................................3

3.1 Hardware Configuration – Dart Present ...................................................................................4

4 Basic Configuration.....................................................................................................................5

4.1 Data Arrays...........................................................................................................................5

4.2 Client Side Connections.........................................................................................................6

4.3 Client Side Nodes..................................................................................................................7

4.4 Client Side Map Descriptors ..................................................................................................8

4.4.1 FieldServer Specific Map Descriptor Parameters ..............................................................8

4.4.2 Timing Parameters..........................................................................................................8

4.4.3 Driver Specific Map Descriptor Parameters......................................................................8

4.4.4 Map Descriptor: Example 1 – Read all possible data....................................................... 11

4.4.5 Map of How Data Aire Device Data is stored in a Data Array..........................................12

4.4.6 Unit Types ................................................................................................................... 17

4.4.7 Map Descriptor: Example 2 – Writing a Set-Point ..........................................................19

4.4.8 Map Descriptor: Example 3 – Writing multiple points using one message. ....................... 20

5 Chapter 5...................................................................................................................................21

6 Advanced Topics....................................................................................................................... 23

6.1 Additional Driver Specific Map Descriptor Parameters ..........................................................23

6.1.1 DA_Func Parameter - Permitted values..........................................................................24

6.1.2 DA_Field Parameter - Permitted v alues.........................................................................25

6.1.3 DA_Method Parameter Values and Notes....................................................................... 27

6.1.4 Advanced Example 1 :.................................................................................................. 28

6.1.5 Advanced Example 2 ....................................................................................................29

6.1.6 Advanced Map Descriptor: Example 3 - Using the 'special' parameter............................. 30

6.1.7 Advanced Map Descriptor: Example 4 - Using the 'DA_Assoc' parameter....................... 31

6.1.8 Map Descriptor: Example 5 - Using a special / diagnostic command. ............................... 32

6.2 Related Documents..............................................................................................................34

6.3 Troubleshooting Tips........................................................................................................... 34

6.3.1 Bad Values................................................................................................................... 34

6.3.2 Dead Nodes ..................................................................................................................34

6.3.3 Ignored Messages......................................................................................................... 34

6.4 Writing data to Dap Devices................................................................................................ 35

7 Revision Change Notices............................................................................................................ 36

7.1 Rev1.06a-Rev0 Changes from previous releases.................................................................... 36

FieldServer Technologies 1991 Tarob Court, Milpitas, California 95035 (408) 262 -2299 fax: [phone]

Visit our website: www.fieldserver.com E-mail: [e-mail]

Page Index

1 Dart Driver Description

The Dart Driver is designed for connection to a Data Air Coporation Dart Device.
The Dart device is a active element on a network of Data Air devices such as DAP panels. It

manages the devices and provides co-ordination and supervision. In performing these duties the
Dart device polls all the devices on the network for all the data. The Dart is capable of ‘echoing’
the responses from these devices on one of its RS232 ports. This driver is designed to listen
passively to these echoes and store device data. In addition the driver can send messages
(containing set point data, for example,) directly to individual devices on the network.

The FieldServer is connected to the RS232 serial port of the Dart. The Fieldserver can read and
write but active polling must be minimized as in reduces the amount of time that the DART
spends controlling the networked devices. The driver operates primarily as a passive client
listening to echoes of the data being polled by the DART. The DART must be set to ‘Echo’ mode
on the front panel of the Dart for the driver to operate correctly. There is no alternative to this
essential but manual setup-step.

The driver may be configured very simply (See example 1 in section 4 of the manual). In addition
a number of advanced configurations are possible. The manual is divided to separate the basic
and advanced topics.

The driver supports the common message formats for common Data Aire devices. A list of the
supported messages is provided in the manual. The driver cannot be used to configure or read the
status of a DART device itself.

The inf ormation that follows describes how to expand upon the factory defaults provided in the
configuration files included with the FieldServer.

Driver Manual

1.1 Performance Issues

Several factors outside FieldServer’s control make for slow communications with Data Aire
devices. The Data Aire communications is based on a very low baud rate. In addition inter­message timing constraints and overhead requirements for active messages in a Dart
configuration add significant time to each transaction.

When a used with a DART device, writing to a set point (or other variable) may take up to 8
seconds to complete the transaction. The results of the write will not be seen until the DART has
timed-out back into control mode and echoes the new data to the Fieldserver. This could take
several minutes if there are many devices on the loop and will take at least 30 seconds.

When writing continuously, with DART configurations, the minimum time interval between
successive writes is 2 minutes and with non-DART configurations is 1.8 seconds.

FieldServer Technologies 1991 Tarob Court, Milpitas, California 95035 (408) 262 -2299 fax: [phone]

Visit our website: www.fieldserver.com E-mail: [e-mail]

Page 1

Driver Manual

2 Driver Scope of Supply

2.1 Supplied by Sierra Monitor for this driver

RS485 connection adapter
Driver Manual.

2.2 Provided by user

Data Aire Dart and documentation
RS232 cable for the loop network

FieldServer Technologies 1991 Tarob Court, Milpitas, California 95035 (408) 262 -2299 fax: [phone]

Visit our website: www.fieldserver.com E-mail: [e-mail]

Page 2

3 Hardware Connections

Hardware

Driver Manual

FieldServer Technologies 1991 Tarob Court, Milpitas, California 95035 (408) 262 -2299 fax: [phone]

Visit our website: www.fieldserver.com E-mail: [e-mail]

Page 3

Driver Manual

3.1 Hardware Configuration – Dart Present

When a DART device is connected to the Data Aire field devices then the Fieldserver is connected to the
serial port of the DART. The DART must be set to ‘Echo’ mode. This is done on the front panel of the
DART.

FieldServer Technologies 1991 Tarob Court, Milpitas, California 95035 (408) 262 -2299 fax: [phone]

Visit our website: www.fieldserver.com E-mail: [e-mail]

Page 4

Driver Manual

4 Basic Configuration

For a detailed discussion on FieldServer configuration, please refer to the instruction manual for the
FieldServer. 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).

The configuration file tells the FieldServer about its interfaces, and the routing of data required. In
order to enable the FieldServer for Dart Driver communications, the driver independent FieldServer
buffers need to be declared in the “Data Arrays” section, the destination device addresses need to be
declared in the “Client Side Nodes” section, and the data required from the servers needs to be
mapped in the “Client Side Map Descriptors” section. Details on how to do this can be found
below.

The Dart Serial Driver cannot be configured as a data server.

Note that in the tables, * indicates an optional parameter, with the bold legal value being the
default.

4.1 Data Arrays

Section Title

Data_Arrays

Column Title Function Legal Values

Data_Array_Name Provide name for Data Array Up to 15 alphanumeric

characters

Data_Format Provide data format. Each data array can

only take on one format.

FLOAT, BIT, UInt16,
SInt16, Packed_Bit, Byte,
Packed_Byte,
Swapped_Byte

Data_Array_Length Number of Data Objects. Must be larger

1-10,000
than the data storage area required for the
data being placed in this array.

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

FieldServer Technologies 1991 Tarob Court, Milpitas, California 95035 (408) 262 -2299 fax: [phone]

Visit our website: www.fieldserver.com E-mail: [e-mail]

Page 5

4.2 Client Side Connections

Section Title

Connections

Column Title Function Legal Values

Port Specify which port the device is

Secondary_Port* Using a Dart ? Do not specify

Baud* Specify baud rate 2400 (Others available but

Parity* Specify parity
Data_Bits* Specify data bits

Stop_Bits* Specify stop bits
Protocol Specify protocol used

Handshaking* Specify hardware handshaking
Poll Delay* Time between internal polls 0-32000 seconds

Example

// Client Side Connections

Connections
Port, Parity, Data_Bits, Stop_Bits, Protocol, Poll_Delay
P1, 2400 , None, 8, 1, Dart , 0.100s

Driver Manual

connected to the FieldServer

This is the port connected to the
DART’s RS232 port.

this parameter.

Either keyword may be used.

P1-P8, R1-R2
(P1-P8) requires 232/485
converter.

P1-P8, R1-R2
(R1-R2) requires 232/485
converter.

Daire only operates at 2400
baud.)

None
8

1

Dart

None
default 1 second

FieldServer Technologies 1991 Tarob Court, Milpitas, California 95035 (408) 262 -2299 fax: [phone]

Visit our website: www.fieldserver.com E-mail: [e-mail]

Page 6

4.3 Client Side Nodes
Section Title

Nodes

Column Title Function Legal Values

Node_Name Provide name for node Up to 32 alphanumeric

Node_ID This is not the node address of

Protocol Specify protocol used Dart
Port Specify which port the Dart is

Example

// Client Side Nodes

Nodes
Node_Name, Node_ID, Protocol, Port
Unit1, 1, Dart , P1

Driver Manual

characters
1-259

the Dart device !
Specify the node address of the

DAP de vice whose data you
wish to monitor.

P1-P8, R1-R2

connected to the FieldServer

FieldServer Technologies 1991 Tarob Court, Milpitas, California 95035 (408) 262 -2299 fax: [phone]

Visit our website: www.fieldserver.com E-mail: [e-mail]

Page 7

Driver Manual

4.4 Client Side Map Descriptors

4.4.1 FieldServer Specific Map Descriptor Parameters

Column Title Function Legal Values

Map_Descriptor_Name Name of this Map Descriptor Up to 32 alphanumeric

Data_Array_Name Name of Data Array where data

is to be stored in the
FieldServer

Data_Array_Location Starting location in Data Array 0 to maximum specified in

Function Function of Client Map

Descriptor

The use of the WRBX keyword
is recommended for DART
configurations as
communications are minimized.

characters
One of the Data Array names

from “Data Array” section
above

“Data Array” section above
RDBC, WRBC, WRBX,
Passive

4.4.2 Timing Parameters

Column Title Function Legal Values

Scan_Interval Rate at which data is polled >0.1s

4.4.3 Driver Specific Map Descriptor Parameters

Column Title Function Legal Values

Node_Name Name of Node to fetch data

from

Length Length of Map Descriptor 1 The length must always be

Address Starting address of read block Not required for client

The following parameters apply only to the Dart Driver.
DA_Func* Tell the driver to poll the device

for all the data that is available.
The data is device specific.

Other uses of this parameter are
permitted. These uses are
discussed in the Advanced
Topics section of this manual.

One of the node names
specified in “Client Node
Descriptor” above

set to one.

configuration. This parameters
is used in simulation
configuration only.

Everything

See table 4.4.3.1 for a map of
how the data is stored in the
Fieldserver data arrays

FieldServer Technologies 1991 Tarob Court, Milpitas, California 95035 (408) 262 -2299 fax: [phone]

Visit our website: www.fieldserver.com E-mail: [e-mail]

Page 8

Driver Manual

DA_Field Onl y required when the

function is a write (wrbc) or
when the map descriptor is
associated with a write by
means of the DA_Assoc
parameter value.

This is the name of the data
field whose value you wish to
set in the device.

Other uses of this parameter are
permitted. These uses are
discussed in the Advanced
Topics section of this manual.

DA_Assoc Use to associate passive map

descriptors with an active map
descriptor.

Using this parameter you
associate multiple fields with
one wrbc map descriptor, thus
reducing writing multiple
values to one device using just
one message.

See Table 4.4.3.3 for a list of
permitted values.

Any positive integer.

FieldServer Technologies 1991 Tarob Court, Milpitas, California 95035 (408) 262 -2299 fax: [phone]

Visit our website: www.fieldserver.com E-mail: [e-mail]

Page 9

Driver Manual

FieldServer Technologies 1991 Tarob Court, Milpitas, California 95035 (408) 262 -2299 fax: [phone]

Visit our website: www.fieldserver.com E-mail: [e-mail]

Page 10