conditional gcode with DSF (3.2) error (works standalone)

garyd9

The following code in my bed.g that I copied from my working standalone configuration is giving me an error with my duet3+SBC running "3.2" on everything:

if {abs(move.calibration.final.deviation - move.calibration.initial.deviation)} < 0.005
		break;

The error message is:

Error: Failed to read code from macro bed.g: Failed to evaluate "{abs(move.calibration.final.deviation - move.calibration.initial.deviation)} < 0.005": unknown value 'abs'

As mentioned, this works perfectly with RRF 3.2 (standalone) on the same duet3 (and worked perfectly with RRF 3.1.1 (standalone.)

Bug? Oversight? Is there a new/different syntax I should be using?

Thanks
Gary

garyd9

@Phaedrux, thank you for moving this to the proper place, but I thought that DSF 3.2 was out of beta. It's coming down from apt on the normal channel...

Phaedrux

@garyd9 Just gathering potential issues for 3.3

garyd9

I think the problem is that it seems that no conditional gcode functions are implemented at all in DSF 3.2. Sadly, that isn't documented in release notes.

All of the following fail with a similar message (failed to evaluate 'function_name')

echo "debug " ^ abs(3)
echo "debug " ^ max(1,3)
echo "debug " ^ min(1,3)

Making the assumption that conditional gcode is evaluated on the SBC (and not sent to the duet3 for evaluation,) I searched in github (https://github.com/Duet3D/DuetSoftwareFramework) for the strings of the function names "atan2", "acos" and "radians" and came up with no search results. (The idea was that if the functions were implemented, there'd be at least one matching string literal in the code.