z-offsets - babystepping - macro question
-
Hi,
I have a dual extrusion delta printer, while it works I have an issue concerning Z offsets.
If I do a print and see the head is a bit high I can adjust it with babystepping.
However every time I stop the print and restart it seems babystepping it reset in the printer but not in the web interface.
Say I move the printhead 0.4mm down and it was still 0.1mm to high, if I cancel and resume the print I then need to set babystepping to -0.9mm (which is -0.5mm)
I find this a bit confusing, is this a configuration error on my end ?
With 2 nozzles I also find it very confusing because it's not because head 1 now has a new height the height of head 2 should be changed, it could, but it's not always the case.Can a macro be made [offset head 1 +0.05mm] and [offset head 1 -0.05mm]
And then the same for head 2, so I can adjust them independent from each other ? (in a way that actually moves the head up and down like babystepping)
Ideally in a way that is saved , so when I set the head 1 to -0.35mm it will remain this way for the next print, the next day.Anyone has any idea on how to do this or point me in the right direction ?
I think this would save me a lot of time.thx
Bram -
In your two head system, how are the individual heads mounted that would allow for different heights? Does each head have a servo or stepper to move the head independently of system Z ?
Babystepping is reset when the printer is homed so if you eliminate automatic homing for every print the issue should not present itself. The down side is that you have to remember to perform homing yourself (or build some sort of macro) that does the homing if the printer is un-homed. -
On the effector I have 2 hotends that can rotate, if head 1 is active head 2 sits a couple of mm above the print bed.
The difference in height between the 2 heads is minimal, 0.2mm or so, and can vary a bit every time I replace or remount the nozzle, in my experience remounting the nozzle can have a small impact on the z-height.I don't home between prints, so that shouldn't cause the issue
