TMC Drivers not detected - Expected 0x21 got 0x0

I recently completed the build for my LRV3 and started the road to the electronics. All was wired and connected as the instructions stated. The Jackpot controller was shipped with the MPCNC config file so this was changed and restarted. The following is the $SS for the bootup. I have changed the firmware multiple times and followed the instructions from the V1 firmware site. need assistance as I am stumped.

$G
[GC:G0 G54 G17 G21 G90 G94 M5 M9 T0 F0 S0]
ok
$SS
<Idle|MPos:0.000,0.000,0.000|FS:0,0|Pn:PZ|WCO:0.000,0.000,0.000>
[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 LowRider]
[MSG:INFO: Board Jackpot V2 TMC2226]
[MSG:INFO: UART1 Tx:gpio.16 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: 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.14 Step:I2SO.13 Dir:I2SO.12 Disable:I2SO.15 R:0.110]
[MSG:INFO: Y2 Neg Limit gpio.35]
[MSG:INFO: Axis Z (-297.000,3.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:ERR: X Axis TMC driver not detected - expected 0x21 got 0x0]
[MSG:ERR: Y Axis TMC driver not detected - expected 0x21 got 0x0]
[MSG:ERR: Y2 Axis TMC driver not detected - expected 0x21 got 0x0]
[MSG:ERR: Z Axis TMC driver not detected - expected 0x21 got 0x0]
[MSG:ERR: Z2 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: Probe gpio.36:low]
ok
<Idle|MPos:0.000,0.000,0.000|FS:0,0|Pn:PZ|Ov:100,100,100>


You don’t have the correct config file. You have a config file that will be used with the Jackpot V2 board (Which is in development, but not yet released.). The IO is slightly different on the Jackpot V2, so you need to get the config file for an LR3 with a Jackpot V1.

I’ll edit this post in a little bit with the correct link for you.

Edit: The recommended software and config for Jackpot V1 and a new build is linked here:

Edit 2: I should have started with this, Rob- Welcome to the V1 community forums.
Hopefully you’ll share more of your build and machine usage of your LowRider as you make progress.

4 Likes

Holy Moly its alive!!! Thanks I was struggling and thought it was the V2 as it is fairly new. I guess I should have looked at the board closer. Thanks a million!

2 Likes

That should be private for downloads until release

1 Like

I’m not sure how Ryan could make a public github have a private section.
Part of the beta and RC process is to sort out how to organize things for release.

I’m sad that we confused @Rfoss but also happy that we can start thinking about how to make it clear.

It won’t be very long and we’ll need to sort out how to best organize the config repos to avoid this confusion.

The development has been going very well from my perspective, and I don’t think it will be too much longer till there is another Jackpot board family member in the shop.

Both will continue to be sold, there are still some reasons for the V1 even with the optimizations in the V2. All of which is just conjecture until Ryan commits to releasing the product.

1 Like

It can be there, just name it differently or with a warning for the untrained eye

2 Likes

Git makes it easy to manage this. I’d just keep it in a separate branch and not merge it into the main branch until V2 is released.

4 Likes

OK, next up let’s see a crown, then that machine cutting it’s own strut plates!

2 Likes

Agreed. But it does take some git-foo to get it onto a branch cleanly now that it has been merged into main.

@vicious1, the easiest thing is to make a PR that deletes it from main and then branch from main and make a PR that adds back in the entire V2 config file. You need to just keep a copy of it on your hard drive during the jump.

3 Likes

This is already the second time this has happened. I changed the instructions page but that did not seem to help.

The J2 is coming, how am I going to make it more clear in the future. Two completely separate config links from the docs, two different git repos?

This is also a new thing I need to add to the Jackpot troubleshooting section.

Call it something completely different? Even as a working title.

Blackjack, bingo, bullseye, bonanza

1 Like

Agreed!

Now is a good time to make sure the silkscreen on the board clearly tells people what version they have haha

A Readme.md right here with a picture of each board and a few sentences would make it clear. Except when people direct link to the config.

1 Like

The current “Jackpot” folders should also be renamed “Jackpot V1.1” (or maybe “Jackpot V1.x”). To maintain links, you could have new “Jackpot” folders with the readme that Jeff suggests in it (and maybe the contents of the V1.x folders).

I would also rename the store items to specify the Jackpot V1.1 (or V1.x).

Not a crown but it seems to work great. Strut plates next.

6 Likes

Heck yeah!

1 Like

It would also be good to bring back some sort of versioning or id to the config.yaml files like we have in the Marlin builds. Something that shows up in $ss.

2 Likes