Advanced Search

First such machine i fixed was back in 1990 !!!
They are complicated machines, but all are made from simple parts, so look at it as separate parts, makes it much easier.
The main hurdle with retrofitting such machines is the logic and interlocks, writing down whatever you already know will help a lot during programing.

TP - Trajectory Planner ( see src/emc/tp/tp.c)
TC - Trajectory Controller. (see src/emc/tp/tc.c))

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.

Makes me wonder why we bother maintaining about 1500 pages of written documentation:

linuxcnc.org/docs/html/

Yes, that's a solution. I'll think about it, if I start modifying the code (I'm not very good at programming) or if I find a solution to add additional control switches (from my window, this solution seems the easiest to me)

Probe Basic is written in Python, you could modify it.

Try a different layout with a 2-element V-box with a 2-element H-box in the top box.

I think that your meter is being constrained to be same width as "Licht" as it is in the same column.

I've already looked through the list, but I didn't find anything conclusive.
It was just in case there was something I'd missed or done wrong.
So your comment supports my analysis, but not really the right one for me. I'll have to find another solution...

Hello,
i created a small ui with glade with two leds, two buttons and a Hal_Meter. How can i enlarge the Hal_Meter? Attached is a screenshot of my main window.

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.