Bondtech MINI dual drive upgrade - help with firmware - z calibration  

RE: Bondtech MINI dual drive upgrade - help with firmware - z calibration

Z calibration is not broken. It works just fine with the Bondtech 

You need to execute M500 after the M92

command to save it to the eeprom. Both commands can be executed multiple ways (Octoprint, pronterface, using bontech’s gcode file or adding it to your start gcode). The eeprom will revert back to the original ESTEPS setting after a printer reset. 

You can verify your current ESTEPS by executing an M503 command.  

RE: Bondtech MINI dual drive upgrade - help with firmware - z calibration

Here is the calibration gcode for the mini. Edit and then run this instead of using the wizard. 

https://github.com/prusa3d/Prusa-Firmware-Buddy/blob/master/doc/gcode/PLA_V2Calibration_MINI.gcode

RE: Bondtech MINI dual drive upgrade - help with firmware - z calibration

Thank you guys! I will use the Gcode yet. Hopefully in future Prusa firmware will have some settings for bondtech etc.

RE: Bondtech MINI dual drive upgrade - help with firmware - z calibration

Unlikely...they have more or less starting locking down their eeprom access in 4.0.5 which is why I have added the M92 and M500 lines to my start gcode in slicer. Every part I slice and then print will set the values automatically (don’t have to remember to set them manually after a printer restart or reset) 

RE: Bondtech MINI dual drive upgrade - help with firmware - z calibration

@unknwnrider

Do you mean the M500 makes change of M92 permanent? (even after turning printer off?)

RE: Bondtech MINI dual drive upgrade - help with firmware - z calibration

M500 saves to the eeprom until your restart or reset your machine. But, if you include those 2 lines in your start gcode, you can be certain that the ESTEPS will always be correct when you print 

RE: Bondtech MINI dual drive upgrade - help with firmware - z calibration

I have the BondTech extruder and heatbreak upgrades on my Mini and would love to be able to save esteps without adding custom gcode via a slicer.

There is a light in the tunnel 😉

"Work on hidden menu for BondTech upgrade is in progress, will be in one of next releases."

https://github.com/prusa3d/Prusa-Firmware-Buddy/issues/767

RE: Bondtech MINI dual drive upgrade - help with firmware - z calibration

Hi, where exactly do I paste in the M92 and M500 code in PrusaSlicer. Could you provide a screen shot, please?

RE:

First, M500 is useless on Mini, because Mini's firmware ignores this code.

In Prusa Slicer, you can write (save) M92 E415 into Printer Settings tab (turn Expert mode on), click Custom G-code (on left side) and you'll see Start G-code listing.
Listing already contains  some default code. Scroll down until you see:

; intro line

Now put M92 code just before that line, so you'll have:

M92 E415
M500 ; you can write that too, but is useless
; intro line

Now Save current Printer Settings (top left, next to printer selector).
From now on, every time you slice with this printer selected, M92 E415 will be automatically added to gcode file and the code will be executed just before printing starts.
It's important to know, that after printing is finished, E415 value will be remembered by printer and used as long you don't turn off the printer (or execute reset). That is, after your print is finished, you can make unload/load filament and first layer calibration correctly.
However, if you turn off the printer and back on, you cannot execute first layer calibration correctly anymore -because E415 value was erased.

In short: I recommend you update to the latest firmware. In that case you don't need to fiddle with E-step code at all. You can simply set it on printer display and forget about it (because in this case, printer will remember E415 even after turning printer off).

RE: Bondtech MINI dual drive upgrade - help with firmware - z calibration

Hi

i was hoping you could help me with my bondtech extruder it is making a horrible clicking noise and grinding noise when i try and load filament this only started happening after i did the new 4.3.4 firmware update on my prusa mini.