Open konsumer opened 6 months ago
It's most likely the firmware. Support for setting encoder position was only recently added: https://github.com/adafruit/Adafruit_seesawPeripheral/pull/21
There's info on updating the firmware here: https://learn.adafruit.com/adafruit-attiny817-seesaw/advanced-reprogramming-with-updi
Hi, I am working on a C pi lib for this quad-encoder seesaw thing, and have been trying to reverse-engineer from working python-code, but I noticed an error with setting a rotary-value:
Results in this, as I would expect:
bytes seem to be reversed int32's, for example
0x2c, 0x1, 0, 0
is300
.When I read the same rotary, I get all 0's though, so I don't think it worked:
Thinking it might be swapped, I tried this too, but still got 0:
I also tried waiting for a bit, and looping, and it stays 0, so I don't think it's a timing issue (reading too fast after setting.)
Could it be bunk firmware, or is it a lib issue?
Also, I'd like to say great & useful contributions ya'll are making to circuitpython/blinka. It's very helpful to essentially be able to use the same easy-to-use python libs on any device I might work with, and I would definitely be using that, if I didn't require C (working on native puredata extensions, for use on pi, for a few devices.)
DebugI2C
has been incredibly helpful, since I can generally find working python code, and see the bytes, then just translate that into C. I really appreciate this. Keep up the good work!