[SOLVED] Date Encoder is not precise, please fix!

When turning the data encoder the values change in steps of 2, 3 or even more. This makes it impossible to select values like BPM exactly. I already tried this method:http://www.bourns.com/docs/technical-do ... f?sfvrsn=4 but no change.

Vincent, could you please fix this with a software update?

KlangGenerator wrote:When turning the data encoder the values change in steps of 2, 3 or even more. This makes it impossible to select values like BPM exactly. I already tried this method:http://www.bourns.com/docs/technical-do ... f?sfvrsn=4 but no change.

Vincent, could you please fix this with a software update?

Solved! For anyone building a Yocto 2 I recommend to delete the encoder that is in the BOM and add this one here:

https://www.mouser.de/ProductDetail/Bou ... HLRPgvI%3D

The difference is that the one I recommend is non-detented. This is making precise adjustments much easier!

At first, I also thought it's up to that.
But the inputs of the Atmega seem to be able to filter bouncing and noise.

KlangGenerator wrote:Date Encoder is not precise, please fix!

too precise

KlangGenerator wrote:When turning the data encoder the values change in steps of 2, 3 or even more.

When turning the data encoder slowly the values change in steps of 1. But 4 times per detent.
Exactly 4. Which indicates that the software counts every change of potential (4 per step), where it should count only one.

This software problem needs to be fixed with the next update.

Just finished a NAVA. The values change in steps of 1 per detent.