Ethercat HAL driver

Hi Stormhold,

The howto pictures are a example how to set some things in qt. They belong to a previous example wich contains a test.c file :
github.com/grotius-cnc/Linux-Embedded/re...halcompile-qt.tar.gz

If you can load above example in qt, you know how to load your archive in qt.
Above example show's how to compile a single component with halcompiler in a .so file.

Your driver now compiles okey. Updated archive :
github.com/grotius-cnc/Linux-Embedded/re...ile-qt-el3004.tar.gz

For the lcec driver, qt uses a linuxcnc-ethercat makefile. This seemed to be the quickest option.
But you have to take a look in
config.mk and configure.mk, set the correct path's over there.

If you have a skynet install with linuxcnc in the /opt/linuxcnc/ folder, you are already configured.

If you have some question's, no problem.

I just received Delta ASDA B3 servo kit. To my understanding I need the XML file for the generic driver to get it working. There was discussion on some older messages that the XML file should be possible to generate automatically from the file provided by the device manufacturer. At that time such a tool didn't exist. Is this still the case or is there a tool like that?

Hi,

I think this tool don't exist for linux-ethercat.

So far i know people use Twincat to retrieve data like xml files. Ethercat cstruct is also usefull.
At the moment i don't have the data to write such a tool. This input data has to come from experienced servo users.

I just went through the process of setting up my first ethercat motion driver, a stepper driver, but for all relevant parts this is the same as setting up a servo driver.
The delta servo driver is a CiA 402 device. "CanOpen over Ethernet"

Go to github.com/dbraun1981/hal-cia402 , download and install the cia402 component, get the example files and put that in your hal file.

CiA402 is standardized so the object numbers 6040 and so on are all ok.

You do need to have the right "vid" and "pid". You can get that by hooking up the servo drivers to the ethercat bus and enter the command find the numbers for "Vendor ID" and "Product ID" and put that in in the vid and pid fields.
Now it should work.

So you want to change settings of the driver? You can't do that with the pdoEntry way, you need to use the And remember that the bytes are little endian ordered.

You need the manual to know what object number to change and which value to set. In this manual downloadcenter.deltaww.com/downloadCente...5&DocPath=1&hl=en-US this is in chapter 11 CanOpen (here is where that canopen/cia comes in)


Or manually using the ethercat command

And no, I didn't use TwinCat

Hi all,
I have lately been facing a really strange case. I have a CNC set up with 4 IndraDrive in velocity command. I had to replace one of the drive and follow my standard procedure for installing a new one which is:

• switch drives to Ethernet communication and reboot the drives
• pushing the parameter file through Indraworks (engineering tool over IP for the drives) to the newly installed drive
• switch drive to EtherCAT and reboot the drives
• Get TwinCAT to establish an EtherCAT communication loop with all drives (scan for devices, ...) It seems that those drives somehow always require to be communicating under TwinCAT at least once to get the EtherCAT eventually working
• unfotunatly my default EtherCAT slave description for TwinCAT for those drive is in pos command so it overrides the pdos from vel cmd configuration to pos command
• so after TwinCAT I had to reswitch to Ethernet (reboot the drive), push again the parameters files through Indraworks for all my drives, then switch the drive to EtherCAT and reboot
• so far the drive have always been working after this process

Supprisingly, without changing anything to my linuxcnc files (ini, hal, ethercat xml for the lcec), it seems that:

• the EtherCAT is still working, I can get all feedback values (torque, pos, error,...), power them on and reset their reference
• all the drives, including the ones I have not changed, do not move anymore (their motor do not move anymore). Their brake is released when the drive is enabled. There is a vel cmd being send correctly, the drive is powered and enable, no error message but it just does not react. I checked all the status words and control words set up through linuxcnc and everything is identical to one other identical machine currently working. Because the drives are not moving, I eventually hit the following error level defined in the .ini file

I was wondering if anyone had experienced something similar and if so could give me some hints or directions to look at.
Thank you for your help.

Nicolas

Hi all,

well apparently rewriting the .xml esi file for TwinCAT by putting the required parameters for Velocity command did the trick. So far, only the original file in pos command had been used and had been working so far to initialize the EtherCAT ability of the IndraDrives.

But apparently for this one, it required the vel command version of this drive to get the EtherCAT ability and get the drive moving from linuxcnc. Not sure exactly how and why but happy to discuss if some people have been facing the same issue.

Thank you,

Nicolas