Fusion 360 probe on probe_basic - Probe tripped during non-probe move

I am trying to enable Fusion 360 probe operation by editing post process and try to run test on probe_basic GUI.

All probe_basic GUI based probe is working well without any problem. however, when I try to run Fusion posted probving I got following error during Fusion ngc based probing process. 

[qtpyvcp.plugins.notifications][ERROR]  Probe tripped during non-probe move.

The reason would be probe_basic GUI detected "probe tripped" by Fusion probe ngc while not on probe_basic's probing tab GUI.

Can someone tell me how to disable qtpyvcp.plugins.notifications or enable Fusion probing ngc out of probe_basic's probing tab ?

All the best,
Bernard

I don't think that "probe tripped during non-probe move" is generated by probe_basic (or by any GUI). It's built-in to core LinuxCNC.

There are a couple of INI settings in [TRAJ] that might be worth trying, though I don't think that they are quite what you want:

linuxcnc.org/docs/stable/html/config/ini...tml#sub:ini:sec:traj
(right at the end of the section, NO_PROBE_..._ERROR )

It seems likely that the problem is with the Fusion probe routine, though, are you absolutey sure that it isn't making a non-probe move into probe contact?

If you set up the HAL so that motion.probe-input is AND-ed with the motion.motion-type == 5 ( "probing") then you can completely bypass the error report. But it is an error indicatiing a genuiune isssue in most cases.
linuxcnc.org/docs/stable/html/man/man9/m...9.html#MOTION%20PINS

As Andy says, the error is from Linuxcnc core, not the GUI.
I would be running the probing from probe basic and not get F360 to do anything with the probe (I didn't know you could)
I've used a probe with F360 and qtdragon and it all worked perfectly.