Duet Maestro in MakerGear M3

guycobb2

M557 reports “grid not defined”. Wtf?

Phaedrux

@guycobb2 said in Duet Maestro in MakerGear M3:

M557 reports “grid not defined”. Wtf?

What do you get if you copy and paste your m557 from config.g into the console?

Phaedrux

@guycobb2 said in Duet Maestro in MakerGear M3:

M557 X25:215 Y16:Y248 P3

I think I see the issue... Do you notice the Y values? You've got an extra Y in there.

guycobb2

Sonofabitch.

Phaedrux

Still curious to see what the console feedback would be from that line.

guycobb2

How in the crap have I overlooked that for 24 hours?

guycobb2

@Phaedrux it said the Y value too small

guycobb2

More specifically “error m557: bad grid definition: Y range too small”

Phaedrux

Well that would have been a clue anyway.

guycobb2

Can someone give a brief explanation of the deviation and error results?

https://imgur.com/zB9In38.jpg

guycobb2

After bed mesh is complete do I need to reload the height map after a reboot of the board?

Phaedrux

the max deviation is the lowest and highest point to either side of wherever you set the Z0 point.

mean error is the average of all the deviations. So your's is slightly below the 0 point on average.

RMS I'm not actually sure.

Yes you need to reload the heightmap after a power cycle. This would typically be done in your slicer start gcode after homing. Use G29 S1

guycobb2

@Phaedrux thanks for everybody’s help. I went ahead and knocked out a quick test print and all looks good. It looks like the duet is removing the artifacts I was experiencing with the stock Rambo board. More testing to confirm, I will play with it more tonight after I get back home from work.

I forgot that I plan on running the quick 9 point mesh at the start of every print so no need to reload the height map. But good to know if I decide to remove that from my starting process. Thanks again everybody.

Phaedrux

@guycobb2 said in Duet Maestro in MakerGear M3:

I forgot that I plan on running the quick 9 point mesh at the start of every print so no need to reload the height map. But good to know if I decide to remove that from my starting process. Thanks again everybody.

If your bed is stable and doesn't really change from print to print you might benefit from doing a more detailed heightmap once, and then loading it, rather than doing a 9 point heightmap each time. Would need to compare to see what works best. It's also useful to do at least one high detail heightmap so you can see what your bed surface actually looks like.

droftarts

@guycobb2 Sorry, I missed that extra Y too!

This post has a pretty good explanation of the results: https://forum.duet3d.com/post/53350

Max deviation is the lowest and highest point.
Mean error is the average error of all points.
RMS error is Root Mean Square. This takes a bit of understanding, probably best to read the thread above. I'm not sure I understand it!

Ian

guycobb2

Quick question that I didn’t find the answer to.

A full step on my Z is 0.0158mm. So is it best to leave that number as is or better to just round up to 0.016? I didn’t know how the firmware handles decimal places. Same thing for the slicer....utilize multiples of 0.0158 or just use multiples of 0.016?

Phaedrux

@guycobb2 I'm not sure I follow. Do you mean that a full step of the motor travels 0.0158mm?

Z_steps_per_mm = (motor_steps_per_rev * driver_microstep) / screw_lead

guycobb2

Yes. Brain fart.....corrected it.

guycobb2

Any info regarding my last question?

droftarts

@guycobb2 From https://forum.duet3d.com/post/7222

The floating point calculations are done in single precision floating point, so 24 bits of precision. The integer calculations used in step generation are done mostly using 32 bits, with 64 bits where necessary.

So it will use all the decimal points you feed it. I'm guessing you're using imperial (1/4" 16 ACME rod?) for a 0.0158mm single step. Do you mean that many people report better Z consistency when they use multiples of the 'full step' distance for layer height? You can do this, though you end up with some strange layer heights; use Prusa's 'optimal layer height for your Z axis' calculator to see: https://blog.prusaprinters.org/calculator/

However, this was more of a problem in the 'old' days, when Z drivers turned off after moving, and when re-enabled moved to the closest full step. Usually now the Z driver is kept enabled, so doesn't lose position, and using multiples of full steps for layer height shouldn't be necessary.

Ian