[etherlab-users] Slave lost forever after power cycling

Tue Feb 18 10:38:04 CET 2020

Hi,

Thank you.

It is the module you've suggested.

We've tried with the DIP switches and with the tool provided by the drive vendor we can see that the "Second Address" parameter is affected correctly by the DIP switch settings. However I can not see that the DIP switch settings affects the alias address when I ask "ethercat slaves". Thus, setting an alias address by using DIP switches doesn't seem to work, at least not together with etherlab. I am puzzled....the vendor claims that this works perfectly well with TwinCAT.

Best Regards,

Joachim Sällvin
________________________________
Från: Graeme Foot <Graeme.Foot at touchcut.com>
Skickat: den 17 februari 2020 20:31
Till: Joachim Sällvin <joachim.sallvin at corpowerocean.com>; Gavin Lambert <gavin.lambert at tomra.com>; etherlab-users at etherlab.org <etherlab-users at etherlab.org>
Ämne: RE: Slave lost forever after power cycling

Hi,

Is it this module here (or similar)?

https://www.nord.com/cms/media/documents/datasheets/TI_275281117_SK_TU4-ECT_EN_4217_screen.pdf

The back of this unit has dip switches:

Second Address (DIP 2..10)

The "Second Address" can be set via this switch and controlled in parameter P181.

If all DIP switches 2..10 are moved to the "OFF" position, the "Second Address" can be set via parameter P160.

This means that if you set an alias on this slave via the "ethercat alias" command it will only remain active until the unit is repowered.  If the dip switches are set it will apply an alias based on the dip switches.  If the dip switches are all off it will use the P160 parameter.

Use the dip switches or P160 to set your alias for this unit, not the "ethercat alias" command.

Regards,

Graeme Foot.

From: etherlab-users <etherlab-users-bounces at etherlab.org> On Behalf Of Joachim Sällvin
Sent: Tuesday, 18 February 2020 6:01 AM
To: Gavin Lambert <gavin.lambert at tomra.com>; etherlab-users at etherlab.org
Subject: Re: [etherlab-users] Slave lost forever after power cycling

Thank you very much for your reply.

It seems like the position on the slave network doesn't matter. What matters i the alias addressing of this particular slave. When I don't give the TU4 slave any alias address I can power-cycle it without loosing it. But as soon as I've given it an alias address and power-cycle it is lost (not every time but almost).

What might cause this? It seems like the EEPROM/Sii of the slave overwritten at start-up when it has been given an alias address. Is there a way to prevent this? How does this work "under the hood"?

I use "sudo ethercat -p1 alias 2" for example to give the slave on position 1 the alias address 2. Nothing wrong here I presume since it seems to work for other slaves.

I've been in contact with the vendor of the TU4 module and they claim that this module is working in big volumes (thousands) on the market. All their other customers use TwinCAT and they haven't heard of this problem. I have also tried three different TU4 modules to exclude the possibility of one failing individual.

Examples:

1.All slaves have alias addresses => TU4-ECT lost after power-cycling.

$ sudo ethercat slaves

0  1:0  PREOP  +  AXL F BK EC, Axioline EtherCAT Fieldbus coupler

1  2:0  PREOP  +  TU4-ECT

2  3:0  PREOP  +  ifm IO-Link Master AL1930

3  4:0  PREOP  +  ifm IO-Link Master AL1332

Power-cycling...

$ sudo ethercat slaves

0  1:0  PREOP  +  AXL F BK EC, Axioline EtherCAT Fieldbus coupler

1  2:0  PREOP  +  ifm IO-Link Master AL1930

2  3:0  PREOP  +  ifm IO-Link Master AL1930

3  4:0  PREOP  +  ifm IO-Link Master AL1332

2. No slave has an alias address => No problem after power-cycling.

$ sudo ethercat slaves

0  0:0  PREOP  +  AXL F BK EC, Axioline EtherCAT Fieldbus coupler

1  0:1  PREOP  +  ifm IO-Link Master AL1930

2  0:2  PREOP  +  ifm IO-Link Master AL1332

3  0:3  PREOP  +  TU4-ECT

Power-cycling...

$ sudo ethercat slaves

0  0:0  PREOP  +  AXL F BK EC, Axioline EtherCAT Fieldbus coupler

1  0:1  PREOP  +  ifm IO-Link Master AL1930

2  0:2  PREOP  +  ifm IO-Link Master AL1332

3  0:3  PREOP  +  TU4-ECT

3. All slaves but the TU4 has alias addresses => No problem

$ sudo ethercat slaves

0  1:0  PREOP  +  AXL F BK EC, Axioline EtherCAT Fieldbus coupler

1  2:0  PREOP  +  ifm IO-Link Master AL1930

2  3:0  PREOP  +  ifm IO-Link Master AL1332

3  3:1  PREOP  +  TU4-ECT

Power-cycling...

$ sudo ethercat slaves

0  1:0  PREOP  +  AXL F BK EC, Axioline EtherCAT Fieldbus coupler

