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 or on UNS TagProvider Connections.
On this page:
Summary
Communication Driver Information | |
|---|---|
Driver name | LCP IC - Local Control Panel Interface Control |
Assembly Name | T.ProtocolDriver.LCP_IC.dll |
Assembly Version | 1.0.0.0 |
Available for Linux | False |
Protocols | EIA-232, EIA-422, TIA/EIA-485, RS-232/422 |
Max number of Nodes | User defined |
Interface | Serial |
Protocol | TCP/IP |
PC Requirements | Standard PC Serial ports, Ethernet port |
Configuration
All initial configurations for devices in the solutions on the software platform encompass the following workflow:
Defining a Channel using a target communication Protocol creates the base instance for linking a Node. Learn more at Devices - Channels.
Defining the Node linked to the created Channel. Learn more at Devices - Nodes.
Defining the Point that you would like to monitor. Learn more at Devices - Points.
Protocols define communication rules between the platform and devices. Channels define global parameters for using a communication protocol. Nodes represent physical field devices (like a PLC) with a unique field address (PrimaryStation). Points represent tags within a device. Additionally, AccessType defines how the device interacts with the platform (Read and/or Write). Learn more at Devices - AccessType.
Channels
Settings
| Baud Rate | Data Bits | Stop Bits | Parity | DTR | RTS | CTS |
|---|---|---|---|---|---|---|
1200 | 8 | 1 | Even | Off | Off | Off |
Nodes
Primary Station
Not used in this Driver.
Points
Available types:
| Type | Read | Write | DataType |
|---|---|---|---|
I - Indicator |  | - | Native(Bit) |
C - Control | - | | Native(Bit) |
U - Update | - | | Native(Bit) |
The Update Type is utilized to periodically refresh the buffer, and it requires configuration with a user-defined time trigger:
Troubleshoot
The status of the driver 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 where the status 0 (zero) means success. Negative values are internal error codes and positive values are protocol error codes.
Driver Revision History
LCP IC Driver Revision History | |
|---|---|
Version | Notes |
1.0.0.1 | Initial release on new documentation standards. |
1.0.0.0 | Initial version published on May, 16th 2023. |
In this section: