X axis Motor issue

Startup
<Idle|MPos:0.000,0.000,67.000|FS:0,0|Pn:X>
$SS
[MSG:INFO: FluidNC v3.7.8]
[MSG:INFO: Compiled with ESP32 SDK:v4.4.4]
[MSG:INFO: Local filesystem type is littlefs]
[MSG:INFO: Configuration file:config.yaml]
[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: I2SO BCK:gpio.22 WS:gpio.17 DATA:gpio.21]
[MSG:INFO: SPI SCK:tgpio.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: Y Neg Limit gpio.33]

I’m back with a problem. After a recent crash while attempting to carve the cup from Estevan project page - my x axis motor has stopped responding to controls.
I can see on fluidic the “jog” happening but the motor stays dormant.
However, when I use the command $MD to disable the motors, I can feel the resistance go away from the motor and when I enable the motors I can feel it return.

I have a new motor in bound, but I’m afraid it’s not gonna be the solution.

Any ideas?

I’ll snap a few pics of my current setup when I get back home this afternoon.

Check your wiring. If you have a loose connection you might be losing one coil in the motor. I would think this would make a noise when you tried to move but possibly not. Still always good to verify your wiring

1 Like

Which type of machine do you have?

Show the full contents of $ss , from FluidTerm if possible, or a couple of times from the WebUI if not.

If you swap a TMC2209 between another position and the driver for the X motor that you are having problems with, does the issue follow the TMC2209 driver or stay with the X motor?

1 Like

Loweider v3

When I ran $SS I get

ok
<Idle|MPos:-1149.520,10.000,-4.000|FS:0,0|Pn:P>
<Idle|MPos:-1149.520,10.000,-4.000|FS:0,0|Pn:P>
<Idle|MPos:-1149.520,10.000,-4.000|FS:0,0|Pn:P>
$SS
[MSG:INFO: FluidNC v3.7.8]
[MSG:INFO: Compiled with ESP32 SDK:v4.4.4]
[MSG:INFO: Local filesystem type is littlefs]
[MSG:INFO: Configuration file:config.yaml]
[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: 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: Y Neg Limit gpio.33]
[MSG:INFO: Motor1]
[MSG:INFO: tmc_2209 UART1 Addr:3 CS:I2SO.14 Step:I2SO.13 Dir:I2SO.12 Disable:I2SO.15 R:0.110]
[MSG:INFO: Y2 Neg Limit gpio.35]
[MSG:INFO: Axis Z (-200.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 Pos Limit gpio.32]
[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 Pos Limit gpio.34]
[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: Connecting to STA SSID:NETGEAR28]
[MSG:INFO: Connecting.]
[MSG:INFO: Connecting…]
[MSG:INFO: Connected - IP is 192.168.1.243]
[MSG:INFO: WiFi on]
[MSG:INFO: Start mDNS with hostname:http://fluidnc.local/]
[MSG:INFO: SSDP Started]
[MSG:INFO: HTTP started on port 80]
[MSG:INFO: Telnet started on port 23]
ok
<Idle|MPos:-1149.520,10.000,-4.000|FS:0,0|Pn:P>

I removed the stepper and swapped it with a new one. It worked until I reassembled it, then gave me another freeze up with the webUI saying it’s moving.

I think it may be my extension wire. It’s not constant, so maybe a nick in the wire that gets exposed at a certain point?

That is possible.

So it was one of my braces? It got off ut of alignment and was pushing one of my conduit ends higher. The core would wedged as it neared that side.

I am confused on this huh it still thought it was my moving once it was wedged. Usually it just grinds in place when it can’t move.

I may still replace the cable but it’s functioning again.