Macro for Calibrating Z Probe - Issues

dc42

By default, M300 does not save the the trigger height to config-override.g. The only values saved to config-override.g by M500 are ones obtained by an automatic tuning process, e.g. heater turning or delta calibration. We made this change because too many users were having trouble when there was a G31 command in config-override.g. However, if you send M500 P31 then the G31 parameters will be written to config-override.g too.

brunofporto

@dc42 said in Macro for Calibrating Z Probe - Issues:

M500 P31

Thank you very much DC42.

Please, is there a way to use the reported probe height from G30 S-1 to automatically crate a G31 Z"new value" within the macro?

ps.: Have a nice vacation!

brunofporto

Also,

Please, where is the correct place to report the M291 bug with PanelDue?

It does not allow the user to adjust the head position on the specified axis from the screen.

dc42

@brunofporto said in Macro for Calibrating Z Probe - Issues:

Also,

Please, where is the correct place to report the M291 bug with PanelDue?

It does not allow the user to adjust the head position on the specified axis from the screen.

Strange, it used to work. Did you home the specified axis first, or else use M564 H0 in config.g?

brunofporto

@dc42 said in Macro for Calibrating Z Probe - Issues:

M500 P31

This command saves at the config-override.g these settings from the probe:

; Z probe parameters
G31 T1 P600 X30.0 Y0.0 Z0.59
G31 T3 P500 X0.0 Y0.0 Z0.70
G31 T4 P500 X0.0 Y0.0 Z0.00

At the Gcode description page it states that the Tnnn is for the probe type. My probe is a type 5. Is the "T1" parameter saved at the override correct?

brunofporto

@dc42 said in Macro for Calibrating Z Probe - Issues:

Did you home the specified axis first, or else use M564 H0 in config.g?

I did home before, the M291 command is right after the G92 Z15, and it works fine at the DWI.

And I do not have the M564 command at my config.g.

dc42

@brunofporto said in Macro for Calibrating Z Probe - Issues:

@dc42 said in Macro for Calibrating Z Probe - Issues:

M500 P31

This command saves at the config-override.g these settings from the probe:

; Z probe parameters
G31 T1 P600 X30.0 Y0.0 Z0.59
G31 T3 P500 X0.0 Y0.0 Z0.70
G31 T4 P500 X0.0 Y0.0 Z0.00

At the Gcode description page it states that the Tnnn is for the probe type. My probe is a type 5. Is the "T1" parameter saved at the override correct?

Yes, probe types other than 3 and 4 share the same set of parameters as type 1.

dc42

@brunofporto said in Macro for Calibrating Z Probe - Issues:

@dc42 said in Macro for Calibrating Z Probe - Issues:

Did you home the specified axis first, or else use M564 H0 in config.g?

I did home before, the M291 command is right after the G92 Z15, and it works fine at the DWI.

And I do not have the M564 command at my config.g.

I'll add this as an item to test/fix in the next release of PanelDueFirmware.

brunofporto

Thank you very much!

brunofporto

For the record this is the working Macro and instructions:

;======== Calibrate Z Probe Macro=========
;Calibrate_Zprobe.g

G28 ; Home all axis
G0 S0 X149 Y140 F6000 ; Move nozzle to the cendter of the bed
G92 Z15 ; DANGER!
M98 P/MACROS/SUBMACROS/BEEP.G
M291 P"Please move the nozzle until it touches the bed or reference." R"Setting Zero" S3 T0 Z1 ;
G92 Z0 ; Set the new Z=0
G0 S0 X119 Y140 Z5 F6000 ; Move probe to the center of the bed and z=5mm
G30 S-1 ; Report the probe height
G0 S0 X119 Y140 Z5 F6000 ; Move probe to the center of the bed and z=5mm
G30 S-1 ; Report the probe height
G0 S0 X119 Y140 Z5 F6000 ; Move probe to the center of the bed and z=5mm
G30 S-1 ; Report the probe height

After the process send G31 Znnn where nnn is the reported probe Height
Send a M500 P31 to record the settings to config_override.g
Make sure you have M501 at your config.g to load the override settings.

Phaedrux

I have also noticed this bug. I use a similar macro and in others that the axis movement buttons will only work from the place the macro was launched. So if you start the macro from the DWC the buttons will work there but not on panel due and vice versa.

Its also a little odd that the scale for movement values is different between the two.

Also perhaps this would be if interest to you.

https://www.dropbox.com/s/8okrxrgtx2d8om7/0_Auto Probe Trigger Height Assist.g?dl=1

brunofporto

@phaedrux said in Macro for Calibrating Z Probe - Issues:

Its also a little odd that the scale for movement values is different between the two.

I find that odd too.. I'll check your macro thank you!

I did not test launching the macro from the PanelDue. I'll try that

brunofporto

@phaedrux said in Macro for Calibrating Z Probe - Issues:

Also perhaps this would be if interest to you.

I am not able to use M109 anymore...

For starting gcodes I am using M116 H0 for the bed and then M116 to wait for the hotend too (tried to define the tool but P0 pr P1 did not work. As the bed was already at temp at this part then the the full m116 worked nicely to wait for the tool)

I liked the preheat for probing and also the grid compensating map - I think this is causing me issues with my current macro. I'll use your as reference! Thank you very much

Phaedrux

If you're interested I also have a macro to assist in manual bed leveling and another to run mesh compensation. Amung others.

https://www.dropbox.com/sh/j8qaxkkardoxzja/AADUDwfeBvVTpXzcr0nOpSPZa?dl=0

brunofporto

@phaedrux said in Macro for Calibrating Z Probe - Issues:

If you're interested

Sure I am

Loved your probe macro! Made my macro looks like a kids drawing in comparison

Thank you very very much.

brunofporto

@dc42 said in Macro for Calibrating Z Probe - Issues:

I'll add this as an item to test/fix in the next release of PanelDueFirmware.

DC42, only to confirm @Phaedrux mentined and add some details do the bug.

If I start the Macro from the PanelDue I can only send the movement commands from there. And vice versa. Also the results from the G30 S-1 (for example) from the macro only shows at the PanelDue console. And vice versa if I start the macro from DWC.

One detail is that @Phaedrux macro test G30 S-1 ten times. This is reported correctly when the macro is started from DWC but only six of them appear at the PanelDue console.

Thanks!