andypugh wrote:
Delron wrote: No, I understand how hal is loaded. I thought maybe the axis.remote command could be hooked to a net and input like a function.
That's what my Python component does. It is a HAL wrapper for the command line instruction.
You know, I should have known that already after you wrote that component. My brain is so tired that it just does not think right all the time. It was a silly question. Sorry.
I still have to see if that Python script works for me. Will be working on it tonight or tomorrow. Thanks again.
Would I be correct in assuming most users simply use the keyboard and mouse to touch-off? I feel like I'm forging my way down a path few others dare. I would have assumed most everybody would want to touch-off via a pendant and not have to manually refresh the corridinate system with the keyboard/mouse to avoid a possible "Outside machine limits" error?
In any case, I will one day figure this out.
I did have a partial working solution by having HAL invoke "haul.mode.mdi" before running the below M-code. It refreshes the program just fine, but then it's stuck in MDI mode and I can't get back to manual mode without hitting another button.
***machine.ini***
# MDI command #5 --Test of New z-probe with Program Reload--
MDI_COMMAND = M101
***custom.hal***
net touchoff halui.mode.mdi halui.mdi-command-05 <= matrix_kb.0.key.r1c4
***M101***
#!/bin/sh
axis-remote -m "o100 call"
axis-remote —reload &
exit 0
***o100***
<pre>
o100 sub
( Set current Z position to 0 so that we will always be moving down )
G10 L20 P0 Z0
( Probe to Z-1.0 at F5 [Uses machine units, I work in inches, this is meant to be slow!] )
G38.2 Z-1.0 f5
( Set Z0 at point where probe triggers with offset of +0.963 [thickness of PCB plate. You must adjust this for your plate / setup] )
G10 L20 P0 Z0.963
( Rapid up to Z1 above the material )
G0 Z2
o100 endsub
</pre>
