r0ket

tracking:reader - add hearbeat packet description

sec — 2012-05-06T20:12:58+02:00

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.

tracking:eh12 - [Reader positions]

sec — 2012-04-25T23:23:22+02:00

Overview The eh12 was our first attempt to use r0kets as readers. This required lots of computes: We used three Laptops and sveral dockstars to power the r0kets and collect and send the reader data. Several “active” usb extension cords were of great help here.

start - add link to m0duls and tracking

sec — 2012-04-24T12:53:34+02:00

r0ketlauncherdocumented For the consumers: * The user manual for the r0ket * A list of often used acronyms * List of l0dables init help For the producers: * The hardware powering the r0ket * The software on the r0ket * How to write your own l0dable * List of m0duls that have been done/planned * Information about r0ket tracking

tracking:aufbau - [Rechner]

sec — 2012-04-24T12:48:15+02:00

Rechner * Software liegt auf * von interesse: openbeacon/host/services/openbeacon-tracker * Aufgabe: Rohdaten von den Trackern sammeln, daraus Positionen bestimmen * Reader eintragen: * src/bmReaderPositions.h {readerid, raumnummer, gruppe(?), x-koordinate, y-koordinate, Kommentar},

tracking

sec — 2012-04-24T11:57:52+02:00

We are tracking r0kets. General Idea is the Openbeacon project. We are using the “new JSON API”, see . 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

tracking:28c3 - add reader positions

sec — 2012-04-24T11:36:11+02:00

For the 28C3 we are setting up an OpenBeacon like tracking system. It will use the new JSON API: We are trying to add two extra fields: nick and room which reflect the users nick and the current room of the r0ket/tag.

m0dul-ethernet

sec — 2012-04-24T10:55:19+02:00

Ethernet m0dul. Makes the r0ket speak IP. Currently in planning. Main reason to do this is to get the received Openbeacon data from the r0ket to a central location in a nice and easy way. Alternate Options There are of course other options to do this:

m0duls - add ethernet-m0dul

sec — 2012-04-24T10:47:10+02:00

m0duls This page is intended to list avaiable hardware components for the r0ket. 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.

init - add r15

sec — 2012-04-18T15:26:42+02:00

This procedure also brings your r0ket back into shape in case you “bricked” it or experience other strange software glitches including a damaged file system for l0dables. RevisionChange 1 Initial 2 Improved Mesh 3 Improved r_player l0dable 4 Improved fahrplan, mesh, fonts 5 Fixed mesh 6 Actually pushed the mesh changes, improved game l0dable 15 numerous small bugfixes Linux * Download the firmware pack here: * Unpack the archive with your favourite tool. * Turn r0ket off (…

acronyms

emdete — 2012-01-08T14:13:21+02:00

This page will explain some of the vocabulary of the r0ket project * r0ket is missing a 'c' by intention and using zero in fav0r 0f an ordinary 'o'. it names the whole project and the peace itself: a pcb in shape of a rocket as seen in * m0dul is a hardware enhancement of a r0ket. * l0dable is a software enhancement of a r0ket which can be loaded by the firmware * firmware is a preinstalled software that shows an idle screen, provides a menu and allows loading modules.

rem0te - [Bridge]

rene-dev — 2012-01-07T19:59:18+02:00

With the rem0te package of r0ket software you can build a game or other installation that can be interacted with, using a r0ket. The system consists of three elements: The game server, the bridge and the l0dable r_player. The game server uses the bridge to announce the game, receive button presses and (in the future) send text to the display of a player.

m0dul-flame

schneider — 2012-01-03T19:24:47+02:00

Description: Ignite your r0ket! Kits Sorry, SOLD OUT! Assembly See Author: kiu Links: https://github.com/kiu/flame Kits Sorry, SOLD OUT! Aww, that's sad. But hey, what about creating new ones? See thoughts on flames production of new RGB flames (internal)

l0dables

hubba — 2012-01-03T16:22:53+02:00

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)

r0ketlauncher - [launch0r]

rene-dev — 2012-01-03T00:31:32+02:00

getDigital left lots of USB missile launchers in our hands. So we'll give you the opportunity to play with them at 28c3! We have quite some of those, so take them apart, solder pins to the hackerbus, launch r0kets, whatever... how will that work? * receive a missile launcher after a security deposit of 20 Euros. You get those 20 EUR back, they are just a deposit! * Missiles are avaible at an additional security deposit of 2 Euros each. * you will get that back when returning the launcher…

lcd_art

ypsy — 2012-01-02T14:43:32+02:00

Here you can publish any LCD art you made.You can display *.lcd files using the “showlcd” l0dable Here's a small script to convert gifs to lcds: Display images as nick * Download the *.lcd * Rename it to “NICK.LCD”. * Replace it with the NICK.LCD on your r0ket. * Choose in the r0ket menu: nick --> chooseAnim --> IMAGE.