• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 2 answers
  • Subscribers 98 subscribers
  • Views 204 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

AM2434: EtherCAT Fast Hot Connect support

Manuel Philippin
Intellectual 1795 points

Part Number: AM2434

Hello team,

I am trying to understand if we are able to support the requirements for Beckhoff's "EtherCAT Fast Hot Connect".

  • Do we support this on a PHY level and which requirements would need to be fulfilled?
  • Are there any firmware requirements in our EtherCAT stack?

Thanks in advance.

Best regards
Manuel

  • 0
    TI__Expert 4270 points

    Hello Manuel,

    According to Beckhoff, Fast Hot Connect (FHC) supported EtherCAT devices should be able to establish the connection and reach OP state within 1 second.
    To support FHC, PHYs should be configured in forced mode (for example, forced to 100Mbps, full duplex with bootstrap configurations) to reduce the link-up latency.

    kind Regards,

  • 0 in reply to Harsha Begihally Shanmukhaswamy
    TI__Guru 50951 points

    EtherCAT Hot Connect - acontis

    In order for “Hot Connect” to be used, no special EtherCAT functionality in the slave is required; in fact, any EtherCAT slave may be a member of a HotConnect group (HC group).
    Every HC group just has to be uniquely identifiable, most often this is implemented using DIP switches.
    This unique slave address then appears either in the Station Alias Register or at some address location within the slave memory.
    Both methods are supported by the EtherCAT Master.
    Furthermore, the application may program the station alias address by means of the master (e.g. for first-time system initialization).