The ATMI ACM driver allows the FieldServer to transfer data to and from devices over
either RS-232 or RS-485 using ATMI ACM protocol. There are eight RS-232 and two
RS-485 ports standard on the FieldServer. The FieldServer can emulate a passive
client. ( A passive client is one that that consumes messages produced by an remote
device.)
2. Driver Scope of Supply
2.1 Supplied by FieldServer for this driver
FieldServer
Technologies
PART #
FS-8915-10 UTP cable (7 foot) for RS-232 use
FS-8915-10 UTP cable (7 foot) for Ethernet connection
FS-8917-02 RJ45 to DB9F Connector adapter
FS-8917-01 RJ45 to DB25M connection adapter
SPA59132 RS-485 connection adapter
Driver Manual.
DESCRIPTION
2.2 Provided by user
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
4. Configuring the FieldServer as a ATMI ACM Client
The ATMI ACM driver is a passive client driver. This means that it processes unsolicited
incoming data. It cannot poll for data.
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).
This section documents and describes the parameters necessary for configuring the FieldServer
to communicate with a ATMI ACM Server.
The configuration file tells the FieldServer about its interfaces, and the routing of data required.
In order to enable the FieldServer for ATMI ACM 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.
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.
Data_Array_Length Number of Data Objects. Must be
larger than the data storage area
required for the data being placed
in this array.
Data from one ACM can be stored
in multiple data arrays. Position in
the array is dependent on gas
number area number. Further
details are provided in section 6.1
Baud* Specify baud rate 110 – 115200, standard baud
Parity* Specify parity Even, Odd, None, Mark, Space
Data_Bits* Specify data bits 7, 8
Stop_Bits* Specify stop bits
Protocol Specify protocol used ATMI
Handshaking* Specify hardware handshaking RTS, RTS/CTS, None
Poll Delay* Time between internal polls 0-32000 seconds
Timeout Specifies the amount of time that
may pass between complete
data screens. If this time expires
a timeout error is produced but
the processing of data is not
affected. The port is not cleared
and gas data is not reset.
IC_Timeout This parameter is used in a way
that is different to most
FieldServer driver applications.
In this case of this driver it
specifies the maximum amount
of time that may pass between
the driver receiving an incoming
character. If the time is
exceeded then an error is
produced but note that the error
has no other effect on the driver.
The port is not cleared and gas
data is not reset.
P1-P8, R1-R2
rates only
1
default 1 second
This value should provide a
margin over the time configured
between samples in the
CONFIG.DAT profile of the
ACM unit.
This value (specified in
seconds) should be set allow a
margin between time stamp
messages from the ACM unit.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com