Global Chrome S error

ours started to make a noise from the gear and belt. " squeaking sound or rubber noise" i took the cover off and found that the gear or belt wheel doesnt run true to the other one.. causing wear on the out side of the belt... maybe its a design issue hexagon knows about maybe not? but if it is slipping or jumping that might cause issues with the servo motor tach and cmm talking to each other properly.

We've had our Global S Chrome in production use since March of 2019 with zero drivetrain repairs needed yet.

However, its' accel parameter has been prudently hard-set at 5x slower (from 2500 to just 500), as this system is NOT compatible with the factory-equipped fabreeka vibration isolation. The only way hexagon was able to pass the mfr specs was to either shut the fabreeka down, or to reduce the accel parameter. What was happening was the drivetrains have springs and the scale's encoders couldn't "stabilize" for over 8 seconds as the fabreeka & springs would both oscillate. With zero dampening involved, they would perpetually oscillate each other, and Hexagon's calibration & mapping protocol would time out.

I'm guessing the reduced accel parameter is going to benefit drivetrain & maintenance frequencies. When it was getting tuned and tested those springs were actually popping out of their respective seats (X axis in particular would do it the most).

Yes, a pulley wheel that wasn't perfectly aligned square to the belt would result in the belt running on the shoulders of the pulley, forcing the motor to overcurrent. You could also see excess lag, overspeed, and overcurrent errors as a result. Sounds like you should get a service rep in to square-up the pulley.

did it since day 1. wanna know what they did to correct it? replace the belt and still does the same thing... its the pulley thats faulty, cant replace that because it cost too much...