The micropython state decoder looks like a solid design for "x4" quadrature decoding that avoids some problems that more naive implementations have. Crucially,

the data checked by the decoder is exactly the seen edges, not a sample of the inputs at a later time
every state transition is handled, rather than just handling certain transitions

Tracking the previous direction (positive or negative) in an attempt to decode changes in both bits simultaneously I think is of dubious value but it doesn't seem to hurt (doesn't affect the behavior when only one bit transition at a time is ever seen) and could make some designs that run just at the margin of the maximum work better, as long as there's enough "physicality" to the quadrature inputs that they don't instantly reverse from "+ludicrous_speed" to "-ludicrous_speed" instantly.

rp2040: implement rotaryio #4226

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions