Advanced Search

see updated link above, also note changed usage as I wanted to follow the 'disable_g92_persistence' setting.

for M99 see (I have never used it myself):
linuxcnc.org/docs/scratch/html/gcode/o-c...fanuc-style-programs

what is your machine spindle tool type? tooltall is for non repeatable holders or er collet type holders where the preet length in the holder is not static. probe basic's native setup is for repeatable holders such as bt30/40 cat40 etc

guys, the 7i77 is fed off an independent 5vdc power supply, switches are set appropriately.

I would like ask you for add this information in manual for M2 and M30 definition.

linuxcnc.org/docs/devel/html/gcode/m-code.html#mcode:m2-m30

How M99 works? What M99 do? I didnt find definition.

ok guys, overwhelming responses!! Thank you all for the awesome support!!

I do have a spindle, z, and x encoder, all attached to servo drives. I do not have the drives powered right now because I do not want to attach anything else for fear that I've done something wrong in the config/pin out. I can afford to replace an MPG, I cannot afford to replace a drive...

The original MPGs that came with the machine (Fryer ET18) are labeled as OLM-01-2AD by Maxmar Controls Inc. I presumed (as unlikley as it was) that both MPGs were bad because they both (X and Z) would crash the computer if they moved even one pulse.
The replacement MPGs are no-name Chinese, but are also 6 wire, 5VDC differential encoders. Pictures of those are in my previous posts. It doesnt appear to matter though, the new encoders make the machine behave the same as the old encoders. I am unable to find an official spec sheet for these, but the google claims they are standard quadrature A/B rotary MPG 5VD.

Hallo zusammen,

ich versuche aktuell einen StepperOnline 750W EtherCAT AC-Servomotor (17-bit Absolutencoder, ohne Bremse) in mein LinuxCNC System zu integrieren.

Der Motor ist bereits mechanisch und elektrisch angeschlossen (Netzfilter, Treiber, Motor + Encoder), soweit ist die Hardware grundsätzlich lauffähig.

Mein Ziel ist es, LinuxCNC als EtherCAT Master einzurichten, um zunächst den einzelnen Motor in Betrieb zu nehmen und später mehrere Achsen meiner Maschine schrittweise auf EtherCAT umzubauen.

Ich hatte bereits einen ersten Installationsversuch mit EtherCAT (vermutlich IgH oder SOEM / LinuxCNC Integration), dabei traten jedoch wiederholt Fehler auf. Nach meiner (mehr GPT) Analyse waren vermutlich noch Reste einer früheren (nicht sauberen) Installation bzw. evtl. Raspberry-Pi-bezogene Pakete oder Konfigurationen im System vorhanden, die Konflikte verursacht haben könnten. Diese habe ich inzwischen entfernt bzw. bereinigt, mit GPT .

Aktuell möchte ich deshalb bewusst mit einer sauberen und nachvollziehbaren Schritt-für-Schritt Anleitung neu beginnen, da ich vermeiden möchte, erneut eine fehlerhafte Konfiguration aufzubauen, die ich nicht verstehe.

Ziel ist es zunächst:
- einen einzelnen EtherCAT Servo in LinuxCNC zu betreiben
- einfache Bewegungen und Tests durchzuführen
- später schrittweise weitere Motoren der Maschine (Masacard/Alt-System) auf EtherCAT umzubauen
- langfristig die gesamte Anlage auf EtherCAT umzustellen

---

## Systeminformationen

Distribution:
Debian GNU/Linux 12 (bookworm)

Kernel:
6.1.0-48-rt-amd64 (PREEMPT_RT)

LinuxCNC:
2.9.8 (linuxcnc-uspace)

CPU:
Intel Core i3-6100 @ 3.70 GHz (4 Threads)

RAM:
8 GB

Storage:
Toshiba SSD ~120 GB (ext4)

Network:
- enp1s0: Realtek RTL8111/8168/8411 (r8168 driver) – DOWN
- enp2s0: Realtek RTL8111/8168/8411 (r8168 driver) – UP (100 Mbit/s)

Kernel Modules:
r8168 driver is used for both NICs

PCI:
Intel H110 chipset system

---

## Kernel / RT Status

PREEMPT_RT kernel is active and confirmed.

---

## Frage

Ich suche eine saubere, empfohlene Vorgehensweise zur Installation und Konfiguration von EtherCAT (z. B. IgH EtherCAT Master oder alternative Lösung) in Kombination mit LinuxCNC 2.9.x auf Debian 12 RT.

Wichtig ist mir vor allem:
- stabile Echtzeitfähigkeit
- keine “versteckten” alten Pakete oder Konflikte
- möglichst nachvollziehbare Schritt-für-Schritt Installation
- Empfehlung für Netzwerkinterface (Realtek vs. alternative NIC falls nötig)

Vielen Dank für jede Hilfe!
Mücke

