M913 behavior not correct for X & Y motors

tommyb

Config file with M906 to and M913

M913 Output

Could it be that there is any reason to believe that the M913 output is incorrect? My x& y motors are running pretty cool even though the output shows 100%.

infiniteloop

@tommyb

Could it be that there is any reason to believe that the M913 output is incorrect?

To begin with a side note: According to the GCode dictionary, usage of M913 without arguments is not documented. So, the reported results should be taken with a grain of salt.

My main concern, however, is with the way you define max. currents with M906 just to reduce them to more reasonable values (for X and Y) in the next line of your config. This only makes sense if you intend to up the currents somewhere in your macros. Depending on which macros have been called after execution of the config, the M913 report in your screenshot may even be telling the truth (although undocumented). At least, I doubt your snippets tell the whole story.

Phaedrux

Firmware version and which Duet board?

dc42

@tommyb do you have any M913 commands in your homing files?

droftarts

@tommyb According to this old post, you do use M913 in your homing files: https://forum.duet3d.com/post/270369

Ian