The publishes pulses per rotation for this odometer encoder is 2000, but the actual count is something like 750 or thereabouts. I would imagine if their was a quadrature reduction then the count would be 500. Could someone please explain this? It's impossible to get accurate odometry without having confidence in the odometer pulses per revolution...
With all respect to gobilda (love the company!) I think there is a couple issues with it - it is a bit overpriced, one can build rev encoder based pods for ($48+$10+$5+$6) = $69 in a small batch (3-6). Second - I think it undermines the spirit of FTC a bit, kids have to invest some time and effort into the hardware, otherwise it will eventually make it a competition of gobilda copycats.
rev encoders are still better, due to the ticks per rotation (rev is something around 8000, go builda is only 2000) but this enables new teams to use odo
