Firmware 2.1.3-b2. "Probing Point" - digits after the decimal point.

Hello. I have a 3d printer "TronXY 5 SA Pro". When calibrating the bed, when I turn on "Bed leveling" using firmware version 2.1.2.5, an integer and two decimal places are displayed on the "Probing Point" screen, but if I use the firmware version 2.1.3-b2, then the "Probing point" shows only an integer.
Tell me what needs to be changed in the firmware version 2.1.3-b2 so that the "Probing point" also shows two decimal places.

This Z value is the position between probes

It is simply displaying the Z_CLEARANCE_BETWEEN_PROBES default of 5

If you change it to

#define Z_CLEARANCE_BETWEEN_PROBES 5.5 // (mm) Z Clearance between probe points

It now displays 5.5

This value is not displaying an integer, its is displaying a float of 5,000000

Hello.
I may have phrased my question incorrectly.
I'll try again.
#define Z_CLEARANCE_BETWEEN_PROBES 5
This parameter sets the amount by which the bed should be lowered.
In the files "Configuration.h" versions 2.1.2.5 and 2.1.3 have the same values for these parameters. (see photo 1)
But depending on the version, the information displayed on the screen is different.
I assume that version 2.1.2.5 adds the difference between the set value and the sensor trigger height.
In photo 2, I attached only three of the sixteen control points during calibration.
These values contain digits after the decimal point and differ from each other.
By these indicators, I can judge the irregularities of my bed.
And in version 2.1.3, I only see the number 5 on all checkpoints.
Well, that's the question again.
What needs to be changed in version 2.1.3 to see the digits after the decimal point?

@TronxyED, I would also like to know why this has changed. I too used the reported value as an indication of the bed flatness. It is certainly not just a parroting of the configuration.h value of "Z_CLEARANCE_BETWEEN_PROBES", but a display of the difference between the assigned z clearance and where the z probe triggers. As such, it used to be of value, but now no longer is.

EDIT: The latest bugfix (Feb.20, 2025) is OK on my delta printer.

Edited 1 time(s). Last edit at 02/22/2025 01:40PM by rq3.