concept
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
concept [2011/06/20 15:28] – [r0ket] lilafisch | concept [2011/06/21 03:39] – iggy | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ==== r0ket ==== | + | ====r0ket==== |
- | r0ket offers the possibility to make cool m0dules, without having the costs for standard parts (controller, | + | r0ket is an electronic name tag and much more. |
- | For small project you have a nice development board that can be extended with already existing m0dules. | + | |
- | And you can combine all the m0dules you want, keep using old ones and show those you developed yourself. | + | |
- | The battery has a higher capacity than the usual for badges, r0ket will last even if you play with it a lot! | + | |
- | r0ket is compatible with the AMD projects, with display and buttons interesting new functions can develop. | + | |
- | ==== history ==== | + | |
- | After seeing lot's of badges for different events (next hope, defcon, troopers 11, eh10, ...), each with its own great functions, the following went through our heads: | + | |
- | * It's a pity you can't really wear them again | + | * Proudly display your nick on [[https:// |
- | * development after the conferences is little/ | + | * Have fun with the camp-applications or alternate firmwares |
- | * each time you get a hand full of use-once batteries | + | * Use it as foundation for your own microelectronics project |
- | * most of the budget goes to standard parts | + | * Provide an interesting component as a [[m0dul]] for your event or workshop and rely on r0ket for the basics like display, CPU, power supply and RF |
+ | * Rapidly develop for and with diverse hardware by combining extensions designed by the community | ||
- | it would be great to have a badge that offers some standard components: | + | ====Motivation==== |
- | * rechargeable battery | + | After collecting lots of badges form different events (defcon, hope, troopers 11, eh2010, ...), each with it's own great features and applications, |
- | * display | + | |
- | * communication (RF, maybe LEDs) | + | * It' |
- | * no additional components for programming | + | * Development after the event is rare and little acknowledged |
- | * connectors | + | * Usually you end up with heaps of empty batteries |
+ | * Most of the budget goes to standard parts, reinventing the same basic functionality again and again | ||
+ | |||
+ | ====Features==== | ||
+ | r0ket aims to be a really useful event badge in itself while also providing a solid foundation for future extensions | ||
+ | |||
+ | * Based on ARM Cortex M3 32-Bit microcontroller | ||
+ | * Unbrickable, | ||
+ | * High capacity lithium-polymer battery, rechargeable via USB | ||
+ | * 2.4 GHz radio interface | ||
+ | * Sockets | ||
- | r0ket is what came out. |
concept.txt · Last modified: 2011/08/02 01:00 by mh