Advanced Search

Ive started using this yesterday as well... honestly, im rooting for it to get 90% as good as fusion, and hopefully 80-90% of the Manufacturing tab, that will bring linux into real world CAM finally.
I even was able to connect claudecode to it to design stuff via prompt. Insane how fast stuff is moving.

I don't think the Axis user interface has any provisions for multiple spindles. For on screen control of spindles other than the primary one you will either have to settle for using MDI commands or build a VCP to control the other spindles (such as PyVCP, GadeVCP, or QtVCP.)

Hello everyone,I'm developing a custom CNC controller on Ubuntu Linux with real-time capabilities. The core control system is being written in C, and I'm working on integrating EtherCAT for servo drive communication.I'm now considering the best approach for designing the user interface (HMI).My main questions are:

• Should I develop the entire application, including the GUI, in C/C++ using a native Linux GUI framework?
• Would it be better to build a modern web-based interface using React, with a separate backend communicating with the C control core?
• What architecture would you recommend for a CNC controller that requires reliable real-time motion control, low latency, and a responsive user interface?
• Are there any existing LinuxCNC components or libraries worth considering for this purpose?

My priority is to keep the real-time control layer independent of the GUI, while making the interface modern, maintainable, and easy to extend.I'd appreciate hearing about your experiences and recommendations.Thank you!

Unfortunately,  I don't know about Debian, I use Mint
and build kernels from source.

Hola, después de mucho tiempo. Finalmente he armado esa pc, bien antigua, hoy con 1024 megas de ram ddr, su procesador 32 bits, y por fin su ssd. Descargué el Ubuntu propuesto, lo instale, re bien, sin internet, pero cuando probé su latencia, dió unos valores altísimos , probé, probé y luego volví a instalarle Linuxcnc 2.7.14, pero al realizar su latencia, iguaklmente muy alto los valores, por ende no me sirve para utilizarlo. Sería tan amable de compartirme su hardware tiene en su Ubuntu usado por años, sin problemas?, sigo insistiendo que me tiene que servir ñeste viejo cpu, pero los valores no acompañan para nada. Muchisimas Gracias!...

How to install 7.x to debian 13 from backports repo ?

Quick Note: Everyone in the EU, looks like the USPS is charging me for prepaid Duties, Taxes, and Fees now on top of the postage.

Upside: Duties and Taxes will be prepaid.
Downside: I have to include that cost in the Shipping quote.

If you have a local dealer, please check with them first. Even used, International sipping and duties/taxes may make my listings cost prohibitive.

Mesa 7I95T has been SOLD, the rest is still available.

Beckhoff EL5001-0012

I think the issue is that you are not using the feedback from the same encoder that's generating
the index. In this case, homing to index cannot work.

I'm certainly open to being educated here but I was reasonably convinced by what I was seeing. Have a look at my notes and perhaps you can see where / if I may have misunderstood what was happening:
www.murraye.com/2026/08/improving-homing...acy-on-linuxcnc.html

In my case, with 5um resolution scales and closed loop controls, my final resting position after homing can't be any more accurate than the resolution of the scales allow, so perhaps I've been chasing up a dead end anyway? A positional accuracy of 5 or 10um from true is probably the best I could hope for on a good day.

The PID element was initially due to my controllers being unstable but the homing velocity did seem to impact accuracy too.

Many thanks for your response.

I have found that 7.x kernels are better than 6.s kernels jitter wise.

It sounds like you are not using the index hardware at all.
There should be no effect of LinuxCNC timing or PID tuning
on the index position homing precision, if the index hardware is
actually used.

That is, the precision of position capture at the index position is
independent of the motion accuracy, though of course motion accuracy
after the index position is captured _is_ dependent on PID etc.

Holzwurm56 wrote:

Hello,
When using a parallel port, entering the jitter value in Stepconf results in the calculation of the maximum step rate. Does this figure—for example, 33333 Hz—apply to each axis individually, or to all axes combined?

For each pin, parallel port so all pins can be controlled in parallel or at the same time.