Devices Using DF1 Protocol (SLC, PLC5)
No custom settings are required.
On TCP/IP settings, you can optimize communication using the field:
NodeConnections: Defines the maximum number of parallel requests that will be sent to each node (asynchronous communication)
Stations syntax: <IP > ; <Port >
Where :
<IP> = IP address of the slave device in the network
< Port > = TCP port where the slave device is listening (default is 2222)
Example: 192.168.1.101; 2222
The syntax for the PLC communication points is: <File Type><Element Number> : <Address>
The valid values for File Type are:
DF1Ethernet Driver File Types | ||||||
|---|---|---|---|---|---|---|
File | Read | Write | Bit Read | Bit Write | Data Type | Address size |
N Integer | Yes | Yes | Yes | Yes | Word | 2 bytes |
B Binary | Yes | Yes | Yes | Yes | Word | 2 bytes |
F FloatPoint | Yes | Yes | Yes | Yes | Single | 4 bytes |
O OutputLogical | Yes | Yes | Yes | Yes | Word | 2 bytes |
I InputLogical | Yes | - | Yes | - | Word | 2 bytes |
The Address field accepts an optional trailing token that controls how the driver handles byte ordering for numeric file types. Syntax:
<File Type><File Number> : <Address> [ : <DF1LittleEndian> ]
Where <DF1LittleEndian> is true or false (case-insensitive). The Address grid in the Designer exposes this as a checkbox column.
DF1LittleEndian Field | |
|---|---|
Value | Behavior |
true (default) | The driver automatically applies DF1 little-endian byte ordering for numeric types. The point’s ByteSwap modifier is ignored. This is the legacy behavior — existing addresses without the optional trailing token behave as if |
false | The driver does not apply its built-in byte ordering. The point’s ByteSwap modifier controls byte ordering directly: when ByteSwap is checked, the bytes are swapped; when unchecked, the bytes are passed through as received. Use this when the device delivers the value in the opposite endianness from what the default DF1 interpretation expects. |
When to set DF1LittleEndian to false. The default (true) is correct for the overwhelming majority of SLC and PLC5 deployments. Disable it only when an integration has confirmed (via oscilloscope, packet capture, or an Excel cross-check against the device documentation) that the standard DF1 byte order produces incorrect numeric values for a specific data file or device firmware variant. Once disabled, set the point’s ByteSwap modifier on the Devices » Points editor to choose the desired byte order.
Examples
Address | Result |
|---|---|
| Legacy form, equivalent to |
| Explicit default. Same behavior as |
| Float read where the point’s ByteSwap modifier on the Points editor controls byte ordering directly. |
| Binary bit read with manual ByteSwap control. |
Backwards compatibility. The optional token is back-compat-safe. Any existing address that does not end in true or false — including sub-element forms such as T4:0.ACC or C5:0.PRE — parses unchanged through the legacy path.
DF1Ethernet Driver Revision History | |
|---|---|
Version | Notes |
1.4.0.3 | Initial release on new documentation standards |
1.4.0.4 | Added optional 7th address field DF1LittleEndian (default |