The CTC driver implements communication with controllers compatibles with the CTC Binary Protocol.
Communication Driver Name: CTC
Implementation DLL: T.ProtocolDriver.CTC.dll
Protocol: Binary
Interface: TCP/IP and Serial
PLC Types Supported: 5200 controller or any compatible
Supported Operands:
| Operand | Read | Write | Data Type | Address Size |
|---|
| R - Register | Yes | Yes | DWord | 4 bytes |
| AO - Analog Output | Yes | Yes | Word | 2 bytes |
| AI - Analog Input | Yes |
| Word | 2 bytes |
| F - Flag | Yes | Yes | Bit | 1 bit |
| DI – Digital Input | Yes |
| Byte | 8 bits |
| DO – Digital Output | Yes | Yes | Byte | 8 bits |
Channel Configuration
Settings
Serial channels:
Default configuration for RTU mode:
- DataBits: 8
- StopBits: 1, if parity is used. 2, if parity is not used
Set the other fields according to your Serial port configuration
TCP/IP channels:
NodeConnections: Defines the maximum number of parallel requests that will be sent to each node (asynchronous communication)
Node Configuration
Station Configuration
TCP/IP channels:
Station syntax: <IP address>
Where:
- <IP address> = The IP address of the slave controller
Ex: 192.168.1.101
Point Configuration
The syntax for the CTC communication points is: <Type><Number>
Where:
- <Type> indicates the memory area. The valid values are:
- R for Register
- AO for Analog Output
- AI for Analog Input
- F for Flag
- DI for Digital Input
- DO for Digital Output
For more information about the valid types, see Supported Operands.
- <Number> indicates the data address in the memory area, from 1 to 65535
E.g.: R10 (Type= Register, Number= 10)
Troubleshoot
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.
