Advanced Search

Can this be made for newer versions of linuxcnc? like 2.9.8

I see — if you want to explore EtherCAT and your machine already has absolute servos (including the tool changer magazine), that’s a perfectly valid reason to go that way.

Just be aware that you’re moving from a very KISS, well-understood Mesa setup into more of a “welcome to the jungle” zone: more knobs to turn, more things that can affect determinism (NIC, kernel, DC config, drive modes, etc.), and more commissioning work before you get the same level of predictability.

Coming from Mechatrolink, where a lot of this is implicit in the controller, with PC-based EtherCAT it looks like you first have to make these fundamentals explicit (DC, cycle stability, NIC behavior, jitter) before worrying about pushing the servo thread frequency.

A lot of people on the forum are still exploring this space too, so expect some iteration and experimentation along the way. And those who are really “in the trenches” with EtherCAT on LinuxCNC can probably give you much more concrete numbers and practical advice.

Please specify what you mean by idle. Is this with LinuxCNC running or one of the other programs polling the pendant?

I left the pendant connected last night directly to the xhc-whb04b-6 component, and now some 15 hours later there still hasn't been a single disconnect.

Hi Meschde,

ich habe meine CNC Portalfräse auf MESA Karte umgebaut. Quasi neue CNC gebaut .
Vorher war es eine alpha version von CNC Graf.
Die Oberflächen und Prozesse sind schon extrem anders...

ABER genau was du beschreibst war vorher mein Arbeitsprozess.
Wenn ich z.B. Karbonplatten schneide: Homing XYZ. Dann Werkzeuglänge messen auf dem Werkzeuglängensensor. Dann nehme ich den selben Sensor und legen ihn auf das Material. Dort messe ich dann Z0. In CNCGraf war die Schalthöhe des Sensors hinterlegt und zieht bzw. addiert diese zur neuen Z0 Koordinate.
Hat perfekt funktioniert.

in Linux CNC QT Dragon bin ich am verzweifeln. ... Wie lässt sich das hier abbilden? Kennt es nur die 3D Probe?

@Derriell
Warum möchtest du den Fräsmotor ersetzen? Fehlt es dir an Leistung? Was hast du schon alles mit der AMB gemacht?

@Plasmanfm
Bitte korrigiere mich, wenn ich was Falsches sage.
Letztendlich ist ein Sprung von 1,4 zu 2,2KW erst einmal „nur“ die Möglichkeit schneller bzw. mehr Material / Zeit abzunehmen.
Was ich gehört habe ist, dass die Effizienz bei HF-Spindeln größer ist. Also was am Fräser noch ankommt.
Man kann natürlich z.B. eine Spinology auf seine CNC-Fräse schrauben.
In meinem Fall wäre das aber Unverhältnismäßig!Zur Erklärung… Ich baue mir gerade ein „Endchen“ (also die Fräse, die Sebastian End auf YouTube vorgestellt hat). Nur alles etwas kleiner. Also keine Servos, 60er statt 80er Profile und kein ATC.
Das alles aber so genau, wie ich es mit meinen Möglichkeiten hinbekomme.
Die ist aber halt eine Hobby-CNC.

I'm trying ethercat for a new machine. It makes sense to go with ethercat because it originally had absolute servos for all axis and for the tool changer magazine. If I'm running a mesa setup i need to get the absolute encoder reading at the start via modbus.

I've been running Linuxcnc for a ling time for 3 of my machines. Also like to play with ethercat as it's more interesting.

I've seen a video of ethercat running at 8kz servo thread but also found out that some Ethernet ports do not support that due to power saving Ethernet stuff.

Running a faster servi thread might solve most of these issues i guess?

Ok es wird Birnen mit Äpfel verglichen das eine sind 1,4 das andere sind 2,2 bzw 3,5 Kw was die für Drehmoment haben sagt keiner und
was an Leistung am Fräser an kommt auch nicht .
Des weiteren ist alles was aus C kommt nicht berauschend.
Wenn man was gutes will muss man Industrie Produkte kaufen oder erheblich Abstriche machen.

Gruß
Juergen

I am getting out of ideas.

