The Siemens TIWAY I driver allows the FieldServer to transfer data to and from devices
over RS-
emulate either a Server or Client.
Max Nodes Supported
Client 1 Only 1 client node allowed
Server 254 Up to 254 secondary PLCs
The FieldServer Siemens TIWAY I driver, hereafter simply referred to as the TIWAY driver,
can be used to emulate the host side of a Siemens Unilink Host Adaptor (UHA) using BDLC
“Host Command Protocol”. The original Siemens UHA device was used to interface other
host devices to a TIWAY I network as shown below:
232C using TIWAY BDLC “Host Adapter Command” protocol. The FieldServer can
FieldServer Mode Nodes Comments
The original Siemens UHA is really a protocol bridge in itself. It speaks “Host Command
Protocol” on the host interface which may contain embedded TIWAY primitives (commands)
and speaks Siemens TIWAY I protocol on its secondary interface. The FieldServer TIWAY I
driver emulates the UHA’s host interface when used in the server mode, however the
FieldServer does not speak Siemens TIWAY protocol and therefore cannot be used to
connect to legacy TIWAY devices directly. The driver’s use is primarily as a server to allow
legacy SCADA systems speaking “Host Command Protocol” containing TIWAY primitives to
communicate with modern PLCs speaking Modbus or other industrial protocols. The
accompanying FieldServer client driver in a configuration setup will typically be Modbus or
some other industrial protocol. The TIWAY driver’s use as a client is limited to emulating a
host to a UHA or for testing purposes.
The TIWAY driver operates in the Master Host Interface Unit ( MHIU ) mode and only
supports a limited selected set of Host Adapter commands and TIWAY primitives which are
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
The FieldServer is connected to the SCADA system as shown below.
Configure the SCADA system according to manufacturer’s instructions.
3.1. Hardware Connection Tips / Hints
To be updated from testing feedback.
4. Configuring the FieldServer as a TIWAY Client
For a detailed discussion on FieldServer configuration, please refer to the FieldServer
instruction
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 TIWAY Server. The driver is normally used in the server
mode, but may be configured as a client for testing purposes.
Configuration mManual. The information that follows describes how to expand
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 TIWAY 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
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
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, AWT
FS-8700-31 Siemens TIWAY I Page 6 of 23
4.4.2. Driver Related Map Descriptor Parameters
Section Title
Map Descriptors
Column Title Function Legal Values
One of the node names
specified in “Client Node
Descriptor” above
A list of PLC memory
addresses that may be
used for random read
and writes
A list of preset step
values to be used with
the Drum_Count_Preset
datatype. Each value is
tied to an address.
addresses to be used
with the Connect_ and
Disconnect_Secondaries
host adapter commands.
Starting address of read
or write block
Report_NM_Config
Soft_Reset
Reset_Adapter
Disconnect_Secondaries
Connect_Secondaries
0-65535
0-255 for loop datatypes and
Drum_Count_Preset
Maximum of 80 space
seperated values allowed.
0-255
Maximum of 80 space
seperated values allowed.
1-255
255 indicates all secondaries
from 1 to 254
0-65535
0-255 for loop datatypes and
Drum_Count_Preset
4.4.3. Timing Parameters
Section Title
Map Descriptors
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
The above map descriptor will continuously read 10 data elements starting from address 0 of type “IE_Ladder” from
PLC_01. The data will be stored in the data array called “RAW16_Data” from an offset of 0.
4.4.4.2. Reading data from random PLC data memory locations
The above map descriptor will continuously read 2 data elements from address 5 and 9 of type “Variable” from
PLC_01. The data will be stored in the data array called “RAW16_Data” from an offset of 10. The data will be
stored at offsets 10 and 11.
4.4.4.3. Reading Drum_Count_Preset data from contiguous PLC data memory locations
The above map descriptor will continuously read 5 data elements from addresses 0-4 of type
“Drum_Count_Preset” from PLC_01. The Preset Steps associated with addresses are (address 0):5, (address 1):8,
(address 2):9, (address 3):33, and (address 4):49. The data will be stored contiguously in the data array from offset
70.
4.4.4.4. Reading Drum_Count_Preset data from random PLC data memory locations
The above map descriptor will continuously read 2 data elements from addresses 5 and 9 of type
“Drum_Count_Preset” from PLC_01. The Preset Steps associated with addresses are (address 5):42 and (address
9):22. The data will be stored in the data array at offset 75 and 76.
The above map descriptor will continuously read the three status values from PLC_01. The status values are
defined as follows and will be stored in the data array contiguously from an offset of zero:
Status element 1 (DD) : Operational Status
Status element 2 (EE) : Auxiliary power source status
Status element 3 (FF) : NIM Operational Status
Please refer to the TIWAY systems manual for operational values and their meanings.
4.4.5. Writing TIWAY data map descriptor examples
4.4.5.1. Writing data to contiguous PLC data memory locations
The above map descriptor will continuously write data of type “Control_Register” to 10 PLC data memory
addresses. The data to write will be collected from the data array “RAW8_Data” from an offset of 20.
4.4.5.2. Writing data to random PLC data memory locations
The above map descriptor will continuously write data of type “Loop_Gain” to 2 PLC data memory addresses of 5
and 9. The data to write will be collected from the data array “FLOAT_Data” from offsets 0 and 1.
4.4.5.3. Writing the same value to a block of contiguous PLC data memory locations
The above map descriptor will continuously write data of type “Drum_Count_Preset” to 5 PLC data memory
addresses. The data to write will be collected from the data array “RAW16_Data” from an offset of 70. The Preset
Steps associated with the addresses are (address 0):5, (address 1):8, (address 2):9, (address 3):33, and (address
4):49.
4.4.5.5. Writing Drum_Count_Preset data to random PLC data memory locations
The above map descriptor will continuously write data of type “Drum_Count_Preset” to 2 PLC data memory
addresses. The data to write will be collected from the data array “RAW16_Data” from an offset of 70 and 71. The
Preset Steps associated with the addresses are (address 5):33 and (address 9):49.
A number of map descriptors that send specific host adapter commands are available mainly for testing purposes
and should not be used under normal circumstances.
4.4.6.1. Read Secondary Log
Returns a list of secondary PLC stations addresses that are connected.
The above map descriptor will continuously execute the indicated host adapter command and will store the list of
connected secondary PLCs in the data array “Secondary Log” from an offset of 0. Offset 0 will correspond to
secondary address 1, offset 1 to secondary 2 up to offset 253 corresponding to secondary address 254.
4.4.6.2. Report HIU Configuration
Reports the HIU Configuration option values that was used to configure the HIU.
The above map descriptor will continuously execute the indicated host adapter command and will store the
following parameter values in the data array “HIU_Config”:
Offset Parameter
0 Dipswitch 1 and 2 settings
1 Config flag ( 0 = HIU not configured, 1 = HIU configured )
2 Option 01 configuration value
3 Option 02 configuration value
4 Option 03 configuration value
4.4.6.3. Report Adapter Configuration
Reports the Adapter Configuration option values that was used to configure the adapter.
The above map descriptor will continuously execute the indicated host adapter command and will store the
following parameter values in the data array “Adapter_Config”:
Offset Parameter
0 Dipswitch 1 and 2 settings
1 Config flag ( 0 = Adapter not configured, 1 = Adapter configured )
2 Option 01 configuration value
3 Option 02 configuration value
4 Option 03 configuration value
5 Option 04 configuration value
4.4.6.4. Report Network Manager Configuration
Reports the Network Manager option values that was used to configure the network manager.
The above map descriptor will continuously execute the indicated host adapter command and will store the
following parameter values in the data array “Nm_Config”:
Offset Parameter
0 Dipswitch 1 and 2 settings
1 Config flag ( 0 = Network Manager not configured, 1 = Network Manager configured )
2 Option 01 configuration value
3 Option 02 configuration value
4 Option 03 configuration value
5 Option 04 configuration value
6 Option 05 configuration value
7 Option 06 configuration value
8 Option 07 configuration value
9 Option 08 configuration value
10 Option 09 configuration value
11 Option 0A configuration value
12 Option 0B configuration value
13 Option 0C configuration value
14 Option 0D configuration value
15 Option 0E configuration value
4.4.6.5. Soft Reset
Forces the UNILINK Host Adapter to do a software reset.
The above map descriptor will execute the indicated host adapter command once every time a value is written to
the data array “Cmd_Triggers” at offset 0.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
The above map descriptor will execute the indicated host adapter command once every time a value is written to
the data array “Cmd_Triggers” at offset 1.
The above map descriptor will execute the indicated host adapter command once every time a value is written to
the data array “Cmd_Triggers” at offset 2. Secondaries 1 9 147 and 254 will be disconnected from the network.
To disconnect all secondaries, use only one value of 255 in the Secondaries_List field.
The above map descriptor will execute the indicated host adapter command once every time a value is written to
the data array “Cmd_Triggers” at offset 4. Secondaries 1 9 147 and 254 will be connected to the network.
To connect all secondaries, use only one value of 255 in the Secondaries_List field.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web:www.fieldserver.com
For a detailed discussion on FieldServer configuration, please refer to the FieldServer
instruction
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 TIWAY Client.
The configuration file tells the FieldServer about its interfaces, and the routing of data
required. In order to enable the FieldServer for TIWAY 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.
Configuration mManual (Virtual PLC). The information that follows describes how
5.3.1. FieldServer Specific Map Descriptor Parameters
Section Title
Map Descriptors
Column Title Function Legal Values
Map_Descriptor_Name Name of this Map Descriptor
Name of Data Array where
Data_Array_Name
Data_Array_Offset
Function
Server_Hold_Timeout*
data is to be stored in the
FieldServer
Starting location in Data
Array
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)
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
>1.0s
5.3.2. Driver Specific Map Descriptor Parameters
Section Title
Map Descriptors
Column Title Function Legal Values
One of the node names
specified in “Client Node
Descriptor” above
The above map descriptor serves 4 data elements starting from address 0 of type “Drum_Count_Preset” for
PLC_01. Each address location is contiguously associated with a preset step value from the Preset_Step_List field.
5.3.5. Serving PLC status data map descriptor example