The r0ket can easily be extended by pluggable m0duls.

See m0duls for existing m0duls.

Please keep in mind that power is a very limited resource on the r0ket. The more a m0dul consumes the less fun you have!

A m0dul can be connected to the r0ket via the m0dulbus. The connectors are in 2.54mm/100mil spacing, prepopulated with female sockets. If available, a stackthrough connector should be used to interface with the m0dulbus. The hackerbus is intended for tinkering, a m0dul should use the m0dulbus only.

The m0dul A and m0dul B connectors are rotated 180 degrees to each other. If your m0dul is symmetric/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).

Links: Eagle

Almost any m0duls can be combined, if you offer the possibility to change the adress (e.g. with solder bridges). Have a look at already existing m0duls to find out which standard addresses are still free/little used - enter your own address!

Please be aware that above the m0dulbus connectors the LCD and button is located - this area should not be covered by your m0dul. Go for the sides and below the connectors :)

As the m0dulbus connectors are not reverse polarity protected, you should document (eg marking your connector with a 1) how your m0dul should be plugged onto the r0ket.

A dual m0dul uses both m0dul connectors on the badge. This gives you maximum mechanical stability and a balanced weight distribution. As the connector on both sides are rotated by 180 degrees you can mount the m0dul 180 degrees rotated.

A single m0dul only uses one m0dul connector. These m0duls go to the side of the badge. By rotating the m0dul you can chose to either mount it on the left or the right side of the r0ket.

Connector: 2×06 female socket (2.54mm/100mil)

• build explains how to set up your build-environment and compile and deploy code for r0ket
• You can either write your own firmware, or, if your code is smaller than 1 kB, a l0dable which can be dynamically loaded into the default firmware.