Hello,
Am 21.01.2013 16:52, schrieb Ralf Roesch:
the current stable-1.5 branch does not work for me, when using FoE
commands.
I checked the FoE datagram flow with Wireshark and detected no errors.
So I looked at the source and found a fix for my problem.
Attached you will find a patch for
Hi,
the current stable-1.5 branch does not work for me, when using FoE commands.
I checked the FoE datagram flow with Wireshark and detected no errors.
So I looked at the source and found a fix for my problem.
Attached you will find a patch for further discussion.
Please note: all fsm-slave by
Hi Henry,
many thanks for you extensive explanation of the drive.
The EtherCAT conformance test tool has been checking the SII contents for many
years already, so there is no reason for the SII contents to be incorrect,
other than not having used the test tool in the first place or simply
Hallo takeshi ikeya,
the SSI-contents (EEPROM) is broken. We had that up until now with two
vendors.
I saw other user's mail about YASKAWA SIGMA5, in which he said he couldn't
even get vendor ID and product code.
Because of this we updated the Master Code. Now it is possible to read
the first
Thank you Wilhelm !
Please contact the vendor and point out, that there is a conformance
test tool from the EtherCat technology group available to check if the
slave meets the spezification.
I'll do it
takeshi.ik...@gmail.com
___
etherlab-users
Hello !!
Anyone knows the reason ?
I'm trying to use EtherLab's master.
When I connect one I/O slave (OMRON GX-MD1611), it goes all well.
I disconnect OMRON, connect YASKAWA's Sigma5 servo driver, and make
EtherLab's master stop-and-start.
While master is starting, it scans the bus, and
