This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
concept [2011/06/21 00:54] iggy |
concept [2011/08/02 01:00] (current) mh [Motivation] |
||
---|---|---|---|
Line 2: | Line 2: | ||
r0ket is an electronic name tag and much more. | r0ket is an electronic name tag and much more. | ||
- | * Show others your nick on Camp 2011 and future events. | + | * Proudly display your nick on [[https://events.ccc.de/camp/2011/wiki/Main_Page|Camp 2011]] and future events |
- | + | * Have fun with the camp-applications or alternate firmwares | |
- | * Have fun with the camp-applications or alternate firmwares. | + | * Use it as foundation for your own microelectronics project |
- | + | * 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 | |
- | * Use it as foundation for your own microelectronics project. | + | |
- | + | ||
- | * Provide an interesting (and possibly expensive) component 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 | * Rapidly develop for and with diverse hardware by combining extensions designed by the community | ||
- | |||
====Motivation==== | ====Motivation==== | ||
- | After collecting lots of badges form different events (defcon, hope, troopers 11, eh2010, ...), each with it's own great features and applications, the following went through our heads: | + | After collecting lots of badges from different events (defcon, hope, troopers 11, eh2010, ...), each with it's own great features and applications, the following went through our heads: |
- | + | ||
- | * it's a pity that you usually can't use them again for a different event. (there still seem to be enough with boring tree-based ones). | + | |
- | + | ||
- | * development after the event is rare and little acknowledged | + | |
- | + | ||
- | * 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 | + | |
+ | * It's a pity that you usually can't use them again for a different event | ||
+ | * Development after the event is rare and little acknowledged | ||
+ | * 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==== | ====Features==== | ||
- | r0ket aims to be a really useful event badge in itself while also providing a solid foundation for future extensions. | + | 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, no-programmer-needed USB-bootloader. | + | |
- | + | ||
- | * high capacity lithium-polymer accumulator with charger | + | |
- | + | ||
- | * 2.4 GHz radio interface (and maybe optical communication, be surprised) | + | |
- | * sockets for extensions (m0duls and hackerbus) | + | * Based on ARM Cortex M3 32-Bit microcontroller |
+ | * Unbrickable, no-programmer-needed USB-bootloader | ||
+ | * High capacity lithium-polymer battery, rechargeable via USB | ||
+ | * 2.4 GHz radio interface (and maybe optical communication, be surprised) | ||
+ | * Sockets for extensions ([[m0dul|m0duls]] and hackerbus) | ||