<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://r0ket.de/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="https://r0ket.de/feed.php">
        <title>r0ket</title>
        <description></description>
        <link>https://r0ket.de/</link>
        <image rdf:resource="https://r0ket.de/_media/wiki:dokuwiki.svg" />
       <dc:date>2026-04-17T04:40:36+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="https://r0ket.de/acronyms?rev=1326028401&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/backup_firmware?rev=1312975905&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/backup_usb_storage?rev=1312975555&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/build_mac?rev=1325557777&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/build?rev=1361280348&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/building_with_a_free_toolchain?rev=1358553423&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/buildtoolchain?rev=1312972798&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/cccamp11_workshop?rev=1313165682&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/colordisplay?rev=1325238236&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/concept?rev=1312239600&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/contact?rev=1313150208&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/crypto?rev=1312355746&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/exploit?rev=1313753912&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/f0nt?rev=1312975125&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/fahrplan?rev=1375067092&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/features?rev=1312983925&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/firststeps?rev=1311959844&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/flame?rev=1325090526&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/hardware-mods?rev=1313260993&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/hardware?rev=1360536704&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/help?rev=1325038304&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/img2lcd?rev=1313013888&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/init?rev=1375298890&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/l0dable?rev=1325247512&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/l0dables?rev=1356717198&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/lcd_art?rev=1325511812&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/m0dul-ethernet?rev=1339270323&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/m0dul-example?rev=1308594498&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/m0dul-flame_rgb-mod?rev=1313679364&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/m0dul-flame?rev=1325615087&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/m0dul-j0y?rev=1311213496&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/m0dul-r0ketc0m?rev=1313406931&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/m0dul-torch?rev=1312987404&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/m0dul?rev=1325200240&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/m0duls?rev=1360408361&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/manual?rev=1325194053&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/nick_animation?rev=1313005691&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/r0ket?rev=1325200625&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/r0ketlauncher_ammunition?rev=1325170069&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/r0ketlauncher?rev=1325547092&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/rem0te?rev=1325962758&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/simulat0r?rev=1324775753&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/software?rev=1338291473&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/start?rev=1514291353&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/tracking?rev=1349697369&amp;do=diff"/>
                <rdf:li rdf:resource="https://r0ket.de/tvr0tator.c?rev=1325247321&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="https://r0ket.de/_media/wiki:dokuwiki.svg">
        <title>r0ket</title>
        <link>https://r0ket.de/</link>
        <url>https://r0ket.de/_media/wiki:dokuwiki.svg</url>
    </image>
    <item rdf:about="https://r0ket.de/acronyms?rev=1326028401&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-01-08T13:13:21+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>acronyms</title>
        <link>https://r0ket.de/acronyms?rev=1326028401&amp;do=diff</link>
        <description>Intro

This page will explain some of the vocabulary of the r0ket project

	*  r0ket is missing a &#039;c&#039; by intention and using zero in fav0r 0f an ordinary &#039;o&#039;. 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.</description>
    </item>
    <item rdf:about="https://r0ket.de/backup_firmware?rev=1312975905&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-08-10T11:31:45+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>backup_firmware</title>
        <link>https://r0ket.de/backup_firmware?rev=1312975905&amp;do=diff</link>
        <description>[Backup has nothing to do with firmware i think... just usb_storage]</description>
    </item>
    <item rdf:about="https://r0ket.de/backup_usb_storage?rev=1312975555&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-08-10T11:25:55+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>backup_usb_storage</title>
        <link>https://r0ket.de/backup_usb_storage?rev=1312975555&amp;do=diff</link>
        <description>Backup usb_storage

This will help you to backup your own r0ket memory and restore it. For example if your r0kets data flash is corrupted.

Backup old usb_storage

	*  Connect your r0ket via USB.
	*  Select the usb_storage mode from the r0ket menu.
	*</description>
    </item>
    <item rdf:about="https://r0ket.de/build_mac?rev=1325557777&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-01-03T02:29:37+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>build_mac</title>
        <link>https://r0ket.de/build_mac?rev=1325557777&amp;do=diff</link>
        <description>You might want to disable .DS_Store files on (network) mounts
...OS
NEVER EVER access the r0ket with the finder.


Build environment on Mac OS X

1. Compiler

Using Mac OS X:
OS

Solution 1

	*  This explains how to build the tool chain on a Mac: Git project: jsnyder / arm-eabi-toolchain
	*</description>
    </item>
    <item rdf:about="https://r0ket.de/build?rev=1361280348&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-02-19T13:25:48+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>build</title>
        <link>https://r0ket.de/build?rev=1361280348&amp;do=diff</link>
        <description>Build environment
...
0. Work in Progress

After all it&#039;s r0ket science. If you actually start developing something for the r0ket now, we&#039;d recommend to join our Mailing List and IRC channel - see contact. 

This article explains the setup on a Linux machine. Instructions for Mac</description>
    </item>
    <item rdf:about="https://r0ket.de/building_with_a_free_toolchain?rev=1358553423&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-01-18T23:57:03+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>building_with_a_free_toolchain</title>
        <link>https://r0ket.de/building_with_a_free_toolchain?rev=1358553423&amp;do=diff</link>
        <description>OS
TL;DR


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:</description>
    </item>
    <item rdf:about="https://r0ket.de/buildtoolchain?rev=1312972798&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-08-10T10:39:58+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>buildtoolchain</title>
        <link>https://r0ket.de/buildtoolchain?rev=1312972798&amp;do=diff</link>
        <description>In this document I will describe how to build a toolchain for ARM.

setup build environment

In this document we will install the toolchain in the users home directory under $HOME/arm-elf.

Installation will take place in /tmp/toolchain.

$ mkdir -p /tmp/toolchain/src</description>
    </item>
    <item rdf:about="https://r0ket.de/cccamp11_workshop?rev=1313165682&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-08-12T16:14:42+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>cccamp11_workshop</title>
        <link>https://r0ket.de/cccamp11_workshop?rev=1313165682&amp;do=diff</link>
        <description>Design your own m0dul for r0ket @cccamp11!

You want to design your own PCB? Go every step from the idea to the finished, working m0dul?
This workshop lets you do exactly that.
In the workshop you&#039;ll learn how to use LEDs, Piezos and Buttons with the m0dul bus.
You can chose those from a selection we are bringing to camp.
You should already know how to solder.</description>
    </item>
    <item rdf:about="https://r0ket.de/colordisplay?rev=1325238236&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-12-30T09:43:56+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>colordisplay</title>
        <link>https://r0ket.de/colordisplay?rev=1325238236&amp;do=diff</link>
        <description>This is a page to collect everything on getting color display (nokia 1600 for now) to work on r0ket.
28C3 firmware


Finally there&#039;s a l0dable to show a color BMP or animation instead of nickname by nihilant: &lt;http://y.nu/nick_colorbmp.zip&gt;  (includes source and compiled binary).

It only works for color displays
and only supports 24- and 32-bits BMP files with resolution 98x(n*70).</description>
    </item>
    <item rdf:about="https://r0ket.de/concept?rev=1312239600&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-08-01T23:00:00+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>concept</title>
        <link>https://r0ket.de/concept?rev=1312239600&amp;do=diff</link>
        <description>r0ket

r0ket is an electronic name tag and much more. 

	*  Proudly display your nick on  Camp 2011 and future events
	*  Have fun with the camp-applications or alternate firmwares
	*  Use it as foundation for your own microelectronics project 
	*  Provide an interesting component as a</description>
    </item>
    <item rdf:about="https://r0ket.de/contact?rev=1313150208&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-08-12T11:56:48+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>contact</title>
        <link>https://r0ket.de/contact?rev=1313150208&amp;do=diff</link>
        <description>Contact

	*  Mail: team@r0ket.badge.events.ccc.de
	*  Twitter @r0ketbadge
	*  Soup: r0ket.soup.io

