The console displays shown help us determine multiple (3X) G32 convergence when called from a macro. Console display are from M665 and M666 calls within the macro.
Under DWC 1.21 the posted results are rationally presented chronologically whereas in 2.0.0-RC6 the M665 and M666 results are separately grouped. Chronological display (1.21) is sensible making associating adjustments with convergence error easy,
Or did you make the change for a reason that is not obvious to me?
Best posts made by Ethelred
-
Irrational G-Code Console Orderingposted in Duet Web Control
-
RE: Hobby servo behaviorposted in Duet Hardware and wiring
I had purchased from Amazon (addicted, I fear) and was unaware of the Pololu info at that time. Amazon almost never has any reliable tech info and sometimes publishes downright lies.
So thanks - I've ordered 180 degree replacements (metal gear MG90S).
I had tested microsecond values but had just not included them in this post. I'll fill in the blanks when the new ones arrive. -
RE: M558 ignores quantity of probe hitsposted in General Discussion
Replacement probe arrived and installed. Works perfectly and converged at 0.003mm - good enough for government work. I must have somehow bumped or otherwise disturbed the optical alignment.
AND the good news is the latest I-R probes now have surface mount emitter/detector optics which are impossible to move out of alignment. Thanks DC42 or Tony or whoever. -
RE: Max file count errorposted in General Discussion
@Ethelred
Flashed an updated PanelDue binary and all is well - gadzooks, the previous version was pre-historic.
Thanks to all for the help.