My search-fu may be lacking here, but is there a way to send gcode wirelessly to the jackpot board rather than a direct connection via USB or taking the SD card out every time?
Feel free to delete this if it’s a stupid question or it’s already been answered elsewhere.
That’s not how these forums work. That is not a stupid question, the only stupid thing would have been not to ask.
For me, with WebUI V3, I select the flash card, then drag-and-drop the .gcode file from my local machine over to the window with files on it. You can also select to upload from that panel on the Web UI as well.
Sorry, I’m not near any of my machines until later today; hopefully someone else will jump in with some screenshots for you.
Newer FluidNC also supports WebDAV, so there are multiple options for you.
For now, until we start using the newer firmware and frontend, it is the most safe to use the SD card directly. Currently, if you do transfer over the air it could not complete but also not error out so you could start a job and have it stop mid cut.
When over the air transfer is more trusted I will make a post about it.
I have mentioned this in other posts so ignore this if you feel it isn’t relevant. While the SD card may seem “safe” it’s also terribly manual, tedious, and subjects the SD card and slot to IMHO unnecessary wear and tear.
I prefer instead the addition of a headless RPi3/4 with Jeff’s V1Pi image and CNCjs or Octoprint (or, a headless mini-PC with RDP and any gcode sender) and connect it to the Jackpot directly thru USB. This allows any of several ways to send a complete job from your browser or with wireless file transfer to the remote device and sender… and then control the job without need of any further involvement of wifi during the actual job run.
No it doesn’t. I have all 3 versions and upload through the Webui V3 exclusively. If you are running Fluidnc 3.9.9 or newer and Webui V3 you shouldn’t have any problems. Mitch did a lot of work to get this working reliably. Just don’t start uploading anything while a job is running.
I have literally never uploaded files directly to the SD card. I always do it via the WebUI. With that said, I am connected in STA mode with a strong connection.
Okay this thread is a mess. I think I made a mistake by not giving a more complete answer.
You can drag and drop files and they should upload through your browser if you are connected to any of the Jackpots. The reason I did not say that way at first is, it depends… You should be on at least fluidNC 3.9.9, and v9-v10 of Mikes WebUI V3, the other thing to make it even more stable is using STA mode if your network is strong enough. To make this even more complete is even with that set up all up to date you do not have a way to know if the transfer completed 100%. So the yellow brick road is to just use the SD card manually until you are very familiar with your machine and network. I would hate to see you struggling with CAM and uploading files and getting so excited you close out your browser and the file did not complete the transfer.
So do wireless file transfers at your own risk. The older the firmware the more likely the file will transfer with errors, if you are using a Jackpot 1 there is a very good chance you have a very old firmware on it the older firmware would error out 100% of the time.
I think for simplicity’s sake, I’ll just wait for the post about the update and try to focus more on minimizing my own errors with the gcode.
I’m attempting to recreate the whole thing in fusion so I can run simulations, but it’s taking a while to build the model with rebuilt stls. They have generic machines already built in, so that’s what I’ve been using so far with some success.
A bit off topic, but somewhat tangential; has anyone already done that yet? Or are the variances in the machine dimensions too numerous to make it practical? (Added a model into fusion CAM, I mean.)
I think there just isn’t as big of a Fusion CAM user base here. People tend to use EstlCAM, and more recently MillMage.
I looked at setting up the machine in Fusion once, but then decided it wasn’t worth it and just would use test cuts, etc to verify my CAM.
If you are doing small tests and pieces that don’t matter, as long as you have a strong connection between your computer and the Jackpot, you can probably use the WebUI to transfer wirelessly.
FluidNC and the WebUI has no way to do file upload verification, so a partial transfer is possible. The weaker the connection and bigger the file, the more likely you are to have an issue.
For important gcode and expensive pieces, you are much safer to transfer SD card directly. Then you know 100% it is right.
When I’m just running tests, I’m more likely to trust it.
Some people have had 0 problems, some people have had partial files run and ruin pieces… YMMV
Nothing to do with you, more about a feature I need to document better and have a solid answer for. It is a highly requested thing…I just don’t trust it because I have lost a job to a partial transfer…a long time ago.
I agree with these guys, and I think Mike just summarized it very well., $ss will tell you what firmware you are on in the terminal, if you are on 3.9.9 you are probably safe.
Thank you, Mike! That makes sense. I already have Fusion, so that’s just what I’ve stuck with. Trusting my CAM work at the moment isn’t exactly where I want it to be. Just though sims would help me learn without putting apprentice marks all over my spoilboard.
I’ll probably stick a sharpie on the machine and run a dry pass with no tool installed for a bit. Seems to be a common answer to the dilemma.
Admittedly, for me it’s like going to the Dr. I don’t know better or I wouldn’t be there.
I’m bound to ask lots of questions, and I try to research before asking. I don’t wanna clog up the works with unnecessary questions, or derail other people’s stuff. Hopefully I can at least help newbie proof things with my questions.