Discuss

	*  Mailinglist: discuss@r0ket.badge.events.ccc.de Subscribe
	*  Our IRC Channel on Blafasel. The default server seems to limit the amount of Camp IPs joining, so here some more of the same Network:
		*  IRC irc://space.blafasel.de/#r0ket
		*  IRC irc://ray.blafasel.de/#r0ket
		*  IRC irc://irc.blafasel.de/#r0ket</description>
    </item>
    <item rdf:about="https://r0ket.de/crypto?rev=1312355746&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-08-03T07:15:46+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>crypto</title>
        <link>https://r0ket.de/crypto?rev=1312355746&amp;do=diff</link>
        <description>OpenBeacon

OpenBeacon packets are encrypted using a private symmetric key using the XXTEA algorithm.

As the key is the same for every participant of the camp it must kept secret inside the firmware. This creates the need to protect
the flash memory of the main micro controller from being read by an attacker. It will therefore be read protected.</description>
    </item>
    <item rdf:about="https://r0ket.de/exploit?rev=1313753912&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-08-19T11:38:32+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>exploit</title>
        <link>https://r0ket.de/exploit?rev=1313753912&amp;do=diff</link>
        <description>This page describes several ways of 0wning your r0ket (i.e. retrieving the original “vendor” keys for encrypting&amp;signing new l0dables and for encrypting&amp;signing messages on the wireless mesh).

0wning the r0ket

The r0ket uses a mesh-network to convei time, highscore and other messages.
To protect these values from evil hackers, the mesh encrypts and signs messages sent to the mesh using a secret key, stored read-protected on the flash of the processor.</description>
    </item>
    <item rdf:about="https://r0ket.de/f0nt?rev=1312975125&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-08-10T11:18:45+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>f0nt</title>
        <link>https://r0ket.de/f0nt?rev=1312975125&amp;do=diff</link>
        <description>A f0nt is a binary compressed bitmap font.

f0n files can be created with makefont.pl - which requires perl and the GD module.

To convert a ttf font file, call it as “makefont.pl -b -f file.ttf -s 18” which should create (amongst others) a .F0N file.</description>
    </item>
    <item rdf:about="https://r0ket.de/fahrplan?rev=1375067092&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-07-29T03:04:52+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>fahrplan</title>
        <link>https://r0ket.de/fahrplan?rev=1375067092&amp;do=diff</link>
        <description>Fahrplan is the Hacker-Event-Schedule f0r r0ket.

The latest version is the OHM Schedule v1.0 in a BETA state.

Get it at: &lt;http://y.nu/r0ket-ohm.zip&gt;

The Archive contains 4 files, a README, the l0dable fahrplan.c0d and two editions of the schedule: fahrplan.scd is the 300K default, containing (length limited) all texts, fp-mini.scd is only 8K for those needing their dataflash for other stuff, but contains only the titles. Warning: some (all? older?) r0ket firmwares have problems with copying b…</description>
    </item>
    <item rdf:about="https://r0ket.de/features?rev=1312983925&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-08-10T13:45:25+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>features</title>
        <link>https://r0ket.de/features?rev=1312983925&amp;do=diff</link>
        <description>Basic functionality

	*  Display your name :) TBD
	*  Access the on-board storage via USB
	*  You can choose to add your information to the collection of Attendee Meta Data
	*  The red LED in the upper right starts blinking when you need a charger TBD</description>
    </item>
    <item rdf:about="https://r0ket.de/firststeps?rev=1311959844&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-07-29T17:17:24+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>firststeps</title>
        <link>https://r0ket.de/firststeps?rev=1311959844&amp;do=diff</link>
        <description>Assembly

LCD

	*  LCD on front
	*  Apply tape
	*  Connect
	*  Apply LCD

Battery

	*  Battery on back
	*  Apply tape
	*  Connect
	*  Apply battery

