New(ish) Jackpot Issue with MicroSD and USB

https://docs.v1e.com/electronics/jackpot/#updating-installing-firmware

Currently, if you use a chrome browser everything is done through the site, the only OS related thing you migh tneed is the USB driver CP2012.

I forgot to mention, I used Chrome on one of my earlier attempts and while it said it was successful, the issue persisted. But that was only in Windows 7. Havenā€™t tried yet in Linux (other than manually). I will keep trying though!

I utilized Chrome (on my Linux machine) to update and load files through the browser. It all appears to have run successfully but, sadly, I still have ā€œNo SD Cardā€ and cannot run or wirelessly load any gcode files (mine or the test crown available).

Hereā€™s what I get when trying to refresh the SD Card window:

[MSG:ERR: sdmmc_card_init failed code 0x108]

Hereā€™s what I get when I try to upload a file to the card through the Web UI:

[MSG:INFO: Upload filesystem inaccessible]
[MSG:ERR: sdmmc_card_init failed code 0x108]

Hereā€™s the startup message, if it helps:

$SS
[MSG:INFO: FluidNC v3.8.0 https://github.com/bdring/FluidNC]
[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: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:  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 (0.000,2440.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: Using spindle NoSpindle]
[MSG:INFO: Flood coolant gpio.2]
[MSG:INFO: Mist coolant gpio.16]
[MSG:INFO: Probe gpio.36:low]
[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]
ok

Should I try another card, even though I can read/write without issue on Linux, Mac, and Windows, and Iā€™ve verified itā€™s FAT32? Or could it be a hardware issue with the board itself? I really like the ease of use and versatility of the Web UI and the concept of running off the SD Card but is there no other way to send gcode to the Jackpot?

I have had problems with certain SD cards in the jackpot. Did you get your card from V1 or using one you have? The ones from V1 are the ones that work the best for me. Any others I have around didnā€™t work at all.

Yes. ā€œBetterā€ cards work worse.
A simple, old, class 4 card works way better in embedded use than the latest super high speed cards.

I have some that do and some that donā€™t.

1 Like

Bought directly from the V1 store.

OK, I believe I have some around here somewhere that I can try.

The one from the V1 store isnā€™t working in your jackpot??? That seems odd. Hopefully @MakerJim has some ideas for you. Thatā€™s above my pay grade lol

All I know for certain is that some of my cards work, some donā€™t. I have them from random sources.

I also have broken a solder joint on an ESP32 SD card socket, so I know that can be done.

Weā€™ll see what happens with other SD cards.

1 Like

That means it was not through the WEBui, or that you changed the github files in some way. It should not say dirty.

How do I correct that? I originally was using the shell files but most recently used the Chrome based tool. I simply followed the instructions but Iā€™d appreciate step by step procedures if Iā€™m missing something.

As far as the GitHub files, I simply downloaded them to my computer.

Just used the web used tool in a chrome browser, do the full wipe version, that should give you a clean install, then you upload our config and macro files.

Ok, thatā€™s how Iā€™ve been doing it but can try again. I specifically used Chrome to wipe, load the firmware, then upload the files when it had completed (also in Chrome). Do I need to do anything else?

Might I be adding files in the wrong order ?

Are you adding files you compiled on your own or the built-in files and ours? 3.8.0?

Does it still say dirty??

Iā€™ve not done any compiling (honestly donā€™t know how to compile yet!), just the built in files and yours. Yes, 3.8.0. I simply downloaded the files directly from GitHub that were referenced earlier (and in your documentation). I have been uploading them (V2 config, json, macros, etc) via Chrome.

Can you try it one more time and let me see the $SS please.

Yes, will do.

To be clear, I should:

  1. Remove the ESP32 from the Jackpot
  2. Connect it to the computer via USB
  3. Navigate to the update URL in Chrome
  4. Select the correct port then click erase, install V3.8.0
  5. After it completes, upload the config file
  6. Is there a specific order I should load the other files after that? Any manual resets needed? Should I load literally everything in the V2 GitHub section?

Again, I appreciate the guidance!

That should do it, you do not need to remove the ESP though.

Got it, will try this evening then report back!

1 Like

With the ESP connected to the Jackpot and the Chrome installer via USB, my only options are to Install or open Terminal. I went ahead and proceeded with a full erase and firmware install. Appears to have completed successfully, however, I cannot upload any files. If I disconnect the ESP from Jackpot, then all of the other options to upload/manage files, etc. reappear. This is the only way I can load the config file but I also get this warning before doing anything (that doesnā€™t appear when connected to Jackpot):

There was an error during boot, likely due to an unvalid configuration.

$SS is still showing:

[MSG:INFO: FluidNC v3.8.0 https://github.com/bdring/FluidNC]
[MSG:INFO: Compiled with ESP32 SDK:v4.4.7-dirty]

If I leave it connected then erase and install, I can no longer connect via wifi as the SSID is no longer there. Clicking on Terminal in the Web Installer appears to not do anything other than display some text when I press reset. Otherwise, I canā€™t type any commands and it mostly stays blank.

I then disconnected from the Web Installer and tried loading the wifi and fs shell files again through Terminal, just to see how it would behave and while that re-establishes the ability to connect via wifi (even with the ESP still connected to the Jackpot), I still get the ā€œdirtyā€ message and ā€œNo SD Cardā€.

I tried erasing and installing the firmware 4 times this evening through the Web Installer, same issues each time.

As for another SD card, I do have a 15 + year old card but itā€™s exactly 2 GB which wonā€™t work as stated by FluidNC. All of my other cards are A1 so I didnā€™t attempt to try them.

Iā€™ve tried downloading the config file and macros several times from GitHub simply by clicking on the file followed by ā€œDownload raw fileā€. Thatā€™s the way to do it, correct?