-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Qwiic & MikroBUS connectors #2
Comments
Seems like good suggestions, thanks! |
I tend to want as few constraints as possible unless there is a specific motivation. What would be the benefit of doing so? |
The benefit for me is that I can design a robot base for the Nano ITX standoffs and use either the Beaglebone AI-64 or your board. Or use it in a printable case I guess some people might also want to stack a AI-64 or a Jetson Xavier Nano ITX on top to do vision stuff on I dunno if there's any benefit for you aside from perhaps a few more users. Same for Pi header too I suppose. |
Bumping the Qwiic and Microbus header suggestion as it looks like your working on a new iteration MikroBUS shuttle 2 x 8 header, this connects to daughter board and 1407 sensors/ peripherals Qwiic because it's small, and why not.. |
I was wondering if, on the next iteration of the board, you could squeeze in three additional connectors
UEXT - Underrated IMHO https://www.olimex.com/Products/Modules/ Olimex produce some nice open hardware bits, notably LoRa modules with UEXT
MikroBUS shuttle 2 x 8 header, this connects to daughter board and 1407 sensors/ peripherals
Qwiic because it's small, and why not..
The text was updated successfully, but these errors were encountered: