Jackpot updating issue from 3.7.16 to anything greater

Software / Firmware Jackpot Board / FluidNC
1

Basics out of the way, ESP32 is not in the jackpot, win 10 running chrome. I am having an issue and figured before chasing it down I should update the firmware from 3.7.16 to current 3.7.18.

When I attempt to fresh install the 3.7.18 wifi firmware, it goes smoothly. When it reboots, I get “There was an error during boot, likely due to an unvalid configuration.
Click here to see details”

Looking at the details, the config.yaml file is missing. I upload all of the files from the V1e git to the esp and now get “[MSG:ERR: Cannot open configuration file:config.yaml]”.

Just for kicks, I can flash 3.7.16 with no errors, but anything above that release kicks the same error all the way to the 3.8.2 release.

I’m reverting to 3.7.16 for now, but any ideas? The ESP32E is the one that came with my second jackpot

***Solved: Ignore the error. Just upload the V1e files and edit the wifi if you need to. Then plug it in to the jackpot (making sure you put it back in the correct way and not backward!).

2

Also, I tried upgrading without full wipe to 3.7.18 from 3.7.16 (even though it’s not the recommended method) and got the same error.

3

After you install the firmware you need to load our config and preferences files. There is a link in the instructions.

3.8.0 is the current recommended. The instructions get updated as that changes.

4

As per the jackpot firmware page

Firmware

FluidNC Firmware - The Current tested and confimed FluidNC version is 3.7.18 (make sure to update your config file as well to add the homing Amps to each stepper), use anything newer than this with caution.

The github repo the docs page send you to has

> Blockquote
has files to 3.7.15

Is there somewhere else to download the 3.8 files?

Is it normal to get the error " There was an error during boot, likely due to an unvalid configuration.
Click here to see details" when doing a fresh-install to 3.8? Mine just did.
" [MSG:INFO: FluidNC v3.8.0 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:ERR: Cannot open configuration file:config.yaml]

[MSG:INFO: Using default configuration]

[MSG:INFO: Axes: using defaults]

[MSG:INFO: Machine Default (Test Drive)]

[MSG:INFO: Board None]

[MSG:INFO: Stepping:RMT Pulse:4us Dsbl Delay:0us Dir Delay:0us Idle Delay:255ms]

[MSG:INFO: Axis count 3]

[MSG:INFO: Axis X (-1000.000,0.000)]

[MSG:INFO: Motor0]

[MSG:INFO: Axis Y (-1000.000,0.000)]

[MSG:INFO: Motor0]

[MSG:INFO: Axis Z (-1000.000,0.000)]

[MSG:INFO: Motor0]

[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]

ok"

5

Fixed it for you, 3.8.0

That is a git comment, and has nothing to do with what version to use.

Again, you did not upload all the config files.

6

Everything in this folder. FluidNC_Configs/LowRider CNC/UI V2 LRCNC at main · V1EngineeringInc/FluidNC_Configs · GitHub

1 Like
7

Should I be using the LR2 files on an LR3?

btw, your shipping dept deserves cookies. They’re consistently quick getting my occasional order out.

2 Likes
8

NVM I just saw that was V2 not LR2

1 Like
9

Thanks for the help, Ryan. I put too much stock in the error. With the UI V2 files uploaded it loaded 3.8 right up.

1 Like
10

@vicious1 go ahead, make yourself some cookies tonight :slight_smile:

5 Likes
11

Thanks, I will give out a raise!

As soon as we get the LR4 out then next on the chopping block is clean up some of the docs so things like this are a bit more clear. There are just to many words, we need more pictures.

3 Likes
12

I am regularly amazed how well Ryan does as a one-man enterprise. He designs, produces parts kits, operates the v1e.com forums, shop, and the rest of his buisines. Plus every other aspect.

My take is it is a labor of love, not just for making awesome machines and sharing them, it also is the community of makers that build them and help each other out.

1 Like
13

I like the people it attracts. Some of my friends are stuck in High school mode (yeah gray headed high schoolers), some are busy, and the rest just don’t share my interests in this stuff. Having to put in a little work to hang out with like minded people that inspire me daily is pretty cool.

3 Likes
14

He does deserve some cookies.

2 Likes