You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was wondering, if we have this modular infrastructure, perhaps it would be good if the controller could auto-detect connected modules.
I suppose a simple ID chip could be hooked to any of the gpio pins via 1wire. (Causing issues if that gpio is used different on any of the connected modules )
Or a chip could respond on a known address on i2c, I guess.
Just throwing that out there for ideas. I'm not even close to needing this with my project. But I had the idea...
The text was updated successfully, but these errors were encountered:
Hi @tbaumann - I hadn't noticed this issue until now. Apologize for the delayed response!
I really do like this idea. I had actually considered doing something like this. The Myriad system by the splitkb team actually had implemented exactly what you described with a known address on i2c, and a collection of documented assigned identifiers.
I am tracking a list of potential items for a future VIK 2.0, and I will keep this issue open as a consideration. Thank you for taking the time to make this suggestion. Really good one.
I was wondering, if we have this modular infrastructure, perhaps it would be good if the controller could auto-detect connected modules.
I suppose a simple ID chip could be hooked to any of the gpio pins via 1wire. (Causing issues if that gpio is used different on any of the connected modules )
Or a chip could respond on a known address on i2c, I guess.
Just throwing that out there for ideas. I'm not even close to needing this with my project. But I had the idea...
The text was updated successfully, but these errors were encountered: