Advanced Search

Are you still looking for testers? I am at a position where I have some capacity to perform testing on this device with you.

I have a 1000w fiber laser running LinuxCNC that I use ~15 hours a week for the last 2 years. I am actively pushing the limits of my height control using the BCL-amp - mainly limited by detection range and sampling rate. Looking at your specs I think it would blow the BCL amp out of the water and lead to more capabilities.

I have a Raytools head BM110

Hello community:

   I have been struggling to install LinuxCNC with the RTAI patch.
   My current computer is Dell Optiplex 980. I was following the previous instructions from this thread

[Solved] Trying to install RTAI, got errors - LinuxCNC


The first error I see if after I tried apt update the

W: Skipping acquire of configured file '2.9-rt/source/Sources' as repository 'www.linuxcnc.org bookworm InRelease' does not seem to provide it (sources.list entry misspelt?)

Then after I enter apt upgrade

raspi-firmware: missing /boot/firmware, did you forget to mount it?
run-parts: /etc/initramfs/post-update.d//z50-raspi-firmware exited with return code 1
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-6.1.0-49-rt-amd64 (--configure):
installed linux-image-6.1.0-49-rt-amd64 package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of linux-image-rt-amd64:
linux-image-rt-amd64 depends on linux-image-6.1.0-49-rt-amd64 (= 6.1.174-1); however:
Package linux-image-6.1.0-49-rt-amd64 is not configured yet.

dpkg: error processing package linux-image-rt-amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of rtai-modules-5.4.258:
rtai-modules-5.4.258 depends on linux-image-5.4.258-rtai-amd64; however:
Package linux-image-5.4.258-rtai-amd64 is not configured yet.

dpkg: error processing package rtai-modules-5.4.258 (--configure):
dependency problems - leaving unconfigured
Processing triggers for initramfs-tools (0.142+deb12u3) ...
update-initramfs: Generating /boot/initrd.img-6.1.0-49-rt-amd64
raspi-firmware: missing /boot/firmware, did you forget to mount it?
run-parts: /etc/initramfs/post-update.d//z50-raspi-firmware exited with return code 1
dpkg: error processing package initramfs-tools (--configure):
installed initramfs-tools package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
linux-image-5.4.258-rtai-amd64
linux-image-6.1.0-49-rt-amd64
linux-image-rt-amd64
rtai-modules-5.4.258
initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)

I get installation error on all the RTAI packages

After I purge the
sudo apt-get purge linuxcnc-uspace
sudo apt-get purge linuxcnc-doc*

and install the dpkg
sudo dpkg -i ./linux-image-5.4.258-rtai-amd64_5.4.258-rtai-amd64-2_amd64.deb

I get this error after while instaling
Found background image: /usr/share/images/desktop-base/desktop-grub.png
Found linux image: /boot/vmlinuz-6.1.0-49-rt-amd64
Found initrd image: /boot/initrd.img-6.1.0-49-rt-amd64
Found linux image: /boot/vmlinuz-6.1.0-30-rt-amd64
Found initrd image: /boot/initrd.img-6.1.0-30-rt-amd64
Found linux image: /boot/vmlinuz-5.4.258-rtai-amd64
Found initrd image: /boot/initrd.img-5.4.258-rtai-amd64
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found Linux Mint 22.3 Zena (22.3) on /dev/sda6
Found Ubuntu 18.04.6 LTS (18.04) on /dev/sda7
done
dpkg: error processing package linux-image-5.4.258-rtai-amd64 (--install):
installed linux-image-5.4.258-rtai-amd64 package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
linux-image-5.4.258-rtai-amd64

then I restart the PC
I do see the RTAI kernel under grub and is able to log in to the machine but when I try to run
Latency-histogram
I get the error pop-up
Stop linuxcnc and hal first(try$halrun -U)

the $halrun -u report
Error: Can't remove RTAI modules kill the following processe(s) first
USER PID ACCESS COMMAND
/dev/rtai_shm: root 1191 ...m halcmd

