Carbide Motion (428) sending wrong config data for x/y size? (grbl params 130, 131)

Software Carbide Motion
17

Thanks, @Luke — will give it a try!

Two questions:

  1. What order should I do these steps relative to Bitsetter setup? Should I install bitsetter and position over it, initialize with Bitsetter but without HDZ, then send the commands you showed?
  2. I’d love your two cents on why CM is sending XXL values for 130, 131 — is this a non-issue? Am I crazy for worrying?