this post was submitted on 28 Aug 2023
19 points (95.2% liked)

3DPrinting

15590 readers
69 users here now

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

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

founded 1 year ago
MODERATORS
j4k3@lemmy.world
andypiper@lemmy.world
henry_rowengartner@lemmy.world
GrayBackgroundMusic@lemm.ee
19
my printer has reset the esteps (it resets settings out of nowhere more often) but i can't get it to take the new gcode. (lemm.ee)
submitted 1 year ago by CrowAirbrush@lemm.ee to c/3dprinting@lemmy.world
14 comments fedilink hide all child comments
 

My printers do this from time to time where they just ignore everything i did tl make them work and start using factory values.

It always pisses me off but usually once i find which setting it is i put it to what it needs to be and it's done.

It's been 3 days of me giving my printer new e step values with zero result.

At first i adjusted the start gcode in cura but now i'm also using an empty print file with settings and it has no effect.

I have a 30:1 extruder and the values i used so far go from 92 all the way up to 33.000, it actually extruded more at 92 then it did at 33k. The extruded amount seems to be random compared to the e steps i put in, i don't really know what is happening.

I checked the extruder gears and they look brand new.

you are viewing a single comment's thread
view the rest of the comments
[–] j4k3@lemmy.world 1 points 1 year ago (1 children)

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.

[–] CrowAirbrush@lemm.ee 2 points 1 year ago

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.