Said differently, FluidNC is a full featured CNC controller targeted at CNC machines.
Marlin is a 3D printer firmware that has been adapted with varying degrees of success to do CNC work on a non-3D printer.
V1 CNC machines use this on Marlin and have for a very long time.
Yeah I think there is confusion. There are some interesting use cases for Marlin on Jackpot.
I’d like it if it were possible to pop in an expansion module and run a flying Z axis CoreXY printer with the Jackpot, as an example.
Marlin is in no way a benefit on Jackpot over FluidNC, though- for the V1 CNC machines.
At least that’s my opinion.
Thanks for disclosing that [quote=“Ryan, post:60, topic:40021, username:vicious1”]
We can auto square X and Y and Level Z, yes.
[/quote]
I will review the forum to find out and ask for help if I don’t grasp how to do that.
Kind regards
It is kinda funny, the Z axis thing was in Marlin already, Then me and Heffe expanded it to do X and Y as well. Well, I bodged it up pretty good, the Heffe fixed it.
Then we had to do it all again to marlin 2.0…it got merged into both branches eventually.
Automatic bed leveling, for example to cut PCBs, exists in Marlin but not in FluidNC.
Depending how deep you look, there can be a lot of features that are present in one but not in the other. Marlin can also launch a gcode file on startup, for example if you have a sand table and you want it to just start running when you apply power.
With FluidNC, if you ask for this kind of thing, they will tell you that you are wrong for wanting it.
Thanks MakerJim for helping me realize the advantages of FluidNC over Marlin in Jackpot.
On the other hand even if I was able to compile Marlin for CNC as per Jamie version, doing more testing, I found out that it will require an index.html.gz specially for CNC in Marlin as the ones I found are for 3D Printers and the FluidNC ones don’t talk “Marlin”. As this is beyond my capabilities I think I will better focus on FluidNC for my Jackpot.
Thanks everyone for the patience and guidance. This is a great forum.
Reflecting on your comment make me want for a dual boot system; say Marlin and then with some command and may be a rebooting you switch to FluidNC. In that fashion you will be able to use the firmware most suitable for your requirements, without needing to re-flash your device. Having 8 MB in Jackpot ESP32 should make no problem to install a second firmware in another partition.
Jamie, do you know how to generate a “Marlin CNC talking” index.html.gz interface?
Thanks for your ideas.
Yes, diversity is good including diversity in machine control software.
Marlin doesn’t serve the Web UI directly, it mostly is used with either Marlin mode (12864 LCDs), BTT TFT mode (where the TFT acts as its own UI and sender), or if you add an ESP-01S you can get a cousin of a similar Web UI to what FluidNC uses on ESP-32s (same original author).
If you want to run that kind of setup and have an SKR Pro 1.2 or other supported BTT board, there’s a full thread here on the forums about this. Ryan used to sell a fully loaded ESP-01S for use on the SKRs here in the shop.
Hi MakerJim,
Your assertion that “Marlin doesn’t serve the Web UI directly” is not grounded. In fact Jamie version (an as a matter of fact current version of Marlin) when compiled gets a webUI. The problem is that is a webUI for 3D printers and as such presents “Temperature section” and “Extruder Section, and at first glance, the appearance is very similar to the default FluidNC.
A nice thing will be to have the Jamies’s Jackpot Marlin version but with a CNC web page; i.e. without the 3D stuff but similar to FluidNC web pages.
The Marlin version for SKR Pro (and others) didn’t have the webUI as they don’t have wifi, so that’s the reason that the clever guys here generated a webUI for the ESP-01s which can connect to the SKR-Pro. Two different stories.
Thanks for your comments
That IS the default Marlin config.
The vast majority of commercial Marlin boards don’t have this built in (e.g. the SKR series from BTT)
Then this is either something Jamie added, or more likely contributed code from around the ecosystem.
That’s a problem exactly how? It bugs you?
I’d love to see you contribute working code to achieve this. It would be a step forward.
The issue isn’t that it wouldn’t be great- the big issue is having a committed code maintainer to keep it working across releases.
Luc built a version that, and there are folks here that contribute a derivative of Luc’s code for FluidNC. Luc still maintains the ESP-01 version and likely other branches I’m not aware of.
I don’t know the full pedigree of the ESP-32 version of Marlin WebUI - but it’s likely related as described.
Not so different a story as you may imagine. More like chapters in the same book.
Thanks for your assessments on all my previous comments. I don’t manage this Forum capabilities as of now so I will try to answer your comments.
But if you go now to the general Marlin GitHub you will find the webUI already there. Today’s Marlin page
Then this is either something Jamie added, or more likely contributed code from around the ecosystem.
Nope. It already there for anyone to use like the ones of MKS TinyBee which Jamie said earlier.
No problem other than is not for a CNC and have meaningless information. I think if you load gcod (Marlin flavor) will do the job.
That interface can’t be customized. Regarding your following point of me doing the modifications, no way, I don have any coding knowledge.
I totally agree with your final comment “ More like chapters in the same book.”. Going thru all of the different issues posted here I have been able to see that and once I managed some of the tools I can follow the process in others.
Kind regards