|
Local Control Panels (LCP)
- Name: LCPIC
- Version: 1.0.0.1
- Protocol: Proprietary
- Interface: TCP/IP and Serial/IP
- Runtime: .NET 2.0 (Multiplatform)
- Configuration:
- Devices / Protocols
On This Page:
Overview
The LCP Interface Control driver enables communication with Local Control Panels (LCP) using serial or TCP/IP interfaces. It supports EIA-232, EIA-422, TIA/EIA-485, and RS-232/422 standards, with configurable parameters such as baud rate, data bits, stop bits, parity, and addressing.
Parameter | Value | Explanation |
|---|---|---|
Driver Name | LCPIC | Identifies the driver that manages communication between the Local Control Panel (LCP) and the system. |
Assembly Name | T.ProtocolDriver.LCPIC.dll | Provides the main dynamic-link library (DLL) that implements the driver functionalities. |
Assembly Version | 1.0.0.1 | Specifies the current version of the driver implementation. |
Available for Linux | FALSE | Indicates that the driver supports only Windows operating systems. |
Supported Protocols | EIA-232, EIA-422, TIA/EIA-485, RS-232/422 | Supports serial communication protocols used for point-to-point and multi-point data exchange. Defines:
|
Max Number of Nodes | User defined | Allows users to configure the number of devices based on system limitations and application needs. |
Interface | TCP/IP and Serial | Supports communication via TCP/IP and serial ports, including COM ports and USB-Serial adapters, enabling direct device connection. |
Network Protocol | TCP/IP | Supports data transmission over Ethernet networks using standard TCP/IP protocols. |
PC Requirements | Standard PC Serial ports, Ethernet port | Requires a PC with standard hardware, including serial communication ports or Ethernet connectivity. |
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
Used only in the TCP/IP interface.
Stations syntax: < IP > ; < Port > ; < SlaveID >
Where :
< IP > = IP address of the slave device in the network.
< Port > = TCP port where the slave device is listening (default is 502).
< SlaveID > = Set this field with the address of the slave device in the network.
Example: 192.168.1.1; 502; 1
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: