Jackpot Connection Issue

Hey,

So after a long night of going down a pretty deep rabbit hole, I am sort of lost and cannot figure out what is going on. I finished building my CNC and plugged in the Jackpot board and all the stepper motor wires (no endstops yet, still waiting on longer wires). I connected via wifi and tried to move the motors using the arrows but nothing worked. After reading some stuff on FluidNC wiki, I plugged the ESP into my laptop, load up the FluidNC Web Installer. I did a fresh install, downloaded the V3 config file and uploaded it under the file manager within the web application. I then restart the controller and try to connect via wifi…no luck.

Next I followed the wifi steps on the FluidNC wiki. Tried to configure Wifi as stated but also no luck.

Was the controller suppose to work straight out of the box when I connected to WiFi? I spent a few hours and can still not figure it out. Any help would be appreciated.

Did you fill out the SSID and password for your home network? If you did, then you’ll need to find it by IP on your home network as in STA mode it won’t show up as an AP named FluidNC any longer.

Depending on your home network setup, you might be able to find your machine by pointing at fluidnc.local. If that fails, you will need to figure out how to see the connected devices to your home AP or router and then use that to point to the IP address of your web interfaxe.

1 Like

Solved!
Honestly I was just about to call it a night, but I figured what the hell, might as well try a full reboot again. This time I did a fresh install, uploaded the config file, but I did NOT touch the WiFi settings. I just let it be and it worked that time. The only problem with this is that I would have to disconnect from my home wifi to access the WebUI instead of just connecting to it while still connected to my home Wifi is that correct?

I will revisit this issue tomorrow, but what a good way to wrap up the night.

2 Likes

yes

If you want to be on your home internet you can use STA mode but you will need to use fluidnc.local or find the IP on your network. We ship in AP mode so it is easy to find.

Yes, every single board is tested on wifi before it leaves.

I’ve since gotten it up and running and drawing pictures. Occasionally it disconnects or lags a little when drawing the pictures. I got this error tonight, anyone know what its for? It will not let me go past this screen.


We need to see what the $SS output shows you. Cut and paste that from the console window.

Also go back down to 3.8.0 you are using a beta branch and is not tested by any of us.

I turned it off and went back downstairs to connect again and seems to be working perfectly fine now. Maybe its the beta version causing some various issues. I will upload 3.8.0 tomorrow after work and try it out.

1 Like

So opening this thread back up. I have been having some issues with FluidNC and the web app. I have done a full wipe and re-configured. Motors worked to home just fine. Unplugged the motors to do some wire management, plugged back in and no connection. Can’t manually jog the axis back and forth. I did another full wipe thinking it was something wrong with that. Tried homing and motors were very jittery (I am guessing its something with software because motors were running fine just minutes before, so not a physical issue with the trucks). Tried connecting again and got an error below, config file is already uploaded but its saying its invalid. Went in to the installer and re-uploaded the config file, re-connected and it wont stay connected to the Jackpot (wifi keeps dropping out after the webapp is opened up. Also got this message when I re-connected to try it again:

ERROR:8 Grbl ‘$’ command cannot be used unless Grbl is IDLE. Ensures smooth operation during a job. Error : undefined :undefined [MSG:ERR: Command requires idle state] [MSG:INFO: Caution: Unlocked] ok

Anything I can try? Do I have a bad ESP? I will note the wifi kept dropping out when I first tried it out. Has been a recurring issue.

ERROR:152 Configuration is invalid. Check boot messages for ERR’s. Error : undefined :undefined [MSG:ERR: Configuration is invalid. Check boot messages for ERR’s.]

Did you modify your config.yaml? That error means there is something wrong in the config. You did upload it back to the ESP after re-flashing correct?

As far as your motors jittering, I would check your wiring. Make sure all the wires are fully seated in all the motor dupont connectors. If one is pulled out just a little it can be making a bad connection. Also check any extension cables where they plug in. If you wire managed too tight it could have pulled something just barely loose where its not making a good connection

You can not unplug a power up stepper. If that is what you did there is a good chance you pooped a driver?

Went for a break actually and figured I might as well try re-uploading it again and in the FluidNC Web Installer it says “The controller does not seem to have FluidNC installed, do you wish to install it?”, which is weird because I did install it and re-uploaded the V3 config file from GitHub. Going to try re-flashing and uploading config again and see what happens.

Motors seem back to normal for a short amount of time I was able to run the machine before it disconnected again. I did unplug a powered stepper…my bad.

This always happened to me and I just installed it again anyway when updating.

I don’t use the web installer anymore, but that’s only because it doesn’t support using the full 8MB of memory on the V1E ESP32s.

2 Likes

I’ve seen that before so I wouldn’t worry about that.

1 Like

Everything seems to be working normally now, had an issue with a Z-stepper motor not connecting, but tried it multiple times and it works now. What do you use instead of the web installer?

I compile the source and flash via PlatformIO. Unless you need more Flash memory for themes and extensions in WebUI v3, I would not go this route.

Some alternatives are described here under “More installing and update options”:
https://docs.v1e.com/electronics/jackpot/#updating-installing-firmware