Topics created by wesc

@dc42 Ok thanks - Yes my printer has separate Z adjustments for each print head - have raised enhancement request.

Referenced Multiple Motion System Mesh Adjustment and Z hopping in the same request - but could separate them out if that would be better.
https://github.com/Duet3D/RepRapFirmware/issues/1106

ukdavewood created this issue in Duet3D/RepRapFirmware open [FeatureRequest]: Multiple Motion System - Micro Z Adjustment and Z Hopping #1106

@generisi said in Independent input shapers per axis:

@dc42 Would the "offline" calculation solution work on both axes on Duet2 boards, or are the RAM limitations still an issue?

If we can use a single shaper to handle two frequencies, that is likely to be usable on Duet 2.

I authorise a warranty replacement for your tool board.

I'm glad you solved it. You should be able to set the visible axes to 4 except during configuration and homing. You may even be able to leave them as 4 during homing, now that you have a valid inverse matrix.

What OnHomingSwitchTriggered does is:

Work out where each motor is, based on how much of the move was executed before it was stopped by a homing switch, and set the axes to those positions. Overwrite the coordinate whoe homing switch was triggered by the homing switch position that was specified in M208.

@wesc Yes I think that would do it because if you had an extrusion say from A to B to C and it missed out B it would do an A C line with and E value appropriate to B C. If kiss is breaking straight lines into short segments then missing some of those out would lead to under extrusion.

So I don't think we blame this on OctoPrint being slow because of OK replies.

That's not what I am requesting. I would like the to have the single value that is returned when doing a bed probe for delta calibrations easily visible without having to do multiple clicks to find it.

So, for example
3:38:36 PMG32
Calibrated 6 factors using 13 points, deviation before 0.303 after 0.019

would display 0.019 somewhere near the calibrate button.

If that number is > 0.40 I recalibrate until it is < 0.40. Sometimes it takes a few times to do so.

It's also annoying that the result isn't displayed both on DWC and on the PanelDue console. It only displays on the one originating the G32.