Global Chrome S error

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).

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).