Ethercat AoE for config IoLink devices

[VincentDruart]

Hello,

I am starting a new project with CtrlX, AL1333 iolink master from IFM and many IoLink devices (30 master, around 200 iolink devices). Communication between CtrlX and AL1333 are in ethercat. Using this topic for setting up : https://developer.community.boschrexroth.com/t5/Store-and-How-to/Set-up-IO-Link-Master-and-IO-Link-S...

For initial setting of every sensor i'm using AoE but it seems to be very slow. Like i can only sent one request each 2 seconds and one sensor at a time. Is it intended ?

Is there an other way to change iolink device setting than IL_ECATAoeWrite ?
I have around 10 configurations i need to change in every iolink sensor, it would take 4000s. On an other system than CtrlX it takes me 5s to make it for 1500 sensors.

I am using the correct technology to send config to my sensors ? Is it the AoE normal speed ? For process the speed is fine. Bus speed is 10ms, cycles speed between 10ms and 100ms.

[EngJay]

Hi @VincentDruart 

I personally prefer IFMs own configuration interface.  Consider using the EoE protocol as described in this example:  https://developer.community.boschrexroth.com/t5/Store-and-How-to/ifm-IO-Link-Master-DataLine-EoE-con...

Let us know if that works faster!

Best regards,

Jay

[VincentDruart]

Hey,

I would prefer to use AoE but in last solution i will take it. Unfortunatly EoE seems not to be comaptible with AL1333, even with expert settings enable, i don't have ethe EoE tab on AL1333. I have the latest ESI file, i will try to re install them.
With LR device solution, when a AL1333 need to be changed or when a new sensor is installed we need to put LR device to configure them, with AoE it's automatic, that's why i prefer this acyclic solution.
On an other network than EtherCAT i already have this working in acyclic with 12k configurations in less than 20s.

[CodeShepherd]

About the EoE topic please get in contact with supplier IFM. There is a firmware that is supporting it. A new ESI will also be needed for this.

We will have a look about the AoE is slow topic. Could you tell us the app versions used on the ctrlX CORE or add a system report (How to generate a system report and switch on additional traces [DOCU])? What is the cycle time of PLC application?

[CodeShepherd]

Some more questions/information:

If you could share your PLC project we also could have a look to that.

Are you doing further acyclic communication like EoE, SoE, CoE... while using AoE? As all of this communication needs to use the same time slow it will slow each other down.

Which ctrlX CORE hardware is used?

[VincentDruart]

Hello,

Please find in theis message the system report.

We are using EoE, CoE and AoE communication. Here are the counters for 1 week of usage.

Hardware is Core X7.

[VincentDruart]

Where and how can i see if timing is different between all acyclic com ? I have the ethercat at 10ms and cpu cycle time for plc task between 10ms and 200ms.

[AutomateSHANE]

It's interesting to me. I did a project with some AL1333 and IO-Link devices and I don't remember if I tried AoE or not. I ended up using CoE to access the IO-Link paramter data using SDO reads and writes. It worked fine, without speed isues. The PLC code is just less simple.

[CodeShepherd]

I forwarded the information for further investigation.

[CodeShepherd]

In the EtherCat all mailbox telegrams (acyclic communication) are sharing the same time slot in the cyclic telegram. So there is no different timing between them, they are simply queued.