Charging

	*  The r0ket can be charged via micro USB (use a USB 2.0 cable or adapter, micro USB 3.0 has a different connector) by any USB powered device</description>
    </item>
    <item rdf:about="https://r0ket.de/flame?rev=1325090526&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-12-28T16:42:06+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>flame</title>
        <link>https://r0ket.de/flame?rev=1325090526&amp;do=diff</link>
        <description>See this page instead: &lt;https://r0ket.badge.events.ccc.de/m0dul-flame&gt;</description>
    </item>
    <item rdf:about="https://r0ket.de/hardware-mods?rev=1313260993&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-08-13T18:43:13+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>hardware-mods</title>
        <link>https://r0ket.de/hardware-mods?rev=1313260993&amp;do=diff</link>
        <description>Button

	*  from BiC crystal pens 
	*  first reprap nipple
	*  Parametric r0ket nipple
	*  Parametric r0ket nipple + lip

Case

	*  reprap casing
	*  full knitted cover
	*  another knitted

Hackberbus

for hardware on the m0dulbus see m0dul

	*  &lt;http://events.ccc.de/camp/2011/wiki/Laser_Tag&gt;
	*  &lt;http://wiki.hx2.org/Geiger_Workshop_r0ket&gt;</description>
    </item>
    <item rdf:about="https://r0ket.de/hardware?rev=1360536704&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-02-10T22:51:44+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>hardware</title>
        <link>https://r0ket.de/hardware?rev=1360536704&amp;do=diff</link>
        <description>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&#039;re happy to help. But you should plan ahead at least 2 months!</description>
    </item>
    <item rdf:about="https://r0ket.de/help?rev=1325038304&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-12-28T02:11:44+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>help</title>
        <link>https://r0ket.de/help?rev=1325038304&amp;do=diff</link>
        <description>If your r0ket isn&#039;t working try the following steps in this order:

	*  check here if we already know about the problem and maybe even have a solution
	*  if nothing helps, join the r0ket irc channel irc://space.blafasel.de/#r0ket (if it is full see contact for other servers) - but our ressources there are limited.</description>
    </item>
    <item rdf:about="https://r0ket.de/img2lcd?rev=1313013888&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-08-10T22:04:48+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>img2lcd</title>
        <link>https://r0ket.de/img2lcd?rev=1313013888&amp;do=diff</link>
        <description>Create Your own image

Use this template.png from github.

The white area will be visible on your display, the 4 black rows at the bottom will not but have to be included.

As soon as you have finished your drawing, use to img2lcd.pl converter located at /tools/image/ in the source repository to convert your picture.</description>
    </item>
    <item rdf:about="https://r0ket.de/init?rev=1375298890&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-07-31T19:28:10+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>init</title>
        <link>https://r0ket.de/init?rev=1375298890&amp;do=diff</link>
        <description>** This page contains the current release of our r0ket firmware release. Feel free to try it and give us feedback if you discover bugs in the firmware or these instructions **

How to flash your r0ket?

This procedure also brings your r0ket back into shape in case you</description>
    </item>
    <item rdf:about="https://r0ket.de/l0dable?rev=1325247512&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-12-30T12:18:32+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>l0dable</title>
        <link>https://r0ket.de/l0dable?rev=1325247512&amp;do=diff</link>
        <description>l0dable documentation

This page documents to how to write a l0dable. depending on the font you are seeing this looks like “I/O dables” but meant is “loadable”. these are small software components (in opposite to m0duls which are hardare components) that can easily copied to the</description>
    </item>
    <item rdf:about="https://r0ket.de/l0dables?rev=1356717198&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-12-28T17:53:18+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>l0dables</title>
        <link>https://r0ket.de/l0dables?rev=1356717198&amp;do=diff</link>
        <description>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 (&lt;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)</description>
    </item>
    <item rdf:about="https://r0ket.de/lcd_art?rev=1325511812&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-01-02T13:43:32+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>lcd_art</title>
        <link>https://r0ket.de/lcd_art?rev=1325511812&amp;do=diff</link>
        <description>LCD Art

