M66 doesn't work

Hi all
Im new to linuxcnc and pathpilot is my first try, i got everything to work accept M66

I tried this code to check the spindle orientation, the code will run again if orientation signal is false


My input signal in status tab still function, i checked it's work fine


This is my hal file


Im stuck with this more than 2 days, i tried all M66 example i can find but it's still not work
when the code run to M66 line the cycle is stop

Please help me what i did wrong ?

thanks for reading

Are you sure pilotpath support M66?. Pilotpath doesn't use the exact same code as linuxcnc so it's hard for the linuxcnc project developers to comment.
Hopefully a pilotpath user can help.

im not sure pathpilot support M66 cause i've changed to linuxcnc from mach3 for 3 months, i use old version pathpilot v2.0.0

i tried M66 example on tormach manual so i guess it does support M66
tormach.com/wait-on-input-m66

thanks for your reply cmorley

So what is it that makes your digital input go high? You might be waiting for something that never happens?

I use mach 3 board for usb io port, when the port go low the usbio inputs light's up

I realy dont understand your question but do you mean even if usbio inputs light's up, M66 still may not work ?

In the picture of your HAL setup there is no setup for motion.digital-in-02 you have two entries for motion.digital-in-03.

You are waiting for motion.digital-in-02 but have not set up a signal.

Duongtantai8624 wrote: Im stuck with this more than 2 days, i tried all M66 example i can find but it's still not work
when the code run to M66 line the cycle is stop

There is a problem in your HAL configuration, it looks like a copy-paste error.

in0
in1
in3
in3

You have set up input 3 twice, and input 2 not at all.

Sorry i just post wrong picture
Im trying everything i could, change port ,change mode etc ...

If you use the halmeter, can you watch the dig-in-2 signal and the motion.digital-in-02 signal to be sure that they are triggering as-expected?

Which Mesa board are you using? It isn't that usual to use the bare gpio pins on most of them now.
Are you sure that gpio-032 is not being claimed as an output pin by a step-generator or similar?
If you can tell us the board, firmware and loadrt_hm2 lines from the HAL file we might be able to help more.