Advanced Search

I know that refers to a path's segment.
Yes, it is possible to mean Trajectory Curve.

If you like ladder, then you can use that for your toolchanger.

(Though it isn't easy to program axis movements from Ladder)

linuxcnc.org/docs/stable/html/ladder/ladder-intro.html
linuxcnc.org/docs/stable/html/ladder/classic-ladder.html
linuxcnc.org/docs/stable/html/ladder/ladder-examples.html

I normally suggest controlling a toolchange sequence with G-code. It is a terrible programming language but does have built-in behaviour for moving axes around, for setting HAL pins, and for waiting for the state of HAL pins to change (with timeout).

See the example G-code routine here (which works in conjunction with the carousel.comp)

github.com/LinuxCNC/linuxcnc/blob/master...hange/toolchange.ngc

You can run that whole config (it's a simulator with a graphical representation of a milling machine) by starting LinuxCNC and picking the sim/axis/vismach/vmc_toolchange config and picking one of the two INI files
(this is also an example of two configs sharing HAL and support files, the configs deomnstrate two different types of tool carousel position feedback)

I have pushed a change.

A new .deb file should appear here in an hour or so:
buildbot2.highlab.com/debian/dists/bookw...uspace/binary-amd64/

You can download the .deb file and then install it with:
Note the "./" which tells apt to look at the file rather than search the repositories for a package of that name.

I will try to remember to fill in the actual .deb file name once it is created.

Maybe Curve?
TC represents a segment of the path.

Nicely done. I like your thrust dyno. How well do the 3D printed rotors hold up?

The machine is the same model as this

Is this topic dead? Every single tutorial i have found is like six to nine years old. I'm just getting started with CNC plasma cutting, my shop computer is on Linux because i really dislike windows, but if there's no new tutorials out there to guide newbs, then i might as well not waste my time and just install windows.

Wenn das Leben nur so einfach wäre.

Das ganze wird in menu-config im Klartext eingegeben,.

Ich bekomme noch eine zweite SSD und werde da mal probehalber die 2.8 für Raspi installieren.
 

I installed live-build from the Debian repos for my bookworm machine and had no luck. Upon looking at the firmware function the code to blacklist the firmware was not there.
Building a live-build package from the Trixie branch on my bookworm machine resolved the issue. As I also stated the same procedure as allowed me to successfully build a ISO on my Mint machine.

@Admins

I feel I overstepped my position and would like this topic deleted.

unknown wrote:

Building on a system running Debian Trixie raspi-firmware IS NOT installed. (built twice on 2 different machines)
Building on a system running Debian Bookworm raspi-firmware IS installed. (single build only attempted)

This is because they fixed it (it's actually fixed in Debian 12.1) 

bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065640

The _joint_ (ie the actual moving part of the lathe) is not outside the joint limits.

However the drill chuck _is_ outside the Axis (XYZ) limits.

The INI specifies the joint and axis limits separately. You might just need to able to set the axis limits to allow a very negative Z (deep down the spindle bore is very reasonable for a long drill)

It came as a surprise to everyone, I think, that a fix for a preview bug in Gmoccapy caused the touch-off dialog in Axis to break.

I mean, who would even think to check that when testing the bugfix? It's about the most obscure interaction I have ever seen.

(And it only showed up if trying to touch-off to anything other than zero, too)

It came down to the fact that the Axis touch-off dialog parses the entry as G-code,and passes it through the G-code parser. (this is actually quite cool, you can touch-off to "sin[45]" if you want to.

But that relied on something in the startup sequence initialising something in the interpreter, and that, in turn, was messing up the Gmocapy (and others) graphical preview position. (specifically it was running STARTUP_GCODE every time, but only for the preview)

The fix was obviously good, but a side-effect was making the Axis touch-off work by accident..,

Well, the only person who knows for sure is the release manager.
And he thinks that a 2.9.7 is very likely given that one of the fixes in 2.9.6 broke the WHB... pendant driver.

But he is also looking at an ISO based on Trixie, but that will need a new archive signing key as the current one is considered too short.

Please submit your work as pull requests to the "official" ISO building repository rather than going off on your own with this.

The question is whether the drives can do preset velocity with no commutation.

ChatGPT (or any AI) is going to do very poorly with anything that hasn't been done before.