t; > -Original Message-
> > From: Nicklas SB Karlsson [mailto:n...@nksb.eu]
> > Sent: March 14, 2025 3:21 PM
> > To: emc-users@lists.sourceforge.net
> > Subject: Re: [Emc-users] Accessing HAL variables.
> >
> > Have the following rows in a .ngc
Have the following rows in a .ngc file run then pressing a button:
o sub
;#1 = 60 ; [ps_searchvel] search speed
;#2 = 10 ; [probe.ps_probe_max] search distance
#3 = 6.5 ; [ps_probe_latch] probe distance
#4 = 60 ; [probe.ps_probevel] probe velocity
#5 = 120 ; [TOOLSENSOR]RAPID_SPEED] rapid speed
#
sts.sourceforge.net
> Subject: Re: [Emc-users] Accessing HAL variables.
>
> Have the following rows in a .ngc file run then pressing a button:
>
> o sub
>
> ;#1 = 60 ; [ps_searchvel] search speed
> ;#2 = 10 ; [probe.ps_probe_max] search distance
> #3 = 6.5 ; [ps_probe
On Thu, 13 Mar 2025 at 17:59, John Dammeyer wrote:
>
> From the MDI command line or from one of the AXIS menu items can I examine
> these values?
>
One way is to insert debug comments in the G-code.
(DEBUG, The touch_result is #)
--
atp
"A motorcycle is a bicycle with a pandemonium attachmen
I'm back to trying to get my head around tool probing and tool length
sensing.
Say I have this in the psng_manual_change.ngc file.
# = #5063
# = #<_ini[TOOLSENSOR]SETTER_HEIGHT>
# = #<_ini[PROBE_SCREEN]WORK_HEIGHT>
# = #<_hal[probe.blockheight]>
; Put new tool length into tool table.
G10 L1 P