G38.2 Probe tripped during non-probe MDI command

Hello,

i want to probe a center of a hole by pressing a button pyvcp.

So i have wrote a Subroutine O900 wich is called from the ini-File
[HALUI]
MDI_COMMAND = O900 call

This work very well but just the probe touch the material the axe stops
and i get the error: "Probe tripped during a non-probe MDI command"

When i call my Subroutine from a "normal" ngc-File per "O900 call"
everything works perfectly.

Now i have linuxcnc updated to 2.5.1 an have hopped the error is patched
(i saw then in the patch report for 2.5.1).
Unfortunelly the error is not gone.

Can anybody help me with a tip?

Many thanks

Best regards horst

Perhaps it would be good to attach a copy of the sub.
Are you using the button from Manual or MDI mode? Same results?

Rick G

Hello Rick,

many thanks for the quick reply.

I have try out to press the button with selected Register Tab "Manual Mode" or "MDI" and
have wrote "O900 call" direct in command line with the same results.

The sourcecode of the subroutine is attached

Horst

Unfortunately the one machine I have a probe on is apart right now so I cannot test.
I took a quick look and do not see any obvious reasons it should not work.

I believe there have been reports of some sub not working correctly from the mdi line or buttons that make MDi call.

I currently use a NGCGUI sub for finding the center of a hole, as I like to set the parameters depending on the work.

Rick G

Hello Rick,

i have try a NGCGUI sub for calling my O900-Subroutine and it works perfectly.

I think, there must be a bug in LINUXCNC when a subroutine is called from a pyvnc-Button per
MDI-Command...

Many thanks for your help!

Best regards

Horst (Germany / Bayern)

Hello Horst,

Glad to hear you have got things working!

Rick G

Also good to keep in mind, that error will come up if your probe makes intermittent contact when returning to the untriggered state.
A debounce would help stop this.

It looks like you had a completely different problem, but for anyone who searches and finds this thread title, I thought it would help someone.

Hi

Does any one know if this problem/bug has been sorted out in Ver 2.6?

I have the same problem. I am developing a gui and has an o-word file with a G38.2 call and when executing with MDI it only executes upto the G38.2 line but if called from within another ngc file it works perfectly.

I don't want to go through the hassle of doing a manual upgrade on my machine computers as they are not linked to the internet.

Or have someone found a work around for this maybe

Cheers

Piet

Hi

It looks as though the bug report was put down to noise on the line, because it went with the addition of a debounce component, so it was closed
sourceforge.net/p/emc/bugs/312/

I would submit another bug report, refering to the last one and be sure to include details of the actual sub you used and the calling method

Make sure you try a debounce component first so that you can rebut noise as being the issue

regards

Hi ArcEye

Thank you for the help, the debounce component did the trick.

Regards

Piet