The Modbus Daniels driver allows the FieldServer to transfer data to and from devices over
either RS-232 or RS-485 using Modbus Daniels protocol. The FieldServer can only emulate a
Client.
Modbus Daniels is an inclusion into Modbus ASCII, allowing floats to be used. Modbus Daniels
is designed to support floats in the address range 7000 to 7999. The "Double" data type is not
supported. Other standard Modbus data types are supported.
Max Nodes Supported
FieldServer Mode Nodes Comments
The maximum achievable number of devices on the
Client 255
network may be less depending on device loading and
network speed characteristics. Only one client device
allowed on multidrop systems.
2. Driver Scope of Supply
2.1. Supplied by FieldServer Technologies for this driver
FieldServer Technologies
PART #
FS-8915-10 UTP cable (7 foot) for RS_232 use
FS-8917-01 RJ45 to DB25M connection adapter
SPA59132 RS-485 connection adapter
- Driver Manual.
Description
2.2. Provided by the Supplier of 3rd Party Equipment
2.2.1. Required 3rd Party Configuration
The Modbus Daniels device must be set to use Modbus ASCII protocol.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
The FieldServer is connected to the Modbus Daniels device as shown in the connection
drawing.
Configure the Modbus Daniels device according to manufacturer’s instructions.
4. Configuring the FieldServer as a Modbus Daniels 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
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
factory defaults provided in the configuration files included with the FieldServer (See “.csv”
sample files provided with the FS).
This section documents and describes the parameters necessary for configuring the
FieldServer to communicate with a Modbus Daniels Server.
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 Modbus Daniels 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.4.1. FieldServer Related Map Descriptor Parameters
Section Title
Map Descriptors
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 Client 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
RDBC, WRBC, WRBX
4.4.2. Driver Related Map Descriptor Parameters
Section Title
Map Descriptors
Column Title Function Legal Values
Node_Name
Data_Type* Data type Register, Coil, AI, DI
Length
Address
Data_Array_Low_Scale*
Data_Array_High_Scale*
Node_Low_Scale*
Node_High_Scale*
Name of Node to fetch
data from
Length of Map
Descriptor
Starting address of
read block
Scaling zero in Data
Array
Scaling max in Data
Array
Scaling zero in
Connected Node
Scaling max in
Connected Node
One of the node names
specified in “Client Node
Descriptor” above