I’ve found it varies from manufacturer to manufacturer as well as colour, some of the petg I’ve got has been chilling in my cabinet in the garage for at least 1 summer and it prints fine, just some stringing, other spools they’re a mess right out the bag. Still worth drying filament, but more so stuff like nylon which is extremely hygroscopic.
Haven’t looked into it but do shops offer lube analysis services? Yeah you could send out your own sample to a lab, having it as a shop service would be way more accessible to people.
Though, in my experience, getting people to commit can be a pain, lots of “yeah I know we have a long p-f interval and it’s super noticeable before it functionally fails, but it’s not that much effort so I’m doing needless maintenance anyhow just in case”, which end of the day you do you.
I’ve always known your world is complex, working closely with accountants and actuaries the last 4 years doing data applications further confirmed that, there’s some legitimately complex math that shows up, and it’s a lot of work to model that correctly.
“It’s just a …” Is a redflag to me, project’s going to be a gongshow.
I find that mentality of not trying to understand the problem and its context totally counter to the engineering method.
Personally, recommend forgejo, gitlab has a lot of features I didn’t need and I found the upgrade process if you didn’t keep on top of it annoying. Forgejo actions are pretty similar to github ones and setting up runners is super straightforward.
Mmmm, yeah that sucks, that first block I mentioned was an older style that wasn’t fixed in place and I must have twisted it accidentally after a nozzle change, super slow leak just enveloped the thing, didn’t help there either!
i was thinking along those lines for equipment monitoring stuff, klipper works with Prometheus & grafana (have metrics from my printers), was thinking about looking at using the extra accelerometers I have to do something like vibration monitoring.
I could see using a second sbc for extra sensors as well for support, thinking about printers that don’t run klipper, so long as you can correlate data it should still be useful. Honestly kinda thinking something similar to PLC data, was fantastic for fault finding and failure investigations, also useful for process control + condition based maintenance, there’s a heck of a lot that could be done with it.
Edit: You have me thinking about this now, what would be really cool is an ability to anonymously federate data tied to events, I recall some enterprise software I used like 5-6 years ago could do this with condition indicators, I have 2 machines, I won’t see every failure mode, but if we had 1000 machines you can get much more accurate information about things like MTBF. Heck I’d even just be happy with some community FMEAs, really just thinking of taking a technical approach to my printer maintenance and usage.
What type of filament? Acetone doesn’t do much to things like pla or petg, stuff that works aren’t things you generally want around the house, industrial solvents and stuff. The jar of acetone can soften it up some but you’ll need to soak for some time, I’ve used MEK too, but that’s in the “don’t keep that at home” category, it’s really flammable and should use ppe (I mean should use ppe for a lot of the stuff we use, 99% IPA is harsh on your skin, I use nitriles because it irritates my hands something fierce.)
Cold pull as others recommended, nozzles are consumables, def should keep some around. Cleaning filament works pretty well in my experience if you have a partial clog.
I’ve been there though, first block I didn’t use a sock and the set screws got encased in degraded petg, I ended up scrapping it and putting it on the shelf as a learning moment, def recommend a sock if you don’t have, it’s saved me a lot of grief.
I kept them with linear rods, rails were more than I wanted to do at the time. I changed over to a dragon HF after liking it on my voron, just to keep common parts. Hey, its good to know at least that I can probably push more, tuning a profile for it is definitely going to be on my list.
The ObXidian nozzles are really nice, I just have a 0.4mm and 0.6mm regular nozzles, I’ve used a bunch of hardened coated nozzles before, seem nicer than those but haven’t tested much.
I bear modded mine at the same time and a few other things, biggest for me was that I liked my macros on my voron and I could share them and the motors are substantially quieter.
I haven’t pushed it acceleration wise, do you have any print profiles for prusaslicer or the like? I definitely have room to work with on mine.
Terminal usage is a tool just like GUI tools, I don’t think it’s helpful either to preload people with the belief that it’s some arcane tool that takes years before you can start using it, like anything you pick it up by doing.
Can’t really say it’s 100% optional as a blanket case either, heavily depends on a user, my work I’ve depended on having a terminal for years, and that was even before I moved into SWE, I’ve seen lots of business developed processes put together as an amalgam of batch files, VBA/VBS, and python because they needed to put something together with what they had rights to.
Be honest that I don’t see the terminal as a barrier to Linux anyhow, for the use case of “I browse the internet and use office programs”, you absolutely do not need to drop to the CLI, at least not for Debian or Mint, can handle installs and updates through their graphical package managers. Most people probably aren’t setting up services or the like on their machines, and if they are they already require terminal usage on any operating system.