Why is the Y position or Y distance inaccurate when compared to calculating from encoder ticks?
|Firmware Version||3.x, 4.x
Encoder spacing is rounded internally in Gocators to multiples of the encoder resolution. The actual encoder spacing or Y resolution is slightly different from the encoder spacing entered in the Gocator interface. For example, using 6.35 mm encoder spacing with an encoder resolution of 0.0975 mm/tick would actually yield 6.3375 mm as the encoder spacing (6.3375 / 0.0975 = 65).
Please sign in to leave a comment.