<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal>Hello,<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I’m new to using EtherLab’s EtherCAT Master, and I’m currently using<o:p></o:p></p><p class=MsoNormal>Version 1.5.1 on Ubuntu 10.4 (Kernel 2.6.32). I have several identical<o:p></o:p></p><p class=MsoNormal>EtherCAT enabled Elmo Motion Control Whistle drives that use CANopen to<o:p></o:p></p><p class=MsoNormal>communicate with the master. I recently updated the Whistle drives’<o:p></o:p></p><p class=MsoNormal>firmware, and an error has popped up that I’m unsure how to handle.<o:p></o:p></p><p class=MsoNormal>Elmo claims this is not a problem on their side but is a problem with<o:p></o:p></p><p class=MsoNormal>EtherLab. I’m struggling to pin down the problem’s root and I am looking <o:p></o:p></p><p class=MsoNormal>to the EtherLab user base for guidance. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>When the EtherLab Master attempts to load the object dictionary, I get a<o:p></o:p></p><p class=MsoNormal>timeout error while the master tries loading a non-existent SDO. I have<o:p></o:p></p><p class=MsoNormal>confirmed with Elmo that SDO entry 0x2206:1 does not exist. This is the<o:p></o:p></p><p class=MsoNormal>log’s output when I have two slave’s attached; slave zero has the firmware<o:p></o:p></p><p class=MsoNormal>update and slave 1 does not.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>[30791.825201] EtherCAT DEBUG 0-1: Finished configuration.<o:p></o:p></p><p class=MsoNormal>[30791.825204] EtherCAT DEBUG 0-0: Ready for requests.<o:p></o:p></p><p class=MsoNormal>[30791.825207] EtherCAT DEBUG 0-1: Ready for requests.<o:p></o:p></p><p class=MsoNormal>[30794.817007] EtherCAT DEBUG 0-0: Fetching SDO dictionary.<o:p></o:p></p><p class=MsoNormal>[30794.819587] EtherCAT DEBUG 0-0: SDO list fragments left: 2<o:p></o:p></p><p class=MsoNormal>[30794.820576] EtherCAT DEBUG 0-0: SDO list fragments left: 1<o:p></o:p></p><p class=MsoNormal>[30796.204805] EtherCAT ERROR 0-0: Timeout while waiting for SDO entry 0x2206:1 description response.<o:p></o:p></p><p class=MsoNormal>[30796.220971] EtherCAT DEBUG 0-1: Fetching SDO dictionary.<o:p></o:p></p><p class=MsoNormal>[30796.223436] EtherCAT DEBUG 0-1: SDO list fragments left: 2<o:p></o:p></p><p class=MsoNormal>[30796.224438] EtherCAT DEBUG 0-1: SDO list fragments left: 1<o:p></o:p></p><p class=MsoNormal>[30796.988003] EtherCAT DEBUG 0-1: Fetched 171 SDOs and 460 entries.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I get this error every time I give power to my servo drives. Additionally,<o:p></o:p></p><p class=MsoNormal>if I try and upload an SDO using the command line tool, I get no response <o:p></o:p></p><p class=MsoNormal>from the slave. EtherLab returns the error “Failed to determine SDO entry<o:p></o:p></p><p class=MsoNormal>data type. Please specify –type” or “Data type mismatch. Expected XXX with<o:p></o:p></p><p class=MsoNormal>YY bytes, but got 0 bytes” . I have never gotten an error with the older<o:p></o:p></p><p class=MsoNormal>version of the firmware. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>If this is an EtherLab bug, does anyone have suggestions to help me isolate<o:p></o:p></p><p class=MsoNormal>the bug or to circumvent the problem? If this is a bug in the firmware and<o:p></o:p></p><p class=MsoNormal>beyond my scope, any suggestions to prove that EtherLab is working correctly<o:p></o:p></p><p class=MsoNormal>and that the bug is with Elmo?<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Also, I am entertaining the idea of upgrading to the EtherLab development<o:p></o:p></p><p class=MsoNormal>version, but I am awaiting the procurement of a new NIC with the necessary<o:p></o:p></p><p class=MsoNormal>supported chipset. <o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Thanks in advance,<o:p></o:p></p><p class=MsoNormal>Josh<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>