First time simple connection between OpENer (Windows) and PLC (CompactLogix 5370)

[Luciana Magno de Almeida]

Good afternoon,

I asked the same as below in the github discussion for OpENer project but I realized here is the correct place to ask.

I'm new to OpENer and Ethernet/IP. We have the Volumes from ODVA and software indicated. I have studied OpENer and ODVA but I'm current trying to do a simple connection between PLC and OpENer with no succes. I'm suspecting that I am not running OpENer correctly or configuring the IP Address, if is needed.

I'm using Windows 10 and compiled in folder bin/win32 and I'm using Visual Studio 2022. I'm running in terminal as .\OpENer "Ethernet", I have the PLC in this port and with Studio 5000 I can connect and download normally to the PLC.

For OpENer connection configuration I used the eds file and imported to Studio 5000 and configured the IP Address as the IP of my PC, is this correct?

I'm not sure what data I need to send to help clarify my doubts, please if there is something I need to send, feeel free to say and I'll do it.

Best regards and TIA, Luciana.

[Luciana Magno de Almeida]

For this firts part above, I realized what I need to do, will test at max tomorrow and give a feedback in this post.

Now, my doubt is, we are adapting a pylogix solution for a OpENer solution because we need ODVA certification to present to our client.

In pylogix we have the tags string that we read and write from, using a Class1 and Class3 communication depending on the functionality in our code.

Can we do this also from OpENer? What would be the steps to do this, functions recommended? 

TIA, Luciana.

[martin...@gmail.com]

Hi Luciana,

as far as I understand pylogix its mainly a communication driver for Rockwell PLCs, where EtherNet/IP is a vendor-independent fieldbus, which means there is no notion of tags in EtherNet/IP.

If you want to transport arbitrary payloads, you can use the assembly object, which can be transported with Class1 and Class3 connections.

Not entirely sure how it then works on Studio 5000, but I assume you then link the assembly object data to a data tag which then can be used for your program. So for each tag you would need an assembly object.

If someone knows better, please correct me.

The assembly object is already part of OpENer, so no code needs to be added.

Best regards,

Martin

[Luciana Magno de Almeida]

Hi Martin, thank you for the confirmation.

I will use the assembly object as indicated.

For a initial development I was able to connect OpENer to PLC and run a first Class 3 and then a Class 1 connection with success.

The next step was to run the CT20 from ODVA for certification and the first error is

37 ----------------------------------------------------------------- 38 Encapsulation Testware Revision = 2.01 09/30/2020 39 ----------------------------------------------------------------- 40 41 Start: Encapsulation Test --------------------------------------- 42 Sending 43 Encapsulation Header 63 00 00 00 00 00 00 00 00 00 00 00 AE 20 01 00 00 00 00 00 00 00 00 00 44 Received 45 Encapsulation Header 63 00 31 00 00 00 00 00 00 00 00 00 AE 20 01 00 00 00 00 00 00 00 00 00 46 Command Specific Data 01 00 0C 00 2B 00 01 00 00 02 AF 12 C0 A8 64 79 47 CIP Data 00 00 00 00 00 00 00 00 01 00 0C 00 E9 FD 02 03 60 00 15 CD 5B 07 09 4F 70 45 4E 65 72 20 50 43 00 48 Encapsulation Commands Test 49 50 Start: NOP Test ---------------------------------------------- 51 NOP test without a session 52 NOP(nDataLength = 0) 53 Sending 54 Encapsulation Header 00 00 00 00 00 00 00 00 00 00 00 00 AF 20 01 00 00 00 00 00 00 00 00 00 55 Command Specific Data 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 56 CIP Data 00 00 00 00 00 00 00 00 00 00 57 NOP(nDataLength = 2000) 58 Sending 59 Encapsulation Header 00 00 D0 07 00 00 00 00 00 00 00 00 B0 20 01 00 00 00 00 00 00 00 00 00 60 Command Specific Data 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 61 CIP Data 10 11 12 13 14 15 16 17 18 19 ... 62 NOP(nDataLength = 65511) 63 Sending 64 Encapsulation Header 00 00 E7 FF 00 00 00 00 00 00 00 00 B1 20 01 00 00 00 00 00 00 00 00 00 65 Command Specific Data 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 66 CIP Data 10 11 12 13 14 15 16 17 18 19 ... 67 1> *** Large size Encapsulation Command caused the DUT to close the TCP connection. See requirement in Vol 2 section 2-3.3. 68 RegisterSession

For a simple test to see if I could resolve this issue I changed the size from 512 to 65512 but the error remains.

Does anyone knows how to solve this issue? Any tips?

Best regards, Luciana M.A..

[vivek.ha...@gmail.com]

