EIP Ethernet/ip driver connection error

Discussions about product bugs & problems!
Note: This is no replacement for the Official ETM Support!
Search

Post Reply
3 posts • Page 1 of 1
imhht1311
Posts: 8
Joined: Tue Mar 17, 2020 12:05 am

EIP Ethernet/ip driver connection error

Post by imhht1311 » Fri Mar 27, 2020 4:56 am

I tried to communicate OMRON PLC using EIP Ethernet/IP Driver.

Two programs are same config.
example) Device driver is Allen-Bradley ControlLogix Ethernet, same IP address, same Slot number, same tag address

When Trying to communicate OMRON PLC using Kepware program, I received "Success: Connection Manager - Forward Open"
but When Trying to communicate OMRON PLC using WINCC OA program, I received "Connection failure: Connection Manager - Forward Open"

I want to communicate OMRON PLC using EIP Ethernet/IP Driver.

I used 'CJ2H-CPU64-EIP'

WINCC OA Version is 3.14 patch 31

Please Help me.
Attachments
Kepware_wireshark.PNG
WINCC OA CONFIG.JPG
WINCC OA_wireshark.JPG

User avatar
leoknipp
Posts: 2206
Joined: Tue Aug 24, 2010 5:28 pm

Re: EIP Ethernet/ip driver connection error

Post by leoknipp » Fri Mar 27, 2020 7:50 am

Please check the PVSS_II.log file for this project if an error is reported for the EIP driver when trying to establish the connection to the device.

Best Regards
Leopold Knipp
Senior Support Specialist

imhht1311
Posts: 8
Joined: Tue Mar 17, 2020 12:05 am

Re: EIP Ethernet/ip driver connection error

Post by imhht1311 » Fri Mar 27, 2020 8:09 am

I checked PVSS_II.log.
It said that "Connection error, EipStackWrapper, Stack error, *ERROR* Failed to start connected-mode session. Err: CIP Error 0X001: Connection Failure"

So, I used -dbg 2 try to find error.

WCCOAeip (99), 2020.03.27 17:07:09.165, IMPL, SEVERE, 63, Connection error, EipStackWrapper, Stack error, *ERROR* Failed to start connected-mode session. Err: CIP Error 0x0001: Connection Failure
WCCOAeip99:>> "Operation: Echo, Type: Logix, TagCount: 0"
WCCOAeip99:WCCOAeip (99), 2020.03.27 17:07:09.145, WORK, EipPlc::sendRequest (Echo) to EIP_TEST in state 3
WCCOAeip99:WCCOAeip (99), 2020.03.27 17:07:09.146, WORK, EipPlc::updateConnState(4)
WCCOAeip99:WCCOAeip (99), 2020.03.27 17:07:09.146, WORK, EipPlc::ProcStateChange(EIP_TEST): Registering session
WCCOAeip99:WCCOAeip (99), 2020.03.27 17:07:09.156, WORK, EipPlc::ProcStateChange(EIP_TEST): Busy
WCCOAeip99:WCCOAeip (99), 2020.03.27 17:07:09.156, WORK, EipPlc::ProcStateChange(EIP_TEST): Ready
WCCOAeip99:WCCOAeip (99), 2020.03.27 17:07:09.156, WORK, EipPlc::updateConnState(2)
WCCOAeip99:WCCOAeip (99), 2020.03.27 17:07:09.164, WORK, EipHWService::generalQuery called for PLC "EIP_TEST"
WCCOAeip99:WCCOAeip (99), 2020.03.27 17:07:09.164, WORK, EipPollGroup::EipPollGroup(0)
WCCOAeip99:WCCOAeip (99), 2020.03.27 17:07:09.164, WORK, EipPollGroup::~EipPollGroup("")
WCCOAeip99:WCCOAeip (99), 2020.03.27 17:07:09.187, WORK, EipPlc::ProcStateChange(EIP_TEST): Disconnect request from stack
WCCOAeip99:WCCOAeip (99), 2020.03.27 17:07:09.188, WORK, EipStackWrapper::disconnect(): plc="172.16.14.210"
WCCOAeip99:WCCOAeip (99), 2020.03.27 17:07:09.188, WORK, EipPlc::ProcStateChange(EIP_TEST): Busy
WCCOAeip99:WCCOAeip (99), 2020.03.27 17:07:09.188, WORK, EipPlc::ProcStateChange(EIP_TEST): No active session
WCCOAeip99:WCCOAeip (99), 2020.03.27 17:07:09.189, WORK, EipStackWrapper::disconnect(): plc="172.16.14.210"
WCCOAeip99:WCCOAeip (99), 2020.03.27 17:07:09.189, WORK, EipPlc::updateConnState(3)
WCCOAeip (99), 2020.03.27 17:07:11.179, SYS, INFO, 0, , EipPlc, ConnEstablished, Established connection to plc EIP_TEST

and then, I compared between WINCC OA's Packet and Kepware's Packet using Wireshark.

Post Reply
3 posts • Page 1 of 1