vilian_ch | 13 Nov 13:30 2012

转发:Master can not recognize slaves on the bus

 

----- 原始邮件 -----
发件人:<vilian_ch <at> sina.com>
收件人:"etherlab-users" <etherlab-users <at> etherlab.org>
主题:Master can not recognize slaves on the bus
日期:2012年11月12日 21点35分

Dear everyone,
We use version 1.5 for our Ethercat master, sometimes I found that the master could not recognize the slaves on the bus when powered on. Using wireshark I could captured datagrams between master and slaves, all datagram types were brd(brocadcast datagram read all slaves's 0x130 registers), it seemed the master could not jump away from this state.
Any one could give me some suggestions?
Thank you in advance!
 
Vilian

 
<div>
<div>&nbsp;<br>
</div>
<br><div>
<div>----- &#21407;&#22987;&#37038;&#20214; -----<br>&#21457;&#20214;&#20154;&#65306;&lt;vilian_ch <at> sina.com&gt;<br>&#25910;&#20214;&#20154;&#65306;"etherlab-users" &lt;etherlab-users <at> etherlab.org&gt;<br>&#20027;&#39064;&#65306;Master can not recognize slaves on the bus<br>&#26085;&#26399;&#65306;2012&#24180;11&#26376;12&#26085; 21&#28857;35&#20998;<br>
</div>
<br><div>Dear everyone,</div>
<div>We use version 1.5 for our Ethercat master, sometimes I found that the master could not recognize the slaves on the bus when powered on. Using wireshark I could captured&nbsp;datagrams between master and slaves, all datagram types were brd(brocadcast datagram read all slaves's 0x130 registers), it seemed the master could not jump away from this state.</div>
<div>Any one could give me some suggestions?</div>
<div>Thank you in advance!</div>
<div>&nbsp;</div>
<div>Vilian</div>
<div>
<br>&nbsp;</div>
</div>
</div>
Mike O'Connor | 10 Nov 00:42 2012
Picon

Alpha Release of LATPROC (Language and Tools for Process Control)

Hi All

Over the last number of months, Martin and I been working on a project
to use EtherCAT and Beckhoff IO to control a Wool Sampling Line.
(http://www.youtube.com/Wooltech1)

The result of this work has been released under the GPL 2 and is hosted
at https://github.com/latproc

Its a long way before a version 1 release and bugs are being found all
the time, but it works and the machine it controls has be installed and
running for a number of weeks.

The code is limited to Digital IO and Beckhoff equipment at this time,
but I hope over time to add support (hopefully with community help) for
other suppliers of EtherCAT compatible products and for more types of
IO, ie counter, analog and motion control.

Tools included are:
* modbusd: Modbus TCP slave
* PHP Website
* persistd: Value persistent store
* device_connector: A program which can interface to raw TCP streams
* iosh: A command line value editor
* zmq_monitor: A message monitoring tool
* beckhoffd: a stand alone interface to EtherCAT
* cw: A control language we are calling ClockWork
* iod: Combind ClockWork and Beckhoffd

This project would not have been possible with out the fantastic work of
the EtherLAB group and I take my hat of too them.

As this is the first project I've ever released to the public, I hope
that I've handled the licences correctly. Please contact me if there are
any issues, or comments.

Cheers
Mike O'Connor

hamelin.philippe | 7 Nov 21:29 2012
Picon

Re: Pinpointing a CoE error

Hi Josh,
 
I didn't know that the cyclic synchronous torque mode wasn't working with previous firmware versions. That's exactly the mode that I need too. Concerning the code that Elmo provided to you, is it based on EtherLab's master? If not, how does it work?
 
Thank you,
 
Philippe

De : Josh Rosenbaum [mailto:jrosenbaum <at> space.nrl.navy.mil]
Envoyé : 7 novembre 2012 15:23
À : Hamelin, Philippe
Objet : RE: [etherlab-users] Pinpointing a CoE error

Hi Philippe,

 

Without the firmware update, EtherLab seems to be working perfectly.  I

can talk to my motors using the command-line tool, and I have tested both of

my motors in cyclic synchronous position mode (the downgraded firmware does

not support any of the other cyclic modes.  Since my application requires

cyclic synchronous torque mode, I will eventually need to use the updated

firmware.)

 

I would suggest contacting Elmo and requesting a previous version of the

Firmware since downgrading has been the only solution that has worked so far.

I would also suggest requesting a test application from Elmo.  They supplied

me with the base code that I am currently using to communicate with my motors.

 

Josh

 

 

From: hamelin.philippe <at> ireq.ca [mailto:hamelin.philippe <at> ireq.ca]
Sent: Wednesday, November 07, 2012 1:07 PM
To: Josh Rosenbaum; etherlab-users <at> etherlab.org
Subject: RE: [etherlab-users] Pinpointing a CoE error

 

Hello Josh,

 

I find it funny but sad at the same time as I was about to write an email similar to yours and I was hoping that I was the only one with this problem. Unfortunately, I see that we are more than one in the same situation. I also made ​​a firmware update recently, but I have not had the chance to test the EtherCAT interface before the update. In your case, does the EtherCAT interface worked well with Etherlab's master before the update?

 

------------------------------------
Philippe Hamelin, ing., M. Ing
Chercheur / Researcher

T: 450-652-8499 x2198
F: 450-652-1316

Expertise robotique et civil
Institut de recherche d'Hydro-Québec (IREQ)
1740, boul. Lionel-Boulet
Varennes (QC) J3X 1S1, Canada

 

De : etherlab-users-bounces <at> etherlab.org [mailto:etherlab-users-bounces <at> etherlab.org] De la part de Josh Rosenbaum
Envoyé : 7 novembre 2012 11:07
À : etherlab-users <at> etherlab.org
Objet : [etherlab-users] Pinpointing a CoE error

Hello,

 

I’m new to using EtherLab’s EtherCAT Master, and I’m currently using

Version 1.5.1 on Ubuntu 10.4 (Kernel 2.6.32).  I have several identical

EtherCAT enabled Elmo Motion Control Whistle drives that use CANopen to

communicate with the master.  I recently updated the Whistle drives’

firmware, and an error has popped up that I’m unsure how to handle.

Elmo claims this is not a problem on their side but is a problem with

EtherLab. I’m struggling to pin down the problem’s root and I am looking

to the EtherLab user base for guidance.

 

When the EtherLab Master attempts to load the object dictionary, I get a

timeout error while the master tries loading a non-existent SDO.   I have

confirmed with Elmo that SDO entry 0x2206:1 does not exist.  This is the

log’s output when I have two slave’s attached; slave zero has the firmware

update and slave 1 does not.

 

[30791.825201] EtherCAT DEBUG 0-1: Finished configuration.

[30791.825204] EtherCAT DEBUG 0-0: Ready for requests.

[30791.825207] EtherCAT DEBUG 0-1: Ready for requests.

[30794.817007] EtherCAT DEBUG 0-0: Fetching SDO dictionary.

[30794.819587] EtherCAT DEBUG 0-0: SDO list fragments left: 2

[30794.820576] EtherCAT DEBUG 0-0: SDO list fragments left: 1

[30796.204805] EtherCAT ERROR 0-0: Timeout while waiting for SDO entry 0x2206:1 description response.

[30796.220971] EtherCAT DEBUG 0-1: Fetching SDO dictionary.

[30796.223436] EtherCAT DEBUG 0-1: SDO list fragments left: 2

[30796.224438] EtherCAT DEBUG 0-1: SDO list fragments left: 1

[30796.988003] EtherCAT DEBUG 0-1: Fetched 171 SDOs and 460 entries.

 

I get this error every time I give power to my servo drives.   Additionally,

if I try and upload an SDO using the command line tool, I get no response

from the slave.  EtherLab returns the error “Failed to determine SDO entry

data type.  Please specify –type” or “Data type mismatch.  Expected XXX with

YY bytes, but got 0 bytes” .  I have never gotten an error with the older

version of the firmware. 

 

 

If this is an EtherLab bug, does anyone have suggestions to help me isolate

the bug or to circumvent the problem?  If this is a bug in the firmware and

beyond my scope, any suggestions to prove that EtherLab is working correctly

and that the bug is with Elmo?

 

 

Also, I am entertaining the idea of upgrading to the EtherLab development

version, but I am awaiting the procurement of a new NIC with the necessary

supported chipset.

 

 

Thanks in advance,

Josh

 

<div>
<div dir="ltr" align="left"><span class="176172520-07112012">Hi Josh,</span></div>
<div dir="ltr" align="left">
<span class="176172520-07112012"></span>&nbsp;</div>
<div dir="ltr" align="left"><span class="176172520-07112012">I didn't know that the cyclic synchronous torque mode wasn't 
working with previous firmware versions. That's exactly the mode that I need 
too. Concerning the code that Elmo provided to you, is it based on EtherLab's 
master? If not, how does it work?</span></div>
<div dir="ltr" align="left">
<span class="176172520-07112012"></span>&nbsp;</div>
<div dir="ltr" align="left"><span class="176172520-07112012">Thank you,</span></div>
<div dir="ltr" align="left">
<span class="176172520-07112012"></span>&nbsp;</div>
<div dir="ltr" align="left"><span class="176172520-07112012">Philippe</span></div>
<br><div dir="ltr" lang="fr" class="OutlookMessageHeader" align="left">
De&nbsp;: Josh Rosenbaum 
[mailto:jrosenbaum <at> space.nrl.navy.mil] <br>Envoy&eacute;&nbsp;: 7 novembre 2012 
15:23<br>&Agrave;&nbsp;: Hamelin, Philippe<br>Objet&nbsp;: RE: 
[etherlab-users] Pinpointing a CoE error<br><br>
</div>
<div></div>
<div class="WordSection1">
<p class="MsoNormal"><span>Hi 
Philippe,<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span>Without the firmware update, 
EtherLab seems to be working perfectly.&nbsp; I<p></p></span></p>
<p class="MsoNormal"><span>can talk to my motors using the 
command-line tool, and I have tested both of<p></p></span></p>
<p class="MsoNormal"><span>my motors in cyclic synchronous 
position mode (the downgraded firmware does<p></p></span></p>
<p class="MsoNormal"><span>not support any of the other 
cyclic modes.&nbsp; Since my application requires<p></p></span></p>
<p class="MsoNormal"><span>cyclic synchronous torque mode, 
I will eventually need to use the updated<p></p></span></p>
<p class="MsoNormal"><span>firmware.)<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span>I would suggest contacting Elmo 
and requesting a previous version of the<p></p></span></p>
<p class="MsoNormal"><span>Firmware since downgrading has 
been the only solution that has worked so far.<p></p></span></p>
<p class="MsoNormal"><span>I would also suggest requesting 
a test application from Elmo.&nbsp; They supplied<p></p></span></p>
<p class="MsoNormal"><span>me with the base code that I am 
currently using to communicate with my motors.<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span>Josh<p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<div>
<div>
<p class="MsoNormal"><span>From:</span><span> 
hamelin.philippe <at> ireq.ca [mailto:hamelin.philippe <at> ireq.ca] <br>Sent: 
Wednesday, November 07, 2012 1:07 PM<br>To: Josh Rosenbaum; 
etherlab-users <at> etherlab.org<br>Subject: RE: [etherlab-users] Pinpointing 
a CoE error<p></p></span></p>
</div>
</div>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal"><span>Hello 
Josh,</span><span><p></p></span></p>
<p class="MsoNormal"><span>&nbsp;<p></p></span></p>
<p class="MsoNormal"><span>I find 
it funny but sad at the same time as I was about to write an email similar to 
yours and I was hoping that I was the only one with this problem. Unfortunately, 
I see that we are more than one in the same situation. I also made &#8203;&#8203;a 
firmware&nbsp;update recently, but I have not had the chance to test the 
EtherCAT interface before the update. In your case,&nbsp;does 
the&nbsp;EtherCAT&nbsp;interface worked&nbsp;well with Etherlab's master before 
the update?</span><span><p></p></span></p>
<p class="MsoNormal"><span>&nbsp;<p></p></span></p>
<p class="MsoNormal"><span>------------------------------------</span><span><br></span><span>Philippe 
Hamelin</span><span>, 
ing., M. Ing</span><span><br></span><span>Chercheur 
/ Researcher<br><br></span><span>T</span><span>: 
450-652-8499 x2198<br></span><span>F</span><span>: 
450-652-1316<br><br>Expertise robotique et civil<br>Institut de recherche 
d'Hydro-Qu&eacute;bec (IREQ)<br>1740, boul. Lionel-Boulet<br>Varennes (QC) J3X 1S1, 
Canada</span><span><p></p></span></p>
<p class="MsoNormal"><span><p>&nbsp;</p></span></p>
<div class="MsoNormal" align="center"><span lang="FR">
</span></div>
<p class="MsoNormal"><span lang="FR">De&nbsp;:</span><span lang="FR"> <a href="mailto:etherlab-users-bounces <at> etherlab.org">etherlab-users-bounces <at> etherlab.org</a> 
[<a href="mailto:etherlab-users-bounces <at> etherlab.org">mailto:etherlab-users-bounces <at> etherlab.org</a>] 
De la part de Josh Rosenbaum<br>Envoy&eacute;&nbsp;: 7 novembre 2012 
11:07<br>&Agrave;&nbsp;: <a href="mailto:etherlab-users <at> etherlab.org">etherlab-users <at> etherlab.org</a><br>Objet&nbsp;: 
[etherlab-users] Pinpointing a CoE error</span><span lang="FR"><p></p></span></p>
<p class="MsoNormal">Hello,<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">I&rsquo;m new to using EtherLab&rsquo;s EtherCAT Master, and I&rsquo;m 
currently using<p></p></p>
<p class="MsoNormal">Version 1.5.1 on Ubuntu 10.4 (Kernel 2.6.32).&nbsp; I have 
several identical<p></p></p>
<p class="MsoNormal">EtherCAT enabled Elmo Motion Control Whistle drives that use 
CANopen to<p></p></p>
<p class="MsoNormal">communicate with the master.&nbsp; I recently updated the 
Whistle drives&rsquo;<p></p></p>
<p class="MsoNormal">firmware, and an error has popped up that I&rsquo;m unsure how to 
handle.<p></p></p>
<p class="MsoNormal">Elmo claims this is not a problem on their side but is a 
problem with<p></p></p>
<p class="MsoNormal">EtherLab. I&rsquo;m struggling to pin down the problem&rsquo;s root and I 
am looking <p></p></p>
<p class="MsoNormal">to the EtherLab user base for guidance. <p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">When the EtherLab Master attempts to load the object 
dictionary, I get a<p></p></p>
<p class="MsoNormal">timeout error while the master tries loading a non-existent 
SDO.&nbsp;&nbsp; I have<p></p></p>
<p class="MsoNormal">confirmed with Elmo that SDO entry 0x2206:1 does not 
exist.&nbsp; This is the<p></p></p>
<p class="MsoNormal">log&rsquo;s output when I have two slave&rsquo;s attached; slave zero has 
the firmware<p></p></p>
<p class="MsoNormal">update and slave 1 does not.<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">[30791.825201] EtherCAT DEBUG 0-1: Finished 
configuration.<p></p></p>
<p class="MsoNormal">[30791.825204] EtherCAT DEBUG 0-0: Ready for 
requests.<p></p></p>
<p class="MsoNormal">[30791.825207] EtherCAT DEBUG 0-1: Ready for 
requests.<p></p></p>
<p class="MsoNormal">[30794.817007] EtherCAT DEBUG 0-0: Fetching SDO 
dictionary.<p></p></p>
<p class="MsoNormal">[30794.819587] EtherCAT DEBUG 0-0: SDO list fragments left: 
2<p></p></p>
<p class="MsoNormal">[30794.820576] EtherCAT DEBUG 0-0: SDO list fragments left: 
1<p></p></p>
<p class="MsoNormal">[30796.204805] EtherCAT ERROR 0-0: Timeout while waiting for 
SDO entry 0x2206:1 description response.<p></p></p>
<p class="MsoNormal">[30796.220971] EtherCAT DEBUG 0-1: Fetching SDO 
dictionary.<p></p></p>
<p class="MsoNormal">[30796.223436] EtherCAT DEBUG 0-1: SDO list fragments left: 
2<p></p></p>
<p class="MsoNormal">[30796.224438] EtherCAT DEBUG 0-1: SDO list fragments left: 
1<p></p></p>
<p class="MsoNormal">[30796.988003] EtherCAT DEBUG 0-1: Fetched 171 SDOs and 460 
entries.<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">I get this error every time I give power to my servo 
drives.&nbsp;&nbsp; Additionally,<p></p></p>
<p class="MsoNormal">if I try and upload an SDO using the command line tool, I get 
no response <p></p></p>
<p class="MsoNormal">from the slave.&nbsp; EtherLab returns the error &ldquo;Failed to 
determine SDO entry<p></p></p>
<p class="MsoNormal">data type.&nbsp; Please specify &ndash;type&rdquo; or &ldquo;Data type 
mismatch.&nbsp; Expected XXX with<p></p></p>
<p class="MsoNormal">YY bytes, but got 0 bytes&rdquo; .&nbsp; I have never gotten an 
error with the older<p></p></p>
<p class="MsoNormal">version of the firmware.&nbsp; <p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">If this is an EtherLab bug, does anyone have suggestions to 
help me isolate<p></p></p>
<p class="MsoNormal">the bug or to circumvent the problem?&nbsp; If this is a bug 
in the firmware and<p></p></p>
<p class="MsoNormal">beyond my scope, any suggestions to prove that EtherLab is 
working correctly<p></p></p>
<p class="MsoNormal">and that the bug is with Elmo?<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Also, I am entertaining the idea of upgrading to the EtherLab 
development<p></p></p>
<p class="MsoNormal">version, but I am awaiting the procurement of a new NIC with 
the necessary<p></p></p>
<p class="MsoNormal">supported chipset. <p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Thanks in advance,<p></p></p>
<p class="MsoNormal">Josh<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
</div>
</div>
Josh Rosenbaum | 7 Nov 17:06 2012
Picon
Picon

Pinpointing a CoE error

Hello,

 

I’m new to using EtherLab’s EtherCAT Master, and I’m currently using

Version 1.5.1 on Ubuntu 10.4 (Kernel 2.6.32).  I have several identical

EtherCAT enabled Elmo Motion Control Whistle drives that use CANopen to

communicate with the master.  I recently updated the Whistle drives’

firmware, and an error has popped up that I’m unsure how to handle.

Elmo claims this is not a problem on their side but is a problem with

EtherLab. I’m struggling to pin down the problem’s root and I am looking

to the EtherLab user base for guidance.

 

When the EtherLab Master attempts to load the object dictionary, I get a

timeout error while the master tries loading a non-existent SDO.   I have

confirmed with Elmo that SDO entry 0x2206:1 does not exist.  This is the

log’s output when I have two slave’s attached; slave zero has the firmware

update and slave 1 does not.

 

[30791.825201] EtherCAT DEBUG 0-1: Finished configuration.

[30791.825204] EtherCAT DEBUG 0-0: Ready for requests.

[30791.825207] EtherCAT DEBUG 0-1: Ready for requests.

[30794.817007] EtherCAT DEBUG 0-0: Fetching SDO dictionary.

[30794.819587] EtherCAT DEBUG 0-0: SDO list fragments left: 2

[30794.820576] EtherCAT DEBUG 0-0: SDO list fragments left: 1

[30796.204805] EtherCAT ERROR 0-0: Timeout while waiting for SDO entry 0x2206:1 description response.

[30796.220971] EtherCAT DEBUG 0-1: Fetching SDO dictionary.

[30796.223436] EtherCAT DEBUG 0-1: SDO list fragments left: 2

[30796.224438] EtherCAT DEBUG 0-1: SDO list fragments left: 1

[30796.988003] EtherCAT DEBUG 0-1: Fetched 171 SDOs and 460 entries.

 

I get this error every time I give power to my servo drives.   Additionally,

if I try and upload an SDO using the command line tool, I get no response

from the slave.  EtherLab returns the error “Failed to determine SDO entry

data type.  Please specify –type” or “Data type mismatch.  Expected XXX with

YY bytes, but got 0 bytes” .  I have never gotten an error with the older

version of the firmware. 

 

 

If this is an EtherLab bug, does anyone have suggestions to help me isolate

the bug or to circumvent the problem?  If this is a bug in the firmware and

beyond my scope, any suggestions to prove that EtherLab is working correctly

and that the bug is with Elmo?

 

 

Also, I am entertaining the idea of upgrading to the EtherLab development

version, but I am awaiting the procurement of a new NIC with the necessary

supported chipset.

 

 

Thanks in advance,

Josh

 

<div><div class="WordSection1">
<p class="MsoNormal">Hello,<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">I&rsquo;m new to using EtherLab&rsquo;s EtherCAT Master, and I&rsquo;m currently using<p></p></p>
<p class="MsoNormal">Version 1.5.1 on Ubuntu 10.4 (Kernel 2.6.32).&nbsp; I have several identical<p></p></p>
<p class="MsoNormal">EtherCAT enabled Elmo Motion Control Whistle drives that use CANopen to<p></p></p>
<p class="MsoNormal">communicate with the master.&nbsp; I recently updated the Whistle drives&rsquo;<p></p></p>
<p class="MsoNormal">firmware, and an error has popped up that I&rsquo;m unsure how to handle.<p></p></p>
<p class="MsoNormal">Elmo claims this is not a problem on their side but is a problem with<p></p></p>
<p class="MsoNormal">EtherLab. I&rsquo;m struggling to pin down the problem&rsquo;s root and I am looking <p></p></p>
<p class="MsoNormal">to the EtherLab user base for guidance. <p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">When the EtherLab Master attempts to load the object dictionary, I get a<p></p></p>
<p class="MsoNormal">timeout error while the master tries loading a non-existent SDO.&nbsp;&nbsp; I have<p></p></p>
<p class="MsoNormal">confirmed with Elmo that SDO entry 0x2206:1 does not exist.&nbsp; This is the<p></p></p>
<p class="MsoNormal">log&rsquo;s output when I have two slave&rsquo;s attached; slave zero has the firmware<p></p></p>
<p class="MsoNormal">update and slave 1 does not.<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">[30791.825201] EtherCAT DEBUG 0-1: Finished configuration.<p></p></p>
<p class="MsoNormal">[30791.825204] EtherCAT DEBUG 0-0: Ready for requests.<p></p></p>
<p class="MsoNormal">[30791.825207] EtherCAT DEBUG 0-1: Ready for requests.<p></p></p>
<p class="MsoNormal">[30794.817007] EtherCAT DEBUG 0-0: Fetching SDO dictionary.<p></p></p>
<p class="MsoNormal">[30794.819587] EtherCAT DEBUG 0-0: SDO list fragments left: 2<p></p></p>
<p class="MsoNormal">[30794.820576] EtherCAT DEBUG 0-0: SDO list fragments left: 1<p></p></p>
<p class="MsoNormal">[30796.204805] EtherCAT ERROR 0-0: Timeout while waiting for SDO entry 0x2206:1 description response.<p></p></p>
<p class="MsoNormal">[30796.220971] EtherCAT DEBUG 0-1: Fetching SDO dictionary.<p></p></p>
<p class="MsoNormal">[30796.223436] EtherCAT DEBUG 0-1: SDO list fragments left: 2<p></p></p>
<p class="MsoNormal">[30796.224438] EtherCAT DEBUG 0-1: SDO list fragments left: 1<p></p></p>
<p class="MsoNormal">[30796.988003] EtherCAT DEBUG 0-1: Fetched 171 SDOs and 460 entries.<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">I get this error every time I give power to my servo drives.&nbsp;&nbsp; Additionally,<p></p></p>
<p class="MsoNormal">if I try and upload an SDO using the command line tool, I get no response <p></p></p>
<p class="MsoNormal">from the slave.&nbsp; EtherLab returns the error &ldquo;Failed to determine SDO entry<p></p></p>
<p class="MsoNormal">data type.&nbsp; Please specify &ndash;type&rdquo; or &ldquo;Data type mismatch.&nbsp; Expected XXX with<p></p></p>
<p class="MsoNormal">YY bytes, but got 0 bytes&rdquo; .&nbsp; I have never gotten an error with the older<p></p></p>
<p class="MsoNormal">version of the firmware.&nbsp; <p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">If this is an EtherLab bug, does anyone have suggestions to help me isolate<p></p></p>
<p class="MsoNormal">the bug or to circumvent the problem?&nbsp; If this is a bug in the firmware and<p></p></p>
<p class="MsoNormal">beyond my scope, any suggestions to prove that EtherLab is working correctly<p></p></p>
<p class="MsoNormal">and that the bug is with Elmo?<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Also, I am entertaining the idea of upgrading to the EtherLab development<p></p></p>
<p class="MsoNormal">version, but I am awaiting the procurement of a new NIC with the necessary<p></p></p>
<p class="MsoNormal">supported chipset. <p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
<p class="MsoNormal">Thanks in advance,<p></p></p>
<p class="MsoNormal">Josh<p></p></p>
<p class="MsoNormal"><p>&nbsp;</p></p>
</div></div>
Carlos Jiménez Leal | 7 Nov 16:59 2012

Time issues with EtherCAT functions

Hello,

I have some problems with the execution time of the EtherCAT functions 
in user space.
I'm using the version of the EtherLAB dated 06/11/2012, linux 2.6.29.5 
and RTAI 3.8.1 (with RTDM) for one cycle at 10kHz,
in a system with the following Beckohff modules: EK1100, EL2004, 
EL1004, EL4132, EL3102, 2xEL3356-0010, EL9510
on a 1.80GHz Intel Atom D525, with a Realtek 8139too

The cycle would be something like this:

cycle () {
	ecrt_master_receive ()
	ecrt_domain_process ()
	phases ()
	ecrt_domain_queue ()
	ecrt_master_send ()
	wait_next_cycle ()
}

I picked up the time it takes each and is far superior to that 
specified in the etherlab manual
(http://www.etherlab.org/download/ethercat/ethercat-1.5-6129a5f715fb.pdf)

			Retrieved 	Manual
Receive Master 		21micro-s 	2.2micro-s
Domain Process 	        11.5micro-s 	1micro-s
Domain Queue 		13.6micro-s 	1micro-s
Master Send 		14.3micro-s 	2.5micro-s

Besides occasionally one of them takes much longer, reaching 3_mili-s_ 
Master Receive
(attached compressed csv file data)

Anyone have any idea what could be happening?

Thank you in advance

-- 
Carlos Jiménez

ENCOPIM S.L.
C/. del Parc 5 (nau 13), P.I. Els Pinetons
E-08291 RIPOLLET (Barcelona)
Tel: (+34) 935 94 23 47
Fax: (+34) 935 94 64 15

==========================================================
La información contenida en la presente transmisión es confidencial y 
su
uso únicamente está permitido a su(s) destinatario(s). Si Ud. no es la
persona destinataria de la presente transmisión, rogamos nos lo
comunique de manera inmediata por teléfono (+34 935 942 347) y destruya
cualquier copia de la misma (tanto digitales como en papel).

The information contained in this transmission is confidential and is
intended only for the use of the addressee(s). If you are not the
designated recipient of this transmission, please advise us immediately
by telephone (+34 935 942 347) and destroy any copies (digital and
paper).
==========================================================
Attachment (EtherCAT.rar): application/x-rar-compressed, 452 KiB
Hello,

I have some problems with the execution time of the EtherCAT functions 
in user space.
I'm using the version of the EtherLAB dated 06/11/2012, linux 2.6.29.5 
and RTAI 3.8.1 (with RTDM) for one cycle at 10kHz,
in a system with the following Beckohff modules: EK1100, EL2004, 
EL1004, EL4132, EL3102, 2xEL3356-0010, EL9510
on a 1.80GHz Intel Atom D525, with a Realtek 8139too

The cycle would be something like this:

cycle () {
	ecrt_master_receive ()
	ecrt_domain_process ()
	phases ()
	ecrt_domain_queue ()
	ecrt_master_send ()
	wait_next_cycle ()
}

I picked up the time it takes each and is far superior to that 
specified in the etherlab manual
(http://www.etherlab.org/download/ethercat/ethercat-1.5-6129a5f715fb.pdf)

			Retrieved 	Manual
Receive Master 		21micro-s 	2.2micro-s
Domain Process 	        11.5micro-s 	1micro-s
Domain Queue 		13.6micro-s 	1micro-s
Master Send 		14.3micro-s 	2.5micro-s

Besides occasionally one of them takes much longer, reaching 3_mili-s_ 
Master Receive
(attached compressed csv file data)

Anyone have any idea what could be happening?

Thank you in advance

-- 
Carlos Jiménez

ENCOPIM S.L.
C/. del Parc 5 (nau 13), P.I. Els Pinetons
E-08291 RIPOLLET (Barcelona)
Tel: (+34) 935 94 23 47
Fax: (+34) 935 94 64 15

==========================================================
La información contenida en la presente transmisión es confidencial y 
su
uso únicamente está permitido a su(s) destinatario(s). Si Ud. no es la
persona destinataria de la presente transmisión, rogamos nos lo
comunique de manera inmediata por teléfono (+34 935 942 347) y destruya
cualquier copia de la misma (tanto digitales como en papel).

The information contained in this transmission is confidential and is
intended only for the use of the addressee(s). If you are not the
designated recipient of this transmission, please advise us immediately
by telephone (+34 935 942 347) and destroy any copies (digital and
paper).
==========================================================
Bilko AS, Oguz Dilmac | 5 Nov 10:50 2012

e1000e driver for 2.6.28.7

Hi,

Where can I find patched driver of e1000e for linux kernel 2.6.28.7?

We are using RTAI kernel modules. I have some problems with touch screen 
in 2.6.32 and I'd like to return to my original kernel (2.6.28.7)
I compared the drivers of e1000e:
* original I used in 2.6.28.7,
* original 2.6.32 from the etherlab repository,
* patched driver for 2.6.32
But there are too many differences. Some files are not exist etc.
I'm not experienced in drivers therefore I dont want to do the patching 
myself.

Best regards,
Oguz

costa | 24 Oct 12:39 2012
Picon

Pdcom for windows

Hello,

I want to make a "mini"-example for windows, like the example for linux.  But I can't include libpdcom-1.dll. Have someone an example code for me?

Thanks

<div><p>Hello,<br><br>I want to make a "mini"-example for windows, like the example for linux.&nbsp; But I can't include libpdcom-1.dll. Have someone an example code for me?<br><br>Thanks<br><br></p></div>
Min Yang | 23 Oct 09:24 2012

Beckhoff AX5201

Hello all,
 
I am using Beckhoff AX5201(2 channel servo drive), the cstruct is:
 
 #/opt/etherlab/bin/ethercat cstruct  -p1
ec_pdo_entry_info_t slave_1_pdo_entries[] = {
{0x0086, 0x00, 16}, /* Master control word */
{0x0024, 0x00, 32}, /* Velocity command value */
{0x0086, 0x00, 16}, /* Master control word */
{0x0024, 0x00, 32}, /* Velocity command value */
{0x0087, 0x00, 16}, /* Drive status word */
{0x0033, 0x00, 32}, /* Position feedback 1 value */
{0x0087, 0x00, 16}, /* Drive status word */
{0x0033, 0x00, 32}, /* Position feedback 1 value */
};
ec_pdo_info_t slave_1_pdos[] = {
{0x0018, 2, slave_1_pdo_entries + 0}, /* MDT 1 */
{0x1018, 2, slave_1_pdo_entries + 2}, /* MDT 2 */
{0x0010, 2, slave_1_pdo_entries + 4}, /* AT 1 */
{0x1010, 2, slave_1_pdo_entries + 6}, /* AT 2 */
};
ec_sync_info_t slave_1_syncs[] = {
{0, EC_DIR_OUTPUT, 0, NULL, EC_WD_DISABLE},
{1, EC_DIR_INPUT, 0, NULL, EC_WD_DISABLE},
{2, EC_DIR_OUTPUT, 2, slave_1_pdos + 0, EC_WD_DISABLE},
{3, EC_DIR_INPUT, 2, slave_1_pdos + 2, EC_WD_DISABLE},
{0xff}
};
 
I need to write "Master control word "of 2 channels in cycle(because 1 channel controls 1 servo). But their pdo entries is the same, if  I register both of them to domain with ecrt_slave_config_reg_pdo_entry(), how to distinguish them?
I also try to write them like this:
ecrt_master_write_idn(master, 0, 0, 0x86, pdata0, 2, error_code);  //for channel 1    drive_no=0
ecrt_master_write_idn(master, 0, 1, 0x86, pdata0, 2, error_code);  //for channel 2    drive_no=1
but when I put them in cycle, I got an error "Failed to write IDN:Iput/output error", then the drive stayed in INIT.  Why I got this error? What's the best solution for my problem?
 
Best Regards
Maggie
<div>
<div>Hello all,</div>
<div>&nbsp;</div>
<div>I am using Beckhoff AX5201(2 channel servo drive), the cstruct is:</div>
<div>&nbsp;</div>
<div>&nbsp;#/opt/etherlab/bin/ethercat cstruct&nbsp; -p1 <div> ec_pdo_entry_info_t slave_1_pdo_entries[] = {<br>
{0x0086, 0x00, 16}, /* Master control word */<br>{0x0024, 0x00, 32}, /* Velocity command value */<br>{0x0086, 0x00, 16}, /* Master control word */<br>{0x0024, 0x00, 32}, /* Velocity command value */<br>{0x0087, 0x00, 16}, /* Drive status word */<br>
{0x0033, 0x00, 32}, /* Position feedback 1 value */<br>{0x0087, 0x00, 16}, /* Drive status word */<br>{0x0033, 0x00, 32}, /* Position feedback 1 value */<br>};<br>ec_pdo_info_t slave_1_pdos[] = {<br>{0x0018, 2, slave_1_pdo_entries + 0}, /* MDT 1 */<br>
{0x1018, 2, slave_1_pdo_entries + 2}, /* MDT 2 */<br>{0x0010, 2, slave_1_pdo_entries + 4}, /* AT 1 */<br>{0x1010, 2, slave_1_pdo_entries + 6}, /* AT 2 */<br>};<br>ec_sync_info_t slave_1_syncs[] = {<br>{0, EC_DIR_OUTPUT, 0, NULL, EC_WD_DISABLE},<br>
{1, EC_DIR_INPUT, 0, NULL, EC_WD_DISABLE},<br>{2, EC_DIR_OUTPUT, 2, slave_1_pdos + 0, EC_WD_DISABLE},<br>{3, EC_DIR_INPUT, 2, slave_1_pdos + 2, EC_WD_DISABLE},<br>{0xff}<br>}; </div>
<div>&nbsp;</div>
<div>I&nbsp;need to write "Master control word "of 2 channels in cycle(because&nbsp;1 channel controls 1 servo). But their pdo entries is the same, if&nbsp; I&nbsp;register both of them to domain with ecrt_slave_config_reg_pdo_entry(), how to distinguish them?</div>
<div>I also try to write&nbsp;them&nbsp;like this:</div>
<div>ecrt_master_write_idn(master, 0, 0, 0x86, pdata0, 2, error_code);&nbsp;&nbsp;//for channel 1&nbsp;&nbsp;&nbsp; drive_no=0</div>
<div>
<div>ecrt_master_write_idn(master, 0, 1, 0x86, pdata0, 2, error_code);&nbsp; //for channel 2&nbsp;&nbsp;&nbsp; drive_no=1</div>
<div>but when I put&nbsp;them in cycle, I got an error "Failed to write IDN:Iput/output error", then the drive stayed in INIT.&nbsp; Why I got this error? What's the best solution for my problem?</div>
<div>&nbsp;</div>
<div>Best Regards</div>
<div>Maggie</div>
</div>
</div>
</div>
Min Yang | 19 Oct 11:52 2012

IDN configuration failure

Hi all,
 
I am using (Ubutu12.04+ethercat master 1.5.1+xenomai2.6.0) to control Beckhoff servo drive AX5101. My system works well at the most of time, but sometimes got IDN configuration errors like this:
 
EtherCAT ERROR 0-0: Failed to receive SoE write response datagram: Datagram received.
EtherCAT ERROR 0-0: Writing IDN 0x0010 failed. 
EtherCAT ERROR 0-0: SoE configuration failed.
 
I checked the mail list and found Florian had given a patch about this issue in 2010. I tried it, without success. Anyone can give more help?
 
Maggie
 
 
<div>
<div>Hi all,</div>
<div>&nbsp;</div>
<div>I am using (Ubutu12.04+ethercat master 1.5.1+xenomai2.6.0) to control Beckhoff servo drive AX5101. My system works well at the most of time, but sometimes got&nbsp;IDN configuration&nbsp;errors like this:</div>
<div>&nbsp;</div>
<div>EtherCAT ERROR 0-0: Failed to receive SoE write response datagram: Datagram received.</div>
<div>
<span lang="EN">EtherCAT ERROR 0-0: Writing IDN 0x0010 failed.</span>&nbsp;</div>
<div>EtherCAT ERROR 0-0: SoE configuration failed.</div>
<div>&nbsp;</div>
<div>I checked the mail list and found Florian had given a patch about this issue in 2010. I tried it, without success. Anyone&nbsp;can&nbsp;give more help?</div>
<div>&nbsp;</div>
<div>Maggie</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
</div>
Shahbaz Youssefi | 18 Oct 13:38 2012
Picon

Re: Changing pdo mapping on the fly

I don't know this motor or its drivers, but I'm forwarding your response to the mailing list in case someone does.

On Thu, Oct 18, 2012 at 12:52 PM, paluan.luca-IWqWACnzNjyonA0d6jMUrA@public.gmane.org <paluan.luca-IWqWACnzNjyonA0d6jMUrA@public.gmane.org> wrote:
I'm using Kollmorgen motors and drivers.
Despite of what the manual
says it seems that putting all together, some variables stop being
mapped.


----Messaggio originale----
Da: shabbyx-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Data:
18/10/2012 12.22
A: "paluan.luca-IWqWACnzNjyonA0d6jMUrA@public.gmane.org"<paluan.luca <at> tiscali.it>

Ogg: Re: [etherlab-users] Changing pdo mapping on the fly

"but I
cannot map all the
different variables I need
at the same time"

What
is the reason that you cannot do this?

On Wed, Oct 17, 2012 at 8:47
PM, paluan.luca-IWqWACnzNjyonA0d6jMUrA@public.gmane.org <
paluan.luca-IWqWACnzNjyonA0d6jMUrA@public.gmane.org> wrote:

> Hello
everybody,
> I need help since I'm trying to build a server which
>
enable clients to access different mode of functions of the motors.
>
It
> must allow clients to use homing, profiled position, profiled
velocity
> and interpolated position motor modes.
> I'm using ethercat
master in a
> realtime environment based on xenomai, but I cannot map
all the
> different variables I need
> at the same time, so I managed
to change on
> the fly the mapped variable on switching the motor mode.

> Unfortunatly
> to do it I need to deactivate the ethercat master,
stop for a moment
> the real time syincronization: the result is
> a
fault (fieldbus
> syncronization lost) on every mode chage, which I
would like to avoid.
>
> Is there any way to unmap and remap pdos while
looping to refresh
> theme.
> Pdo input would be fixed, so I don't need
to remap theme,
> instead I would remap the output pdos depending on
the mode.
> Thanks in
> advance for your help and advices.
> Best
Regards, Luca
>
>
> Invita i tuoi amici e Tiscali ti premia! Il
consiglio di un amico vale più
> di uno spot in TV. Per ogni nuovo
abbonato 30 € di premio per te e per lui!
> Un amico al mese e parli e
navighi sempre gratis:
> http://freelosophy.tiscali.it/
>
_______________________________________________
> etherlab-users
mailing list
> etherlab-users <at> etherlab.org
> http://lists.etherlab.
org/mailman/listinfo/etherlab-users
>





Invita i tuoi amici e Tiscali ti premia! Il consiglio di un amico vale più di uno spot in TV. Per ogni nuovo abbonato 30 € di premio per te e per lui! Un amico al mese e parli e navighi sempre gratis: http://freelosophy.tiscali.it/

<div>
<p>I don't know this motor or its drivers, but I'm forwarding your response to the mailing list in case someone does.<br><br></p>
<div class="gmail_quote">On Thu, Oct 18, 2012 at 12:52 PM, <a href="mailto:paluan.luca <at> tiscali.it">paluan.luca@...</a> <span dir="ltr">&lt;<a href="mailto:paluan.luca@..." target="_blank">paluan.luca@...</a>&gt;</span> wrote:<br><blockquote class="gmail_quote">I'm using Kollmorgen motors and drivers.<br>
Despite of what the manual<br>
says it seems that putting all together, some variables stop being<br>
mapped.<br><br><br>
----Messaggio originale----<br>
Da: <a href="mailto:shabbyx@...">shabbyx@...</a><br>
Data:<br>
18/10/2012 12.22<br>
A: "<a href="mailto:paluan.luca@...">paluan.luca@...</a>"&lt;<a href="mailto:paluan.luca@...">paluan.luca <at> tiscali.it</a>&gt;<br><br>
Ogg: Re: [etherlab-users] Changing pdo mapping on the fly<br><div class="HOEnZb"><div class="h5">
<br>
"but I<br>
cannot map all the<br>
different variables I need<br>
at the same time"<br><br>
What<br>
is the reason that you cannot do this?<br><br>
On Wed, Oct 17, 2012 at 8:47<br>
PM, <a href="mailto:paluan.luca@...">paluan.luca@...</a> &lt;<br><a href="mailto:paluan.luca@...">paluan.luca@...</a>&gt; wrote:<br><br>
&gt; Hello<br>
everybody,<br>
&gt; I need help since I'm trying to build a server which<br>
&gt;<br>
enable clients to access different mode of functions of the motors.<br>
&gt;<br>
It<br>
&gt; must allow clients to use homing, profiled position, profiled<br>
velocity<br>
&gt; and interpolated position motor modes.<br>
&gt; I'm using ethercat<br>
master in a<br>
&gt; realtime environment based on xenomai, but I cannot map<br>
all the<br>
&gt; different variables I need<br>
&gt; at the same time, so I managed<br>
to change on<br>
&gt; the fly the mapped variable on switching the motor mode.<br><br>
&gt; Unfortunatly<br>
&gt; to do it I need to deactivate the ethercat master,<br>
stop for a moment<br>
&gt; the real time syincronization: the result is<br>
&gt; a<br>
fault (fieldbus<br>
&gt; syncronization lost) on every mode chage, which I<br>
would like to avoid.<br>
&gt;<br>
&gt; Is there any way to unmap and remap pdos while<br>
looping to refresh<br>
&gt; theme.<br>
&gt; Pdo input would be fixed, so I don't need<br>
to remap theme,<br>
&gt; instead I would remap the output pdos depending on<br>
the mode.<br>
&gt; Thanks in<br>
&gt; advance for your help and advices.<br>
&gt; Best<br>
Regards, Luca<br>
&gt;<br>
&gt;<br>
&gt; Invita i tuoi amici e Tiscali ti premia! Il<br>
consiglio di un amico vale pi&ugrave;<br>
&gt; di uno spot in TV. Per ogni nuovo<br>
abbonato 30 &euro; di premio per te e per lui!<br>
&gt; Un amico al mese e parli e<br>
navighi sempre gratis:<br>
&gt; <a href="http://freelosophy.tiscali.it/" target="_blank">http://freelosophy.tiscali.it/</a><br>
&gt;<br>
_______________________________________________<br>
&gt; etherlab-users<br>
mailing list<br>
&gt; <a href="mailto:etherlab-users@...">etherlab-users <at> etherlab.org</a><br>
&gt; <a href="http://lists.etherlab" target="_blank">http://lists.etherlab</a>.<br>
org/mailman/listinfo/etherlab-users<br>
&gt;<br><br><br><br><br><br>
Invita i tuoi amici e Tiscali ti premia! Il consiglio di un amico vale pi&ugrave; di uno spot in TV. Per ogni nuovo abbonato 30 &euro; di premio per te e per lui! Un amico al mese e parli e navighi sempre gratis: <a href="http://freelosophy.tiscali.it/" target="_blank">http://freelosophy.tiscali.it/</a><br>
</div></div>
</blockquote>
</div>
<br>
</div>
Gavin Lambert | 18 Oct 05:48 2012

e1000e driver and kernel 3.2.31-rt47

I'm trying to use the e1000e driver on kernel 3.2.31 with the PREEMPT_RT
rt47 patches applied, but the driver is giving me an error.  I'm using the
latest hg source of the etherlab master (4151f6f4c3e1).

The startup of the normal driver looks like this:

e1000e: Intel(R) PRO/1000 Network Driver - 1.5.1-k
e1000e: Copyright(c) 1999 - 2011 Intel Corporation.
e1000e 0000:01:00.0: Disabling ASPM  L1
e1000e 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
e1000e 0000:01:00.0: setting latency timer to 64
e1000e 0000:01:00.0: irq 41 for MSI/MSI-X
e1000e 0000:01:00.0: eth0: (PCI Express:2.5GT/s:Width x4) 68:05:ca:0a:99:18
e1000e 0000:01:00.0: eth0: Intel(R) PRO/1000 Network Connection
e1000e 0000:01:00.0: eth0: MAC: 0, PHY: 4, PBA No: D50868-008
e1000e 0000:01:00.1: Disabling ASPM  L1
e1000e 0000:01:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
e1000e 0000:01:00.1: setting latency timer to 64
e1000e 0000:01:00.1: irq 42 for MSI/MSI-X
udev[9851]: renamed network interface eth0 to eth1
e1000e 0000:01:00.0: irq 41 for MSI/MSI-X
e1000e 0000:01:00.0: irq 41 for MSI/MSI-X
ADDRCONF(NETDEV_UP): eth1: link is not ready
e1000e 0000:01:00.1: eth0: (PCI Express:2.5GT/s:Width x4) 68:05:ca:0a:99:19
e1000e 0000:01:00.1: eth0: Intel(R) PRO/1000 Network Connection
e1000e 0000:01:00.1: eth0: MAC: 0, PHY: 4, PBA No: D50868-008
udev[9851]: renamed network interface eth0 to eth2
e1000e 0000:01:00.1: irq 42 for MSI/MSI-X
e1000e 0000:01:00.1: irq 42 for MSI/MSI-X
ADDRCONF(NETDEV_UP): eth2: link is not ready

The startup of the EC driver looks like this:

ec_e1000e: EtherCAT-capable Intel(R) PRO/1000 Network Driver -
1.5.1-k-EtherCAT
ec_e1000e: Copyright(c) 1999 - 2011 Intel Corporation.
ec_e1000e 0000:01:00.0: Disabling ASPM  L1
ec_e1000e 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
ec_e1000e 0000:01:00.0: setting latency timer to 64
ec_e1000e 0000:01:00.0: irq 41 for MSI/MSI-X
EtherCAT: Accepting 68:05:CA:0A:99:18 as main device for master 0.
ec_e1000e 0000:01:00.0: irq 41 for MSI/MSI-X
ec_e1000e 0000:01:00.0: (unregistered net_device): MSI interrupt test
failed, using legacy interrupt.
EtherCAT 0: Starting EtherCAT-IDLE thread.
ec_e1000e 0000:01:00.0: (unregistered net_device): (PCI
Express:2.5GT/s:Width x4) 68:05:ca:0a:99:18
ec_e1000e 0000:01:00.0: (unregistered net_device): Reset adapter
ec_e1000e 0000:01:00.0: (unregistered net_device): Intel(R) PRO/1000 Network
Connection
ec_e1000e 0000:01:00.0: (unregistered net_device): MAC: 0, PHY: 4, PBA No:
D50868-008
ec_e1000e 0000:01:00.1: Disabling ASPM  L1
ec_e1000e 0000:01:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
ec_e1000e 0000:01:00.1: setting latency timer to 64
ec_e1000e 0000:01:00.1: irq 41 for MSI/MSI-X
ec_e1000e 0000:01:00.0: (unregistered net_device): Hardware Error
ec_e1000e 0000:01:00.1: (unregistered net_device): Hardware Error
ec_e1000e 0000:01:00.1: eth0: (PCI Express:2.5GT/s:Width x4)
68:05:ca:0a:99:19
ec_e1000e 0000:01:00.1: eth0: Intel(R) PRO/1000 Network Connection
ec_e1000e 0000:01:00.1: eth0: MAC: 0, PHY: 4, PBA No: D50868-008
udev[9825]: renamed network interface eth0 to eth2
ec_e1000e 0000:01:00.1: irq 41 for MSI/MSI-X
ec_e1000e 0000:01:00.1: irq 41 for MSI/MSI-X
ADDRCONF(NETDEV_UP): eth2: link is not ready
ec_e1000e 0000:01:00.0: (unregistered net_device): Reset adapter
ec_e1000e 0000:01:00.0: (unregistered net_device): Reset adapter
ec_e1000e 0000:01:00.0: (unregistered net_device): Reset adapter
ec_e1000e 0000:01:00.0: (unregistered net_device): Reset adapter

And then this reset repeats every 2 seconds until I reload the regular
driver.

Any ideas where it's going wrong and how to resolve it?


Gmane