Advanced Search

Axis UI => Machine menu => Show LinuxCNC Status => settings


or from linuxcnc.stat attributes
linuxcnc.org/docs/stable/html/config/pyt...ding_linuxcnc_status

settings
    (returns tuple of floats) - current interpreter settings. settings[0] = sequence number, settings[1] = feed rate, settings[2] = speed, settings[3] = G64 P blend tolerance, settings[4] = G64 Q naive CAM tolerance.

 

lcec.0.n.pos-scale
Set it to how much the encoder increases when moving the axis one mm.
setp lcec.0.2.pos-scale 500
for example, or maybe you have one of those with crazy big numbers. Same anyway.
Read encoder value from lcec.0.2.actual-position (before any scaling)

Where are you seeing that? I don't recall seeing the blending tolerance displayed anywhere, though I suspect I'm just being blind.

That answer works well enough for my purposes- regardless of whether that means "always uses mm" or "always uses machine units".

I guess Y-axis turning/parting wasn't really a thing in the early days of LCNC.

Pausing and axis (disconnect feedback) works fine, especially since the X-axis won't move during the swap.  Your C-axis encoder disconnect component is a perfect example of this.

But I don't see how to 'write' a new/different position for an axis after it's homed.  Unless there's some sort of math going on backstage that takes the current V-axis position and adds/subtracts/whatever from the X-axis.  Switching the stepgen is, as you've shown, pretty straight-forward.

My particular config may be slightly easier to dea with, at least for testing since the X-axis machine zero corresponds with the subspindle in-line with the main spindle.  G53 X0 is where the X-axis will need to stay during the axis swap.

Any idea what a switchable kinematics axis swap thing looks like?

I can see the number changing on the DRO when i turn the shaft of the motor, i guess there is some setting missing on the pitch/turns per mm ?

I did that, but it didn't work. Then remebered i am in mm. And i changed axis.ini and not axis_mm.ini. Commented out everything except the cia halfile in the mm file, and it worked. I can now drive the servo from the gui. But i get an immediate following error on the joint.

Tem que colocar abaixo do link do código mais essas linhas:

net tool-prepare iocontrol.0.tool-prepare iocontrol.0.tool-prepared

It's because it is loaded twice, and once it is from coresim.hal
you will see loadrt [KINS]KINEMATICS or loadrt trivkins or something similar in your hal, that conflicts with the same thing that is written in coresim,hal you can only load kinematics once
and you cannot modify that, it's in the libraries, you can remove the
HALFILE = core_sim.hal
from your ini file
Or as I advised before start from a pncconf configuration, that is more local, and it is easier to understand, as you change settings in pncconf and you see the hal changing, it is more intuitive, just take it easy, it is a steep learning curve.

 

Tried removing all halfiles with sim, still get error trivkins already exist.

im reinstalling the whole unit today.
i was trying trixie as i had to redo my host for the new cnc. But apparently is this very experimental with debian 13.

Im installing the linuxcnc 2.9.4 iso now, which should still be bookworm. then updating to 2.9.8 and installing the patch again

Not sure but looking at this makes me think that CSS is indeed hard coded to the X-Axis:
github.com/LinuxCNC/linuxcnc/blob/4025bf...ontrol.c#L1918-L1922

So the only thing I can think of is to use a switchable custom kinematic that swaps the joints used for the V axis and the X axis.

coresim will still be in the hal lib, which is symlinked and cannot be modified by user.

try to make a base configuration with pncconf, I think that is how I started.

it makes it easier to understand what is happening, also read the docs, very insightful.

switching live I think is last refinement, YangYang working in separating the TP on a separate thread, switching will be refined after that.
At least spiking is gone, the fall back messages with TP1 are expected, just debugs, will be removed in next PR I think, thank you for spending the time testing.

The phasing is done before all-op, it is about phasing with first drive DC epoch, the epoch arrives ages before all-op

Your problem is CPU and or network jitter, the symptoms your are reporting as Hakan correctly deduced, are telling us your latency is too high. 

refClockSyncCycles="1" syncToRefClock="false"

I think is your best bet.

if you still get jitter, I'd say look at your latency, cpu? kernel version? network harware? latency histogram results with a few glx gears?
isolcpus, nohz_full ?

When you start lnuxcnc with sim config from the window system menu, there is a question
whether to make a copy of the config, say yes. You find it then at $HOME/linuxcnc/configs/sim_axis or similar
and your user should own the files.

In the ini file, remove all HALFILE= that has "sim" in them.