It's a new computer so if you haven't done so already, you can check overall latency withand make sure the min and max are below +- 20 microseconds or so.

If that doesn't give anything I think you should go back to the working setup you had
with a laptop. If I understood right that setup worked, with the Realtek dkms driver.
Follow your own notes in this thread.

Ethercat master is always distributed as a package separate from linuxcnc due to licensing constraints.
So there is no better or worse linuxcnc version, they are all the same what concerns ethercat and locally compiled master.

Rod you should check out the new V8 Sheetcam. Increased license price, no linux version,
marginal support, company sold and lead developer left the ship (if I understood right).

Anyway, I do most prototypes, one-offs of everything. Sometimes 2 or maybe even 10 but not more. And never again.
I find the Conversational tools to work well, but could be expanded upon.
I already have G-code when it enters QtPlasmaC.
Nesting of several G-code files would be very helpful. Positioning, rotation. Some tools exists in Conversational.
Interactive positioning would be nice. Moving lead-in positions would be nice, but I see the problem.
Very rarely, if ever, I go via dxf and Sheetcam.

Ok Peter, so that is resetting my original understanding. But I have been unable to get the index pulse, which is clearly present in halscope to trigger the position reset. The sensors I am using for both the toothed wheel (a pair in quadrature) and a separaste index tooth, is ATS616LSG by Allegro. Datasheet
Just wondering if there is some magic in the devices that makes them unsuitable here. ( a straw to clutch at).

Re the speed variation, then I don't think there is anything in the config that is altering the analogout.
I have these:- But I think they are only used for the pyvcp speed display bar and at speed led. Can the act of processing them anyway do something?  I guess the thing to try is a minimum basic clean build and see what goes from there.

setp lowpass.spindle.gain 1.000000
net spindle-vel-fb-rpm => abs.spindle.in
net spindle-vel-fb-rpm-abs abs.spindle.out => lowpass.spindle.in
net spindle-fb-rpm-abs-filtered lowpass.spindle.out



# ---Setup spindle at speed signals---

#sets spindle-at-speed true
net spindle-vel-cmd-rps => near.0.in1
net spindle-vel-fb-rps => near.0.in2
net spindle-at-speed  <= near.0.out
#net spindle-at-speed spindle.0.at-speed <= near.0.out
setp near.0.scale 1.000000
setp near.0.difference 1.666667
 

I was about to ask if i should delete the short double....

Thank you so much, Mr Hakan.
I set udev rule, and then I don't need to type "chmod 666 /dev/EtherCAT0" anymore to exec LinuxCNC.

I'm using  PC,  HP Elite800 G4 which have Intel NIC , And I clean installed for 3 times. (In BIOS I disabled SecureBoot )

But all results was same.
Ethercat is unstable. (Alarm A12 flicking,  I can't do anything.  But I could reset if A12 happend before with EoE disabled master, and I could Jog, Run GCode with Yaskawa servo with DELL OLD PC)

I have attached dmesg file.

By the way, which LinuxCNC version (iso?) are good for EtherCAT( Especially DisablingEOE) ?


 

Interesting, a lot of output there.
I was just about the write that it must be the connection to linuxcnc, hal that's the problem.
Then I noticed that it disconnects when I turn the wheel. Almost always, when idle.
You have that too?

If your current Mesa setup already delivers stable rigid tapping, and you’re not confident you can guarantee the same margin of performance and robustness with EtherCAT, then from an engineering and risk standpoint there’s no strong reason to change.

EtherCAT can certainly work and can reach high performance, but it requires more integration effort, tuning, and understanding of the drives and control cycle to achieve the same level of determinism you already have with Mesa.

If the goal is simply to get “the same performance” you already have, the change becomes technical risk without a clear benefit. In that case, the most conservative and rational decision is to stay with Mesa.

Moving to EtherCAT only really makes sense if there is a clear advantage (architecture, cabling, drive availability, industrial standardization, etc.) and you’re willing to invest the time needed for commissioning and tuning to extract the same level of performance.

It seems remora is working ok. There must be issue with GUI. Try using axis gui first. UART just shows startup msgs on remora.