1  2:0  PREOP  +  ifm IO-Link Master AL1930

2  3:0  PREOP  +  ifm IO-Link Master AL1332

3  3:1  PREOP  +  TU4-ECT

Best regards,

Joachim Sällvin

________________________________

Från: Gavin Lambert <gavin.lambert at tomra.com<mailto:gavin.lambert at tomra.com>>
Skickat: den 16 februari 2020 23:58
Till: Joachim Sällvin <joachim.sallvin at corpowerocean.com<mailto:joachim.sallvin at corpowerocean.com>>; etherlab-users at etherlab.org<mailto:etherlab-users at etherlab.org> <etherlab-users at etherlab.org<mailto:etherlab-users at etherlab.org>>
Ämne: RE: Slave lost forever after power cycling

Have you tried putting it in different positions on the slave network?  Perhaps it only vanishes when downstream of a particular slave; then the problem might be with that slave’s configuration.

Etherlab typically assumes that all slaves are configured with DL auto-open mode (so that slaves that are connected or rebooted are automatically brought into the virtual ring network), but it’s possible that one of your upstream slaves has been configured in the explicit open mode instead.

Gavin Lambert
Senior Software Developer

[cid:image001.png at 01D5E634.B3939860]
[TOMRA]<http://www.compacsort.com>[Facebook]<https://www.facebook.com/Compacsort>[Linkedin]<https://www.linkedin.com/company/compac-sorting-equipment/>[Youtube]<https://vimeo.com/compacsort>[twitter]<https://twitter.com/compacsort>[instagram]<https://www.instagram.com/compacsort/>

COMPAC SORTING EQUIPMENT LTD | 4 Henderson Pl | Onehunga | Auckland 1061 | New Zealand
Switchboard: +64 96 34 00 88 | tomra.com<http://www.tomra.com>

The information contained in this communication and any attachment is confidential and may be legally privileged. It should only be read by the person(s) to whom it is addressed. If you have received this communication in error, please notify the sender and delete the communication.

From: Joachim Sällvin
Sent: Friday, 14 February 2020 22:34
To: etherlab-users at etherlab.org<mailto:etherlab-users at etherlab.org>
Subject: [etherlab-users] Slave lost forever after power cycling

Hi all,

I loose contact with my TU4-ECT (freq inverter from Nord Drive) slave after power-cycling it when there are other slaves on the bus. This happens intermittently. Only a EEPROM reset (I use TwinCAT for this ) can make it accessible again. When it is the only slave on the bus it seems as I can power-cycle and always access again.

Has anyone experienced the same problem? What might cause this? Workarounds?

Example:

Before power-cycling the TU4-ECT (all slaves have been given alias addresses):

$ sudo ethercat slaves

0  1:0  PREOP  +  EK1100 EtherCAT-Koppler (2A E-Bus)

1  2:0  PREOP  +  EL2004 4K. Dig. Ausgang 24V, 0.5A

2  3:0  PREOP  +  ifm IO-Link Master AL1332

3  4:0  INIT   E  TU4-ECT

After power-cycling the TU4-ECT:

$ sudo ethercat slaves

0  1:0  PREOP  +  EK1100 EtherCAT-Koppler (2A E-Bus)

1  2:0  PREOP  +  EL2004 4K. Dig. Ausgang 24V, 0.5A

2  3:0  PREOP  +  ifm IO-Link Master AL1332

3  8:0  PREOP  +  ifm IO-Link Master AL1332

Lost!!!

I'm using Linux kernel 4.13.13-rt5, Ubuntu 18.04 and EtherCAT master 1.5.2.

Joachim Sällvin

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.etherlab.org/pipermail/etherlab-users/attachments/20200218/c38776b4/attachment-0003.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 11438 bytes
Desc: image001.png
URL: <http://lists.etherlab.org/pipermail/etherlab-users/attachments/20200218/c38776b4/attachment-0028.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 1629 bytes
Desc: image002.png
URL: <http://lists.etherlab.org/pipermail/etherlab-users/attachments/20200218/c38776b4/attachment-0029.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 1750 bytes
Desc: image003.png
URL: <http://lists.etherlab.org/pipermail/etherlab-users/attachments/20200218/c38776b4/attachment-0030.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 1855 bytes
Desc: image004.png
URL: <http://lists.etherlab.org/pipermail/etherlab-users/attachments/20200218/c38776b4/attachment-0031.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 1970 bytes
Desc: image005.png
URL: <http://lists.etherlab.org/pipermail/etherlab-users/attachments/20200218/c38776b4/attachment-0032.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 20278 bytes
Desc: image006.png
URL: <http://lists.etherlab.org/pipermail/etherlab-users/attachments/20200218/c38776b4/attachment-0033.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.png
Type: image/png
Size: 1506 bytes
Desc: image007.png
URL: <http://lists.etherlab.org/pipermail/etherlab-users/attachments/20200218/c38776b4/attachment-0034.png>