RRF 3.5.0-b2 occasionally throwing weird errors

Exerqtor

RRF3.5.0-b2, Standalone, Duet 3 Mini & 1LC

I've been trying to chase down the cause of RRF throwing some intermittent errors when i run my bed tramming macro, bed meshing macro, and even some times in the middle of a print.

This last time the errors was in a phase where i can with great certancy say that the errors don't correspond with any actual errors/issues in my macros though.

If we look take a look at this console readout:

27.4.2023, 17:36:50	ABS filament loaded & config applied
27.4.2023, 17:35:51	Warning: the height map has a substantial Z offset. Suggest use Z-probe to 
                        establish Z=0 datum, then re-probe the mesh.
                        20 points probed, min error -0.091, max error -0.014, mean -0.056, deviation 0.022
                        Height map saved to file 0:/sys/heightmap.csv
                        Height map saved to file 0:/sys/adaptive_heightmap.csv
27.4.2023, 17:35:18	Z probe trigger height set to -0.697 mm
27.4.2023, 17:35:17	var.tram is: false
                        Default grid: X10.0:340.0, Y10.0:340.0, Number of points: X12 Y12, 144 points
                        Adaptive grid: X120.408:229.592, Y86.3788:226.196, Number of points: X4 Y5, 20 points
27.4.2023, 17:35:15	Error: in file macro: G10: Z probe readings not consistent
                        Error: in file macro: meta command: Z probe readings not consistent

To give some context here NONE of the macros ran to this point contain a G10, and none of the lines in either macros contain the text Z probe readings not consistent .

Having a look at the eventlog (S1 = log level) it's nothing else getting thrown out either:

2023-04-27 17:33:31 [warn] Started printing file 0:/gcodes//Shape-Box_0.2mm_ABS_0.4n_2h48m.gcode
2023-04-27 17:35:14 [warn] Error: in file macro: G10: Z probe readings not consistent
2023-04-27 17:35:15 [warn] Error: in file macro: meta command: Z probe readings not consistent
2023-04-27 17:35:49 [warn] Warning: the height map has a substantial Z offset. Suggest use Z-probe to establish Z=0 datum, then re-probe the mesh.
2023-04-27 17:35:49 [warn] 20 points probed, min error -0.091, max error -0.014, mean -0.056, deviation 0.022

Might be a good idea to run a separate S3 = log level for debuging while trying to chase this down? hmm

Phaedrux

@Exerqtor said in RRF 3.5.0-b2 occasionally throwing weird errors:

RRF3.5.0-b2

tried b3?

Exerqtor

@Phaedrux Yeah thats a total shitstorm (pardon my French). So b3 is not a viable option regretably 😓