Using Josh Pieper Probe with Fusion 360

All things CAM and G-Code
#21

So after some digging, I’ve come up with this:

in the tool-probe.ngc file in the subroutine:

O<tool-probe> SUB

I’ve added a parameter:

#<_ToolProbeButtonTravel> = 1.05/25.4     ( Set Tool probe button travel here, 1.05mm / 25.4 to use Inches as per _UseInches param)

And then created a conditional statement that applies it if T14 is being measured

o10 IF [#<T> NE 14]
	G10 L1 P[#<T>] Z[-3+#<_OriginOffset>+#<_ToolZProbe>-#<_ProbeSensor123Offset>]
o10 ENDIF
 
o20 IF [#<T> EQ 14] (T14 is the probe and triggers on contact with thetool probe rateher than depressing it)
	G10 L1 P[#<T>] Z[-3+#<_OriginOffset>+#<_ToolZProbe>-#<_ProbeSensor123Offset>+#<_ToolProbeButtonTravel>]
(debug, T14 selected, assuming Probe, allowing for 1.05mm button travel.)
o20 ENDIF

Not sure if the sign should be + or - will need to try it out tomorrow and see.

I assume if I add this to my local subroutines folder it will override the default routine??

Thoughts?

Cheers
BPM

#22

Yes, copying the tool-probe.ngc to your local subroutines directory and making your modifications there will override the default.

#23

Thanks @john,
After a lot of experimenting and figuring out how fusion expects the probe to be configured and then understanding how the PNC is setup I have modified routines to get the probe working correctly for z probing operations. X/Y tbc, hopefully they will work now the probe is setup appropriately for fusion.

When Fusion calls the probe on and probe off routines are these mapped to a pin on the Beaglebone. If so is there a reference mapping for the BBB pins?

Looking for a signal to aid with preventing fault conditions when the probe is not connected.

Any suggestions would be greatly appreciated.

Many thanks
Barry M

#24

The probe on and probe off routines don’t trigger a pin on the Beaglebone to change. They set software variables that can be used to abort if a probe is not detected on the Solo. The V2 is set up to use the basic_probe feature (see /opt/pocketnc/Settings/features/basic_probe), which simply doesn’t error. There’s not a great way to splice something in there (certainly nothing official).