I was given a mini 1 by a friend and successfully did a couple of prints.
On connecting via usb to CuraLE I was notified of a firmware update as it had previously been connected via octoprint not direct
After firmware update and setting my probe z offset to its previous settings it fails auto level every time?
Might it have updated to the incorrect firmware version via Cura.
Not sure what firmware to download to try and flash manually.
Not you, searching the forum you would find plenty of others who have had this problem.
Downgrade your firmware and ignore the new firmware messages.
Old firmware can be found at Index of /Mini/1.04/software/firmware
It’s no longer supported, but I am disappointed that they broke the old printer with a firmware update.
Thanks for the reply I will give that a go.
Should I not be using CuraLE 4.13.17?
I think the Cura version is fine, you just have to ignore the firmware warning. The actual leveling process is a firmware operation that is called, not a direct series of GCODE that the slicer creates.
I don’t have a Mini1 to test with (otherwise, I’d probably have a working updated firmware).
If it does have issues, run the old firmware and cura 3.x version
I’m pretty sure this is a bug with Marlin in general when you have four point linear bed leveling as the Drunken Octopus firmware has the same issue. The mini Rambo boards aren’t very powerful anyway and the later firmwares really don’t bring anything notable except bloat.
Taz 6 uses the same four-point leveling and isn’t having issues with the newer firmwares.
I think it’s something with the nozzle position with the legacy printers and toolheads. They shifted to the default nozzle position to correlate to the Titan Aero-series of toolheads, but on the unsupported printers they haven’t bothered to verify backward compatibility. The code compiles, so they just let it be.
I hadn’t considered it being a problem with the mini rambo boards though, but the four-point worked with them (as good as dirty nozzle probing can work) on original firmware, so I don’t think it’s a hardware limitation.
