concept
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
concept [2011/06/20 14:59] lilafisch history: why we did what we did |
concept [2011/08/02 01:00] mh [Motivation] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ==== r0ket ==== | + | ====r0ket==== |
| + | r0ket is an electronic name tag and much more. | ||
| - | r0ket offers the possibility to make cool m0dules, without having the costs for standard parts (controller, display, batteries). For an event you can chose an interesting (and expensive) component and focus workshops, games and experiments on that component. | + | * Proudly display your nick on [[https://events.ccc.de/camp/2011/wiki/Main_Page|Camp 2011]] and future events |
| - | For small project you have a nice development board that can be extended with already existing m0dules. | + | * Have fun with the camp-applications or alternate firmwares |
| - | And you can combine all the m0dules you want, keep using old ones and show those you developed yourself. | + | * 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 | ||
| + | * Rapidly develop for and with diverse hardware by combining extensions designed by the community | ||
| - | ==== history ==== | + | ====Motivation==== |
| - | 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: | + | 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 you can't really wear them again | + | * It's a pity that you usually can't use them again for a different event |
| - | * development after the conferences is little/little acknowledged | + | * Development after the event is rare and little acknowledged |
| - | * each time you get a hand full of use-once batteries | + | * Usually you end up with heaps of empty batteries |
| - | * most of the budget goes to standard parts | + | * Most of the budget goes to standard parts, reinventing the same basic functionality again and again |
| - | it would be great to have a badge that offers some standard components: | + | ====Features==== |
| - | * rechargeable battery | + | r0ket aims to be a really useful event badge in itself while also providing a solid foundation for future extensions |
| - | * display | + | |
| - | * communication (RF, maybe LEDs) | + | * Based on ARM Cortex M3 32-Bit microcontroller |
| - | * no additional components for programming needed (except for standard usb connector) | + | * Unbrickable, no-programmer-needed USB-bootloader |
| - | * connectors for additional badges of different events/purposes that can be combined freely | + | * 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) | ||
| - | r0ket is what came out. | ||
concept.txt · Last modified: 2011/08/02 01:00 by mh
Page Tools
