@@ -360,7 +360,7 @@ can be reduced. A virtual encoder with lower resolution can be useful in some
360
360
applications.
361
361
362
362
The driver allows limits to be assigned to the virtual encoder's value so that
363
- a dial running from (say) 0 to 100 may be implemented. If limits arenused ,
363
+ a dial running from (say) 0 to 100 may be implemented. If limits are used ,
364
364
encoder values no longer represent absolute angles, as the user might continue
365
365
to rotate the dial when it is "stuck" at an endstop.
366
366
@@ -388,7 +388,7 @@ Constructor arguments:
388
388
receives two args, ` v ` being the encoder's current value and ` delta ` being
389
389
the signed difference between the current value and the previous one. Further
390
390
args may be appended by the following.
391
- 8 . ` args=() ` An optional tuple of args for the callback.
391
+ 8 . ` args=() ` An optional tuple of positionl args for the callback.
392
392
393
393
Synchronous method:
394
394
* ` value ` No args. Returns an integer being the ` Encoder ` current value.
@@ -397,20 +397,21 @@ Class variable:
397
397
* ` delay=100 ` After motion is detected the driver waits for ` delay ` ms before
398
398
reading the current position. This was found useful with the Adafruit encoder
399
399
which has mechanical detents, which span multiple increments or decrements. A
400
- delay gives time for motion to stop, enabling just one call to the callback.
400
+ delay gives time for motion to stop enabling just one call to the callback.
401
401
402
402
#### Note
403
403
404
404
The driver works by maintaining an internal value ` ._v ` which uses hardware
405
405
interrupts to track the absolute position of the physical encoder. In theory
406
- this should be precise, but on ESP32 with the Adafruit encoder it is not.
406
+ this should be precise, but on ESP32 with the Adafruit encoder it is not:
407
+ returning the dial to a given detent shows a small "drift" in position.
407
408
408
409
Currently under investigation: it may be a consequence of ESP32's use of soft
409
410
IRQ's.
410
411
411
412
This is probably of little practical consequence as encoder knobs are usually
412
413
used in systems where there is user feedback. In a practical application
413
- ([ ugui ] ( https://github.com/peterhinch/micropython-micro-gui ) ) I can see no
414
+ ([ micro-gui ] ( https://github.com/peterhinch/micropython-micro-gui ) ) I can see no
414
415
evidence of the missed pulses.
415
416
416
417
###### [ Contents] ( ./DRIVERS.md#1-contents )
0 commit comments