Search Results (Searched for: )

  • Todd Zuercher
07 Apr 2026 10:15 - 07 Apr 2026 13:19
Replied by Todd Zuercher on topic Homing To Index Following Error
It's the current release 2.9.7

(Edit)
Had to go look at what was actually on the machine, and it's 2.9.8 running on Debian Trixi.
  • grandixximo
07 Apr 2026 09:37
Replied by grandixximo on topic Ethercat random jitter fix
I've used LeadShine and XingJie same issues with both, there may well be mitigations on the servos side for some manufacturer, but that does not mean the standard of Ethercat says they should be doing such a thing. So it's luck?
  • Aciera
07 Apr 2026 09:21
Replied by Aciera on topic Rotary axis backplot — centre of rotation not following WCS offset
Note that the _preview_ does not take offsets into account:
linuxcnc.org/docs/stable/html/config/ini...sub:ini:sec:rs274ngc

 
  • dredivan
07 Apr 2026 08:35 - 08 Apr 2026 14:14
Rotary axis backplot — centre of rotation not following WCS offset was created by dredivan
 
Hi,

I have a 4-axis MPCNC with a rotary B axis mounted at the far end of the Y travel (machine Y=700mm). The rotary axis is fixed — it does not move along Y.

G-code is generated by CAM with program zero at the chuck face, all moves go in Y-.

The problem: the backplotter does not display the toolpath correctly. Instead of showing the wrapped toolpath around the tube near the chuck, it draws a large circle. I believe this happens because the backplotter uses machine zero as the centre of rotation rather than the actual chuck position.

Setup:
- LinuxCNC 2.9.8 stable
- trivkins coordinates=XXYYZB, 6 joints
- qtdragon_hd interface
- GEOMETRY = !-BXYZ

Is there any way to tell the backplotter where the centre of rotation is?
Code:
[DISPLAY] DISPLAY = qtvcp qtdragon_hd # qtdragon saves most preference to this file PREFERENCE_FILE_PATH = WORKINGFOLDER/qtdragon.pref POSITION_OFFSET = RELATIVE POSITION_FEEDBACK = ACTUAL MAX_FEED_OVERRIDE = 2.000000 MAX_SPINDLE_0_OVERRIDE = 1.5 MIN_SPINDLE_0_OVERRIDE = .5 DEFAULT_SPINDLE_0_SPEED   = 12000 # spindle up/down increment in RPM SPINDLE_INCREMENT = 200 # min max apindle speed manually allowed  MIN_SPINDLE_0_SPEED = 1000 MAX_SPINDLE_0_SPEED = 20000 # max spindle power in Watts MAX_SPINDLE_POWER = 2000 #MAX_SPINDLE_OVERRIDE = 1.000000 #MIN_SPINDLE_OVERRIDE = 0.500000 INTRO_GRAPHIC = linuxcnc.gif INTRO_TIME = 5 #PROGRAM_PREFIX = /home/user/linuxcnc/nc_files PROGRAM_PREFIX = /home/user/cnc-programs INCREMENTS = 5mm 1mm .5mm .1mm .01mm  ANGULAR_INCREMENTS = 1, 5, 10, 30, 45, 90, 180, 360 POSITION_FEEDBACK = ACTUAL DEFAULT_LINEAR_VELOCITY = 40.000000 MAX_LINEAR_VELOCITY = 100.000000 MIN_LINEAR_VELOCITY = 0.500000 DEFAULT_ANGULAR_VELOCITY = 12.000000 MAX_ANGULAR_VELOCITY = 180.000000 MIN_ANGULAR_VELOCITY = 1.666667 EDITOR = gedit GEOMETRY = !-BXYZ CYCLE_TIME = 100
  • Hakan
07 Apr 2026 08:32
Replied by Hakan on topic Ethercat random jitter fix
Theoretically the problem is there. 
Some drives may be better than others to conceal the problem.
When you use syncToRefClock and don't hear it you will not hear it.
I mean the drives will not suddenly start being noisy.
The chance of hearing it is roughly every servo loop time/jitter start of linuxcnc.
With 7 microseconds jitter, you can hear it every 142'nd start of linuxcnc.
And you hear it throughout the linuxcnc session.

I thought my drives were immune to this, but after carefully listening I found they also
experience this, but they don't sound awful, just a very mild "tic".
The drives don't have to make noises, but they should definitely react to it.
It's basically a disturbance in the position flow, requesting an artificially very high or low acceleration.
  • rodw
07 Apr 2026 07:53
Replied by rodw on topic LinuxCNC not working with new 64-bit desktop and parallel port

This rang a bell from when I wrote a terminate-and-stay-resident PC-DOS (stop laughing) program that intercepted data.
I did something similar but it trickled point of sale transactions out of a cash register to accounting software (And I got paid for it!)
  • rodw
07 Apr 2026 07:49
Replied by rodw on topic Ethercat random jitter fix

I’ve been following this thread with interest all along. What surprises me, though, is that I haven’t experienced the jitter issues described so far. I’d be interested to know what hardware you’re using. Perhaps there’s a correlations 
Its never been an issue for me  either. I did wonder the other day if newer hardware was  not a concern.
  • meister
07 Apr 2026 07:39
Replied by meister on topic LinuxCNC-RIO - RealtimeIO for LinuxCNC based on FPGA (ICE40 / ECP5)
soooooo, dev is merged to main, no way back :)

there are some big changes:

### Warning
* breaking changes, please open your config in rio-flow to fix/convert some stuff

### Gui
* new graphical config-gui: rio-flow
* removing old rio-setup

### Genaral
* move all stuff into plugins (boards/modules/breakouts)
* replacing modbus -> mbus/mbus_device/mbus_hy
* replacing i2cbus -> i2c/i2c_device
* better simulation
* test-tool is now based on the hal-component c-code
  • opw
07 Apr 2026 07:11
Replied by opw on topic Simple G7x Profile editor for Linuxcnc/Axis
Thanks for reporting this. I am a little pressed for time these days, so I don't know when I get around to checking and fixing it. 

 
  • meister
07 Apr 2026 06:38
Replied by meister on topic Raspberry with LinuxCNC direct interface
Untested

 

 

File Attachment:

File Name: rpi4-stepper.zip
File Size:597.68 KB
  • Tserakhau
07 Apr 2026 06:36
Replied by Tserakhau on topic Retrofitting a 1986 Maho MH400E
  Good afternoon.My name is Victor, and I'm restoring a MAHO 600E milling machine and converting it to Linux (the original Philips operating system).Thank you so much for this thread; many questions were resolved using the forum.I received the machine without a spindle motor, coolant system, and most relays.I've already done almost everything; the machine moves and finds its home position.I installed and tested the speed control box; all speeds shift perfectly! (The box is completely identical to yours, although the motors are installed slightly differently.)I've also already configured the lubrication system, hydraulic clamp, and MPG control panel.My question is: what needs to be done next after setting up the simulator? How do I implement this into the .ini or .hal files?I apologize for any inaccuracies in the text of this message; I'm using Google Translate because my English is poor.
  • masawee
07 Apr 2026 06:15 - 07 Apr 2026 06:17
Replied by masawee on topic Raspberry with LinuxCNC direct interface
i think NOT need this HAT, i think can build own "hat" mean connect to gpio pins shift level converter tx108 chip module, input is 3,3V and this module convert output to 5V and this 5V signal can wired to stepper driver board DM556 etc, step pin and dir pin and enable pin. but problem have how i setting rpi4 linuxcnc all gpio pins ? rpi4 and has installed linuxcnc but if looking have only config wisard and this can only setting paraller port pins, and pnconfig tool has only how setting mesa card pins, i not understand how can setting rpi4 gpio pins all step, dir, enable and all input pins home, e-stop, limits, probe, etc pendant encoder, rotary SW, axis select, scale select. i have installled linuxcnc to rpi4 and software/image working ok, but how setting gpio pins ?
  • grandixximo
07 Apr 2026 03:23 - 11 Apr 2026 14:03
Replied by grandixximo on topic LinuxCNC S-Curve Accelerations
 
I was wrong, on closer inspection the planner can stay within the jerk limit without falling back to a full stop.

It was a bug in the jerk budget split during Bezier blends. Tangential jerk (Ruckig along the path) and centripetal jerk (curvature change through the blend) were budgeted independently, 50% and 100% of the per-joint limit respectively, assuming they're orthogonal. They are in Cartesian space, but not per joint axis, where they add as scalars. For @ruediger123's octagon: 25k + 50k = 75k on a 50k limit, matching the ~47% overshoot in the HALscope trace.

Fix: subtract the tangential share before allocating centripetal. 25k + 25k = 50k, exactly at the limit, no overshoot, no wasted headroom. Corner velocity drops ~20% vs the buggy code, but it's the true physical maximum.

@PCW was right, the TP should always obey constraints. Fix is in the 9d branch.

Edit:
the artifacts at the end of the page.
I'm also looking at what Automata had reported, I think I can improve merging of small segments, I'll put some effort into that


Edit:
I think the previous build maybe have some issue because I merged master without being careful
New build, still working on speed, not ready yet

delete link, this had issues too
  • spumco
07 Apr 2026 01:32
Replied by spumco on topic Lathe C axis homing
Here you go.

Again, it's complicated.  Feel free to ask questions if something is unclear.

A few thoughts:
  • Still a work in progress, but the part(s) you want works.
  • HAL files are broken up by major components of the config.
  • Lots of comments - you should get a sense of the uncountable number of times I've tried or tweaked something.
  • Signal names are all upper case because LCNC's halshow sorts by case first, then alphabetically.  Drives me nuts searching for signals if they're all jumbled due to upper/lower case.
  • Sub-spindle is not connected to an axis.  LCNC doesn't have duplicate rotary axes like UVW for XYZ.  I found (so far) M19 works fine for the sub.
  • Main spindle motor is a SZGH 'servo spindle' - an induction motor with a pretty smart drive.
    • The drive has position, velocity, and torque modes, just like a brushless PM servo
    • I believe @Aciera switches his drive between velocity and position when he switches LCNC between spindle and C-axis.
    • I found that position mode had a bit of dither at stand-still, possibly due to the induction motor characteristics.  So my drive/motor is always in velocity mode, unlike @Aciera's example.  This may help you with your Schaublin's spindle drive.
  • --Matt--
06 Apr 2026 22:58 - 06 Apr 2026 23:01
Replied by --Matt-- on topic Does auto-leveling for Probe Basic exist?
You may find that the user tab for Z-compensation is suitable for PCB machining (that is what I intend to use it for)...

forum.linuxcnc.org/qtpyvcp/56808-surface...asic?start=13#339938

This lets you probe the surface with a grid and then when compensation is enabled it applies an interpolated Z offset so that it tracks the surface. This way you don't actually have to modify the g-code. (Should make engraving depth more consistent if the bed isn't perfectly level).
Displaying 5011 - 5025 out of 11813 results.
Time to create page: 0.348 seconds
Powered by Kunena Forum