If you are trying to integrate an OpENer-based device into a Rockwell Logix controller then I recommend you take a look at this document:

https://literature.rockwellautomation.com/idc/groups/literature/documents/pm/1756-pm002_-en-d.pdf

My understanding is that the sample EDS file provided with OpENer is mostly compliant - but I am not entirely certain. You may still need to check / modify the EDS.

In terms of the question of tags - Logix can make use of the parameters you define in your EDS - if you have an EDS key. These are issued on a case-by-case basis by Rockwell. For details, see here - https://rockwellautomation.custhelp.com/app/answers/answer_view/a_id/1061418/loc/en_US#__highlight

Regards

Vivek

[Luciana Magno de Almeida]

Good evening all,

Thanks for all the repplies, for the tags we decided to adapt our code to using indexes and not tags so we don't have security issues. Thanks vivek for the information and the link, it was of great help.

Now we are in the developing fase of adjusting and correcting the network configuration to pass the CT20 test. But we have encounter to many error messages and would like to ask for help. We received a lot of errors message and I'm trying to work in a sequence, a few issues at a time.

1 - The report indicated that we configure LLPD. ODVA sent us a LLPD mib file but how do I use this to achieve what is needed certification wise? Message "EtherNet/IP Devices undergoing certification for the first time and multi-port devices receiving an update that adds CIP functionality are required to implement LLDP protocol and LLDP Management Object starting from May 2022."

2 - Another message is about the "return to factory defaults". Any suggestion on how to fix this error?

"1> *** User skipped Identity Instance "Return to Factory Defaults" (Type 1) Reset service.  This test is required and must be run at least once in order to pass the conformance test."

Thanks in advance and thanks also for the patience in the responses and all the care this communit is giving.

Best regards, Luciana Almeida.

[Luciana Magno de Almeida]

Good evening,

Concerning the (2) topic I was able to do this setting in the ODVA test and is ok now. 

The other issues I understand that this group might not be the correct place to ask and I thank you guys if in (1) topic I could get some help.

3 - New help and now something that is more likely to be related to OpENer, thanks. Message: "1> *** The DUT does not support required Electronic Key Format 4."

Thanks in advance, Luciana Almeida.

--
You received this message because you are subscribed to a topic in the Google Groups "EIP Stack Group OpENer users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/eip-stack-group-opener-users/4xuNice-2nI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to eip-stack-group-open...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/eip-stack-group-opener-users/dc6ac8eb-5cdd-4b00-a59f-b8809197f559n%40googlegroups.com.

[Luciana Magno de Almeida]

