This page has specific information related to OmronCIP Communication Driver. For a generic explanation of Device Module, Channels, Nodes, and Points configuration, please refer to the reference guide.
On this page:
Table of Contents maxLevel 3 style none
Summary
Communication Driver Information | |
|---|---|
Driver name | OmronCIP |
Implementation DLL | T.ProtocolDriver.OmronCIP.dll |
PLC types supported | NX-Series (tested with NX102-9020) |
Manufacturer | OMRON |
Protocol | OmronCIP (CIP over TCP/IP) |
Interface | TCP/IP |
PC Requirements | Ethernet board |
Channels Configuration
Protocol Options
Model: Set the PLC model.
It can be:
NX-Series: For all models in the NX-Series and compatible.
Nodes Configuration
Station Configuration
Stations syntax: <IP > <IP>; <Port > <Port>; <Slot>
Where:
<IP> = IP address of the slave device in the network
< Port > = TCP port where the slave device is listening (default is 44818)
<Slot> = Slot is the Slot number where the CPU is connected.
ExampleNodes Configuration Example
Name | Node Channel | PrimaryStation | SecundaryStation BackupStation | Description |
|---|---|---|---|---|
Node1 | OmronCIP | 192.168.1.101;44818;0 | OmronCIP [OmronCIP Communication Driver] |
Points Configuration
Address Column Configuration
The syntax for the ControlLogix communication points are:
<Type> : <DeviceTagName>
Type: Type is the data type of the Tag in PLC.
The valid type values are:
| Type | Read | Write | Size |
|---|---|---|---|
BOOL | Yes | Yes | 1 bit |
SINT | Yes | Yes | 1 byte or 8 bits |
INT | Yes | Yes | 2 bytes or 16 bits |
DINT | Yes | Yes | 4 bytes or 32 bits |
REAL | Yes | Yes | 4 bytes or 32 bits IEEE Floating point |
LREAL | Yes | Yes | 8 bytes or 64 bits IEEE Floating point |
STRING | Yes | Yes | n bytes |
DeviceTagName: Tag Name in PLC.
Troubleshoot
The status of the driver execution can be observed through the diagnostic tools, which are:
- TraceWindow (with Settings, Device enabled)
- PropertyWatch
- ModuleInformation
The status value of 0 (zero) means communication success. Negative values indicate internal driver error and positive values mean protocol error.
Error Codes
| ErrorCode | Description | PossibleSolution |
|---|---|---|
0 | Success | None |
-100 | Error Sending Message |
|
-101 | Error Sending and Waiting Message | |
-102 … -105 | Error creating TCP/IP connection | |
-106 | Error Receiving Message | |
-112 | Timeout Start Message |
|
-113 | Timeout between Treated Chars | |
-114 | Timeout End Message | |
-115 | Timeout Connect | |
-200 | Protocol Error |
|
-201 | Invalid Protocol |
|
-202 | Invalid Station |
|
-204 | Invalid Message Sequence |
|
> 0 | CIP Error | See CIP error codes table |
CIP Error Codes
The following error codes are in decimal.
| Error Code | Description |
|---|---|
1 | Connection Failure. |
2 | Insufficient resources. |
3 | Value invalid. |
4 | IOI could not be deciphered or tag does not exist. |
5 | Unknown destination. |
6 | Data requested would not fit in response packet. |
7 | Loss of connection. |
8 | Unsupported service. |
9 | Error in data segment or invalid attribute value. |
10 | Attribute list error. |
11 | State already exists. |
12 | Object model conflict. |
13 | Object already exists. |
14 | Attribute not settable. |
15 | Permission denied. |
16 | Device state conflict. |
17 | Reply will not fit. |
18 | Fragment primitive. |
19 | Insufficient command data / parameters specified to execute service. |
20 | Attribute not supported. |
21 | Too much data specified. |
26 | Bridge request too large. |
27 | Bridge response too large. |
28 | Attribute list shortage. |
29 | Invalid attribute list. |
30 | Embedded service error. |
31 | Failure during connection. |
34 | Invalid reply received. |
37 | Key segment error. |
38 | Number of IOI words specified does not match IOI word count. |
39 | Unexpected attribute in list. |
In this driver is very important to enable the TraceWindow messages, as invalid addresses can cause all the communication block with the PLC to fail, the TraceWindow tool (when Device is enabled on the settings) will display the first invalid address found on the block.
In order to have a quick view on the many communication blocks, open the ModuleInformation, navigate on the tree to find OmronCIP and them select the Read Groups. Looking at the number and success and fail communication counters, you can easily identify if there is a block with error and then use the TraceWindow to locate the wrong address.
Solution OmronCIP Driver -200 Fault
Using the OmronCIP driver to communicate with an Omron NX-102 PLC.
Decrease the value of your MaxSimultaneousConnections property, if it's settet as 5, you can try decrease to 4 or 3. Besides that, you can try to decrease value of NodeConnections too. These properties can be found in Edit > Devices > Channels > Settings, like the image bellow:
Add value 3 to retry property, in Edit > Devices > Channels > Timeout, like the image bellow:
In this section...
| Page Tree | ||||
|---|---|---|---|---|
|