This document has only the specific information about the device connection settings and its address syntax.
Refer to the User Guide for more information on the Device Module.
On this page:
Modbus driver implements communication with PLC and IO devices compatible with 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 Information | |
---|---|
Driver name | ControlExpert |
Assembly Name | T.ProtocolDriver.ControlExpert |
Assembly Version | 1.7.0.0 |
Available for Linux | False |
Devices supported | PLC's Quantum, Momentum M340 and M580 - Schneider-Electric |
Manufacturer | Schneider-Electric |
Protocol | MODBUS RTU, ASCII and TCP |
Interface | TCP/IP and Serial |
PC Requirements | Standard PC Ethernet interface board, RS485 or RS232 port |
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 250, the driver can create the internal groups with 125 Registers or 2000 Coils.
Encoding: Determines how the information will be packed into the message fields and decoded. The options are:
Serial and MultiSerial channels:
Set the other fields according to your Serial or MultiSerial port configuration
TCP/IP channels:
Serial channels:
E.g.: 1
MultiSerial channels:
Where:
E.g.: com1 ; 1
TCP/IP channels:
Where :
E.g.: 192.168.1.101 ; 502 ; 1
The syntax for the UnityPro communication points is: <Operand><Address>
Where:
Operand |
---|
0 – %Q or %M - Coils |
1 – %I - Input Status |
3 – %IW - Input Registers |
4 – %MW - Holding Registers |
For more information about the valid operands, see the Supported Operands table aforementioned.
E.g.: 400001 (Operand = 4 (%MW), Address = 1)
Modbus protocol error codes | ||
---|---|---|
Error | 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. |
UnityPro Revision History | |
---|---|
Version | Notes |
1.7.0.0 | Initial release on new documentation standards. |