Hello, I’m here today because after a lot of testing, I cannot manage to make my mpcnc work properly. The first thing that you’ll see in this video, is that the first port does not work at all, no current is going inside my stepper motor. But Elecrow (where I bought my Control Board) wants me to first ask on these forums to make sure that my control board is defective …
I have carefully followed all precautions and adapted my configuration so that the motors operate in pairs. I have thoroughly checked everything and even tested new components to rule out any external issues.
I have always been careful to disconnect the power supply before making any modifications or handling the board. Despite these precautions, the issue persists. The board does not show any visible defects, but I suspect a manufacturing issue with the electronic components.
To provide more context, I have recorded a video explaining the problem in detail, which you can find here:
Of course, the config for voltage etc is the same for each motor …
Yes on this video I know that all the motors are not plugged in, i did a lot of tests since receiving the board to find the issue…
Jackpot CNC Control Board is from Elecrow
ESP32, the first one on Aliexpress, the new ones are from Amazon
TCM2209 are from Aliexpress
I made sure to buy products only with good reviews and a lot of it of course
Rule #1 when trying to speak in another language… it is never your fault that you can’t speak the language, but them that can’t understand what you say! Your level is more than acceptable and the message gets across well. I am a French native speaker with over 30 years in the USA, so I went through the same struggles and fear of expressing myself in English at first.
For your issue, I wish that I could help but I am on a similar noob journey with my LR3 & got my board pre-programmed from Ryan (it helps), so no issues there.
To rule out the X board output being broken, have you tried to change the 2209 driver and/or the motor? Also maybe check the X limit switch (I am not sure if it has a play to block the motor outside of homing).
Something to note if you’re not already aware but YAML is extremely sensitive to formatting - even an extra space at the end of a line or the file can cause issues. For troubleshooting I would recommend downloading the known good config.yaml and uploading it.
Its not clear from your video if you’re extension cables of any kind but if you can plug one stepper into a driver using its included cable only.
What we want to do is eliminate variables.
So establish
a tested stepper
with a tested cable
Into a tested driver
In a tested slot
With a tested config.yaml
It’s tedious but being methodical is important.
Edit: I apologise, I gave you the wrong command for the terminal, could you please use $SS and paste the results?
Yes, actually my problem dates back from the time I received the board.
I already tried a lot of things, changing the extension cables, trying different drivers, different motors on this port, and I used the MPCNC Config available on github.
I tried putting my X motor on the Z axis and he was doing perfectly fine
**Yes, I used the given config for the MPCNC, and just changed the gpio ports, to match the C slot, because my X one didn’t work … But the C slot works but not that great, it’s like jumping idk how to explain it. **
No problem, here is the result :
$SS
[MSG:INFO: FluidNC v3.9.4 LINK DELETED]
[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.21Min Pulse:2us]
[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:3 CS:NO_PIN Step:I2SO.21 Dir:I2SO.20 Disable:I2SO.23 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:ERR: X Axis TMC driver not detected - expected 0x21 got 0x0]
[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
**I already tried this, and noticed that no TMC driver was detected on the X port. Of course, I tried using a working driver on this port, for example the Z axis one. **
BEFORE : Motors on Y Z A B C ports (C is being the X replacement) AFTER : Motors on X Y A B C ports (Move the Z driver to X port)
$SS
[MSG:INFO: FluidNC v3.9.4 LINK DELETED]
[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.21Min Pulse:2us]
[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:3 CS:NO_PIN Step:I2SO.21 Dir:I2SO.20 Disable:I2SO.23 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:ERR: X Axis TMC driver not detected - expected 0x21 got 0x0]
[MSG:INFO: X2 Axis driver test passed]
[MSG:INFO: Y Axis driver test passed]
[MSG:INFO: Y2 Axis driver test passed]
[MSG:ERR: Z Axis TMC driver not detected - expected 0x21 got 0x0]
[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
As you can see, the X port still doesn’t detect any driver … So my only thought is that the Control Board is defective …
That seems logical if it’s not detecting a working driver board. Have you had a close look at both sides of the board for anything visibly wrong - missed solder pads or anything?
I don’t know the minimum number of posts you need to post images but clear pictures of both sides of the board would be good.
Hopefully Ryan will be waking up soon so can take a look at the info you’ve collected so far.
Here are pictures of my board. I cleared up what was in the way of course to make the pictures. I already checked my board multiple times, but cannot see any visible defect. I’m pretty sure that the defect is from the board itself before the coating ?
Yeah I tried uploading the pictures with no success, I’m doing it the illegal way sorry lol.
You can very carefully pry up on the plastic headers on the X stocket and remove them (seperate them from the socket pins) and check that they’re not touching anywhere.
We’ve seen this a few times. I’ve personally fixed three that were identified as defective by pulling the plastic, finding where they’re shorting, straightening them, and then reinstalling the plastic.
If that doesn’t work for you, then you can debate reflowing the solder or returning it to elecrow.
Finally got a reply from Elecrow after sending them this post. It looks like I’m getting a replacement and maybe they will tell me what the problem was on this card.
It was so refreshing when I was over there a couple of weeks ago. Even just opening a browser was a much more pleasant experince. It’s a shame I didn’t insist on taking more time to explore. Maybe mid year when I go back.
