Eipc Client Protocol
Tags that are created from AB PLC and imported in Cscapevia "Import Tags from L5K File" option, can be viewed and verified using this protocol.
Note: Please refer to Cscape help for procedure on importing tags to Cscape.
Cscape Configuration
In order to verify if the tags are imported or not, select the Protocol Configuration from the Programs menu in Cscape configurator. Select the appropriate protocol type. To make sure that the Software is able to configure the equipment for the correct protocol, ensure the EipcClient.dll file is in the Ethernet Protocols directory of the current working/opened configurator.
Network Configuration
After selecting the desired protocol, click on Network button which opens Network Config window as shown:
Configure the status register and click on OK. No other changes are required.
Device Configuration
After network configuration select "Devices" which opens up Device List window as shown:
Here the added device with IP Address from L5k is displayed.
Note: In Devices List, Add button will be disabled.
Scan List
Click on the Scan List button, here the imported tags with the assigned registers are displayed as shown:
Note: In Scan List, Add, Config and Edit Names buttons will be disabled.
Network Communication Errors
In order to access the Network statistics, user must assign the “Network status register” in network configuration. The table below gives the details of statistics.
| Number | Statistics | Location | Description |
|---|---|---|---|
| 1 | Update interval exceeded count | %Rx |
This register explains number of times that the actual transaction scan time to complete all transactions exceeded specified update interval. Generally used as an indicator that an excessive number of triggered transfers or failed communication retries are occurring that is lengthening the expected transaction scan time. If the Update interval is set to zero (update as fast as possible), this 32-bit register alternately specifies the actual transaction scan time in mSec resolution. |
| 2 | No response count | %R(x+2) | This register explains number of times that a device(s) did not respond to a transaction. This includes ALL failed transaction, not just those after the retry count is exceeded. |
| 3 | Corrupt response count | %R(x+4) | This register explains number of times that a device(s) returned an invalid or failed response to a transaction. This includes ALL failed Transaction, not just those after the retry count is exceeded. |
| 4 | Valid response count | %R(x+6) | This register explains total number of valid responses. |
Note: %Rx: 32-bit network status register configured in Network configuration.
Device Communication Errors
| Error | Error Number | Description |
|---|---|---|
| ENET_LINK | 40 | Ethernet Link is down |
| NODE_OFFLINE | 45 | Node is offline |
| INVALID_BLOCK | -203 | Invalid size for data type. |
| NO_RESPONSE_FROM_PLC | -204 | Timeout while waiting for remote node response. (Device is connected to Slave node but not responding to Modbus queries) |
| INVALID_RESPONSE_FROM_PLC | -205 | Corrupted response from remote node. |
| INVALID_INITIALISATION | -207 | Internal Error - Unable to open port. |