Still pretty new to this, forgive any ignorance in asking:
Has anyone published a tutorial video on the use of FluidNC similar to what Christian provided for Estlcam? I was watching it for a second time this morning and I’m really appreciating how thorough that tutorial is.
What would be the process for moving away from FluidNC and towards Estlcam for control? Pros and Cons? Settings for use with the Jackpot board?
Thoughts?
FluidNc (based on grbl) is the firmware that runs the controller board other firmwares are: mach3-marlin-linux cnc
Estlcam is a cam software used to create gcodes to run on any flavor of firmware you select in the options. Also gives you the chance to run your machine with a certain controller an run directly with your computer attached. Maybe a couple of people are using this around here but not the majority.
I have both the Jackpot for my old Primo and the OpenCNCShield2 (which uses Estlcam as control as well) for my LowRider. I personally like the controls via Estlcam much better, though you need a USB connection at all times. So for really large machines it might be the worse choice.
It sounds like Estlcam can drive the machine but only with a USB connection, and thus eliminating all the wireless connection requirements and associated connectivity problems?
Am I getting that correctly? That sounds ideal in my opinion, I hate trying to operate this wirelessly. The FluidNC AP is constantly dropping out when I first fire up the machine, and in the event that I have to kill the power because something is going awry, it will not initiate a restarted AP network. I am finding that I have to shut everything down, walk away and come back later.
If I can get away from all that, I definitely want to.
Your wireless issues with the Jackpot are not normal. I would see if we can figure that out. Note that the wireless functionality is only used for managing/controlling the machine. When running an actual job, it’s running off the SD card.
Note that there are a ton of people using the Jackpot here and only a handful using Estlcam for control (many use it for CAM only).
Thank you, all, for the information.
If there’s a wired option, I definitely want to pursue it. I’m not much of a computer programmer/troubleshooter and I frankly have no patience with it, especially if there’s a wired option.
Additionally, the tutorial Christian provides is really appealing, and does a very good job of explaining all the functions. Where can I find an equivalent (video or pdf) that goes through the FluidNC Web UI as thoroughly?
I’m not aware that there is one. However, I think you’re missing how little you actually need to use the WebUI. When you generate gcode, you normally include everything you need in there for zeroing the machine and handling tool changes. So, all you are doing via the WebUI is uploading the file to the SD card (or you can put the SD card in your computer, copy the file, and put it back in the Jackpot), homing the machine, jogging to the starting location, and clicking run on the file. During a tool change, there would be a pause that you need to resume via the WebUI.
You can still go 100% wired with the Jackpot although it still might make sense to do the initial configuration via the WebUI. You would do this by adding a wired pendant. With this method, you would transfer the gcode to the SD card manually and then control the machine via the pendant.
You can also use a compatible gcode sender like UGS. This requires a computer connected via USB. I’m not sure I recommend this approach since it involves the computer essentially streaming the gcode over USB.
http://wiki.fluidnc.com/en/support/gcode_senders
I guess I just want to make it clear that you have options with the Jackpot.
I’m also not sure you realize that you can only use FluidNC on the Jackpot. Using Estlcam for control requires a different board.
Thank you for that info and clarification!
I’m not aware of much of what you’re sharing for info, and definitely learning.
Hay buddy did you ever get anyware on this?
To a degree, yes.
For the LowRider I built, I ended up going to a pendant control to help eliminate the need for a computer (as much) to operate it.
I still decided that EstlCAM was the direction I wanted to go in as I’ve had a poor experience with FluidNC thus far. To be clear, my issues with it are completely related to my ignorance with the tech, and I feel I’ve had better luck understanding EstlCam due to the tutorials available for it online.
Hope that helps, feel free to reach out with any questions!
I am in the boat right next to you. This link is to my topic on the subject.
I have been plugging along with FluidNC but it’s a pain,it will run the code but 1/2 the time PAUSE button isn’t there or no connection, so useless.
I have an M5dial on order
im using my fluidnc controllers via wifi/touchscreen for the webui and have yet to see that issue. i can always pause/resume form the tablet interface ( i only use the webui2)
Like I said, I believe the problems I have are due to my own ignorance. I have little patience to troubleshoot the tech unless I have a very explicit set of instructions.
I found the M5 dial to be similarly frustrating to get working, again, due to the lack of explicit instructions and online resources.
Good luck!
Mine will connect and disconnect throughout the print no pause button and I get a nag in the toolbar action needed if I click on it, it opens a new browser window.
What tablet are you using? Cesar
I’ve had bits of the FluidNC interface not update or disappear. Using an iPad Air (3rd gen? maybe 4th…I don’t remember)
The problem for me is when the iPad goes to sleep and then wakes up the browser doesn’t always update correctly. If I keep the iPad from going to sleep then all is well. But I’ve had a few instances where I would do something like:
Start Z probe
Go to hit Start after
No start button…no indicate that the machine is in paused state at all.
And if I reload the browser then I get a warning screen about being in the middle of an operation and needing to cancel it if I want to do a reload…so now no UI at all.
So I’ve learned to never reload the browser or I lose the UI completely if I’m in the middle of something.
I did find that just navigating to a different tab and then coming back (say go to settings the back to the main tab) it will usually refresh and the current status will now be accurate.
But the two best solutions I’ve found are:
-
Add a pendant and use it - though I’ve found I don’t care for the M5 pendant (screen too small and knob too notchy) and both the M5 and the CYD are a little flaky and slow.
-
Don’t let the ipad go to sleep
Despite this annoyance I still find I prefer it over the old Marlin firmware I ran on my MPCNC and I prefer both over having to be connected to a computer since I really don’t want to put a computer out in my garage for a number of reasons.
raspberrypi/wifi/touchscreen
whatever device you have, get rid of the sleep mode
I agree with you on the Marlin also have a primo was happy with that setup.
I have an old SURFACE Microsoft seemed perfect but does not connect at all.I guess I could just get SKpro board
I tried both on my MPCNC build and ended up sticking with FluidNC. The Wi-Fi interface is super convenient, and once it’s set up, it’s really stable. ESTLCAM was nice too, especially the all-in-one workflow, but I didn’t love being tied to Windows.