• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 96 subscribers
  • Views 1689 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.

AM4377: EtherCAT: Line-Crossed error with Acontis EC-Engineer

Bernd Sprenger
Intellectual 340 points

Part Number: AM4377

Hello,

we have some issues with our own EtherCAT-Slave based on the AM4377. On TwinCAT everything works fine as it should. However, when using the Acontis EC-Engineer or the Acontis EC-Masterstack we most of the time get the error message "Line Crossed! At least one cable incorrectly connected (IN port and OUT port crossed)!". However we use the right ports and even EC-Engineer shows that the input and outputs are ok.

Due to availability issues of Ethernet Phys, we had to choose the DP83848, which is compliant with EtherCAT according to the Beckhoff "Application Note - PHY Selection Guide" page 8. To only thing to do is to "Use LED_LINK for link detection".

We set the link-polarity in tiescbsp.c:

    mdioParamsInit.enhancedlink_enable = TIESC_MDIO_RX_LINK_ENABLE;//TIESC_MDIO_RX_LINK_DISABLE;
    mdioParamsInit.link0pol = TIESC_LINK_POL_ACTIVE_LOW;
    mdioParamsInit.link1pol = TIESC_LINK_POL_ACTIVE_LOW;

Configured the eeprom to use enhanced link detection in tiesc_epprom.h:

        unsigned char tiesc_eeprom[] = {
        0x80,0x3E,0xE0,0x88,0xE8,0x03,0x00,0x00,0x01,0x00,0x00,0x00,0x00,0x00,0x0C,0x00,

Printing the values of the ESC registers 0x0140 & 0x0141:

0x0140: 80; 0x0141: 3e

This shows the enhanced link detection is enabled.

The schematics of the EtherCAT ports are shown in the attached PDF:

11_EtherCAT-BootStrap.pdf

Can you please give us a hint, what might be the cause of the issues?

Thanks a lot for your help,

have a nice day,

Bernd

  • 0
    Intellectual 340 points

    Finally, the issues are solved. There were two issues. The first one was, that the definition of the PHY_PORT_ADDR of the second PHY was wrong. And the second more severe one was, that there was a board assembly fault. The termination resistors which should be 49.9 Ohms were assembled with 49.9 kOhms instead. On the PC Interface, everything worked out somehow, despite the missing termination, but on the target controller it failed understandably...

    I can now certify that the DP83848 works fine with the AM4377. However, the ESD protection of the DP83848 is poor - taking the DP83826 would be the way to go if the availability would not be an issue.