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.

  • j4k3@lemmy.worldM
    link
    fedilink
    English
    arrow-up
    1
    ·
    10 months ago

    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.eeOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      10 months 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.