Advanced Search

Danke, das ist schon mal ein Ansatz! 

Im Moment sehe ich da zwei Möglichkeiten:
- Raspberry Pi 5 + ein Parallel Hat von byte2bot
byte2bot.com/products/parallel-port-rasp...gak8F2DJq1o7WoFK2x-g

Verstehe ich das richtig, dass damit die Erzeugung der Signale die an meine Fräse gesendet werden im Raspberry stattfindet, und somit von der Systemauslastung, Latenz, etc.. abhängt?

- Raspberry Pi 5 + MESA 7C81
Während hier die Signale in/von der Mesa Karte erzeugt werden?

In beiden Fällen muss ich die .hal Dateien so anpassen dass die korrekten Pins angesprochen werden, das ist mir klar.

Aber funktioniert das grundsätzlich so, oder liege ich daneben?

Hallo zusammen!

Ich heiße Bernhard, bin Mitte 40 und komme aus dem Osten Österreichs.
Beruflich bin ich in der IT unterwegs, und habe auch etwas Erfahrung mit Linux.

Daher war das ausstatten meiner vor 5 Jahren angeschafften kleinen CNC Fräse (Mutronic Diadrive) mit LinuxCNC logisch, und das funktionierte auch im großen und ganzen sehr gut.

Die letzten 5 Jahre lief ein PC mit einem ASUS Mainboard aus 2005, an dessen Parallel-Port direkt die Fräse hing.

Wie zu erwarten, macht das natürlich irgendwann Probleme. Im Moment wird die Festplatte (SSD) nicht mehr erkannt.
Ich krieg das grundsätzlich zwar sicher wieder hin, aber möchte das eigentlich gleich nutzen um auf aktuelle Hardware umzusteigen.
PCs mit Parallel-Port zu finden die dann auch akzeptabel funktionieren dürfte eher die Nadel im Heuhaufen sein.
Alles was mir so in den letzten Jahren vor die Füße gefallen ist, hat im Latency Test grausam abgeschnitten.

Daher meine Frage an die Wissenden:
Was nehme ich 2025 für Hardware, um eine Fräse anzusteuern die einen Parallel-Port Eingang hat.

Ich lese was von Raspberry Pi, Mesa Karten, ..., blicke aber ehrlich gesagt nicht durch wie das alles zusammenspielt.
Eine Raspberry Lösung fände ich sehr sexy, aber was nehme ich dann als Umsetzer zur Fräse?

Habt ihr eventuell Links zu funktionierenden und dokumentierten Setups, oder Tipps in welche Richtung ich mich weiter schlau machen sollte?

hilfesuchende Grüße,
Bernhard


 

you can get sma cables with a bulkhead adapter at one end. use that cable, attach to where the wifi antenna was, drill a hole in the cabinet and you can then attach your antenna to the extension cable.

Glad you got that sorted John. Just wanted to mention that I did somewhat similar - wanted to "move the WiFi 10ft away to the top of the HMI box" since that's the highest point of the machine.  Looked at external antennas but none had a cable long enough. So have Rpi --> industrial USB hub --> 10ft USB cable to a tiny  8821CU  dongle with the antenna sticking out of the HMI.  Trap for young players: that particular dongle already has a driver included in the Rpi .iso, but that driver absolutely would not work.  Had to follow the directions at the link to compile a special new driver for it.  After a lot of head-scratching and configuration, have the on-board WiFi disabled and the dongle enabled, and it works a treat.  Cheers.

LinuxCNC 2.9.6 has been released.

This is a bug-fix release. Shortly after the release of 2.9.5 it was
noticed that a fix for a graphics bug in Gmoccapy had resulted in the
Axis touch-off dialog box no-longer working for non-zero entries.

This update is for all users, but especially users of the Axis GUI.

Packages for 2.9-uspace for amd64 (PC) for Debian Buster, Bullseye,
Bookworm and Trixie and for arm64 (Raspberry Pi 4/5) for Buster and
Bookworm have been added to the linuxcnc repository. If you installed
from one of our live images or Pi SD-card images then the update
should be available immediately.

