The Spectronics driver allows the FieldServer to transfer data to and from devices over either
RS-232 or RS-485 using Spectronics protocol. The FieldServer can emulate either a Server or
Client.
The information that follows describes how to expand upon the factory defaults provided in the
configuration files included with the FieldServer.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
4. Configuring the FieldServer as a Spectronics 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 FS).
This section documents and describes the parameters necessary for configuring the FieldServer
to communicate with a Spectronics 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 Spectronics 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.
Data Array can only take on
one format.
Number of Data Objects. Must
be larger than the data
storage area required by the
map descriptors for the data
being placed in this array.
Up to 15 alphanumeric
characters
FLOAT, BIT, UInt16, SInt16,
Packed_Bit, Byte,
Packed_Byte, Swapped_Byte
1-10,000
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
4.4.1. FieldServer Related 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 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
4.4.2. Driver Related Map Descriptor Parameters
Column Title Function Legal Values
Node_Name
Length Length of Map Descriptor 1-125 (Register,AI)
Address
Data_Array_Low_Scale* Scaling zero in Data Array
Data_Array_High_Scale* Scaling max in Data Array
Node_Low_Scale*
Node_High_Scale*
Name of Node to fetch
data from
Starting address of read
block
Scaling zero in Connected
Node
Scaling max in Connected
Node
One of the node names
specified in “Client Node
Descriptor” above
40001, 30001, etc
-2,147,483,648 to
2,147,483,647, 0
-2,147,483,648 to
2,147,483,647, 100
-2,147,483,648 to
2,147,483,647, 0
-2,147,483,648 to
2,147,483,647, 100
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
FS-8700-42_Spectronics Driver Manual Page 10 of 15
5. Configuring the FieldServer as a Spectronics 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” sample files
provided with the FieldServer).
This section documents and describes the parameters necessary for configuring the FieldServer
to communicate with a Spectronics Client.
The configuration file tells the FieldServer about its interfaces, and the routing of data required.
In order to enable the FieldServer for Spectronics 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
FS-8700-42_Spectronics Driver Manual Page 11 of 15
5.2. Server Side Node Descriptors
Section Title
Nodes
Column Title Function Legal Values
Node_Name Provide name for node Up to 32 alphanumeric characters
Node_ID Node ID of physical server node 1 – 255
Protocol Specify protocol used Spectronics
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 Function Legal Values
Node_Name
Data_Type Data type Register, Coil, AI, DI
Length Length of Map Descriptor 1 - 125
Address
Data_Array_Low_Scale* Scaling zero in Data Array -32767 to 32767, 0
Data_Array_High_Scale* Scaling max in Data Array -32767 to 32767, 100
Node_Low_Scale* Scaling zero in Connected
Node_High_Scale* Scaling max in Connected
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
When writing the default data types can be overwritten using the “Single_Coil” and
“Single_Register” settings as part of the Map Descriptor configuration. In that case the
Function codes for writes will be as follows:
Add a parameter to the Spectronics client side Map Descriptor called Data_Type.
If you specify the Data_Type as Single_Register and the Function as WRBC or WRBX,
then a Spectronics poll with FC 6 will be generated.
Of course Single_Register implies a length of one, and even if you try to set the length
longer in the csv file, the length is limited to 1 in the driver.
Appendix A.3. Write-Thru Operation
Consider a client Map Descriptor that is configured to read data using a FC 3 (Read Multiple
Register) operation. It is now possible do a write thru operation on the existing Client Map
Descriptor by storing data to the Client Map Descriptors Data Array.
The Write Cache Map Descriptor that is created will use the following function codes
depending on the Cache Map Descriptor Length and the Clients Node Type.
Single Register Write - FC 6 - When the length of the Cache Map Descriptor is one. This will
normally be the case.
Multiple Register Write – FC 16 - When the length of the Cache Map Descriptor is larger
than one or the Node_Type has been set to “Block_Mode”.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
FS-8700-42_Spectronics Driver Manual Page 14 of 15
Appendix A.4. Connection to York Modbus Microgateway
If connecting the FieldServer to a York Modbus Microgateway, the Node_ID of the
Microgateway is defined by the address DIP switches. If switch 4 is set to ‘On’ and the other
switches are set to ‘off’ then Node_ID of the Microgateway is ‘247’, the parity is ‘Even’, and
the stop bits are 1. Other Node_ID combinations can be found in the York Modbus
Microgateway Installation Manual.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com