Advanced Search

Thatś it. Thanks

My custum_postgui.hat is now correct
#[Spindel]
net spindle-vel-cmd-rpm => gladevcp.Spindel1

I guess i really have some problems with reading signals in the machine.hal. I thought in my case "spindle.0.speed-out" give me directly my float value. Have to write a small manual for me.

This has been asked before on here (but don't bother looking, there was no helpful answer).

If you load the system then open a terminal and type "halcmd show pin" you will get a list of all the HAL pins. You would then need to search that list to see if any pins are of the OUTPUT type and look to be increment-related.

From a brief scan of the source code,I don't see anything, but I am not clear how QtPyVCP creates HAL pins (if it does)

Have fun with windows...

Entry level regular PLCs are not all that expensive as well.

Linux CNC has Classic ladder to do PLC logic.

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