#relative_reference_index deprecated

10 messages · Page 1 of 1 (latest)

tropic geode
#

Do we need to change our configs before we update to the new klipper version? it sounds to me like if I don't change something in bed meshing I will get errors and not be able to print. Kliper update - 20230619: The relative_reference_index option has been deprecated and superceded by the zero_reference_position option. Refer to the Bed Mesh Documentation for details on how to update the configuration. With this deprecation the RELATIVE_REFERENCE_INDEX is no longer available as a parameter for the BED_MESH_CALIBRATE gcode command.

jovial slate
tropic geode
#

thank you for letting me know 🙂 👍 now its time to update my printer then

chilly turret
#

i see relative_reference_index in the macros.cfg file. is that why my ratos install keeps alerting to its presence?

jovial slate
#

ah you mean
BED_MESH_CALIBRATE PROFILE={default_profile} algorithm={algorithm} mesh_min={mesh_x0},{mesh_y0} mesh_max={mesh_x1},{mesh_y1} probe_count={mesh_count_x},{mesh_count_y} relative_reference_index=-1
?

#

That doesn't do anything

#

Klipper is warning that the config option will throw errors. We don't use it (that's why the parameter is -1).

#

Everyone will get that warning, kevin don't know your personal config when he writes those on github.

#

Just dismiss it and move on 🙂