Completing the message of before, this are the errors related to topic 3. If anyone could help, I saw in that this issue was reported in 2022 but did not see a solution or instructions (https://github.com/EIPStackGroup/OpENer/issues/359).

2666841 6.3.2.2) Electronic Key Test for UCMM
2666842  Sending
2666843   Encapsulation Header 6F 00 18 00 01 00 00 00 00 00 00 00 98 50 0B 00 00 00 00 00 00 00 00 00
2666844   Command Specific Data 00 00 00 00 00 00 02 00 00 00 00 00 B2 00 08 00
2666845   CIP Data 0E 03 20 01 24 01 30 06
2666846  Received
2666847   Encapsulation Header 6F 00 18 00 01 00 00 00 00 00 00 00 98 50 0B 00 00 00 00 00 00 00 00 00
2666848   Command Specific Data 00 00 00 00 00 00 02 00 00 00 00 00 B2 00 08 00
2666849   CIP Data 8E 00 00 00 15 CD 5B 07
2666850 6.3.2.2a   Valid Format 4 Electronic Key
2666851  Sending
2666852   Encapsulation Header 6F 00 22 00 01 00 00 00 00 00 00 00 99 50 0B 00 00 00 00 00 00 00 00 00
2666853   Command Specific Data 00 00 00 00 00 00 02 00 00 00 00 00 B2 00 12 00
2666854   CIP Data 0E 08 34 04 01 00 0C 00 E9 FD 02 03 20 01 24 01 30 01
2666855  Received
2666856   Encapsulation Header 6F 00 14 00 01 00 00 00 00 00 00 00 99 50 0B 00 00 00 00 00 00 00 00 00
2666857   Command Specific Data 00 00 00 00 00 00 02 00 00 00 00 00 B2 00 04 00
2666858   CIP Data 8E 00 04 00
2666859   1> *** The DUT does not support required Electronic Key Format 4.
2666860 6.3.2.2b   Valid Format 4 Electronic Key in UCMM Service Request
2666861  Sending
2666862   Encapsulation Header 6F 00 20 00 01 00 00 00 00 00 00 00 9A 50 0B 00 00 00 00 00 00 00 00 00
2666863   Command Specific Data 00 00 00 00 00 00 02 00 00 00 00 00 B2 00 10 00
2666864   CIP Data 01 07 34 04 01 00 0C 00 E9 FD 02 03 20 01 24 01
2666865  Received
2666866   Encapsulation Header 6F 00 14 00 01 00 00 00 00 00 00 00 9A 50 0B 00 00 00 00 00 00 00 00 00
2666867   Command Specific Data 00 00 00 00 00 00 02 00 00 00 00 00 B2 00 04 00
2666868   CIP Data 81 00 04 00
2666869   2> *** Unexpected fail to UCMM service with an valid Electronic Key in Format 4.
2666870 6.3.2.2c   Electronic Key with Mismatch VendID
2666871  Sending
2666872   Encapsulation Header 6F 00 22 00 01 00 00 00 00 00 00 00 9B 50 0B 00 00 00 00 00 00 00 00 00
2666873   Command Specific Data 00 00 00 00 00 00 02 00 00 00 00 00 B2 00 12 00
2666874   CIP Data 0E 08 34 04 02 00 0C 00 E9 FD 02 03 20 01 24 01 30 01
2666875  Received
2666876   Encapsulation Header 6F 00 14 00 01 00 00 00 00 00 00 00 9B 50 0B 00 00 00 00 00 00 00 00 00
2666877   Command Specific Data 00 00 00 00 00 00 02 00 00 00 00 00 B2 00 04 00
2666878   CIP Data 8E 00 04 00
2666879   3> *** Expected General Status 0x25 and Extended Status 0x114
2666880 6.3.2.3d   Electronic Key with Mismatch Product Code
2666881  Sending
2666882   Encapsulation Header 6F 00 22 00 01 00 00 00 00 00 00 00 9C 50 0B 00 00 00 00 00 00 00 00 00
2666883   Command Specific Data 00 00 00 00 00 00 02 00 00 00 00 00 B2 00 12 00
2666884   CIP Data 0E 08 34 04 01 00 0C 00 EA FD 02 03 20 01 24 01 30 01
2666885  Received
2666886   Encapsulation Header 6F 00 14 00 01 00 00 00 00 00 00 00 9C 50 0B 00 00 00 00 00 00 00 00 00
2666887   Command Specific Data 00 00 00 00 00 00 02 00 00 00 00 00 B2 00 04 00
2666888   CIP Data 8E 00 04 00
2666889   4> *** Expected General Status 0x25 and Extended Status 0x114
2666890 6.3.2.3e   Electronic Key with Mismatch Device Type
2666891  Sending
2666892   Encapsulation Header 6F 00 22 00 01 00 00 00 00 00 00 00 9D 50 0B 00 00 00 00 00 00 00 00 00
2666893   Command Specific Data 00 00 00 00 00 00 02 00 00 00 00 00 B2 00 12 00
2666894   CIP Data 0E 08 34 04 01 00 0D 00 E9 FD 02 03 20 01 24 01 30 01
2666895  Received
2666896   Encapsulation Header 6F 00 14 00 01 00 00 00 00 00 00 00 9D 50 0B 00 00 00 00 00 00 00 00 00
2666897   Command Specific Data 00 00 00 00 00 00 02 00 00 00 00 00 B2 00 04 00
2666898   CIP Data 8E 00 04 00
2666899   5> *** Expected General Status 0x25 and Extended Status 0x115
2666900 6.3.2.3f   Electronic Key with Mismatch Revision
2666901  Sending
2666902   Encapsulation Header 6F 00 22 00 01 00 00 00 00 00 00 00 9E 50 0B 00 00 00 00 00 00 00 00 00
2666903   Command Specific Data 00 00 00 00 00 00 02 00 00 00 00 00 B2 00 12 00
2666904   CIP Data 0E 08 34 04 01 00 0C 00 E9 FD 03 03 20 01 24 01 30 01
2666905  Received
2666906   Encapsulation Header 6F 00 14 00 01 00 00 00 00 00 00 00 9E 50 0B 00 00 00 00 00 00 00 00 00
2666907   Command Specific Data 00 00 00 00 00 00 02 00 00 00 00 00 B2 00 04 00
2666908   CIP Data 8E 00 04 00
2666909   6> *** Expected General Status 0x25 and Extended Status 0x116

Best regards, Luciana Almeida.

[Luciana Magno de Almeida]

Hi all,

I got the format 4 to work in OpENer. Thanks.

Now I'm just testing and fixing other issues. It seems to be going ok.

Thanks 

[martin...@gmail.com]

Great to hear,

Could you be so kind and provide your fixed to the project?

Best regards,

Martin