Beckhoff ethercat 64 with bit linuxcnc, How to install.

Hello Grotius!

so this means you dont use the ena signal on the drivers and ony stp+dir for one axis?

Yes, in both tutorials you have to create the halfile called postgui.hal. thats a bit confusing because when you use the (already) existig postgui_call_list.hal to shorten things up (i thaught in that moment), you wont succeed
What item do you mean?

Cheers,
Conny

@Conny,

That is correct. I don't use enable signals, do you know why?

Yes, in both tutorials you have to create the halfile called postgui.hal.

You need the postgui.hal file. It's a very good program flow for the linuxcnc software. Some developper's had to think about
this file at that time.

What item do you mean?
Yes, in both tutorials
In my tutorial there is no file like :
postgui_call_list.hal

No, I really don't know why. Please tell me the reason why.

@Jim,

I will tell you why..

Once i was expert programmer related to Kuka robotic's.

Safety is number one in automotive industry. So enable the robot servo drives is not a option if a person is trapped by a robot.
It will only cause more (hours) of delay to free the person. To free the person first the drives have to be enabled. For lineair machines main power shut down is the best option.

Hi Grotius,

thanks, that makes sense.

There is one other thing:
Please tell me, that i have a chance to use Beckhoff KL modules with linuxcnc. (if not - i may have a problem..)

Hello Grotius,

Grotius wrote:

3. Modify the EL3255.c and EL3255.h to your EL3062.c and EL3062.h needs.
It's almost as simple as the find and replace function for whole document with text editor geany.

I didnt get this. So please can you say what in your example was really needed to change?

Thanks
Conny

Hi Conny,

I didnt get this. So please can you say what in your example was really needed to change?

What i mentioned, if a driver not exist's it is possible to copy and edit a existing driver.

What i meant was what exactly is needed to change in this files.
In the .h file i have seen its the PID VID and PDOS lines but what do i need to change in the .c file?
I am asking because today i get my K-Bus modules wich now i need to adopt drivers for :/

Thank you!
Conny

@Conny,

but what do i need to change in the .c file?
It depend's of the difference. If you are only editing a driver name, it's quite easy.
If you want to edit a 2 channel analog input from 16 to 10 bit for example, it's more complicated.
You have to edit more related to the 16 and 10 bit input size.

But if you think logical it would be to do. And take your time. If you are stuck for 36 hour's we can help you with coding.

Header file's are not so important. But you have to look at it alway's if there are differences.

Hi everyone,
I've build an XXYZ gantry and have it running on step/dir but wanted to move to EtherCAT for improved performance.
(using Kollmorgen Servo Drives)

I stumbled upon this guide but I'm stuck at installing etherlab.
When i run the step:

dpkg-buildpackage
and the output I get is:
~/ec-debianize/etherlabmaster$ dpkg-buildpackage
dpkg-buildpackage: info: source package etherlabmaster
dpkg-buildpackage: info: source version 1.5.2+20190904hg33b922p8ea394-1
dpkg-buildpackage: info: source distribution lucid
dpkg-buildpackage: info: source changed by Sascha Ittner <This email address is being protected from spambots. You need JavaScript enabled to view it.>
dpkg-buildpackage: info: host architecture amd64
dpkg-source --before-build etherlabmaster
fakeroot debian/rules clean
dh clean --with autoreconf,dkms
dh_testdir
dh_auto_clean
dh_autoreconf_clean
debian/rules override_dh_clean
make[1]: Entering directory '/home/paul/ec-debianize/etherlabmaster'
rm -f ChangeLog
dh_clean
make[1]: Leaving directory '/home/paul/ec-debianize/etherlabmaster'
dpkg-source -b etherlabmaster
dpkg-source: error: can't build with source format '3.0 (quilt)': no upstream tarball found at ../etherlabmaster_1.5.2+20190904hg33b922p8ea394.orig.tar.{bz2,gz,lzma,xz}
dpkg-buildpackage: error: dpkg-source -b etherlabmaster gave error exit status 255

I've found various people with this problem with quilt and they used different build arguments, and while some build arguments appear to make it farther (or the build output is more verbose), it always has the same failure.

I saw someone earlier mention that they had a similar problem that was solved by making sure they had the correct headers - I updated my RT kernel and headers and removed all others but am still having this same issue.

Has anyone else run into this issue?

Best Regards,
Paul