Advanced Search

Yes and no.
It's programmatically possible (lathe views gets closer) but not built in.
What version of linuxcnc do you use?

Here I modded to show a more lathe like perspective:
 

Anyway, I solved it with 7i80db_16_7i85sx2d.bit and replacing stepgen00 with stepgen04, now everything works. I'll leave it like this, as I'll switch the 7i97t to analog soon. Thanks!

dlv wrote:

tuxcnc I'll check out dxf2gcode.  I can export a DXF and post process that.  You're not wrong, Fusion is a beast.  But I'm really quite comfortable on the design side and for the most part I like working with it.  That said since I'm learning the CAM side I am definitely open to trying some alternatives especially if they're open source.

 

I'm not against Fusion if the user paid for commercial version.
I'm against the "free" versions (student, hobby, etc.), because someday thats may become won't start without any warning.
However Fusion is large program with thousands functions, so the good question is it worth learn this for simply projects...
I suggested Librecad plus dxf2gcode not because this is Fusion replacement (is not), but because it is very simple and enought for simple projects.
In Librecad you easy can place small circle at the center of big circle, and in dxf2gcode yo can learn the edition of postprocesor  in one hour, because it is plain text human readable.
For example this is fragment of my laser postprocessor:My laser has no Z axis, so no lines for Z moves, but the feed of Z move is simply translated to laser power (F -> S).
I don't know how is in Fusion (I'm not curious about it), but I think this is more complex. In some CAM you can nothing without programming knowlege...

 

OK, see if there is something useful here
www.google.com/search?q=linuxcnc+Hole+Sp...ox-b-lm&hs=BQhV&sa=X

Thanks. I added the message, which displayed, so that is the .ngc being loaded. 
I had just run a facing cut which had a taper. Ran it after adding that msg, and had no taper. I will need to see what the error correlates with.

Ahh that's a pin file error, I'll fix that today or tomorrow.

Thanks Rod.  Fusion has cut profiles.  The approach would be similar to the layers you mention I think.  Select the holes to be spotted in one cut profile and the rest of the part sans the small holes in another.  Perhaps a bit more "one click" in Sheetcam but it's really no trouble in Fusion.  Then from the two profiles I post two different NC files so I can change my torch amps between spotting and cutting (I have to do that manually, no fancy Hypertherm for me!).

I will look into writing a gcode filter take small holes and replace with the spotting commands I have in my test code.  That's the approach I've been thinking of anyway.  Was wondering if anyone had already done that.  If there are examples out there of gcode filters anyone can point me at I'd appreciate it.  I've got decent C and Python skills.

Tommy I looked at the feature I think you're referring to and from what I read QtPlasmaC will take a gcode command to only run the pierce operations it finds in the file and no cut ops.  I guess I'd use the cut profile approach above with just the holes in it and set the lead in to put the torch in the hole center for the pierce.  Like 2mm holes with a 1mm 90deg lead in.  Then use this: So yeah that would be ok if I wanted to actually pierce the hole centers.  I like the "center punch" dimples I'm getting with the M3 command test above but this certainly would be a solution to try and I will.  Might work better on thicker steel.  So far I'm just testing on aluminum sheet.

tuxcnc I'll check out dxf2gcode.  I can export a DXF and post process that.  You're not wrong, Fusion is a beast.  But I'm really quite comfortable on the design side and for the most part I like working with it.  That said since I'm learning the CAM side I am definitely open to trying some alternatives especially if they're open source.

Thanks guys!

Good Day CnC's

I am a "TOTAL" new bee to Linux and to LinuxCnC trying to get the new Ver. 10 to run with the help of AI and maybe 5-6 hours installing on my  Zorin 18.1 Linux computer.
I managed to get it installed only to get an terminating error on opening the program it says to create a report file which i did but can not find the report and don't know how to send it to someone if i did find it. so I seem to need some help if some one can provide some guidance
here is a cut and paste of the error. it will not be hooked to any machine at this time. Just would like to get the program to run for right now

Tks if anyone would like to tackle this. if not I'll understand.

5280 (ken)


Print file information:
RUN_IN_PLACE=yes
LINUXCNC_DIR=
LINUXCNC_BIN_DIR=/home/ken/linuxcnc-dev/bin
LINUXCNC_TCL_DIR=/home/ken/linuxcnc-dev/tcl
LINUXCNC_SCRIPT_DIR=
LINUXCNC_RTLIB_DIR=/home/ken/linuxcnc-dev/rtlib
LINUXCNC_CONFIG_DIR=
LINUXCNC_LANG_DIR=/home/ken/linuxcnc-dev/src/objects
INIVAR=inivar
HALCMD=halcmd 
LINUXCNC_EMCSH=/usr/bin/wish8.6
LINUXCNC - 2.10.0~pre1
Machine configuration directory is '/home/ken/linuxcnc-dev/configs/by_machine/cooltool'
Machine configuration file is 'Basic540_3axes.ini'
INIFILE=/home/ken/linuxcnc-dev/configs/by_machine/cooltool/Basic540_3axes.ini
VERSION=1.1
PARAMETER_FILE=stepper.var
TPMOD=
HOMEMOD=
TASK=milltask
HALUI=
HALBRIDGE=
DISPLAY=axis
COORDINATES=X Y Z
KINEMATICS=trivkins
Starting LinuxCNC...
Starting LinuxCNC server program: linuxcncsvr
Can't execute server program linuxcncsvr
Shutting down and cleaning up LinuxCNC...
Removing HAL_LIB, RTAPI, and Real Time OS modules
Removing NML shared memory segments