Can someone point me a hint where i did wrong?
 

There should be many included 4 axis sims with LinuxCNC, so what am i missing?

1. everything related to networking is Debian
2. pretty sure LinuxCNC does not use IPV6 at all
Remove this line

If LinuxCNC fails to verify that IPv6 is disabled and looks for the script/path in the wrong place, that is rather a software bug, not an OS issue.

I found the "locking up" mentioned above was due to a loop counting in the wrong direction. I'm back to the stock XYZ sim.axis version. Other than the "real time delay" at start up this seems to work.

For hand coding, which is what I wanted the simulator for, I'm only doing fourth axis positioning. If I just comment out the A axis moves I can go a long ways towards de-bugging code. Then uncomment and carefully check the A moves before going to the real machine. Should work OK.

But if anyone has a XYZA simulator that works like a mill with rotary table I'd sure like to get a copy. Thank you.

Thank you. This morning I started to realize the *.hal file(s) would be involved. I implemented your fix and it seems to work, at least for jogging and MDI. Thank you.

I'm still getting an "Unexpected real time delay". Also having some trouble with homing as I don't know the configuration in sim.axis. I could likely strip the homing out and fix the real time delay. However, trying to load a program file locks the simulator, infinite loop which eventually crashing VBox.

Poking at the MDI I found another problem for my use. This model rotates the spindle about X and what I need is to rotate the part around X. In the first case the part is fixed to the table and the tool tilts relative to both, tilting the spindle. In the second case the part rotates relative the the table and the XYZ cutting axes are fixed to the table, rotary table on X axis. I'm surprised as I suspect the rotary table on X is much more common that a tilting spindle (as a 5 axis machine would have).

I could likely dig thru the *.hal files and get a 4th axis working, time if the constraint here. But I doubt I could implement a new motion control model. I have it working on my mill but that was developed with PnCconf. I suppose I'll look for another way to test G-Code files.

Thank you for your help.

This is great. I have just started looking into this and so far it is better than all that I have found, just by looking at the gcode output even, others with heavy configuration to get the base plasma cuts are lacking all the way around. I will keep testing and hopefully make some cuts. I do not have a z-axis on my newly built machine so easily remove the z motions. 

I purchased these and tested with a door sensor magnet and then the 3 coil wrap and works great for ARC_OK on fluidNC board.

www.amazon.com/dp/B07YDJ1PMB?ref_=ppx_hz...ed_asin_title_1&th=1

 

Sehr umfangreich.
Das muss ich mir morgen in Ruhe ansehen.
Heute bin ich an keinem Rechner mehr.
Zumindest vorab, schaue dass du ein CAT6 Kabel bekommst und die Netzwerk Karte sollte ein intel chip haben bzw. Ethercat kompatibel sein.
 

Hallo andrax,

danke für Deine Rückmeldung.

Ich habe die Infos jetzt noch einmal etwas sortiert, damit es nicht durcheinandergeht.

Auf dem neuen Rechner sind aktuell zwei Maschinenkonfigurationen vorhanden:

**Rechner:** neuer Debian 13 Rechner

**Maschine 1: A6-E-Drehmoment**
Beschreibung: Hier ist nur der EtherCAT-Servo hinterlegt, sonst nichts.
Status: Läuft sauber und stabil.

**Maschine 2: demo2023**
Beschreibung: Schrittmotoren ohne Encoder, über die Mesa-Karte verbunden.
Diese Konfiguration enthält kein EtherCAT. Es ist auch kein EtherCAT-Teil in der HAL/INI eingebunden.
Die vollständige Konfiguration hatte ich im ersten Beitrag bereits mit HAL und INI angehängt.

Status:

* Auf dem alten Debian-12-Rechner läuft diese Konfiguration stabil.
* Auf dem neuen Debian-13-Rechner läuft dieselbe Konfiguration nicht stabil.

Die Systeminformationen habe ich als Dateien angehängt:

* `systemreport_debian13_...`
* `systemreport_debian12_...`

