User Tools

Site Tools


m0dul

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
m0dul [2011/06/19 15:24]
kiu [Interface]
m0dul [2011/12/30 00:10]
emdete
Line 1: Line 1:
-The r0ket can easily be extended by pluggable m0dules.+====== Intro ======
  
-See [[m0dules|m0dules]] for existing ​m0dules.+The r0ket can easily be extended by pluggable m0duls. 
 + 
 +See [[m0duls]] for existing ​m0duls.
  
 ====== Hardware ====== ====== Hardware ======
  
-Please keep in mind that __power__ is a very __limited resource__ on the r0ket. The more a m0dule ​consumes the less fun you have!+Please keep in mind that __power__ is a very __limited resource__ on the r0ket. The more a m0dul consumes the less fun you have!
  
 ===== Interface ===== ===== Interface =====
  
-m0dule ​can be either ​connected ​via the m0dulebus or the hackerbusAll connectors are in 2.54mm/​100mil spacing ​where __only__ the m0dulebus is 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.+m0dul can be connected ​to the r0ket via the m0dulbusThe connectors are in 2.54mm/​100mil spacingprepopulated with female sockets. If available__stackthrough connector__ should ​be used to interface with the m0dulbus. The hackerbus is intended for tinkering, a m0dul should ​use the __m0dulbus only__.
  
-Please ​be aware that __above__ ​the __m0dulebus__ connectors the __LCD__ and __button__ is located - this area should __not be covered__ by your m0dule. ​+<note tip>​Stackthrough connectors kits (2x 2x06) will be on sale at the campsite!</​note>​
  
-As the m0dulebus and hackerbus 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 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).
- +
-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 ^ ^ m0dul A ^ m0dul B ^
Line 22: Line 22:
 | SS2 | SS5 | | SS2 | SS5 |
  
-{{:m0dule-bus-brd.png?​direct&​200|}}+Links[[https://​github.com/​r0ket/​r0ket/​tree/​master/​hardware/​m0dul|Eagle]]
  
-Links: ​[[https://​github.com/​r0ket/​r0ket/​tree/​master/​hw/​m0dule|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|m0duls]] to find out which standard addresses are still free/little used - enter your own [[m0duls#​registry|address]]!
  
-==== M0dulebus ​====+ 
 +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. 
 + 
 +==== Dual M0duls ==== 
 +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. 
 + 
 +{{:​m0dul-dual.brd.png?​direct&​200|}} 
 + 
 +==== Single M0duls ==== 
 +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. 
 + 
 +{{:​m0dul-single.brd.png?​direct&​200|}} 
 + 
 +==== M0dulbus ​====
 Connector: 2x06 female socket (2.54mm/​100mil) Connector: 2x06 female socket (2.54mm/​100mil)
  
-{{:r0ket-bus-m0dule.png?200&direct |}}+{{:r0ket-m0dulbus.png?400&​direct| }}
  
 ^ Pin ^ Description ^ ^ Pin ^ Description ^
 | +3V3_EXP | Fixed 3.3V | | +3V3_EXP | Fixed 3.3V |
-| VCC | Battery voltage (3.7-3.3V) |+| VCC | Battery voltage (4.5-3.5V) |
 | GND | Ground |  | GND | Ground | 
 | SCL, SDA | I2C bus | | SCL, SDA | I2C bus |
Line 40: Line 55:
 | BUSINT | Active LOW open-drain interrupt ​ | | BUSINT | Active LOW open-drain interrupt ​ |
  
-==== Hackerbus ​==== +====== Further reading ======
-Connector: Optional (not prepopulated) 1x06 female socket (2.54mm/​100mil) +
- +
-{{:​r0ket-bus-hacker.png?​200&​direct |}} +
- +
-^ Pin ^ Description ^ +
-| +3V3_EXP | Fixed 3.3V | +
-| VCC | Battery voltage (3.7-3.3V) | +
-| GND | Ground |  +
-| HBx | General purpose IO |+
  
-====== Software ======+  * [[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.
  
m0dul.txt · Last modified: 2011/12/30 00:10 by emdete