Ncam and Lathemacros conflict

  • tuxcnc
  • Away
  • Elite Member
  • Elite Member
More
07 Aug 2026 14:30 #348532 by tuxcnc
Ncam and Lathemacros conflict was created by tuxcnc
You can install ncam and lathemacros together, but only lathemacros will works properly.
The cause is use the same names for different subroutines:
root@HP-15:~/linuxcnc/configs/sim-lathe# ls -ln *.ngc
-rw-r--r-- 1 0 0 1182 2026-01-07  boring.ngc
-rw-r--r-- 1 0 0  595 2026-01-07  facing.ngc
-rw-r--r-- 1 0 0 1151 2026-01-07  radius.ngc
-rw-r--r-- 1 0 0 1037 2026-01-07  threading.ngc
-rw-r--r-- 1 0 0 1184 2026-01-07  turning.ngc

root@HP-15:~/linuxcnc/configs/sim-lathe/ncam/lib/lathe# ls -ln *.ngc
-rw-r--r-- 1 0 0 1891 04-20 18:51 boring.ngc
-rw-r--r-- 1 0 0 1491 04-20 18:51 facing.ngc
-rw-r--r-- 1 0 0 3781 04-20 18:51 radius_od.ngc
-rw-r--r-- 1 0 0 3334 04-20 18:51 threading.ngc
-rw-r--r-- 1 0 0 4678 04-20 18:51 turning.ngc
(I removed results not matter.)
You can recognize ncam's files by "(author : Fernand Veilleux)" comment, thats lack in lathemacro's.
Ncam (Python 3.0)) works properly and generates good g-code, but LinuxCNC uses subroutines that found first... 
This causes horrible and confusing errors, like :
G-code error in ncam.ngc
Near line 101 of
~/linuxcnc/nc_files/ncam.ngc
Negative word used
But actually there is no error in ncam.ngc, but only wrong subroutine file is used...

The solution is very simple (rename subroutines and change some lines in python sources), but this must be done by the authors, not by users...

Please Log in or Create an account to join the conversation.

Time to create page: 0.143 seconds
Powered by Kunena Forum