This is an old revision of the document!
The r0ket can easily be extended by pluggable m0dules.
See m0dules for existing m0dules.
Please keep in mind that power is a very limited resource on the r0ket. The more a m0dule consumes the less fun you have!
A m0dule can be connected to the r0ket via the m0dulebus. The connectors are in 2.54mm/100mil spacing, prepopulated with female sockets. If available, a stackthrough connector should be used to interface with the m0dulebus. The hackerbus is intended for tinkering, a m0dule should use the m0dulebus only.
Please be aware that above the m0dulebus connectors the LCD and button is located - this area should not be covered by your m0dule. Go for the sides and below the connectors :)
As the m0dulebus connectors are not reverse polarity protected, you should document (eg marking your connector with a 1) how your m0dule should be plugged onto the r0ket.
The m0dul A and m0dul B connectors are rotated 180 degrees to each other. If your m0dule is symmetric and has no orientation requirements, it can be plugged both ways. Keep in mind though that the chip select pins on A and B differ (that should be configurable via defines in your software).
|m0dul A||m0dul B|
Almost any m0dules can be combined, if you offer the possibility to change the adress (e.g. with solder bridges). Have a look at already existing m0dules to find out which standard adresses are still free/little uses, enter your own standard adress!
Connector: 2×06 female socket (2.54mm/100mil)
|VCC||Battery voltage (4.5-3.5V)|
|SCL, SDA||I2C bus|
|MISO, MOSI, SCK||SPI bus|
|SSx||Chip select for SPI or general purpose IO|
|BUSINT||Active LOW open-drain interrupt|