The Modbus driver implements communication with PLC and IO devices that are compatible with the Modbus Open Standard protocol. It operates as a Master on TCP/IP or serial networks. The communications blocks are dynamically created according to the pooling cycle defined on the AccessType for each Device Point.
Communication Driver Name: UnityPro
Current Version: 1.1
Implementation DLL: T.ProtocolDriver.UnityPro.dll
Protocol: MODBUS RTU, ASCII, and TCP Interface: TCP/IP and Serial
PLC types supported: PLC's Quantum, Momentum M340 and M580 - Schneider-Electric
Communication block size: User configurable. Default is 250
Protocol Options: Message Format (ASCII, RTU, or RTU TCP). Use the block write command (0x0F or 0x10) or the single write command (0x05 or 0x06) for single writings
Multi-threading: User configurable. Default is five threads to each network node
Max number of nodes: User defined
PC Hardware requirements: Standard PC Ethernet interface board, RS485 or RS232 port
Supported Operands:
| Operand | Read | Write | Data Type | Address Size |
|---|---|---|---|---|
| 0 – %Q or %M - Coils | Yes | Yes | Bit | 1 bit |
| 1 – %I - Input Status | Yes | Bit | 1 bit | |
| 3 – %IW - Input Registers | Yes | Word | 2 bytes | |
| 4 – %MW - Holding Registers | Yes | Yes | Word | 2 bytes |
BlockSize: Defines the maximum amount of items per group. The default value is 250
If the communication points are configured in sequence and the BlockSize equals to 250, the driver can create internal groups with 125 Registers or 2000 Coils
Encoding: Determines how information will be packed into the message fields and decoded. The options are:
SingleWrite: Indicates the behavior of the driver for the writings with only one item:
Serial and MultiSerial channels:
Default configuration for the ASCII mode:
Default configuration for the RTU mode:
Set the other fields according to your Serial or MultiSerial port configuration
TCP/IP channels:
NodeConnections: Defines the maximum number of parallel requests that will be sent to each node (asynchronous communication)
SlaveId: Set this field with the address of the slave device in the network. They can be addressed from 1 to 247 for serial nodes or 0 to 255 for TCP/IP nodes. 0 is used for the broadcast
Serial channels:
Ex: 1
MultiSerial channels:
<Com Port> = The serial port number
Ex: com1;1
TCP/IP channels:
<IP address> = The IP address of the slave device in the Modbus network
<Port number> = The TCP port where the slave device is listening (default is 502)
Ex: 192.168.1.101;502;1
The syntax for the UnityPro communication points is: <Operand><Address>
Where:
0 (%Q or %M) for Coils
1 (%I) for Input Status
3 (%IW) for Input Registers
4 (%MW) for Holding Registers
For more information about the valid operands, see Supported Operands.
Ex: 400001 (Operand = 4 (%MW), Address = 1)
The status of the driver's execution can be observed through the diagnostic tools, which are:
• Trace window
• Property Watch
• Module Information
The above tools indicate if the operations have succeeded or have failed. A status of 0 (zero) means communication is successful. Negative values indicate internal driver errors, and positive values indicate protocol error codes.
| Term | Name | Description |
|---|---|---|
| 1 | ILLEGAL FUNCTION | The function code received in the query is not allowable |
| 2 | ILLEGAL DATA ADDRESS | The data address received in the query is not allowable |
| 3 | ILLEGAL DATA VALUE | A value contained in the query data field is not allowable |
| 4 | SLAVE DEVICE FAILURE | Error while attempting to perform the requested action |
| 5 | ACKNOWLEDGE | Request accepted, but a long duration of time will be required |
| 6 | SLAVE DEVICE BUSY | The slave is engaged in a long–duration program command |
| 7 | NEGATIVE ACKNOWLEDGE | Cannot perform the program function received in the query |
| 8 | MEMORY PARITY ERROR | Parity error in the extended memory |