Profinet IO device, "unresolved references" error

tsimpson
2023-03-29
2023-03-30
  • tsimpson - 2023-03-29

    I have a windows 10 panel pc running "CODESYS Control RTE". Currently I am using version 3.5.17 of the engineering software and runtime. I also go "advanced" when I select my devices and use 3.5.17. I am trying to setup as a Profinet device. I have the "Ethernet device" followed by "CODESYS Profinet device" and reserved an InOut_64_Byte.

    The ethernet device alone works fine. As soon as I add the Profinet device however I get all of the "unresolved references" in the attached screenshot and my upload fails. Ive been through countless version combinations from 3.5.16 through 3.5.19 and its always the same. Can someone PLEASE help as I really need this to work for an upcoming project where the PC will be a "slave" for a Siemens Profinet system.

    As a side note, I get the same problem if I make the system a Profinet controller.

     

    Last edit: tsimpson 2023-03-29
  • eschwellinger

    eschwellinger - 2023-03-30

    you need to install the CODESYS networkdriver:
    https://youtu.be/10oj4wABaKc
    this will solve it

     
    • tsimpson - 2023-03-30

      Thanks for the help and the link. I did this and went to ....\Codesys control RTE\CmpEt1000 (and 100) MPD. It showed me no compatible drivers. The Ethernet device I have is an Intel I211 Gigabit......

      Does this mean my hardware is not compatible with RTE? What adaptors are compatible with RTE? If I read the directories properly there is the Intel 1000 / 100 and 2 Realtech ethernet adaptors. Is this correct?

      If all of this is correct, will the standard "Control Win (non-RTE)" run ok or do I have a brick on my hands?

      EDIT: I installed the non RTE runtime and that seems to be working with my network adaptors. The only problem I see with the "basic" non-RTE install is, how do I get the PLC to "autostart"? In the RTE there is a start at boot option. I find no such thing here.

      At least the programs load and run. Now the problem is Profinet device or master. For this I start a new thread.

       

      Last edit: tsimpson 2023-03-30

Log in to post a comment.