Homing fail. Pull off travel failed to clear limit switch. Try increasing pull-off setting or check wiring

MPCNC, Jackpot board, no changes to firmware/YAML. It was working great for a long time. Now whenever I try to home Y, I get " Homing fail. Pull off travel failed to clear limit switch. Try increasing pull-off setting or check wiring."

Well, thank goodness the Jackpot has those LEDs for limit switches. I verified all four work as intended manually. I even tested the Z probe light, and made sure it wasn’t touching. (Does that even matter btw?) All this tells me the limit switches are good… right?

So maybe something is weird with stepper motor wiring / connections. What’s crazy is I can move/jog every axis and all motors work. So if it’s not the motors, and it’s not the limit switches… I’m stumped.

Curiously, the console shows Pn:YZ, which I think means the Y axis is touching the endstop. The endstop lights on the controller itself indicate otherwise. Why isn’t the console getting the message? :crazy_face:

When I do “home Y”, it backs away from the axis instead of going toward it, like it is trying to do a homing pull off. But WHY?

Whenever troubleshooting weird FluidNC issues, start with the machine in the weird state. Then go into the terminal and send a $SS.

Copy / paste the $SS results here as a first step. Be sure to use the preformatted text formatting (The </> symbol on the forum message edit toolbar)

Hmm… so GPIO34 is the likely loose connection. Will check.

$SS
[MSG:INFO: FluidNC v3.7.12 GitHub - bdring/FluidNC: The next generation of motion control firmware]
[MSG:INFO: Compiled with ESP32 SDK:v4.4.4]
[MSG:INFO: Local filesystem type is littlefs]
[MSG:INFO: Configuration file:config-laser.yaml]
[MSG:INFO: Machine MPCNC]
[MSG:INFO: Board Jackpot TMC2209]
[MSG:INFO: UART1 Tx:gpio.0 Rx:gpio.4 RTS:NO_PIN Baud:115200]
[MSG:INFO: I2SO BCK:gpio.22 WS:gpio.17 DATA:gpio.21]
[MSG:INFO: SPI SCK:gpio.18 MOSI:gpio.23 MISO:gpio.19]
[MSG:INFO: SD Card cs_pin:gpio.5 detect:NO_PIN freq:20000000]
[MSG:INFO: Y2 Neg Limit gpio.34]
[MSG:INFO: Axis Z (-100.000,200.000)]
[MSG:INFO: Motor0]
[MSG:INFO: tmc_2209 UART1 Addr:2 CS:NO_PIN Step:I2SO.10 Dir:I2SO.9 Disable:I2SO.8 R:0.110]
[MSG:INFO: X Axis driver test passed]
[MSG:INFO: X2 Axis driver test passed]
[MSG:INFO: Probe Pin: gpio.36:low]
[MSG:INFO: Connecting to STA SSID:mine]
[MSG:INFO: Connecting.]
[MSG:INFO: Connecting…]
[MSG:INFO: Connected - IP is 192.168.xxx]
[MSG:INFO: WiFi on]

First off, that’s a really incomplete $SS output. Something’s wrong.
Try pulling the diags again.

Next, FluidNC 3.7.12 isn’t a good version. You should update to 3.7.17, or perhaps 3.9.2-pre1.

We need to see a full $SS output before we go too crazy with other troubleshooting.

I had accidentally attached Y2 (GPIO34) to Z (GPIO32). Oops. :laughing: Everything is working great now.

Why is my FluidNC version bad? I haven’t had any problems.

When I have had this happen on my MPCNC it was where the endstop extension wire plugs into the main wire that goes to the stepper driver and the endstop on the Jackpot. For whatever reason it was loose.

Yeah, I’m thinking hot glue may be in my future. What threw me off is all the limit stop lights worked. I just didn’t notice it was the Z light instead of Y2. Man that was maddening! :laughing:

1 Like

Just look for a printed part *mod in the search box. I think @DougJoseph did it. It secures the conecction for the endstops

Maybe this is what you remembered?

1 Like

Exactly!!

1 Like

closing old topic to help fight spambots