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: Update ethercat slave code with new esi file

Part Number: LP-AM243

Tool/software:

Hello;

I am planning to try ethercat_slave_simple_demo application with AM243x eval board. But firstly, I have a question. ESI files are shared in ESI folder. However, if I want to restructure this ESI file, how will I transfer the updates to the sample code. For example, suppose I generate a new ESI file with Beckhoff SSC tool. I want to move these changes to the code side. How can I do this? Is there a structure that parses ENI file and updates the code?

Thanks

  • Hi,

    You can flash the EEPROM with the updated ESI file in order to reflect the ESI change within the EtherCAT SubDevice. You can refer to the following documentation to flash the updated ESI file to the EEPROM using TwinCAT: Load ESI file to EEPROM

    Regards,
    Aaron 

  • Hi Aaron;

    There are 3 subDevice demos in the SDK that I am interested in. These are SubDevice_Simple, Cia402 and Subdevice Beckhoff SSC. Can I update the ESI file for all 3 examples and flash it to the ESC memory? What is the difference between the Subdevice Beckhoff SSC project and the other 2 projects? Which of these should I use when I start a new project? For the EtherCAT SubDevice Beckhoff SSC Demo project, it is explained how to compile the SDK libraries by downloading the Beckhoff sources. Isn't this also valid for the other demo projects?

    Thanks for your support
    Kadir

  • Hi Kadir,

    What is the difference between the Subdevice Beckhoff SSC project and the other 2 projects?
    • EtherCAT SubDevice Demos provides details on the features added by TI stack on top of Beckhoff SSC. Beckhoff SSC Demo uses Beckhoff stack as it is.
    • Also, TI stack uses Beckhoff SSC underneath.
    Which of these should I use when I start a new project?
    • You can compare the features supported within the documentations and based on your use case, you can choose the apt one. 

    Regards,
    Aaron

  • Hi Aaron;

    Thank you very much for all sharing.

    If I do not have a need that is only covered by Beckhoff SSC, I will prefer to use TI SDK. However, when using TI SDK, I will also need ESI file. I will create this ESI file with Beckhoff SSC Tool and load it into slave device ESC memory. In this way, all ESI variables can be read or parsed by slave application. (by SDK libraries)

    Can you please confirm all this information?

    Regards
    Kadir

  • Hi Kadir,

    For the EtherCAT SubDevice Beckhoff SSC Demo project, it is explained how to compile the SDK libraries by downloading the Beckhoff sources. Isn't this also valid for the other demo projects?
    • TI EtherCAT stack demo examples (Simple,CTT,CIA402) which comes with SDK can be built in CCS without the Beckhoff stack sources. These examples use prebuilt Beckhoff stack libs and there are enabled with timeout for eval version. If customer has Beckhoff sources then they can build the licensed version libs and use it. For the EtherCAT SubDevice Beckhoff SSC Demo project Beckhoff sources are required.
    However, when using TI SDK, I will also need ESI file. I will create this ESI file with Beckhoff SSC Tool and load it into slave device ESC memory.
    • You can use the ESI file present in the SDK at {IND_COMMS_SDK}/examples/industrial_comms/ethercat_slave_demo/device_profiles/{DEVICE_PROFILE}/esi

    Regards,
    Aaron

  • Hi Aaron;
    What should I do if I need to have new ESI, or update some details in the ESI file? Should I use SSC tool to generate new ESI?
    Regards
    Kadir

  • Hi Kadir,

    You can create new ESI by following Steps to Run the Example - Using Beckhoff SSC Tool

    Regards,
    Aaron