@COFHAL – you asked about the ~/nativecam directory and OWord macros. Here's what's going on:

NativeCAM creates and uses ~/nativecam as its working directory for temporary files, tool tables, and post-processor configs.

The SUBROUTINE_PATH in your LinuxCNC INI file must include the path to the OWord subroutines that NativeCAM generates. Without that, LinuxCNC won't find the macros.

If Axis shows no errors but QTDragon fails with "can't find macros or OWord," it's almost certainly a path issue.

Quick fix: add something like this to your INI file:

text
[RS274NGC]
SUBROUTINE_PATH = ~/nativecam:/usr/share/linuxcnc/ncfiles
Restart LinuxCNC and try again. If it still doesn't work, paste your full INI file here and I'll debug it with you.

— Axemas

@Surmetall – thank you for the kind words and for the continued excitement about the lathe features, especially the polyline workflow alongside G71/G72/G73. That preview video took a lot of work, and it means a lot that it sparked anticipation.

Since my last update, I've been testing the polyline path generation on real G-code scenarios. No major blockers – mostly fine-tuning the toolpath logic and cleaning up the UI response for lathe operations. I'm planning to push a test package soon.

And yes, I'd absolutely love for you to test it on a real machine. Your offer to provide feedback, screenshots, and G-code examples is gold. I'll reach out to you directly when I have something ready for real-world testing.

— Axemas

Hey @giunta.gio — apologies for the late reply, I completely missed your question back in May.The main hardware specs and overview are now live at cncproton.com/ We're currently finalizing the full technical documentation package. Over the next couple of weeks, the site will be updated with:

• Detailed wiring diagrams and complete pinout tables
• Example HAL configuration files for LinuxCNC
• More photos of the assembled modules and various configuration options

If you have any specific questions about your machine or particular hardware features, feel free to ask here or reach out through the contact form on the site — I'm happy to go into detail.Axemas

Hello Tommy:

The installation worked and I am able to launch the latency_histogram and 3D gears tests.

However do you know if there is a script or I am still missing steps in compiling the 
rtai_lxrt.ko, rtai_fifo.ko, rtai_sem.ko,rtai_sem.ko, rtai_tbx.ko, rtai_bits.ko and rtai_mq.ko kernel modules.

I check the /usr/realtime-5.4.258-rtai-amd64/modules and I only see a shorter list of compiled RTAI specific kernel modules
drwxr-xr-x 3 root root   4096 Jun 10 15:36 .
drwxr-xr-x 7 root root   4096 Jun 10 15:36 ..
drwxr-xr-x 2 root root  24576 Jun 10 15:37 linuxcnc
-rw-r--r-- 1 root root  26785 Nov 18  2022 Module.symvers
-rw-r--r-- 1 root root  38088 Nov 18  2022 rtai_hal.ko
-rw-r--r-- 1 root root  43368 Nov 18  2022 rtai_math.ko
-rw-r--r-- 1 root root  21368 Nov 18  2022 rtai_mbx.ko
-rw-r--r-- 1 root root  46816 Nov 18  2022 rtai_msg.ko
-rw-r--r-- 1 root root 268328 Nov 18  2022 rtai_sched.ko


thanks
Michael 

 

Always the 'joint 1 on limit switch error' or 'joint 0 on limit switch error'.
Mostly at pierce now, but has slowly been creeping in and would do it halfway through a cut. same error.

rodw wrote:

Spumco, great work. If you have to manually start the service each time. sounds like you overlooked the udev rules in the first post, Sorry about the formatting errors but its an awful post to edit

sudo geany /etc/udev/rules.d/99-ethercat.rules
and the following code block.
 

Rod - I hadn't actually gotten to that section of the installation yet.  The first 'ethercat slaves' check is before the 99-ethercat.rules line.

I just stopped when I got the errors starting ethercat service for the first time.  Bulldozing ahead past errors has not served me well in the past, despite my habitual attempts.
 

OK, hold the EMI filter thought for now. When I had EMI issues, fitting one solved it.
Choose from here locally, but there are other IEC connectors with mains switch and fuse built in
www.jaycar.com.au/components-electromech...-emf-products/c/2GLC

But in your case what is odd is that its been trouble free for so long. When you say error, is it always a limit switch error or could it be the arcOK is failing?

 

Still using the hypertherm XP45. it's been on it the entire time.

no EMI filter yet.

Hello,
I'm wanting to set up an environment for learning cnc concepts with Linuxcnc
  e.g. Machine PC plus development/simulation PC
Goals are to
  understand cnc systems
  experiment with cnc systems
  build a capable hobby machine
Skills
  Familiar with Linux (Gentoo)
  Basic coding skills. Bash, Python, read, write, loops and if statements

So far I have a working pen plotter built, and based around Openbuilds Acro XYYZ using Fluidnc ESP32 controller.
Linuxcnc installed on old PC (parallel port), in my garage workshop with Aliexpress BOB arriving soon. Plan is to move to Linuxcnc.
Main PC in my house. No network connection yet

Question
  What is good set up?
    Simulation setup on main PC to sort out configurations... transfer to machine PC? Is this workable.
    SSH into Linuxcnc box and used command line tools to work in Linuxcnc?
    VNC or something similar?


Phil

  


 

What plasma cutter are you using these days?
Do you have an EMI filter on your mains inlet to the control box? Jaycar have them
 

Couldn't find any spots showing voltage.

Ran new earth wires everywhere, from the gantry, torch holder, x axis motor mount, y axis motor mounts, table, water table.

No change, still getting errors when the torch begins a pierce.

Spumco, great work. If you have to manually start the service each time. sounds like you overlooked the udev rules in the first post, Sorry about the formatting errors but its an awful post to edit

sudo geany /etc/udev/rules.d/99-ethercat.rules
and the following code block.

Thanks PCW,
I will try this morning

You could use the hal scale  component to subtract 50 from the commanded spindle speed,
something like:

loadrt scale
setp scale.0.gain 1
setp scale.0.offset -50
net spindle-vel-cmd-rpm => scale.0.in
net fixed-spindle-rpm scale.0.out  [HMOT](CARD0).pwmgen.00.value
addf scale.0 servo thread

 

sudo apt update and upgrade seems to have fixed whatever was wrong.

after reboot:

mill@debian:~$ sudo systemctl start ethercat.service
[sudo] password for mill: 
mill@debian:~$ ethercat slaves
0  0:0  INIT  E  AS715N_sAxis_V0.10
1  0:1  INIT  E  AS715N_sAxis_V0.10
2  0:2  INIT  E  AS715N_sAxis_V0.10
3  0:3  INIT  E  AS715N_sAxis_V0.10

I think I'm in business.

Thanks a ton for the assistance.