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.
Board:MCU-PLUS-SDK-AM243X
Demo:ethercat_slave_beckhoff_ssc_demo
When I burn the demo program onto the AM243X-LP board, the program is always running and the TI_ESC.xml file is configured.
When I open TwinCAT and scan for I/O devices, the following error appears:
First, my computer Ethernet is normal, can connect to a wired network or can communicate properly. Second, I also followed the steps of the presentation step by step.
Hi
TwinCAT is not able to detect the slave as expected. I have following questions:
Regards
Dhaval Khandla
Hi,
1. I has copied the EtherCAT Source files generated by SSC tool to the My Project.
2.Also, TI_ESC.xml has been added to the {TWINCAT_INSTALL_DIR}\TwinCAT\3.1\Config\Io\EtherCAT
folder.
3.Maybe, my computer network card is not Intel, but it connects to the Ethernet network normally. In addition, I clicked on the link you gave to it and it shows that it is invalid and out of date. As shown in the following figure.
Clicking on the red link in the figure above shows the following:
When I went to the official website of Beckhoff's website. to find what you said“TwinCAT RT Ethernet intermediate driver”, I did not find it either.
I hope you can give you a valid link, thank you for your help!
Regards!
Shaoxing Ke.
Clicking on the red link in the figure above shows the following:
I don't use TwinCAT but Supported network controllers appears to be the list of supported network controllers for the TwinCAT RT driver
Hi
We will fix the hyperlink in our documentation.
Maybe, my computer network card is not Intel, but it connects to the Ethernet network normally. In addition, I clicked on the link you gave to it and it shows that it is invalid and out of date. As shown in the following figure.
Based on the figure, it looks okay. The required driver is installed.
I have following questions for you:
Do you see prints in UART console as mentioned here : https://software-dl.ti.com/mcu-plus-sdk/esd/AM243X/08_00_00_21/exports/docs/api_guide_am243x/EXAMPLES_INDUSTRIAL_PROTOCOLS_ETHERCAT_SLAVE_BECKHOFF_SSC_DEMO.html#autotoc_md920 ?
Regards
Dhaval Khandla
Hi,
For the first question,
When I load the application on R5F and run it, the display in the CCS software interface is shown in the following figure.
Do I need to work on which item on CCS and will it display this information?
The R5F is always running, and there are no reminders or messages displayed below.
For the second question,
I tried both RJ45 connector connections separately, but both show the same error. I'm going to try a computer with an Intel network card tomorrow. (Before that, I tried my AM243X-LP with a colleague's computer and also reported the same error. However, TwinCAT can communicate with F2838X on my colleagues' computers)
So, I look forward to receiving more detailed information. Does it require me to modify the underlying code, such as the macro definitions?
Hi
When I load the application on R5F and run it, the display in the CCS software interface is shown in the following figure.
After you load the .out binary to R5F core, does the execution of R5F halt at main function?
The R5F is always running, and there are no reminders or messages displayed below.
This looks to be the problem. I see that you are loading after CPU reset from CCS. Do you see the same behavior when you load and run after a power reset of the board?
Does it require me to modify the underlying code, such as the macro definitions?
No changes should be needed, unless there are modifications made to the board.
Regards
Dhaval Khandla
Hi,
After you load the .out binary to R5F core, does the execution of R5F halt at main function?
It does not show halt.
This looks to be the problem. I see that you are loading after CPU reset from CCS. Do you see the same behavior when you load and run after a power reset of the board?
When I power down and reload the program, it still reports the same error.