Welcome to our new forum
All users of the legacy CODESYS Forums, please create a new account at account.codesys.com. But make sure to use the same E-Mail address as in the old Forum. Then your posts will be matched. Close

Ethernet/IP: Class 1 Connection ( "Explicit Messaging")

2021-02-02
2021-02-03
  • justthefacts77

    justthefacts77 - 2021-02-02

    HEy Folks,

    I have the CODESYS Scanner/Master running Win PC with the Etnernet/IP Scanner library.

    I am trying to connect to an Adapter/Slave which is another PLC and it doesnt reckognize the Adapter.

    Want to receive periodic variable/tag updates automatically over Ethernet/IP but I am getting the following error:

    Says no "Class 1" Adapter allowed.

    That is a very common topology.

    ?- Am I missing something.

    Thanks

     
  • justthefacts77

    justthefacts77 - 2021-02-02

    Per the CSYS EThernt/IP Sperc sheet:

     
  • i-campbell

    i-campbell - 2021-02-02

    Hehe, you chopped the message!
    "... Class 1 Connections as Target not supported."
    So you would not be able to add the CODESYS as a slave (i.e. Target) to the third party PLC. But you can have Class 1 Connections as Originator (a.k.a. Scanner).
    I would say it is more of an info message than an error.
    If you do want the functionality of CODESYS as both Class 1 Target and Class 1 Originator, you must add the two Devices under the Ethernet Device: Ethernet/IP Scanner and Ethernet/IP Adapter.

    For troubleshooting, what does the + show for the red circled Error message?

    Make sure you use the 3.5.16.40 device description for the Scanner

     
  • justthefacts77

    justthefacts77 - 2021-02-02

    Updated error code when I attempt another time

     
  • justthefacts77

    justthefacts77 - 2021-02-02

    My Scanner setup for Adapter connection

     

    Last edit: justthefacts77 2021-02-02
  • justthefacts77

    justthefacts77 - 2021-02-02

    My Adapter setup....

     
  • i-campbell

    i-campbell - 2021-02-03

    The hint about the consuming application path being invalid suggests the class instance attribute does not match for the consumer.
    If I compare your two configs, you have:
    Scanner:
    O-->T Instance = 0x65
    Adapter:
    AdapIn_Scanout Instance = 0x66

    Now the 'O' is Originator, and is the one that opens the connection.

    I would try swapping the two instance IDs in your scanner config.

     
  • justthefacts77

    justthefacts77 - 2021-02-03

    Thank you very much! Looked at that 10x and still missed.

    Combination of 2 things:
    - The Instance Swap like you said and
    - Change the Target to Scanner format to "Pure Data"

     

Log in to post a comment.