Hello, I am wondering version of Marlin Snapmaker 2.0 is currently I have struggled to find a definitive answer even with the M115 command.
Also, if it is running Marlin 2.1.x is it possible to get input shaping running?
I have struggled to see that the GIHUB for both the Snapmaker 2.0 firmware and LUBAN have been updated in months (or even year) yet there are releases still made.
Yeah, would be nice to fix a lot with firmware, we have a bunch of of people with seems like centuries of coding experience combined. But non have real input.
Snapmaker is slacking on GitHub, hopefully they will update it soon. Best way to let them know itās important - submit ticket Support Ticket Form
input shaping - [Now compatible with 8-lead] Vibration Compensation Beta Firmware for 2.0 Series: Stable Print Quality at Higher Speed
The Snapmaker firmware is technically not Marlin, so you wonāt find a Marlin version for it. It is a highly customized derivative that is only based on Marlin. The Snapmaker Devs have been working an a firmware version that will include āvibration compensation,ā and the beta version of it is available here on the forum, but an official stable version of it is not expected until after the end of the year at the earliest.
Itās not customized enough to get rid of inherited arc issues and support things that are already in marlin code. Like screen messages.
Id say itās more of a censored version of an older Marlin. Not even v2.
I would be interested to know where those beta firmwareās are?
Also, my concern is that the license of this being open source is not being kept any where near up to date with the current firmware. We are unable to update the firmware or software ourselves from the GitHub because it is the older firmware closer to year or more.
Even Luna is out of date not including any of the newest build updates on GitHub whatās up with that?
I posted the link above for firmware.
The thing with open source - is luck of enforcement. Look at Bambu - they took basically everything from open source, slapped some lipstick on it with lidar and are making shit tone of money without contributing back in any way.
Let them know your concerns - Support Ticket Form
Snapmakerās version control is all over the place. When thereās a release itās never clear what commit itās based on (sometimes itās probably even from a private fork or a branch other than main). Thereās no CI/CD in place that produces nightly builds or even just regular release builds when a tag is created.
I wish they would sort this out. It would make it a lot easier for the community to contribute to the firmware.
Would you share some examples, we might be able to share this with snapmaker team.
A good example is the Portapack Mayhem repository (GitHub - eried/portapack-mayhem at master). They have automated nightly builds in place that produce packages; both for their ābleeding edgeā branch as well as their stable release branch. Every successful build is nicely tagged and the artefacts resulting from the build are automatically published (when successful).
Thereās also a good pull request process in place with peer reviewing and some automated checks (syntax style/formatting).
The nightly ābleeding edgeā builds are nice but not a necessity. Just automated builds of the stable branch with proper tagging and publishing of artefacts would be a fantastic improvement. Combined with a properly defined pull request process their repository would be in good shape for community contributions.
Last but not least, Snapmaker developers should no longer publish builds they built locally on their fork. Anything published to customers should be traceable to a build published by the automated build process on GitHub.
Just type into the forum search bar āvibration compensation firmwareā and you will find it.
I feel there are good ideas provided by Mayco, and I agree with many of the things that he has shared. The more I look I do see forks where people do have the code available. It would be really nice to see there be a beta branch and a main branch. There is a branch and page on here for the Vibration Control that was implemented, but it does not include all the newer updates as well with it. So testing it as beta would also take away a lot of the main branch new feature releases.
Some examples that could be shared with the snap maker team too is with LUBAN, there are no updates to the software that are related to new settings. It uses a very old foundation of CURA.
Also, if there could be official profiles for CURA and especially PRUSA as only user ones exist that are really good. However, I still struggle to get the same results of well tune profiles and ways to print to the same quality I get from the standard profiles and slicing using LUBAN?
I would like to contribute to Snapmaker Code if I can such as finding a better way, for example I own multiple SNAPMAKERS, to authorize the device. Switching between 2 SNAPMAKERS I have to get up constantly and confirm the device when I want to send a file to it over WIFI.
You make a good point and this is good that it does exist, it was difficult to find and understand where to find it without the forum. The github is the main location for the CODE and would be really nice to see the release notes there as well as what they have added or fixed.
@CSOOPY35 - have you seen the GitHub - shurushetr/awesome-snapmaker: Curated list of things that help you make something awesome with Snapmaker machines. ?
I have in the past. Been a while since came across it. I think the 2 or 3 biggest things you could share with the team is
beta releases for the firmware and software is update on the GitHub along side with the same thing being that they have the code for the most current version of the Snapmaker printers in there as well. The code is not organized nor main branch been update for 1 or 2 years to match what I have installed on my machine. So I canāt see the current code and upload or make changes to it if I wanted a current version
Luna needs some major updates GitHub as well as the ability toe cut move objects and add text easier etc
remove the need to authenticate per device and then disconnect to use the screen. It would be nice that you authenticate once per computer and be able to view multiple printers at the same time in the work space
Itās developed based on Marlin 2.0, an early version in around early 2019.
The M115 command is mainly queries the current configuration of the machine, which functions are enabled and which functions are not enabled. You can contact the support team to ask for more info currently as there is no public document about this explanation. Sorry for the inconvenience. Support Ticket Form
I have forwarded this feedback and a few other similar feedback on the G-code commands document request to the team. We will update/add some Gcode commands to the shared document soon.
BTW. The input shaping firmware is expected to be released by the end of this year.
Thank you for doing this. However, I am wondering about the firmware release. I have yet to see the 1.19 version released that would include the updates as well as No github code updates made to the github to match the PRODUCTION code releases a.k.a V1.18.1 ? I could be wrong.