At the moment i cant run my routines with parameters.

easy to test:

#333 = 20
g0 g54 g43 z#333



 

Edit:
The error occurs on different ui, so it seems linuxcnc related. If other axis are affected, i dont know, because first z-movement lead to abort.
No matter if numbered or named parameter are used
Preview is working

Could you post your configuration files so we can take a look and see what the problem is?

The latest 2.97 version is also available in Debian Testing. The Debian Trixie release version includes 2.94 but it's a trivial 5 minute job to set up APT pinning to just get LinuxCNC from testing and everything else from Trixie as I show here:
forum.linuxcnc.org/9-installing-linuxcnc...97-and-later-forever
This will support any future LinuxCNC upgrades that are pushed to Debian

Hello, everyone. I have a problem configuring a servo from StepperOnline: A6-1000EC. My goal is to control this servo via the python api. It should be possible to position it between 0 and 360° as well as rotation with different speeds.

My first attempt was to configure the servo as an angular axis. Then I wrote a simple python program to control the axis via JOG_INCREMENT and JOG_CONTINOUS. For absolute positioning I switch to MDI mode and send my target position. This works totally fine, but I can't run gcode with this solution, because I can't turn the servo continuous in one direction.

So I tried setting up this as a spindle instead. At first I changed my xml so I can process target-velocity and control-mode. Then I used a mux2 to change the control-mode depending on the use of M3/M4/M5 or M19. This works fine and my frequency drive changes between mode8 and mode9. The spindle control with M3/M4/M5 also works fine, but when I enter a command like M19 R180 Q2 P0 the servo drive throws a fault. When the target position is near the actual position this works, so I assume it is some sort of following error. My bigger problem is, that the actual position of the motor after using M3 for some time is very large, cause it is not restricted to one revolution. Is there a way to change that? At my first attempt using it as an axis I used wrapped_rotary, but that only affected the display, not the actual value.

Does anyone know what I could do, or if there is a better way for the use of an servo as position and continuous motion?

Many thanks in advance

linuxcnc.org/docs/html/gcode/m-code.html...programmed%20timeout )%20occurs.

If you insert M66 P0 L0 between the probe moves then the queue might be cleared as a side effect.

Great news, thanks for the idea. I'll check it out tomorrow with version 2.9.7 and let you know the results.

I'm looking for suggestions for a simple bread & butter Linux CNC install.

It seems like an Raspberry Pi 5 + Mesa 7i96S might be the current standard, but it's not super clear? A while back it seemed like the Beaglebone was a good option, but it seems things have not gone that way?

Background...
I've built/retrofitted a number of machines with Linux CNC, but not for perhaps 10 years.  I've done a lot of machining and I'm fully competent with Linux.

I've got a new project that wants to integrate 2 Sherline CNC chucker lathes with some additional widgets.  Each lathe would get its own LinuxCNC hardware & software and the integration would be via ssh/linux command line.

If I can get the system working well, I might get orders for 10 or 50 of these systems over the next few years, so I would really like to use a stable, easy to get, standardized off-the-shelf parts, that can be expected to remain available for the next 5 years. I'm *not* looking to cobble something together out of 10 year old PCs, and I'd prefer not to build on some wierd/cheapo/legacy PC off Amazon which may go away in 3 months.

I'm looking for a simple reliable bread & butter LinuxCNC platform.

Suggestions?

BB