Beckhoff EL7031 (Timeout Error) and EL5152

RMP 10.7.0, INtime version 7.1.25030.3

Hi community,

My network wouldn’t start after discovering and generating ENI file:

May I know what might be the root cause for this timeout error?

I tried removing every instance of 0x10F3 SubIndex 5 InitCmd from the ESI file (Default in RSI ESI folder - Beckhoff EL7xxx_RSI.xml) as per this forum post but to no avail

And as for Beckhoff EL5152 Encoder Interface, I would like to know how is the encoder value read as it is declared as a term by default in NodeInfo.xml:

Is the encoder value retrieved from its EtherCAT address through PDO/SDO?
Eg. Reading the network index of that specific address in Network Data or NetworkNode.ServiceChannelRead()

or

Do we have to declare it as a drive (axis) ItemSubType to read using axis.ActualPositionGet()?

Appreciate the help and feedback on this. Many thanks!

Hi @gregory,

For the EL7031, I would also remove the 0xF081 InitCmd. Beckhoff often adds in initcmds that are specific to their own TwinCAT master. I haven’t found a case where they were needed though. If you’d like, I can do a Zoom session with you to help get you operational. Just shoot me an email and I’ll send over a link.

Term/Box/Drive aren’t really significant. If I redesigned things today, everything would simple be a Node. You can use any of them as desired. In the past, I’d recommend Term for something like a EBus slice (similar to the EL7031), Box for something like the EK1100, and Drive for any axis. You could declare the EL7031 (a term) as a axis using<AxisCount>1</AxisCount> Then you could link in <PositionActual>PDO.Position actual value</PositionActual> using the correct string value.

Hi jacob,

Thank you for the suggestion, I will test it out by removing the 0xF081 InitCmd instance from the ESI file as well. Your help is much appreciated.

Noted, we would probably map the device as an axis to link the actual position PDO for ease of use. Thank you!