[EDIT: For info and to provide context for the references below, this thread was culled from a parallel one at: XYZ Probe Plus with VFDs and other ground-loop inducing components ] I seem to have a similar problem setting up my new OpenBuilds probe. This gives similar error message mentioned at the beginning of this thread by Peter Van Der Walt "The probe is not in the expected initial state before starting probe cycle, where G38.2 and G38.3 is not triggered and G38.4 and G38.5 is triggered." - pic attached. My setup is xPro v5 and Router11. I have no VFD. I'm connecting via a MacBook running off battery power. I've been through all the above issues and fixes and crossed off each one as far as I'm aware. Obviously double checked wiring per docs:xyzprobe:wiringgeneric [OpenBuilds Documentation] and have correct separation between Earth (AC) and Ground (DC) with zero continuity. The probe LEDs light up correctly when the plate touches the router bit and also the clip wire. Any advice welcome
Use the Troubleshooting tab to view the Probe status, then disconnect things until the problem clears - thats the best way to find where the short is coming from
Troubleshooting shows probe on (off when touching clip wire). I don't believe I have a short - the LEDs don't come on when the plate touches the router bit when clip not attached.
And btw, I also checked there's no continuity between end mill and GND. When I run the Probe routine (after confirming position) the spindle moves +22.5mm in X and Y before error code shows. Not sure if this is relevant, but everything I've tried so far yields the same result
It's now working. In settings I changed it to $6=Enable (it was $6=Disable) and saved changes to firmware. Your mentioning "that's opposite of normal" made me try this as I wasn't sure whether 0=Enable or Disable. Anyhow, that worked for me Thanks for the prompt!!
Hey Tim - Looks like an old version of Control. Any reason why you havent updated? (btw - this question has nothing to do with your issue.)