After completing a carve that was a disaster I found that my X axis wouldn’t home properly. The resulting carve (see picture) I am assuming is the result of this error. What I found was the X1 axis stepper motor was not receiving any power. After checking all wiring and replacing the stepper with a spare I still had no power to the stepper. I had a spare TMC 2209 that I tried and it fixed the problem……X axis now has power to all steppers and homing is working.
What would cause the TMC 2209 to stop functioning?
Am I correct that the stepper motor not functioning caused the carve problems? The carve is actually 2 copies (or more) of a tree displaced by about 10mm! Is that because each stepper was at a different X coordinate? I will be trying a test cut soon. Just trying to understand what happened.
Stepper motors almost never fail. The wiring can fail, but the motors almost never are the reason.
What type of controller do you have on your MPCNC?
One helpful thing would have been for you to pull diagnostics so more about the failure can be understood. Since you’ve replaced the driver, there’s no need for that.
To answer your question about what kills drivers- there are a few ways I know of that have a good probability of destrying a driver:
Disconnect the driver while the machine is on. This can be by unplugging a stepper, or a wire extension coming loose.
Manually move the axis at a decent rate of speed while the machine is off (or the steppers are disabled). This is more a problem on flying Z 3D printers- but we have seen it on CNCs as well.
I’m using a Jackpot. I was showing the mpcnc to my som in law and moved the axis when it was off. Guess I was the cause of the failure!
I checked the wiring first. The stepper motor and TMC were easy to check since i had spares available. Once a new TMC was plugged in, everything worked.
Learn something new each day……never too old to learn!
It was frustrating since I had just completed a really nice carve on a cutting board the day before. Hopefully a test run will show everything is fixed.
Still having trouble with this issue. I have apparently lost another TMC 2209. the ) end stop ight is out, the machine will not move in either axis. Same symptoms I had previously but on a different axis. The last one was resolved by replacing the TMC 2209. Before I do that this time I want to try and determine what is burning the TMC 2209 out, if that is the problem. I did not move the axis manually and didn’t unplug anything. I had used it several times to surface some scrap wood and two cutting boards. I was preparing to surface another cutting board when it stopped working.
Here is my $SS
$G
$SS
[MSG:INFO: FluidNC v3.9.1 GitHub - bdring/FluidNC: The next generation of motion control firmware]
[MSG:INFO: Compiled with ESP32 SDK:v4.4.7-dirty]
[MSG:INFO: Local filesystem type is littlefs]
[MSG:INFO: Configuration file:config.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: Stepping:I2S_STATIC Pulse:2us 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 (3.000,1223.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: X Neg Limit gpio.25]
[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: X2 Neg Limit gpio.35]
[MSG:INFO: Axis Y (3.000,2443.000)]
[MSG:INFO: Motor0]
[MSG:INFO: tmc_2209 UART1 Addr:1 CS:NO_PIN Step:I2SO.5 Dir:I2SO.4 Disable:I2SO.7 R:0.110]
[MSG:INFO: Y Neg Limit gpio.33]
[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: 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: Z Neg Limit gpio.32:low]
[MSG:INFO: X Axis driver test passed]
[MSG:INFO: X2 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: Kinematic system: Cartesian]
[MSG:INFO: STA SSID is not set]
[MSG:INFO: AP SSID FluidNC IP 192.168.0.1 mask 255.255.255.0 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]
[MSG:INFO: Flood coolant gpio.2]
[MSG:INFO: Mist coolant gpio.16]
[MSG:INFO: Probe gpio.36:low]
ok
Standing by for more details, but in the meantime some questions:
Some questions/ observations that may have nothing to do with your issues:
What AWG is the power supply wiring going into the jackpot? It looks undersized to me.
Where do you normally install/route the SD extension cable pictured in the lower left? Is it in or out when the system is misbehaving?
Note the area I marked up in green. You really don’t want any wires in this area in order to have usable WiFi. Try to route the cables more in line with the yellow sketch.
If you pull the multi-connector endstop holder, with no connection at all, can you jog?
Have you tried jogging with gcode from the terminal, or are you only using the UI? Which version of UI?
What AWG is the power supply wiring going into the jackpot? It looks undersized to me.
I bought the power supply from Ryan......whatever he supplies.
Where do you normally install/route the SD extension cable pictured in the lower left? Is it in or out when the system is misbehaving?
The SD extension plugs into the SD card slot. It is presently disconnected. Plugging it back in has no effect on jogging.
Note the area I marked up in green. You really don’t want any wires in this area in order to have usable WiFi. Try to route the cables more in line with the yellow sketch.
These cables were rerouted several weeks ago and have not been an interference issue. I can try to move them but the cabling is very tight. I see a major effort to clean up my wiring in the near future.
If you pull the multi-connector endstop holder, with no connection at all, can you jog?
No..jogging still not working.
Have you tried jogging with gcode from the terminal, or are you only using the UI? Which version of UI?
UI is version2. I tried $H and $SS on the command line. They return an error 500, web socket dead.
I was able to fix the end stop issue. It was a bad wire connection. But that fix didn’ change anything.
I also noticed that the alarm signal is on and will not reset. I also cannot make any choices on the movement ‘wheel’. There are no arrows shown.
More…the alarm just reset…now in idle. it also responded to $SS but it still will not jog. I am using my ipad and had to restart it. Back to alarm mode.
When my computer went out I tried using my IPad. Apparently my IPad and CNC do not like each other. Once I got my computer (a really old Surface laptop) running and used it to connect to the Jackpot all the problems disappeared.
Does using an iPad require some additional steps to interface with the Jackpot?
I knew you used an iPad. That’s why I gave it a try but obviously I don’t know what I am doing.
I’m not sure what you mean but I will be trying to learn what you are talking about. I’ve had an iPad for a long time but I apparently don’t know how to really use it.
Not just iPads, but most OS will detect the FluidNC AP server and present a “login” screen.
This has limited functionality, so you can’t do everything from that browser.
After I connect, whether it is iPad, Mac, Linux, or Windows- I always close the OS opened portal signon browser and then open a fresh browser. Only after that do I go back to the web UI and use the machine.
