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.
I generated f2838x_cm_echoback_solution code and ESI file using SSC tool. When loading and running the code on the Connectivity Manager using CCS, TwinCAT was not able to scan the device. I was able to successfully create and run devices on CPU1, which were detected and brought up to OP mode without issues. Is there any known issue with EtherCAT devices on CM? I can share the full CCS project and ESI file if needed.
Hi Mohamed,
Are you running the f2838x_cpu1_allocate_ecat_to_cm example on CPU1? I've never had a problem with the CM when following the instructions in the EtherCAT_Slave_Controller_User_Guide document.
Best Regards,
Ben Collier
Hi Ben,
Thanks for the prompt reply. No I am not running the f2838x_cpu1_allocate_ecat_to_cm example on CPU1. I can try it and circle back to you.
Best regards,
-Mohamed
Hi Ben,
Thanks for the advice. It took me a few trials to get it to work. I will try to move my application SSC to CM.
Thanks again for your help.
Best regards,
-Mohamed