Advanced Search

Delete the red potion and make sure the lines above and below it are there still for the manual tool change.

need some lines in your main hal file also, check the docs it spells it out very clearly in the machine config setup docs. step 5.

kcjengr.github.io/probe_basic/machine_config.html

Hello All!

We are preparing to merge a BIG Probe basic update. it will require some config setting updates and some new folders be added.  I have added a new "Update Release Notes" section to the docs page which should be very helpful going forward for when we have updates release.  please feel free to have a look and give feedback!

kcjengr.github.io/probe_basic/update_notes.html

My manual tool changing does the Probe Basic. 
If in MDI I use "T2 M6 G43" , the line stays active with the play icon, but never ends.  The same issue in NC files.

Nothing happens, no pop-up, etc

Here is probe_basic_postgui.hal

forum.linuxcnc.org/show-your-stuff/32784...-15-retrofit?start=0
Payed much more (3280 Euro + Mesa boards) for this but it was working...till mice had a run at it in my shop!
Retrofitted and working with LinuxCNC (see videos on that link), so yes it is worth retrofitting it.
Difficulty is high for sure, so see if you can get the schematics for it, that will save a lot of time and headache.

Do it, we are here to help as much as humanly possible.

I am new to LinuxCNC, but I play a software engineer in life.  I have identified a few areas where new or updated (and refactored) components could be beneficial.  What is the current best practice to build HAL components?  I would assume halcompile, but more specifically, .comp files or just long-hand .c?  The components that I am currently thinking about are in the user-space.   The first one I want to tackle is an updated/new hy_gt vfd component.  I am running 2.9, so backward compatibility is not a personal concern for me, but maybe people don't update?

Any feedback would be appreciated.
Thanks