This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

LP-AM243: CODESYS /EDS /Ethernet/IP -CODESYS where the EDS file works the first time but fails (e.g., LEDs do not run) after deleting and reinstalling the same EDS is a known issue

Part Number: LP-AM243

Tool/software:

I am working on 8 Analog input, but Problems I can not update my EDS file.  I tried 100 time same problems. 

, and It not work!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

1)  I installed first time and I save it , I ran this Codesys programs , Save Archive to fews files , worked , no problems. (work good only no change on device) 

2) When remove and ad device ,marked red , run again it will not turn on and off LED  (Not work )

I used ChatGPG , but can not solve problems.

Thanks, 

Thien Tran

  • Hi,

    I've assigned your thread to our EtherNet/IP stack expert to help aid your issues.

    Regards
    Archit

  • Hi,

    it is unclear what is the device you are connecting your PLC, is it the default Generic_Device example for AM243x-LP? Or is it with your own application modification for transferring ADC values?

    1) What is the EDS file you are using?

    2) If the application running on AM243x-LP is not the original Generic-Device example, but with your modification for reading ADC values, Is your EDS updated to reflect the C-code changes in your am243x-LP part?

    3) Please use a tap between your PLC and your AM243x-LP to capture Wireshark logs and send the log for better understanding.

    Regards,
    Pourya

  • I verified and tested with Orignal TI Ethernet_IP_demo , and ESD file from TI. on New hardisk and new Codesys ver 21. Target 14.0  . It will have same problems only work first time installed . I can shut down computer save to new fille no problems. But when I removed or deleted Ethernet IP scanner or EDS file. Run it . it will no work!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

  • I means , Add new device same EDS file to Ethernet. It will not turn on/Off LEDs.  (I see adapter on , but  LED will not on /off . 

  • Here is TI EDS file , I used            

    All programs 100 % from Ti , No modifed code will worked only first installed.

    or  My new  EDS file will work with TI CCS code or My new CCS code only first installed  

  • Hi,

    1) if the device connected to the PLC remains the same, what is the reason for removing and adding the EDS file again?

    2) we'd like to confirm our understanding of the problem: if during runtime the device is disconnected from the PLC and then reconnected, does the IO connection fail to establish (i.e., the LEDs do not blink)? If this is the case, please provide us with the Wireshark logs for further analysis.

    Regards,
    Pourya

  •  Answer # 1 I am working on 8 Analog input , I2c ,DAC . I need to change parameter or assemby in  EDS file . So  I need to change ESD file in Codesys. But every I change , it is not active the adapter with means it is not link to hardware. ( How do I verify  problems, If I use  original Internet_IP_demo program, and ESD file, Copy ESD file to file1.EDS file2.EDS or file3.EDS , It means I can delete file1  and add device file2 or file3 and it should work, but it not work!!!! ). If it not work then I can not run my EDS file.

    Note file1.ESD file .... file2.EDS  all of this file when you run LED on LP-AM243 (i.e., the LEDs must  blink) but it not !!!!!!

      

  • Hi,

    I'm a bit confused about the context of our previous discussion. Could you please clarify which TI example you're referring to - is it the Generic Device or Discrete I/O Device example?

    From your last response, I understand that you want to test your custom device with an updated EDS file that includes assembly parameters. Is that correct?

    To avoid confusion, let's break down the testing into two separate scenarios:

    1. Scenario 1: Original TI Example Run the original TI example (e.g., Generic Device) with the original EDS file. Please try this first and verify that it behaves as expected.

    2. Scenario 2: Custom Device and EDS File Run your custom example (8 Analog input, etc.) with your updated EDS file. Verify the behavior of this setup as well.

    Please start with Scenario 1 and only proceed to Scenario 2 if the first scenario is successful. This will help us rule out any potential issues that might be contributing to the problem. If either scenario fails, please provide the Wireshark log and UART log for that specific scenario so we can further investigate.


    Best regards,
    Pourya

  • It is  problem from  Codesys. I firgured out  a way to work for temperary. Thanks