Zusätzlich habe ich auf dem neuen Debian-13-Rechner noch `dmesg`-Ausgaben erstellt:

* `dmesg_debian13_20260608_191000_vor_dem_Start_von_LinuxCNC.txt`
→ erstellt, bevor ich LinuxCNC mit der Maschine `demo2023` gestartet habe.

* `dmesg_debian13_20260608_191000_nach_dem_Start_von_LinuxCNC.txt`
→ erstellt, nachdem ich LinuxCNC mit der Maschine `demo2023` gestartet und den Fehler reproduziert habe.

Ablauf auf dem neuen Debian-13-Rechner:

1. Maschine `demo2023` gestartet.
Diese Konfiguration hat kein EtherCAT und es war auch kein EtherCAT-Gerät angeschlossen.

2. Die Maschine ist ohne Fehlermeldung gestartet.

3. Alle Achsen konnten problemlos referenziert werden.

4. Sobald ich aber irgendeine Achse verfahren möchte, egal ob per Joystick oder über Axis, kommt sofort ein Positionsfehler.

5. Danach habe ich die zweite `dmesg`-Datei nach dem Start von LinuxCNC erstellt.

Da EtherCAT bei dieser Konfiguration aktuell nicht verwendet wird, habe ich danach noch nicht so genau geschaut. Hardwaremäßig ist der EtherCAT-Servo aber folgender:

Servo-Kit:
www.omc-stepperonline.com/de/750-w-ether...p67-a6-ec750h2a1-m17

Die Kabel zum Servo/Treiber sind die originalen Herstellerkabel.
Das Netzwerkkabel ist aktuell ca. 1 m lang und geht auf meinen Schreibtisch, wo auch der Motor mit Treiber steht. Der Servo ist im Moment aber nicht angeschlossen, da der Motor selbst gerade in der Werkstatt ist und ich noch den Flansch anpassen muss.

Das Netzwerkkabel ist ein normales Kabel, das ich noch von einem alten Router herumliegen hatte. Da EtherCAT in der aktuellen `demo2023`-Konfiguration aber nicht verwendet wird, sollte das für den aktuellen Fehler vermutlich erst einmal keine Rolle spielen.

Ein Bild vom Servotreiber habe ich ebenfalls angehängt.

Falls noch etwas fehlt oder ich etwas Bestimmtes zusätzlich auslesen soll, bitte einfach kurz sagen. Dann liefere ich das noch nach.

Gruß
Mücke

Debian issue, not LinuxCNC, so might be better to post this on their forums, if you feel like it.

 I've seen some other people posting similar issues, did these problems start with the switch to GTK3 or might it be closer connected to the switch to Preempt RT or a later Debian version?

I'm not really competent to determine exactly what's going on, but I did look through old GH issues - and there are a number of similar reports over the years.  They go back to 2.7.

However, there may be two (or more) underlying problems which present the same - more or less - undesired behavior.

I get the sense that one of the scenarios involves switching tabs or otherwise changing window focus during a continuous jog.  At the very least, something other than just pressing/releasing a keyboard key is happening.

The other scenario is what the OP reports - no change in window focus, no pop-ups, nothing but a continuous jog even though the key is released.

The two scenarios may not have anything to do with each other beyond the end result.

My suggestion for the OP would be to turn off keyboard auto-repeat in Debian settings and see if the problem continues.  If the problem goes away this may point to a Debian change rather than an LCNC change.

This is becoming useful for debugging a running LinuxCNC instance. I still have some features to add and bugs to fix before releasing an installer.
Up-to-date source code is available at the link on my first post.

video:
git.disroot.org/nwe/halflow/src/branch/m...a/halflow-tour-1.mp4

Ja, erstmal die bestehende Konfiguration auf den neuen Rechner nehmen (ohne Ethercat)
Bei Problemen die dmesg posten (immer sehr aufschlussreich)
Wenn es keine Probleme gibt, dann ethercat mit rein.
Bei Problemen wieder die dmegs posten.