DRIVE ERROR: command refresh timeout on X axis

That is a result of the machine's drivetrain and readhead sensor not "settling".

Do you have a Fabreeeka (active airbag vibration isolation) system?

The global S series, (specifically the CHROME's) have springs at the drive belt clamps, which are intended to allow the machine to run with higher acceleration, but when coupled with vibration isolation system, the oscillating of the two literally prevents the machine from stopping to move, and as such can never lock down an X axis value within the allotted settle time (i think it's <8 seconds).  Basically, Hexagon sold you conflicting hardware (a lemon).  You'd have to shut off your fabreeka system, or reduce your accel parameter from i think 3000 to 500 on all axis.

If that isn't the case here, Hit your e-stop.  Manually move your X axis left-right, feeling for any inconsistent resistance while it's gliding on the air bearings. Also use air to blow and an IPA saturated techwipe to clean any dust off the readhead and the scale.

If you feel weird drivetrain resistance on X axis, you might need belts/pullies or motor tuned/serviced/replaced.

hmmmmm that's very interesting. After spending some more time, I found this to be the most plausible diagnosis. I found simply moving the fixture to a different section of the machine yielded better, more accurate, results. Even my scans had less hiccups. I'm commenting in the hopes that maybe someone else who has these problems might find this helpful.

hmmmmm that's very interesting. After spending some more time, I found this to be the most plausible diagnosis. I found simply moving the fixture to a different section of the machine yielded better, more accurate, results. Even my scans had less hiccups. I'm commenting in the hopes that maybe someone else who has these problems might find this helpful.