This week, I worked more on the encoder software simulator. This module has to tie in pretty closely with both the settings and display modules, so I’m trying to find a setup that is extensible enough to work in a variety of circumstances, yet well-tuned enough to work with these modules without much fuss. My current plan is as follows:<\/p>\n
We split the encoders into two modules. The first module takes in the raw data of the encoder, synchronizes it, and outputs pulses for increments and decrements to the encoder’s rotation, as well as a pulse for the button’s state. Then, another module takes in that data, and, using an enable bit, will have those increment and decrement pulses modify a value. That way, I can abstract away from the actual logistics of the specific encoder we’re using relatively quickly.<\/p>\n","protected":false},"excerpt":{"rendered":"
This week, I worked more on the encoder software simulator. This module has to tie in pretty closely with both the settings and display modules, so I’m trying to find a setup that is extensible enough to work in a variety of circumstances, yet well-tuned enough to work with these modules without much fuss. My current plan is as follows: We split the encoders into two modules. The first module takes in the raw data of the encoder, synchronizes it,…<\/p>\n