Here you can publish any LCD art you made.
You can display *.lcd files using the “showlcd” l0dable
Here&#039;s a small script to convert gifs to lcds: &lt;http://www.pastebay.com/148888&gt;

Display images as nick

	*  Download the *.lcd
	*  Rename it to “NICK.LCD”.
	*  Replace it with the NICK.LCD on your r0ket.</description>
    </item>
    <item rdf:about="https://r0ket.de/m0dul-ethernet?rev=1339270323&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-06-09T19:32:03+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>m0dul-ethernet</title>
        <link>https://r0ket.de/m0dul-ethernet?rev=1339270323&amp;do=diff</link>
        <description>Descritption

Ethernet m0dul. Makes the r0ket speak IP. Currently in planning.

Idea

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:</description>
    </item>
    <item rdf:about="https://r0ket.de/m0dul-example?rev=1308594498&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-06-20T18:28:18+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>m0dul-example</title>
        <link>https://r0ket.de/m0dul-example?rev=1308594498&amp;do=diff</link>
        <description>Description: The example m0dul is an example! 

Author: example@example.com

Links: author, project site, whatever

Usage

Usage instructions

Mounting

The example m0dul has a “1” mark on the PCB. Plug onto either m0dul A or m0dul B connector.

Used addresses
 I2C  0000000  Chip select  #DEFINE</description>
    </item>
    <item rdf:about="https://r0ket.de/m0dul-flame_rgb-mod?rev=1313679364&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-08-18T14:56:04+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>m0dul-flame_rgb-mod</title>
        <link>https://r0ket.de/m0dul-flame_rgb-mod?rev=1313679364&amp;do=diff</link>
        <description>material

	*  original  flame m0dul
	*  1x RGB LED
	*  2x 100K SMD Resistors
	*  a few centimeters hookup wire (german: Fädeldraht)
	*  soldering equipment

Source LRTB G6TG RGB MultiLED
 LED Datasheet

building



Step 1

	*  unscrew the acrylic flame
	*  unsolder the original one-color LED

Step 2

	*</description>
    </item>
    <item rdf:about="https://r0ket.de/m0dul-flame?rev=1325615087&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-01-03T18:24:47+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>m0dul-flame</title>
        <link>https://r0ket.de/m0dul-flame?rev=1325615087&amp;do=diff</link>
        <description>Description: Ignite your r0ket!

28C3 Flame

Kits

Sorry, SOLD OUT!

Assembly

See 

Camp Flame

Author: kiu

Links: https://github.com/kiu/flame

Kits

Sorry, SOLD OUT!

Aww, that&#039;s sad. But hey, what about creating new ones? See thoughts on flames  production of new RGB flames (internal) 

maybe you like to modify your Flame? See RGB Flame mod</description>
    </item>
    <item rdf:about="https://r0ket.de/m0dul-j0y?rev=1311213496&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-07-21T01:58:16+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>m0dul-j0y</title>
        <link>https://r0ket.de/m0dul-j0y?rev=1311213496&amp;do=diff</link>
        <description>Description

j0y+ m0dul is a game controller for your r0ket .

Usage

Just connect the j0y+ m0dule to your r0ket. Eventually you will have to flash a new firmware onto the r0ket, we are not sure about this at the moment.

WTF is it?

This is a gamepad, so feel free to program games that use a analog stick, 4 buttons, some LEDs and perhaps a vibro motor (yes, we live in fear of</description>
    </item>
    <item rdf:about="https://r0ket.de/m0dul-r0ketc0m?rev=1313406931&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-08-15T11:15:31+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>m0dul-r0ketc0m</title>
        <link>https://r0ket.de/m0dul-r0ketc0m?rev=1313406931&amp;do=diff</link>
        <description>This m0dul will use a VS1053b audio dsp to connet a microphone and headphone jack to your rocket.
With a populated SD-slot you get an mp3/vorbis player, but main purpose is intendet to be a streaming player for talks / PTT coms device.

Expect to see hardware in a few days. Planed on a 200pcs production run.
Coders needed</description>
    </item>
    <item rdf:about="https://r0ket.de/m0dul-torch?rev=1312987404&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-08-10T14:43:24+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>m0dul-torch</title>
        <link>https://r0ket.de/m0dul-torch?rev=1312987404&amp;do=diff</link>
        <description>Description

Torch is a simple parasitic m0dule for r0ket. It uses the regulated 3.3v power supply and r0kets plentiful battery to drive a couple of white leds triggerd by an attached pushbutton.  

Usage

Grip your r0cket so you can reach the pushbutton. Then press it. If your r0ket is turned on then it should light up.</description>
    </item>
    <item rdf:about="https://r0ket.de/m0dul?rev=1325200240&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-12-29T23:10:40+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>m0dul</title>
        <link>https://r0ket.de/m0dul?rev=1325200240&amp;do=diff</link>
        <description>Intro

The r0ket can easily be extended by pluggable m0duls.

See m0duls for existing m0duls.

Hardware

Please keep in mind that power is a very limited resource on the r0ket. The more a m0dul consumes the less fun you have!

Interface

A m0dul can be connected to the r0ket via the m0dulbus. The connectors are in 2.54mm/100mil spacing, prepopulated with female sockets. If available, a</description>
    </item>
    <item rdf:about="https://r0ket.de/m0duls?rev=1360408361&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-02-09T11:12:41+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>m0duls</title>
        <link>https://r0ket.de/m0duls?rev=1360408361&amp;do=diff</link>
        <description>m0duls

Intro

This page is intended to list available hardware components for the r0ket. Hardware/interface description at m0dul

Registry

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.</description>
    </item>
    <item rdf:about="https://r0ket.de/manual?rev=1325194053&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-12-29T21:27:33+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>manual</title>
        <link>https://r0ket.de/manual?rev=1325194053&amp;do=diff</link>
        <description>R0ket User Manual



Intro

The r0ket was developed as the badge for the Chaos Communication Camp 2011. Besides being a shiny electronic name tag, the r0ket is an easy to use full featured microcontroller development board. We want to encourage you to tinker with your r0ket. 

On first bootup, you will have to go to two configuration screens. Don&#039;t worry about the settings, you can change them later.</description>
    </item>
    <item rdf:about="https://r0ket.de/nick_animation?rev=1313005691&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-08-10T19:48:11+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>nick_animation</title>
        <link>https://r0ket.de/nick_animation?rev=1313005691&amp;do=diff</link>
        <description>Animated Nick

Specification

	*  Each frame is a .lcd file.
	*  All frames are concatenated and saved as “nick.lcd”.
	*  Each frame is shown with a fixed frame rate of 0.5s.

Notes on lcd files

	*  Pixels are not quadratic, but rectangular with a 1.209 ratio (each pixel is 1.209 times higher than its width).</description>
    </item>
    <item rdf:about="https://r0ket.de/r0ket?rev=1325200625&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-12-29T23:17:05+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>r0ket</title>
        <link>https://r0ket.de/r0ket?rev=1325200625&amp;do=diff</link>
        <description>a r0ket is a r0ket is a r0ket</description>
    </item>
    <item rdf:about="https://r0ket.de/r0ketlauncher_ammunition?rev=1325170069&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-12-29T14:47:49+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>r0ketlauncher_ammunition</title>
        <link>https://r0ket.de/r0ketlauncher_ammunition?rev=1325170069&amp;do=diff</link>
        <description>Ammunition for the r0ketlauncher

Improvised ammunition for the r0ketlauncher, if you don&#039;t have enough foam missiles.

Roll your own



It does not get much more simple than this. A small piece of paper, ~3x~5 cm, rolled together and bent.
No tape is needed, but that might reduce air resistance and increase range a bit.</description>
    </item>
    <item rdf:about="https://r0ket.de/r0ketlauncher?rev=1325547092&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-01-02T23:31:32+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>r0ketlauncher</title>
        <link>https://r0ket.de/r0ketlauncher?rev=1325547092&amp;do=diff</link>
        <description>getDigital left lots of USB missile launchers in our hands.
So we&#039;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.</description>
    </item>
    <item rdf:about="https://r0ket.de/rem0te?rev=1325962758&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-01-07T18:59:18+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>rem0te</title>
        <link>https://r0ket.de/rem0te?rev=1325962758&amp;do=diff</link>
        <description>With the rem0te package of r0ket software you can build a game or other installation that can be interacted with, using a r0ket.

Overview

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.</description>
    </item>
    <item rdf:about="https://r0ket.de/simulat0r?rev=1324775753&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-12-25T01:15:53+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>simulat0r</title>
        <link>https://r0ket.de/simulat0r?rev=1324775753&amp;do=diff</link>
        <description>Simulat0r


...



1. What is it?

The simulat0r basically is a set of headerfiles and some C code which enables you to compile r0ket applications on x86 machines and run them using a qt GUI frontend. Currently only the LEDs, display and input button are supported, but that should be enough to develop simple games, a cool nickname-scroller firmware or similar stuff.</description>
    </item>
    <item rdf:about="https://r0ket.de/software?rev=1338291473&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-05-29T11:37:53+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>software</title>
        <link>https://r0ket.de/software?rev=1338291473&amp;do=diff</link>
        <description>You can find the whole software in our git repository on github: &lt;https://github.com/r0ket/r0ket&gt;

The code is released under BSD license.

Structure

The base firmware provides you with a set of functions to control the r0ket

	*  How to build your own software
	*  Use the simulat0r to test your software without having a r0ket</description>
    </item>
    <item rdf:about="https://r0ket.de/start?rev=1514291353&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-12-26T12:29:13+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>start</title>
        <link>https://r0ket.de/start?rev=1514291353&amp;do=diff</link>
        <description>http://rad1o.badge.events.ccc.de/
r0ketlauncherdocumentedl0dables



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</description>
    </item>
    <item rdf:about="https://r0ket.de/tracking?rev=1349697369&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-10-08T11:56:09+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>tracking</title>
        <link>https://r0ket.de/tracking?rev=1349697369&amp;do=diff</link>
        <description>Overview

We are tracking r0kets. General Idea is the Openbeacon project.

We are using the “new JSON API”, see &lt;http://www.openbeacon.org/API&gt;.

Json changes

We added some new fields to the JSON

	*  added tag-&gt;nick: nickname as sent by r0ket
	*  added reader-&gt;name: string that describes reader location</description>
    </item>
    <item rdf:about="https://r0ket.de/tvr0tator.c?rev=1325247321&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-12-30T12:15:21+00:00</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>tvr0tator.c</title>
        <link>https://r0ket.de/tvr0tator.c?rev=1325247321&amp;do=diff</link>
        <description>tvr0tator.c

/* Licensed under CC0 1.0 Universal (CC0 1.0)
 * by andy (andy_@jabber.ccc.de)
 * see http://r0ket.badge.events.ccc.de/r0ketlauncher
 */

#include &lt;usb.h&gt;
#include &lt;stdio.h&gt;
#include &lt;stdlib.h&gt;
#include &lt;errno.h&gt;
#include &lt;signal.h&gt;
#include &lt;string.h&gt;

usb_dev_handle* launcher;
pid_t pID;

int send_message(char* msg, int index)
{
	int i = 0, j;
	j = usb_control_msg(launcher, 0x21, 0x9, 0x200, index, msg, 8, 1000);
	memset(msg, 0, 8);

	return j;
}

void movement_handler(char contro…</description>
    </item>
</rdf:RDF>
