Replies: 9 comments 46 replies
-
Basic stuff, so no display, working without crashes (headcrash) or frequent 'bugs' (software). Considering the software which is running that is mostly out of our hands anyway so I would say no obvious bugs due to the way the OS is configured.
Basic idiot proof diy description with massive caveat-emptor. You already made lots of issues and discussions which should be fine. It's better than most commercial software. I would add a basic "how to build" so someone with a bit less experience embedded wise can do some basic stuff. |
Beta Was this translation helpful? Give feedback.
-
|
Same idea here. altough, I don't use wifi. But I can imagine that a lot of users do. |
Beta Was this translation helpful? Give feedback.
-
|
For Wifi it's more or less straightforward how it works. Questions is more how it can be configured. I will add basic Wifi support to public beta milestone. |
Beta Was this translation helpful? Give feedback.
-
|
I think there are few important things to be validated, possibly by more than a single person:
And few things to tweak:
|
Beta Was this translation helpful? Give feedback.
-
|
Yes, good points. Also the "power" outputs must be removed from Mainsail/Fluidd, because we don't really know yet what they do.
Not sure how to do that. With ntp timesync now enabled, Moonraker will subscribe to it's notification channels and show that in Mainsail/Fluidd (it was failing cert verification before). But any 'auto' update should not be possible already, and it would fail probably, if it was. We could try block these subscriptions in iptables, don't know if that's nice though ... |
Beta Was this translation helpful? Give feedback.
-
Works by running the uninstall ( Did it twice now. Note: did a leveling just to be sure. No idea why it would be needed but it felt safe. |
Beta Was this translation helpful? Give feedback.
-
|
Good, we should check again with the very last version before "public beta" once it is ready :D. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
I can also confirm the "revert to stock on install error" works since I used the old script calling S90 instead of S00 and it reverted. |
Beta Was this translation helpful? Give feedback.
-
|
I uploaded a new alpha release yesterday, now also added some release details:
Please do some testing with this. Feedback would be useful especially on:
Some ADM5 Pro feedback in general would be good, because I don't have it. And some feedback about regular printing would be great. I have done more printer modding than actual printing, lately 😅 Note: I wont't have time for more development until after the weekend. May plan is to then improve the documentation a bit, make minor fixes and have everything public by the end of next week. |
Beta Was this translation helpful? Give feedback.
-
|
Oof sounds rough on the hotend. At least the good news is klipper worked. I'll try 32 microsteps as well, seems like a reasonable choice. |
Beta Was this translation helpful? Give feedback.
-
on this note. Settings the timezone with |
Beta Was this translation helpful? Give feedback.
-
|
Yes, but fortunately noting seems to be damaged. I don't want to change the microsteps before public beta. We should probably start a discussion thread about optimizing the default config / printer calibration for that - I have other some other changes in mind. |
Beta Was this translation helpful? Give feedback.
-
Is that required? I thought C.utf8 should be compiled-in default locale, even if nothing is explicitly set. Timezone should be UTC. There is also no timezone data enabled in buildroot. |
Beta Was this translation helpful? Give feedback.
-
|
In that case without TZ data it's pretty much a done deal and doesn't matter. Klipperscreen starts barking error messages if LANG and LC_* are not set to something sane. I'll check what it was exactly but for now the startup script sets it to I doubt this will have any effect or issues on the normal release. |
Beta Was this translation helpful? Give feedback.
-
|
If you revert to stock, does it change the printing time on the printer info screen? |
Beta Was this translation helpful? Give feedback.
-
|
If you power it off it resets, no matter what you use. The RTC has no capacitor or battery for persistence. It "resets" by ntp query in the mod so times should be off by |
Beta Was this translation helpful? Give feedback.
-
|
I think @AJolly is referring to the printer statistics of the Flashforge app. That should be totally unaffected by the mod. I.e., if you print via the mod, and then go back to the stock system, the statistics do no change. The stock app doesn't know anything about the printing that happens with the mod. |
Beta Was this translation helpful? Give feedback.
-
|
Exactly it was wondering about the printer statistics, because I recently needed technical support, and they asked for a photo of that screen. Want to make sure we're not causing anyone reason to have their warranty denied. |
Beta Was this translation helpful? Give feedback.
-
Don't know where you are but I'm pretty sure I'll win that battle no matter what they say. (Woudn't be my first rodeo, then again consumer laws here have some bite, just like my credit card company's insurance.) If you want to set it to whatever: edit edit: You asked about printing time ... not meters, but the idea is the same, just a different variable. This includes the "serial number": There is a reason I blanked out the only thing which can actually identify your purchase. Again, these modules are so plentyful, doubt they actually can. Might be a good idea to back it up to the data partition anyway. |
Beta Was this translation helpful? Give feedback.
-
|
I updated the the Public Beta Milestone with some small tasks: https://github.com/xblax/flashforge_adm5_klipper_mod/issues?q=is%3Aissue+milestone%3A%22Public+Beta%22+is%3Aopen That are mostly some easy things to improve usability. I think most critical things are solved, otherwise. Does anybody see something that should be done and is missing on that list? Otherwise if nobody has any show-stoppers, I would plan get everything done, make a beta release and open the repo to the public. I think it would be nice if that can happen this sunday. |
Beta Was this translation helpful? Give feedback.
-
|
As a test I also used SuperSlicer and no issues. Wasn't expecting any but at least it has been tested now (so almost covering all slic3r variants) Did add the G17 code to klipper as I was getting very irritated by all the error messages. Has anyone tested with cura? |
Beta Was this translation helpful? Give feedback.
-
|
Another minor update (from yesterday, forgot to post). I experimented a bit with the niceness and have not noted any issues while messing with the system while klipper was at -5 (no noticeable difference with -20). The 10 for klipperscreen makes it take a bit longer to boot but afterwards I can toggle with it without the system choking and no real noticeable lag, except for the expected subprocesses running like iwctl/iwlist. @xblax added smem, I'm not familiar with it but for what I can see memory is definitely the most critical and not processing power or priority (with the current settings). I guess someone in the beta will run a several 100mb big gcode file and we shall see how that goes 🤣 |
Beta Was this translation helpful? Give feedback.
-
|
Yes, memory usage must be looked at in more detail at some point after beta launch. The smem utility is useful, because it takes shared memory into account. Otherwise it can look like some processes take much more than they actually do. With klipper-screen we have too look how much page trashing happens with the swap, that could be critical. Especially in combination with a Webcam being active as well. I also feel like there might a regression with Klipper + Moonraker memory usage somewhere. I feel like they needed less with the initial build. But we can go back to an old chroot to verify that. I'm not to worried about large G-Codes files. They are streamed, so in theory their size should not matter at all. |
Beta Was this translation helpful? Give feedback.
-
Some wild guesses:
Also matters a bit when you check ofcourse. |
Beta Was this translation helpful? Give feedback.
-
|
Everything should be compiled with -O3, vfpv4, neon etc. I will check cross-check current memory usage against an older build at a later point. For now I think it's working fine as is. |
Beta Was this translation helpful? Give feedback.
-
|
I will probably later tag the v00.03-beta version and upload the release builds. I thing the still outstanding documentation does not has to be in the tag necessarily. @consp I guess it will take 1 or 2 more days until everything is ready and I finally set this to public. |
Beta Was this translation helpful? Give feedback.
-
Will do that later today, editing some docs now. (wifi specifically, it's in the feature branch right now, hope I understood the klipper_mod dir on the usb drive correctly)
It should be really clear the normal one is preferred unless they know what they are doing. Would be a shame to get issues which only show up on the KS branch to blurr the normal issues (if any exist) |
Beta Was this translation helpful? Give feedback.
-
Yes, I will describe the klipper_mod dir feature in the install doc. But the Wifi doc should probably mention that an iwd config file can manually created, maybe have an example myWifi.psk and mention that it can be installed via usb drive (link to the install doc). |
Beta Was this translation helpful? Give feedback.
-
That's mostly what I attempted, |
Beta Was this translation helpful? Give feedback.
-
|
Ah yes, looks good! Didn't see you had already worked on it. |
Beta Was this translation helpful? Give feedback.
-
|
Tagged and uploaded the public beta release. The release notes are still pending: Will also do the missing documentation (install / uninstall, maybe camera) tomorrow evening. Too tired for today 😴 |
Beta Was this translation helpful? Give feedback.
-
|
I'm building now and then testing. Should be done in a few minutes. If it works without glitches I'll add the file. I also forgot how slot it is if you use the tgz file instead of the lose files 🤣 Secretly the klipperscreen alpha already contains the nfs client utils, forgot I already added them to the buildroot ... Don't expect any issues though. Actually works as well, both nfs and nfs4 mounts. Can be merged in buildroot feature branch, added to defconfig. And the completion sound on the end of the install was a jumpscare since I was not expecting it 😐 Looks to work as expected. |
Beta Was this translation helpful? Give feedback.
-
|
Also went and updated some of the issues to make it more nice when people see it. (And assigned the klipperscreen bugs to myself) |
Beta Was this translation helpful? Give feedback.
-
I'd like to start a discussion on what is still missing before this repository should go public. It should not stay closed for too long. I would be nicer to allow everyone interested to participate in the discussions / development. The demand for this seems to be there, even though we didn't really announce the ongoing development in many places.
What do you all think should be done? Feature-wise or documentation.
I've created thee milestones: https://github.com/xblax/flashforge_adm5_klipper_mod/milestones
Some planned enhancements are already tracked as an issue https://github.com/xblax/flashforge_adm5_klipper_mod/issues but probably there is other stuff to be done or even trivial things that could be improved easily.
I will create additional issues and add them to milestones as this discussion proceeds.
Beta Was this translation helpful? Give feedback.
All reactions