I have had this happen before and not sure what cleared it. If it matters (it doesn’t), I am currently using Bjoern’s firmware v.1.14.6 with display v.1.14.3. I say it doesn’t matter because this has happened with Sovol sourced firmware.
I recently ran a print in Single 1 mode and worked as expected, but a small detail on the part didn’t print well, so I thought I would run through the bed-leveling routine as it had been awhile since I ran that.
I am setup to use the left extruder which was used for the initial print, but after the leveling routine, I ran the same gcode, but the printer started heating the right extruder and after that reached the target temperature, the right extruder advanced itself into the left extruder which was used to auto home (as expected) and was sitting at or near x150.
Also, if it matters (it doesn’t), I am starting the use Prusa slicer. This doesn’t matter as this happened in the past while using Cura to produce the gcode.
I have went into “Set hotend offset” and selected Initialize EEPROM which I am guessing resets some (all?) settings as the Z offset changes to -1.85 and I had it saved to -1.10 before selecting Initialize.
Is there a way to reset this error condition? I have loaded a previous firmware version and then turned around and reloaded the v.1.14.6 firmware hoping it would reset some issue causing my problem.
Hello urbnsr,
without knowledge of your specific print file / slicer settings, I can only make unfounded assumptions about the cause of the observed behavior - I will not do this.
In general, the “Initialize EEPROM” function resets all saved settings to the default settings of the current firmware (in case of firmware v.1.14.6 the default settings are for my SV04). After initializing EEPROM all previously saved settings have to entered/done again (hotend offsets, Z-offset, auto leveling) and saved afterwards.
/R
Björn
That’s just it. Print file / slicer settings do not seem to be the source of the problem. If the gcode ran the print as programmed the first time, but the next run (and many more times) of the same gcode results in incorrect extruder, I don’t see how the print file, slicer settings could be part of the problem. Thanks for the info on “Initialize EEPROM” - That reset checks off my curiosity there. I have power cycled the printer many times - sometimes by hours.
If I just wanted to get a good print by using the right extruder while this condition is active, I would, but the left extruder is being used to home the Z axis, doesn’t go home and is still at the x150 area, so the right extruder runs into the left one and stepper position become inaccurate.
So, today, in an attempt to gather further info for this post by running gcode from a previous Cura slicer gcode (it worked fine before), the SV04 ran as expected using the left extruder. So, I ran the Prusa slicer file (same file from above) and it now runs correctly with the left extruder. !?!
Now I don’t know what caused the problem -again- and also don’t know what corrected the problem! I assume it will happen again as this wasn’t the first time. What can I check when this happens the next time?
Be sure to know what your SV04 did before starting the problematic print (e.g fresh power-on / previous prints before, current print mode, whether all axes have been homed before).
Compare (diff) the start g-code instructions of your print files. Check out for multi nozzle mode instructions M605 and auto home instructions G28.
Additionally, you could enforce a printer power-on status by adding M0 as last instruction in your custom slicer end code. In firmware v1.14.6 this will put all variables back to power-on default values (not affecting any saved settings)…