Use this page as a quick reference for the communication drivers used in our control systems. This document is written for operators, field technicians, and integrators who need to understand what each driver is for, how it is typically configured, and what the main settings mean in day-to-day work.

The examples below are based on the driver names and block format typically seen in our system configuration. Site values such as IP address, baud rate, port name, and slave address will vary by project, but the overall format is usually the same

The driver blocks below show how communication settings are stored in the workbook. Each block defines how the system talks to one device or one communication path. The driver name identifies the communication section, and the settings below it define the protocol, address, serial settings, or port information needed to make communication work.

Driver Name
Examples: VFD1,InfluentPLC,GeneratorPLC,TempHumiditySensor,MicrologixPLC

This is the name of the communication block in the Tag map. Each driver gets a worksheet that matches its name. Tags defined on that worksheet are created on the referenced driver. This can be whatever you would like to call the device just as long as it matches the excel page name, but try to name it something meaningful.

Driver Type
Examples: ModbusRTU, ModbusTCP, EthernetIP MicroLogix, EthernetIP ControlLogix, DF1

This tells the system which communication protocol and device type to use. Driver type must match device settings and wiring. If it doesn't communication will fail and an alarm will be generated.

Address
Examples: 192.168.0.23, 192.168.1.101

This is the IP address of the Ethernet device the driver communicates with. It is used on Ethernet-based drivers such as Modbus TCP and Ethernet/IP.

Port
Example: 502

This identifies the communication port for Modbus TCP drivers. The default Modbus port is 502.

Slave Address
Examples: 1, 2, 255

This is the device address used by the protocol. For Modbus RTU, it is the slave address on the serial bus. For Modbus TCP, it is the unit ID when needed. For DF1, it is the PLC or node address used by the driver.

Baudrate
Example: 9600, 19200, 38400, 57600, 115200

This is the serial communication speed. It must match the device exactly or the driver will not be created.

PLCFormat
Example: 8-N-1, 8-E-1, 8-O-1

This is the serial framing, meaning data bits, parity, and stop bits. It must match the connected device exactly.

• Data bits - How many data bits are used per transmitted byte

• Parity - Is an optional basic error-checking bit. N means no parity bit is sent; E adds a bit so the total number of 1 bits is even; O adds a bit so the total number of 1 bits is odd.

• Stop bits - Mark the end of each serial data character and help the receiving device stay synchronized.

PLCUSBPort
Example: usbBackLeft, usbBackRight, usbFrontRight, usbFrontCenter, usbFrontLeft

This identifies which USB serial interface is used for the connection. If the wrong physical port is selected, the driver will not be talking to the device you expect.

Extended
Example: n, y

This setting controls whether the driver uses the standard Modbus register map or the extended Modbus register map.

• n = Use the standard register map.

• y = Enable extended registers and the extended register map.

Use y only when the connected device or site tag map is configured to use extended Modbus registers. Otherwise, use n.

For a Modbus master/client, this determines which available tag/register mapping the driver uses. For a Modbus RTU Slave or Modbus TCP Server, it allows the system to expose mapped values using extended registers.ModbusDevice.h+2

Open