M66 keeps waiting

I have configured a hydraulic tailstock on a CNC lathe. It has 2 valves (in/out) and 2 proximity sensors (min/max). I want to use M-codes to control the tailstock, but I can't get M66 to work. M64 and M65 do work properly. I've attached the sensor inputs to motion.digital-in-00 and 01. I can see the signals changing low/high in halshow. But when I try to test this functionality with a small G-code file, it keeps waiting on the M66 line.

It keeps waiting on line M66 P1 L4 Q10. Even if I manually turn the sensor on/off, it doesn't do anything. But when I use this line in MDI, it works without problems. When I use MDI I can see the gmoccapy interface "freeze" when I execute this line. It "unfreezes" when the sensor is operated.

Why doesn't my G-code work?

L3 is correct for this application, but out of interest, does L1 work?

Does the 10 second timeout work?

Which LinuxCNC version?

In halshow are you looking at the motion.digital-in pins? (rather than the IO pins)

The other L-modes also don't work. Timeout doesn't work. Nothing happens after 10 seconds. Yes I'm looking at the digital-in-xx pins. LinuxCNC version on the splash screen is 2.9.0~pre1+git20230208.f1270d6ed7

Since you're observing activity at hal pin “motion.digital-in-xx”, this confirms that the hardware input is functioning correctly. The issue likely lies further downstream—could it be that Gmoccapy is monopolizing this pin?

Firehunter wrote:

LinuxCNC version on the splash screen is 2.9.0~pre1+git20230208.f1270d6ed7

I really thought we had a newer version than that on Bookworm, but the package lists suggest otherwise. 

I don't think that anything has changed with M66 since that version (which was a prerelease that found it's way into the Debian archives during their testing phase, expected to be replaced, and then wasn't. 

I don't expect it to make a difference to this particular issue but there are other fixed bugs that I would be happier knowing you are not going to see. The current release version (outside Debian) is 2.9.4.  You can just download the .deb file and install it from our server: 
www.linuxcnc.org/dists/
What Linux are you running? (eg, Debian Bookworm (my first guess)) and on what platform? (PC? Pi? Oher?) we can then point you to the exact package file you need. 

andypugh wrote:

I really thought we had a newer version than that on Bookworm, but the package lists suggest otherwise. 

[/quote]
You do. Looks like the OP is using the version included in bookworm and has not used the 2.94 ISO
But that's not an issue. Just follow the instructions in the 2.94 docs under getting Linxucnc, section 7.

But also Debian Trixie should be released in the next couple of days. Once that happens an early adopter can do a
sudo apt dist-upgrade
should install Trixie and upgrade to 2.9.4

Thanks for the replies. I guess updating Linux and LinuxCNC is the only option left. The machine is at an other location, I will try installing the updates when I'm there again.

I made some changes to the gmoccapy interface, added some custom buttons using the Glade editor if I remember correctly. Will these modifications be overwritten when I do the updates?

Te linuxcnc folder is preserved on an upgrade but keep a copy off the pc.
What version of linuxcnc are you using? Versions before 2.8 might need some more work.

I have found its best to build a rough config with stepconf or pncconf, then cut and paste your ini file data into the generated ini file.It only takes an hour or so that way.

Firehunter wrote:

Thanks for the replies. I guess updating Linux and LinuxCNC is the only option left.
 

Note that I don't actually expect that to fix this issue. 

Can you attach your HAL files(s)?

The sample code works (standalone) for me,
That is just by manipulating/watching the pins in halshow: