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.
Tool/software:
Hi TI team,
This is regarding EtherCAT communication in TMS320F28388D processor. Upon referring EtherCAT Slave Controller Software document fromTI (page 16), there is a section where you create EtherCAT slave files by selecting existing sample codes from TI from the drop down menu like /examples/f2838x_cpu1_echoback_solution directory. I understand this creates the necessary ESI file - F2838x CPU1 EtherCAT Slave.xml which is to be copied to the TwinCAT directory. This enables to listing of the input and output mappings in the TwinCAT Solution Explorer.
But what is to be done if I want to customise the above sample code to meet my application requirements, how do I generate such an ESI file as we need to select the solution directory from the drop down. The customised code may have it's own local variables which may need to be accessed from TwinCAT. Kindly guide.
Also can float data typed values be communicated from ESC to TwinCAT in the same way as mentioned in the document with CCS example showing UINT values?
TIA,
Sapna
Hi Sapna,
But what is to be done if I want to customise the above sample code to meet my application requirements, how do I generate such an ESI file as we need to select the solution directory from the drop down. The customised code may have it's own local variables which may need to be accessed from TwinCAT. Kindly guide.
I recommend that you reach out to Beckhoff/ETG about this issue since they own the tool.
Best Regards,
Ben Collier
Hi,
We tried to contact Beckhoff team, but their reply was to contact TI support as they have developed the slave device. Kindly guide as on what can be done.
Hi Sapna, Ben is OOO this week due to US holiday. He is expected back next week and can provide a response then.
Sapna,
Honestly I am not that experienced with the SSC tool. I could help you with modifying the code that has been generated by the tool, but I am not sure if that is the best practice. I was hoping that ETG could point you towards documentation for their SSC tool.
Best Regards,
Ben Collier