• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 101 subscribers
  • Views 1451 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Starterware: DC error

Cazaban Laurence
Expert 1500 points

Tool/software: Starterware

Hello everyone,

I am still working on the same project: a control motor application which is running on an Ethercat Slave Texas Instrument ARM3359 with an OS realtime Intime. I'm using an Ethercat Stack KPA and I make some tests with KPA Studio (So an Ethercat Master KPA Server).

Everything was working all right but I have recently decided to update the code which is running on the Texas Slave.

So I have updated several files and now I Have an synchronisation error with DC !

- if I use the ESI file distributed by texas TI_ESC. xml but modified to take into account my several inputs/outputs (So I use the TI_ESC_adapt2.xml)+ the eeprom file distibuted by Texas tiesc_eeprom.h: OK

- 8130.TI_ESC_adapt2.xml6472.FULL_BIAXIAL_BOARD_NCN.xml4380.eeprom_ti.h7725.eeprom_lectra.hif I use a new ESI file modified to change the vendor Id and some other info (FULL_BIAXIAL_BOARD_NCN.xml) and an eeprom file generated by the KPA Tool for this ESI file tiesc_eeprom_lectra.h: I have a synchronization Error :"AL status code and description: 0x002D - No sync Error" and I can't reach the operational mode.

I don’t understand what is the difference between these files and why it doesn’t work !

Can you help me please ?

Thanks a lot

Laurence

  • 0
    Expert 1500 points

    Hello everyone,

    I am still working on the same project: a control motor application which is running on an Ethercat Slave Texas Instrument ARM3359 with an OS realtime Intime. I'm using an Ethercat Stack KPA and I make some tests with KPA Studio (So an Ethercat Master KPA Server).

    Everything was working all right but I have recently decided to update the code which is running on the Texas Slave.

    So I have updated several files and now I Have an synchronisation error with DC !

    - if I use the ESI file distributed by texas TI_ESC. xml but modified to take into account my several inputs/outputs (So I use the TI_ESC_adapt2.xml)+ the eeprom file distibuted by Texas tiesc_eeprom.h: OK

    - if I use a new ESI file modified to change the vendor Id and some other info (FULL_BIAXIAL_BOARD_NCN.xml) and an eeprom file generated by the KPA Tool for this ESI file tiesc_eeprom_lectra.h: I have a synchronization Error :"AL status code and description: 0x002D - No sync Error" and I can't reach the operational mode.

    I don’t understand what is the difference between these files and why it doesn’t work !

    Can you help me please ?

    Thanks a lot

    Laurence

    8371.TI_ESC_adapt2.xml2451.FULL_BIAXIAL_BOARD_NCN.xml0268.eeprom_lectra.h

  • 0 in reply to Cazaban Laurence
    TI__Mastermind 43121 points
    Hi Laurence,

    based on a comparison between the two XML files I would assume they work in the same way. There are no functional changes in there, correct? Just names and IDs have changed.
    So either the generation of the binary ESI has an issue or it is something totally different. Did you try to generate the binary with some other tool? I think you can also use Beckhoff tools. Then check if it gets you the same.

    Are you sure you updated your master configuration with the new XML?

    Regards,
  • 0 in reply to Frank Walzer
    Expert 1500 points
    Hello Frank
    Yes, you are right: there is no big difference between the 2 xml files...
    I'm going to try to generate the eeprom with another tool; do you have an idea of the nam's tool from Beckhoff ?
    I will keep you informed !
    Thanks
    Laurence
  • 0 in reply to Cazaban Laurence
    TI__Mastermind 43121 points
    Hi Laurence,

    as far as I can remember it was part of TwinCAT. But I haven't used it for quite some time...

    Regards,