http://r0ket.badge.events.ccc.de/ 2013-06-19T00:30:21+02:00 http://r0ket.badge.events.ccc.de/ http://r0ket.badge.events.ccc.de/lib/tpl/vector/images/favicon.ico text/html 2013-02-19T14:25:48+02:00 trapicki http://r0ket.badge.events.ccc.de/build?rev=1361280348&do=diff ... 0. Work in Progress After all it's r0ket science. If you actually start developing something for the r0ket now, we'd recommend to join our Mailing List and IRC channel - see contact. This article explains the setup on a Linux machine. Instructions for Mac OS X are available here. text/html 2013-02-10T23:51:44+02:00 trapicki http://r0ket.badge.events.ccc.de/hardware?rev=1360536704&do=diff Hardware Intro We want to encourage you to tinker with your r0ket. Write your own software or build a pluggable hardware m0dul. Surprise with your creative ideas! Several people contacted us about producing r0kets for other occasions. All necessary information is on github and we're happy to help. But you should plan ahead at least 2 months! text/html 2013-01-19T00:57:03+02:00 ratte http://r0ket.badge.events.ccc.de/building_with_a_free_toolchain?rev=1358553423&do=diff curl -s https://github.com/matthiasr/summon-arm-toolchain/raw/master/summon-arm-toolchain | /bin/sh git clone git://github.com/matthiasr/r0ket.git r0ket cd r0ket/firmware cp SECRETS SECRETS.release PATH=$HOME/arm/bin:$PATH ./release-all Another working example: text/html 2012-12-28T18:53:18+02:00 hybris http://r0ket.badge.events.ccc.de/l0dables?rev=1356717198&do=diff l0dables Intro this page is intended to list l0dables that are already implemented, their features and source. How to write your own l0dables is documented in l0dable L0dables are small (<2.5k) loadable modules for the r0ket firmware. In the default released firmware these need to be encrypted signed to be run (only true for original camp firmware) text/html 2012-11-21T00:45:39+02:00 fubbi http://r0ket.badge.events.ccc.de/m0duls?rev=1353455139&do=diff m0duls This page is intended to list available hardware components for the r0ket. Hardware/interface description at m0dul As m0duls use I2C and/or SPI to communicate with the r0ket, its possible that multiple m0duls use the same addresses. Here is a list of used addresses to verify compatibility. text/html 2012-10-08T13:56:09+02:00 foolsdelight http://r0ket.badge.events.ccc.de/tracking?rev=1349697369&do=diff We are tracking r0kets. General Idea is the Openbeacon project. We are using the “new JSON API”, see <http://www.openbeacon.org/API>. Json changes We added some new fields to the JSON * added tag->nick: nickname as sent by r0ket * added reader->name: string that describes reader location text/html 2012-09-04T18:11:11+02:00 sec http://r0ket.badge.events.ccc.de/tracking:reader?rev=1346775071&do=diff openbeacon readers dump one RF channel/MAC and send them via UDP packets to a central server. Original Original OpenBeacon Readers are nice little black boxes created by milosch with two nRF24L01 and two antenna. (i.e. two receivers in nearly the same position). Problem is: they are expensive, and we currently don't have any. text/html 2012-09-02T11:42:26+02:00 sec http://r0ket.badge.events.ccc.de/tracking:29c3?rev=1346578946&do=diff 29 will be at a new venue, so this would be a lot of work. It looks like it's not happening. We (Munich) don't have the manpower/time for it. (Busy with different projects) Milosch also doesn't want to do it (he will probably attend <http://ehsm.eu> instead) text/html 2012-09-02T11:34:58+02:00 sec http://r0ket.badge.events.ccc.de/tracking:aufbau?rev=1346578498&do=diff Computer * Software is at <http://git.42.org/openbeacon.git/> * the interesting part is: openbeacon/host/services/openbeacon-tracker * Job: Collect raw data from trackers, and calculate positions from that * add readers here: * src/bmReaderPositions.h {readerid, roomnumber, group(?), x-coord, y-coord, comment}, text/html 2012-09-02T11:24:31+02:00 sec http://r0ket.badge.events.ccc.de/tracking:sigint12?rev=1346577871&do=diff Overview The SIGINT 2012 was our first attempt to use tp-link routers to talk to reader-r0kets. Notable stuff We expected to have ethernet connectors for all the readers, turns out sigint 2012 only had wireless everywhere. The tp-link routers do have a wifi chipset, so we attempted to use that instead.