view the rest of the comments
3DPrinting
3DPrinting is a place where makers of all skill levels and walks of life can learn about and discuss 3D printing and development of 3D printed parts and devices.
The r/functionalprint community is now located at: !functionalprint@kbin.social or !functionalprint@fedia.io
There are CAD communities available at: !cad@lemmy.world or !freecad@lemmy.ml
Rules
-
No bigotry - including racism, sexism, ableism, homophobia, transphobia, or xenophobia. Code of Conduct.
-
Be respectful, especially when disagreeing. Everyone should feel welcome here.
-
No porn (NSFW prints are acceptable but must be marked NSFW)
-
No Ads / Spamming / Guerrilla Marketing
-
Do not create links to reddit
-
If you see an issue please flag it
-
No guns
-
No injury gore posts
If you need an easy way to host pictures, https://catbox.moe may be an option. Be ethical about what you post and donate if you are able or use this a lot. It is just an individual hosting content, not a company. The image embedding syntax for Lemmy is ![](URL)
Moderation policy: Light, mostly invisible
Sounds like buggy code.
This is pure speculation, but it could be due to how the flash memory is written. Flash stores bits in page blocks. There is no way to partially write to flash memory. Even if a single variable needs to get stored in persistent memory, a whole page (like 4096 bits) must be retrieved, old values copied, new values added or changed, and the whole page gets written back into Flash. If something like power is lost while a page is getting written it is very possible for the last bits to get missed. If these bits are critical it can ruin the page and that can do stuff like mess up your settings. For a dev, there are ways around this in software by adding a redundant page in flash so that old, new, and changing are always on their own pages. If there is a problem the software knows to retrieve the redundant page. These are the types of features that do not make it into cheap project parts printers, and some expensive ones too.
That is way above my knowledge level, damn. Usually what i've found on google is that people have a different issue that causes this to happen like a different printer that uses another flavour of gcode that doesn't use the start gcode.
None of the things i've found so far has fixed my issue.
In the past i would do a fresh calibration of all the different settings and eventually the printer would start behaving again.
I'm going to have to do that either way as i have a new hot end coming in today for this printer.