M66 doesn't 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.

My setup is a little bit weird cause im in third wolrd country so i have to stick with third world solution

This is pci e motion control card


This is linuxcnc bob


I use mach 3 board + relay board for io pin


Here's the loadrt line, but it no hm2 ::pinch:


I dont know how to open halmeter, i will figure out how to do it later but this is io port list show in operator_login

That seems to be a clone of a 5i25. So there is no real guarantee that the dmesg output that tells you that GPIO 32 is on DB25 pin 12 is correct.

Can you use Halshow with PathPilot? That would let you check which physical input (if any) triggers when you toggle the physical input.