Debug file information:
Stopping realtime threads
Unloading hal components
rtapi_app: exit received while not running

I don't see anything in 'facing.ngc' that could cause a simultaneous move in X and Z.

Could you put a debug message inside of your 'facing.ngc' and run that macro again. Just to be sure that that is the actual file being executed (You should see a info message popup in the gmoccap gui).

Something like adding '(MSG, Executing facing.ngc)' to the start of the sub:

Hi Andy,
Sorry for the slow response. I dropped the ball on this as I was doing wood working .

This is the facing.ngc file I am using. I have not modified it at all. I just noticed I have both a "lathemacro.ini" and a "lathemacros.ini" (plural) in my machine directory. Could that be the issue?
Cheers,
Mark

Most UIs allow you to adjust the view direction.

linuxcnc.org/docs/html/gui/qtvcp-widgets...idgets:gcodegraphics

Seems to suggest using the _view property in the handler code.

I have a good model of my lathe, but the mill model is rather lacking.
There are a few milling machine models on Thingiverse / Printables etc.

grandixximo wrote:

github.com/mika4128/liscio/tree/main
new trajectory/gcode compressor for the future trajectory planner, testers wanted, feed your gcode to it, check the SVG output
 
Hi grandixximo and mika4128 (Yang Yang),
Curve smoothing is the correct and best way to tackle Jerk that is normal to the motion path. This is reflected in the curve smoothing features from the large CNC controller brands referenced in the Liscio documentation.
I put the liscio library through an AI based analysis for integration into linuxcnc.
This is the analysis it has come up with.

Let me know how we can progress on this topic and the eventual jerk limitation implementation.

-automata

 

Library facts (verified in source, not the README):
- 6 `.c` files + 1 internal header + 1 public header; MIT licensed, single author (Yang Yang
  `This email address is being protected from spambots. You need JavaScript enabled to view it.` — the same upstream author as the already-vendored `cruckig`).

- Exactly one `calloc` (create) and one `free` (destroy); zero allocation afterward. No printf/assert/
  globals in library paths. Context is ~148 KB (91% of it a 64-slot arc-merge buffer); fitter stack
  worst case ~25–30 KB (bounded recursion, depth 8).

- `liscio_pose_t` is layout-identical to `EmcPose` — nine consecutive doubles x,y,z,a,b,c,u,v,w
  ([emcpos.h:19-23](../src/emc/nml_intf/emcpos.h), liscio.h:44-50). Add a `static_assert(sizeof)` in the
  adapter as cheap insurance.

- Emit is a synchronous callback invoked inside `add_*`/`flush` calls.### Known library defects and gaps (must be addressed before starting integration)| # | Defect | Evidence (liscio clone) |
|---|---|---|
| L1 | `liscio_reset()` does not clear `arc_buf_n` — arcs buffered before an abort are emitted into the **next program** | src/liscio.c:1437-1444 |

| L2 | No runtime tolerance setter — cfg is copied at `liscio_create`; G64 P/Q changes mid-program have no cheap path | src/liscio.c:108-131, liscio.h:285-309 |

| L3 | XYZ-collinear LINE fast path skips the ABC/UVW linearity gate — interior rotary nonlinearity silently discarded | src/liscio.c:540-561 |

| L4 | No `isnan`/`isfinite` anywhere; tolerance gates are `if (dev > tol)` so **NaN passes** | grep of src/ |

| L5 | F-word changes are absorbed silently (first-F-wins, plus an off-by-one via the flush reseed) | src/liscio.c:669-676, 1302-1311 |

| L6 | `liscio_emit_stop(pos=NULL)` emits zero poses despite header docs claiming last-known-position | src/liscio.c:1402-1407 vs liscio.h:363-367 |

| L7 | `liscio_add_arc` validates nothing (unit normal, radius/center consistency, type field) — caller trust | src/liscio.c:1181-1239 |

| L8 | Corner/discontinuity detection is XYZ-only — pure-rotary reversals never split the window | src/liscio.c:687-709, 736-752 |

| L9 | Struct doc mentions a `turn` field that does not exist (direction+wrap live in signed `arc_angle`) | liscio.h:98-105 |

| L10 | Independent verifier (`test_verify`) and fuzzer are XYZ-only / add_line-only — 9D fidelity is not regression-gated upstream | test/test_verify.c:53-62, test/test_fuzz.c |

L1 and L3 are correctness bugs; L2 is a hard integration blocker; the rest are adapter obligations.

The original bearings are 6209 2RS and 6009 2RS; they don't have "C3" stamped on them, so they are likely CN (standard clearance). They are press-fitted without any additional clamping.

You only need C3 if the bearing is an interference fit in the housing and on the shaft.
What are the original bearings? If they are C3 it will say on them.