Hello guys :DAfter a lot of troubleshooting - and even trying out another motor driver (Festo CMMT-AS), which I found out wayyyyy too late was not suited for the planned use case - I ended up settling back on the Danfoss VFD. I finally got it working after over a year of trying! In case anybody wants to use a Danfoss VFD like this in their CNC mill or a similar setup, they are really cheap on eBay right now. This one is even equipped with the required EtherCAT communication module (MCA124 - quite hard to find). eBay link: www.ebay.de/itm/327118691814The files can also be found in my fork of the linuxcnc-ethercat project. I'm not sure whether I will make a pull request for these implementations, due to vibe-coding reasons. GitHub repo: github.com/PedPEx/linuxcnc-ethercatA detailed 'manual' is attached in the form of a Markdown file. You will just have to manually remove the .txt file extension.In case you need further details or anything similar, just let me know :)

Have a look at this PR:
github.com/LinuxCNC/linuxcnc/pull/4093

These are my HAL and INI files     
I can ping 10.10.10.10 but every time it goes over 0.500 ms it throws the error 
These are my W2 and W3 jumpers
This is power to the board 
This is the power supply to the board 
And I also have a Meanwell MDR 60 24 for testing its just a really old one. 

+1

I have wished for a possibility to op-out of this automatic resetting to G54 on M2/M30 several times in the past.

This is why I suggested using an external 5V supply
(shorting an external supply would not affect the PC)

Hello guys,

I did some further testing of the modified EL5021 terminal. As expected, when a 120-ohm resistor is added to each channel, it is indeed able to read 1V_pp sensors again. I confirmed this with a Baumer OG73 S SN1024 (SEW branded). So, it was time to get the EL5021 integrated into LinuxCNC. For this, I used my Claude subscription and pretty quickly got a working driver for the encoder input terminal. As far as I can tell, there are no bugs in the driver. Unlike the EL5101 and EP5101, the EL5021 doesn't have the option to reset its counter with every C pulse (at least with the revision that I have - HW: 08; SW: 05). I also found out that Beckhoff seems to have made a major revision change with the newer terminals. A lot of the documented Data Objects from the Beckhoff Information System are not implemented in my terminal.

The only thing left to do is to write a component that takes care of the Beckhoff Latch-C and Latch-C-valid signals and makes them as easy as possible to use for the standard homing procedure of LinuxCNC.

Wish you all a nice Sunday

**TL;DR:** I built a free, open-source (GPL) language server that gives you autocomplete, hover docs, go-to-definition and *live error checking* for your `.hal`, `.ini` and `.ngc` files — so config mistakes show up as red squiggles in your editor instead of as a cryptic failure when you start LinuxCNC.

Marketplace: marketplace.visualstudio.com/items?itemN...erStolz.linuxcnc-lsp

We all know the drill: you tweak a HAL file, start the machine, and it dies with an error about a pin that doesn't exist — because you typed `parport.0.pin-02-ot` instead of `-out`. Or a signal silently does nothing because nothing actually writes to it. This catches that stuff *while you type.*

**What it catches for you (HAL):**
- Unknown components and **misspelled pin/parameter names** (it knows 214 HAL components, 2,153 pins, 589 parameters)
- **Signals with no writer, no reader, or two writers** fighting over one signal
- **Type conflicts** — linking a `bit` pin to a `float` signal
- **`setp` on a read-only parameter**
- It actually understands `count=`, `names=`, and array modparams like `num_chan=`, so multi-channel components resolve correctly — and it matches halcompile's prefix rules (e.g. `loadrt hal_parport` → `parport.0.*`)

**For INI files:**
- Unknown keys, duplicate/conflicting keys, values that don't match the expected type or enum
- Hover any key for docs; homing keys link straight to the LinuxCNC manual
- Cross-file aware: HAL files that reference `[SECTION]KEY` get checked against the actual INI

**For G-code (.ngc/.nc/.tap):**
- Hover docs for ~229 G/M-words, autocomplete for codes and parameters, O-word subroutine support

Plus the usual editor niceties everywhere: autocomplete, go-to-definition, find-all-references, rename-across-files, document outline, and quick-fixes (e.g. "add the missing INI key").

**A couple of things I think you will appreciate:**
- It's **pure static analysis** — no running LinuxCNC instance, no special setup. Just open your config folder.
- I validated it against **all 247 stock LinuxCNC configs**. That audit even turned up a handful of real conflicting-key bugs in the shipped configs.
- It's a standard **LSP**, so while the easy path is the VS Code extension, it'll plug into Neovim/Emacs/etc. too.
- **GPL-2.0**, source on GitHub: github.com/PeterStolz/linuxcnc-lsp — issues and PRs very welcome.

It's early (v0.1.x), so if it flags something it shouldn't, or misses something it should, please tell me — bug reports against your real configs are exactly what makes it better.

I suspect the MPG has a defective output and causing a short to 5V supply, that in turn causes the 7i77 to error out. Or it draws to much current maybe?

Thank you for help.

I preffer:

Default value AUTOMATIC_G54 = TRUE