X axis motor is playing up

Hi everyone, i am back.
My brother managed to get me a smaller space in his work shop, so i am back working on the LR3.

So everyone remembers its a somewhat standard LR3 with a jackpot board and a m5 fluid dial (thanks @DougJoseph for your instructions)
FW is 3.13 (newest is .17 but issues getting that installed)

So now the problem.
Before i had to pack it up, i had this problem that the x axis would work for homing and jogging etc and would work for cutting, but randomly it would just cut out.
It took me ages to figure this out, as you dump the power (or at least i do) when the LR3 goes wrong. So i was not able to find the problem. I proved the problem when i was cutting a bit of 17mm film face ply (the one with super smooth black coating) and ii noticed t was just driving back and forward and getting deeper when it was supposed to be making a square.
So sure enough the x axis was like it was un powered as i could move it around by hand while the machine was in a cut.

So fast forward to today and over my break i thought it might be the holding and driving amp settings. But that made no difference. (So i changed them back)

Also now homing is affected, when trying to home Z works fine, Y works fine, but X either jumps around like the steps are out of sync or just tried to move and then just stops and then the motor has no power.
While this is going on the jackpot is just sitting there waiting and i can manually hit the end stop twice and its happy. But the X motor no longer holds its self.

So the motor is not and the only way to get power back to the motor is power cycle the board, via the power switch.

Any ideas?

Have you double and triple checked the wires?

Maybe more importantly, have you checked the grub screws that hold the pulleys on the motor shafts?


What do you get from the terminal window when all of this is going on?

When it happens, get us the result of the following command:

1 Like

As best as i can i have. I have checked each wire with a multi meter, while moving the gantry. and they all tone out fine.

in terms of the grub screw, i could see that error if i was missing steps, but the whole axit motor looses power. Prior to homing I can push the X axis, with a bit of force and it wont move. Sure i can over come it and it skips steps and stops and then it is holding again.
But as soon as I try to home it, it looks like the step pins are wrong and it stutter back and forth until I kill it. I have a video, but no way to upload it.

Oddly enough if i dont home and just try to move x with the pendant or the web interface all that happens is the x axis make the sound of it trying to move one step and then goes slack. none of the stuttering etc.
Even though the X axis is now, dunno “switched off” as in i can move freely, with no power to the motor, the Z and Y axis are still working fine via the pendant or the web interface.

hi Jim.

If we are talking about jogging the X axis, then i get no errors at all. Nothing out of the ordinary.

If we are talking homing then, yes i get the error saying it can fin the home endstop in the correct amount of time.

here is the output of teh $SS command after homing
[MSG:INFO: FluidNC 3.7.13 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.yaml]]
[MSG:WARN: Increasing stepping/pulse_us to the IS2 minimum value 4]]
[MSG:INFO: Machine LowRider]]
[MSG:INFO: Board Jackpot TMC2209]]
[MSG:INFO: UART1 Tx:gpio.0 Rx:gpio.4 RTS:NO_PIN Baud:115200]]
[MSG:INFO: UART2 Tx:gpio.14 Rx:gpio.13 RTS:NO_PIN Baud:115200]]
[MSG:INFO: uart_channel2 created at report interval: 75]]
[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: Stepping:I2S_static Pulse:4us Dsbl Delay:0us Dir Delay:1us Idle Delay:255ms]]
[MSG:INFO: User Digital Output:0 on Pin:gpio.26]]
[MSG:INFO: User Digital Output:1 on Pin:gpio.27]]
[MSG:INFO: Axis count 3]]
[MSG:INFO: Axis X (0.000,1220.000)]]
[MSG:INFO: Motor0]]
[MSG:INFO: tmc_2209 UART1 Addr:0 CS:NO_PIN Step:I2SO.2 Dir:I2SO.1 Disable:I2SO.0 R:0.110]]
[MSG:INFO: Y2 Neg Limit gpio.35:low]]
[MSG:INFO: Axis Z (-300.000,0.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: Z Neg Limit gpio.32:low]]
[MSG:INFO: Motor1]]
[MSG:INFO: tmc_2209 UART1 Addr:3 CS:I2SO.19 Step:I2SO.18 Dir:I2SO.17 Disable:I2SO.16 R:0.110]]
[MSG:INFO: Z2 Neg Limit gpio.34:low]]
[MSG:INFO: X Axis driver test passed]]
[MSG:INFO: Y Axis driver test passed]]
[MSG:INFO: Y2 Axis driver test passed]]
[MSG:INFO: Z Axis driver test passed]]
[MSG:INFO: Z2 Axis driver test passed]]
[MSG:INFO: Kinematic system: Cartesian]]
[MSG:INFO: Using spindle NoSpindle]]
[MSG:INFO: Flood coolant gpio.2]]
[MSG:INFO: Mist coolant gpio.16]]
[MSG:INFO: Probe Pin: gpio.36:low]]
[MSG:INFO: STA SSID is not set]]
[MSG:INFO: AP SSID FluidNC IP mask channel 1]]
[MSG:INFO: AP started]]
[MSG:INFO: WiFi on]]
[MSG:INFO: Captive Portal Started]]
[MSG:INFO: HTTP started on port 80]]
[MSG:INFO: Telnet started on port 23]]

ok, i found it!
@jeffeb3 was right, sorta, it was the wires… ish

reading jeffs comment i pulled the plug out of the jackpot, did the testing and put it back in etc. more testing for the $SS command etc.

then i was thinking i need to rule out the driver chip and i was just moving the cables around to clear the driver chips etc and i noticed that when i was moving the cable bundle of most of the axis the red cable on the X connector was moving! So the black block connector is not holding the pins any more.

I also know why it was not happening on the old BTT board as they were held in and on with hot glue. I had not done that yet on this board due to the testing a sorting of wires etc.

So problem is know known, and that is easy to solve.

THanks every one!


You can upload it to google photos, imgur, or youtube and post a link here.

Glad you found it. Wiring issues are the worst because you can only diagnose them by eliminating everything else. And unless you find a smoking gun (like you did), it can be hard to be confident it is fixed. Maybe slightly worse than wiring is EMI problems. Those are like ghosts.

1 Like


When it started happening i was like "@$$!###%!%!#%!%!%%@!$$!!!% thing " and honestly i just hopped it just went away.


But now i am hopping i can finish cutting my tool storage unit!

Finally done.

Now my brother wants payment for storing my stuff at his workshop, he wants his own one. Lol