[solved] M66 P1 L4 Q24000 this command can make gcode iterruption?

Excuse me seems a stupid question, but I have a machinery that this line after half an hour or perhaps an hour waiting to stop the code. Is there a mistake somewhere else or can this happen because the set values ​​are incorrect? For example, is the time entered too high?
for some reason these machine stop at that row but only sometime, and only after the M66 pause of 30/60min .... not find the solution to these situation (I use a mesa card so i/o signal not seems a problem and I plan to insert a galvanic isolator to make the cause of the noise out of the question.).

regards
Giorgio

That is supposed to stop and wait until input 1 is low (or time out in 6.666 hours)

I would look at the hal inout 1 signal with watch, halmeter or halscope and see if it behaves as expected

Thanks for reply.

already done some month ago ... it seems all ok, but the problem exist. So I asked to remove any doubt.
I was afraid there was a limit to the time that you can set. I buy the isolator today.

Regards.
Giorgio

If its a noise issue, debouncing the signal should fix it, no hardware needed

And I'm not clear on the exact issue

Are you saying input 1 is low but the M66 still waits or that the input is high and M66 doesn't wait long enough?

If you want to check if long waits work independent of the hardware, just tie the input high with a setp in hal
and it should wait 6.666 hours (the 24000 second timeout) before proceeding

the second one: the input is high and M66 doesn't wait long enough..... but really after only 30 or 60 min (1800 - 3600 sec) the program stop sometime and sometime all work fine.

regards
giorgio

I would try debouncing the signal, it sounds like a noise issue