I had my machine working great, was working on the squareness test however i accidently reset the firmware on the FluidNC tab for the Jackpot board, no nothing is working (homing, movement, ect)
Do i need to somehow reload the firmware, and how is this done?
Even easier, just erase and reload the whole thing here in a chrome browser, FluidNC Web Installer, then drop our config files back on it from the jackpot docs page.
So I was able to get everything back up and working. Several things that I noticed… FYI im a mechanical engineer, so the software stuff is a learning curve for me every time.
Don’t reset the firmware, this is what happens when you press buttons you don’t understand lol
Never delete any of the firmware files, I accidentally deleted index.html.gz, this seems to be how the controller talks to wifi somehow and how I lost connection to my controller.
This ESP Controller…
—EN: Reset button.
—Boot: Download button. Holding down Boot and then pressing EN initiates Firmware
Download mode for downloading firmware through the serial port.
—Was initially not sure what these buttons actually did.
—The cable you plug into your computer maters. Luckily I have a “box of cables” and was able to
find one that supported data transfer, not just power. I was struggling for a while because I
though my cable was working, but it was only powering the board and not enabling data.
— You need specific drivers on your PC to read this ESP board through the USB port
After some trial and error with the cable, the web installer made this super easy. I am now back up and running. Just completed my build last week, was in the middle of squaring and leveling when I pressed buttons i did not understand.
In all honesty this documentation is better than some of the documentation that I have seen in the production and manufacturing world. ( I work in lithium ion battery development) There is a fine line between too much detail and not enough detail. I usually lean towards too much detail and try to never assume the capability of the party on the receiving end, that way my engineering documentation is consistent across projects.
This however is a little bit different as all of us users, are not paying for a service. Better documentation takes a lot of time, resources, and more time. And this documentation is sufficient to complete the product, especially when you take into account the Fluid NC wiki as well.
The only thing I would change is adding a structured BOM and Assembly Drawing. Something that can be printed if the user chooses (which I can help with since I feel like i owe this community after all the help i have received with the lowrider build.