M32 command acting strangely

handyandy

Hi,
I have recently finished the build on my new cartesian printer, similar to a Prusa i3.
I am now working through the commissioning / calibration of it. All has been going well until I start to tune 1st layer calibration.
I have a .gcode program that will print a meander so I can adjust the Z height using BabySteps to get a good adhesion on the bed.
I have been calling this program from a general macro in the DWC via with...

M32 "0:/macros/03_Maintenance/01_First Layer Calibration/gcodes/Test.gcode"

However for some reason the M32 makes my printer do some sort of calibration that probes the bed on the left hand side, then on the right, and finally in the centre. It does this 3 times, then continues.
As it does this calibration it throws up a red error box...

X Error: This kinematics does not support auto-calibration.
Followed by a blue confirmation box...
Gantry deviation of 0,000mm obtained.

When the printing has finished you can review events in the console and it shows the program being called correctly. Then 3 error boxes as above, then the blue Gantry message, and finally that the program has successfully completed.

I have tried not using M32 but M23/M24 instead with the same results.
I have also tried just typing the M32 instruction in the Send box, again with the same results so it is definitely something odd with M32 and M23/M24!

chrishamm

@handyandy M32+M23/M24 are used to control print/CNC jobs, they're not meant to be used for macro files. I suggest you use M98 for macros instead. Perhaps you have a start.g in your sys files? If yes, that would explain why something happens before the file content is processed.

Can you share the content of your Test.gcode if the problem persists even though you call it via M98 P"0:/macros/03_Maintenance/01_First Layer Calibration/gcodes/Test.gcode"?

handyandy

@chrishamm , Thanks that (of course) cured things. I'm not sure why I used M32 in this case! I have used M98 several times before!