- Posts: 11
- Thank you received: 0
Ethercat HAL driver
I will try further after configuring an actual system
Thank you guys for help
Regards,
Steve
Please Log in to join the conversation.
and experimented with a couple of Bechhoff EtherCAT terminals.
At the moment I can't afford to buy servos. Would it be possible to use Sascha's generic
driver with Bechhoff's EL7041 stepper motor driver?
Sascha, in an earlier post you mentioned documentation. If you have some notes in German
or in English I would be happy to put together some documentation (I can translate) which I
would hope would help both others and me to understand and use your driver. EtherCAT makes
so much sense for LinuxCNC it would be great to make it much easier for all to use.
Please Log in to join the conversation.
Now I follow this post and Andreas's manual to connect Yaskawa servopack with linuxcnc, everthing goes well until :
There are two error as I analyzed, first of all [705602.382934] EtherCAT ERROR 0-0: Corrupt mailbox response received, Is it means there is something wrong with slave?
Second, there is sychronization error, what does it mean? I have to set slave as reference DC clock? DC cycle time is how much? please refer to ethercat_config_my.xml. I am trying to figure it out refer to William post and Ivan 's post ,since
Enable notLRW:yes shows by ethercat slave -v
Attachment not found
Attachment not found
.
I am appreciated anyone can give any solution I also will post it to etherlab mailing list.
Thanks!
Please Log in to join the conversation.
<dcConf assignActivate="300" sync0Cycle="*1" sync0Shift="0"/>
<dcConf assignActivate="0" sync0Cycle="0" sync0Shift="0"/>
I think you must delete the second one
Besides you can't comment the entering pdo. You must define all the data that the master are receiving and sending.
Please Log in to join the conversation.
I use two two dcconf lines:
<dcConf assignActivate="300" sync0Cycle="*1" sync0Shift="0"/>
<dcConf assignActivate="0" sync0Cycle="0" sync0Shift="0"/> because I tried to test William's post
I commented the entering pdo because I would like to try Ivan's method , since he mention that his driver also Enable notLRW: yes.
I did as you comment before, the result is the same.
If anyone has other suggestions, I will try it.
Anyhow I will update my status.
Thanks!
-chengxi
Please Log in to join the conversation.
In any case have you tried to connect and get the OP mode using TwinCAT from Beckhoff? It helps me a lot to understand what was happening and how to write the .xml files.
Other possible error is that you are using fixed pdo configuration 1602 but you don't specify to the slave configuring parameter with sdoconfig
Please Log in to join the conversation.
narogon wrote: Two DC lines have no sense for me, the parser is going to read one and overwrite the info in the second line.
Understand, Thanks for your explaination.
narogon wrote: In any case have you tried to connect and get the OP mode using TwinCAT from Beckhoff? It helps me a lot to understand what was happening and how to write the .xml files.
Yes, I tried it. It works well with Twincat, I can rotate the motor. Maybe I have to come back and try again, because I just tried it, never figure out how does it work and how to write .xml files.
narogon wrote: Other possible error is that you are using fixed pdo configuration 1602 but you don't specify to the slave configuring parameter with sdoconfig
I am not clear out this, I will read .xml from vendor creafully and to see how.
-chengxi
Please Log in to join the conversation.
euerka wrote:
narogon wrote: Other possible error is that you are using fixed pdo configuration 1602 but you don't specify to the slave configuring parameter with sdoconfig
I am not clear out this, I will read .xml from vendor creafully and to see how.
-chengxi
I've read quickly the manual of your servo, check 0x1c12 and 0x1c13 entries. I think you must configure them before sync mode using sdo.
Sorry I'm from my phone and can't describe it better.
Please Log in to join the conversation.
to be able to better coordinate future development and for easier setup I've decided to build up a separate project for the Ethercat HAL driver stuff. Please find the new repos (including new devices, functions and bugfixes) here:
github.com/sittner/linuxcnc-ethercat
So, if you have new functions, device drivers or fixes please feel free to fork and send me pull requests.
I also have set up a simple Debian repos (currently without keys) which is intended to be used with the current LinuxCNC Debian Wheezy based dist. This way installation should be very easy:
- create a file "/etc/apt/sources.list.d/linuxcnc-mds.list":
Code:deb http://repo.modusoft.de/linuxcnc/wheezy ./
- # sudo apt-get update
- # sudo apt-get install linuxcnc-ethercat
The etherlabmaster should be installed automaticaly.
Currently you will get a warning about missing key. - edit /etc/default/ethercat to match your setup
- # sudo update-ethercat-config
- reboot
- # ethercat slaves
this sould show your connected slaves - start working with Ethercat enabled LinuxCNC
After installation you will find some examples in /usr/share/linuxcnc-ethercat/examples.
Have Fun & Kind Regards
Sascha
Please Log in to join the conversation.
Thanks to all your help, now I can jog 3 servos using Omron G5 servo drivers. However, when I hit "home all" button, nothing happens...
- I've connected "axis.N.home-sw-in" to a homing switch, and it seems working fine
- in my ini file, under axis, I added:
HOME = 0.0
HOME_DELAY = 1.0
HOME_OFFSET = 0.0
HOME_SEARCH_VEL = 3.0
HOME_LATCH_BEL = 3.0
HOME_FINAL_VEL = 0.0
HOME_USE_INDEX = NO
HOME_IGNORE_LIMITS=NO
HOME_SEQUENCE = 0
- when I press the home switch, linuxcnc says homing is completed (although the servo did not move at all)
- I did not connect velocity command pins (axis.N.joint-vel-cmd)....would this cause a problem in homing? I can jog all right using position command..
Does anyone encountered a similar issue?
Best regards,
Steve
Please Log in to join the conversation.
