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.

CCS/TMDSECATCNCD379D: 2837x, EtherCAT, TwinCAT3.1

Part Number: TMDSECATCNCD379D
Other Parts Discussed in Thread: CONTROLSUITE

Tool/software: Code Composer Studio

Hello, I connected TMDSECATCNCD379D to the computer's twincat3 software, and confirmed that the port is connected correctly, but the following problems still occur, twincat3 software can not find my ethercat controller, how to solve? Is my operation wrong or is there a problem with the board? (Figure USER-20160626PU is my computer host name, not the name of the slave controller), there is no more detailed board connection tutorial, because I have been unable to connect the board to twincat3 software, thank you

  • Hello

    Did you complete step 4 in section 3.2 in this guide: https://www.ti.com/lit/ug/spruif9/spruif9.pdf ?

    Make sure the 379D is running at least the PDI test app before trying to scan for it.

    Best regards

    Chris

  • thank you for your reply!

    I have encountered the following problems when I follow the steps in SPRUIF9. I hope you can provide some guidance.

     

    1 The slave name searched in SPRUIF9 is Box1 (TI_C2KESC). The slave name I searched for is Box1 (P00000002 R03160002). How does this affect the subsequent operations? I can be sure that my previous steps are correct.

    2 SPRUIF9 burns pdi_test_app_spi.bin into EEPROM and the Memory interface appears different from mine. Why is this?

    3 SPRUIF9 on page 26 in Figure 34   Why Box1 (TI_C2KESC) becomes Box1 (P00000002 R03160002)

    4 In the ESC RAM READ TEST, the value of the memory interface of my twincat is different from that in SPRUIF9. The test_address and dtest_data are not displayed in ccs. How do I operate?

    All the programs and files I use are from controlSUITE

     

    I look forward to your reply, thanks

  • Hello

    You need to follow completely through the guides. First you run the HAL test app, which you program the EEPROM with the bin file. This programs just the basic EEPROM values needed. This test essentially verifies basic functionality. Then you program the EEPROM using the ESI XML file (provided with the demo files after running the separate installer) or can be generated using the SSC tool. Once programmed with ESI file, then it will update your box name and you can run the echoback example.

    Best regards

    Chris

  • Thank you very much for your reply.
    Your answer is helpful to me, but when I follow SPRUIG9, the last step, the slave status is displayed as INIT, can't be OP status, is it wrong with me, or hardware device problem?  I hope you can give me some guidance, thank you!

  • Hello

    Make sure of two things:

    • You've power cycled the board after that ESI file was loaded and re-started the application
    • TwinCAT master is in OP mode. Restarting TwinCAT in config mode will correct it if it isn't in OP mode. (Try doing this after it discovers the box)

    Best regards

    Chris

  • thank you for your reply!
    I am sure that I have done two things that you mentioned, but when I restart  TwinCAT in config mode, box1 is still in the INIT state. Is it a problem with my hardware?

  • Hello

    • Verify that the switch on the adapter board is aligned with the application running
    • Make sure you are running the echoback application and not the HAL test app
    • If you aren't using the prebuilt demo, make sure if you generated the slave stack code that you are using version 5.11

    Best regards

    Chris

  • Hello, I have solved my problem according to your suggestion, thank you very much for your help.