If you installed into a normally-installed Debian from the Debian
repositories then hopefully the new version can be queued up for the
next point release. If you can’t wait then it is possible to add the
LinuxCNC repositories to the apt sources. One way to do this and
install the security keys is via the shell script here:
linuxcnc.org/docs/stable/html/getting-st...th_preempt_rt_kernel

At the moment the live-image installer and SD card images will install
2.9.4 but update should be trivial (and possibly automatic)

RTAI is still supported, but in the short term building from source is
likely to be the most expedient way to get 2.9.6 on that platform.

Changelog

qtvcp -Qt5_graphics: issue 2753; preview wrongly uses INI startup code
Merge pull request #3567 from Sigma1912/2_9-Correct_bad_fix_for_2753
Gremlin: Don’t use RS274NGC_STARTUP_CODE when updating the preview
Docs: Address G52 Circular Link #3565

Acknowledgements

As always, we couldn’t do this without the contributions from the
community, so many thanks to:

CMorley
Sigma1912

 

I am finding that

1. the stepper motors for the two spindles work as expected, however
2. the stepper motors for the axes (B, U, V, X, &, & Z) run at a VERY slow speed. 

The latency test on my Raspberry Pi 5 gave:

• Servo Thread
  • Max Interval = 1,013,089nS
  • Max Jitter = 13,089nS
• Base Thread
  • Max Interval = 46,407nS
  • Max Jitter = 24,074nS

I ran the Step Timing Calculator to set the BASE_PERIOD based on using StepperOnline DM542T drivers.

• Step Length = 2.5µS
• Step Space = 2.5µS
• Direction Setup = 5µS
• Direction Hold = 5µS

The recommended BASE_PERIOD = 26.57µS.

When I run LinuxCNC based on this configuration, the value for the parameter, hm2_yi92.0.stepgen.02.maxvel = 1.

Regardless, the stepper motor does NOT run at 1 rev / sec.

---

Attached are the HAL, INI, and include files for

• Spindle0 (Spindle1 is the same)
• Axis X (axes Y, Z, B, U, & V are the same)

The X Axis is set as Joint 0, Channel 02.

---

Help would be GREATLY appreciated!

Thank you and kind regards,
Rich

Hi everyone,I’ve been working on a CNC project for a while and I’d like some advice before committing to hardware. Here’s my situation:

• I originally built a 3-axis CNC router running on GRBL (ESP32) + a custom PCB. I used that setup for a long time and gained good experience with it.
• Later, I decided to upgrade to 5-axis by adding A and C axes to the same GRBL-based system. While it functions, I quickly discovered a limitation: ESP32 GRBL doesn’t support TCP, so the machine can’t act as a proper 5-axis system.
• Because of this, I started looking into LinuxCNC. At first I wanted to use my Raspberry Pi 5, but I read that the Pi version of LinuxCNC can’t really handle full 5-axis control.
• I then tried installing LinuxCNC on an old laptop, but since it has no parallel port, I searched for hardware solutions that use Ethernet. That’s how I found Mesa boards.

From what I’ve gathered so far:

• The 7i76 series supports 5 axes and spindle control, but its encoder inputs are only for the spindle, not for axes.
• The 7i95 series seems more suitable because it supports encoder inputs for the axes as well. My thinking was that even though steppers usually work fine, it would be good to have encoder feedback to check for missed steps.

Where I’m at now:

• When testing LinuxCNC setup, I couldn’t find any 7i95 options in PNCconf, which left me confused.
• My current hardware: 2.2 Nm NEMA 23 steppers with DM556 drivers on all axes (6 motors total, since Y has dual rails).
• I don’t have encoders yet, I was waiting to see which types are actually supported by the mesa boards.
• As another option, I do have a couple of 400 W Delta B3 servos, but not enough to equip all axes. I’ve considered using them if steppers turn out too weak, but that would mean buying more servos.
• My main goal with encoders is simply to check for missed steps on the steppers.

My questions to the community:

1. Am I on the right track with the 7i95 + LinuxCNC setup for a 5-axis machine with encoder feedback?
2. Would you recommend a different Mesa board or configuration for this?
3. Are there any guides/resources for setting up a 4+ axis machine with Mesa boards and LinuxCNC?

Thanks in advance for any advice!Ozan T.