wiki:WikiStart

Welcome!

This is our project development area, where you can

If you'd like to help out, have a look at our Contributors Page!

Project Overview

Questions?

If you have any problems or questions, don't hesitate and submit a ticket or if you don't think thats helpful/annoying enough,  send a mail

Cheers,

riot

What would you like to see here, furthermore? Discuss the Welcome page!

Blog

cape flashtalk on 30c3 && repository glitch

Flashtalk 30c3

riot just held a flashtalk (like a lightning talk, but only 3 minutes) at the very magnificient 30th Chaos Communication Congress in Hamburg.

The slides are available  here.

Repositoryserver currently borked

Please be patient, if you'd like to clone our source code, the repository server is currently borked and will be repaired in the next few days. riot will see if we can mirror the repositories cleanly on github.

Discover your embedded!

Ever took your embedded system to another place and wondered which network address the darn unit chose and then went the long way to connect display and keyboard just to find out?

Out of that same reason, an exciting new cape component has its debut in this blogpost: We now have a quite well working zeroconf-based discovery component!

Of course this one only makes sense, if you already use cape as daemon.

It is still in development, so to use it, install the cape.dev package into your cape environment or use the cape install tutorial if you don't have cape, yet.

If you have tkAdmin installed, you can add "cape.dev.discovery" via System/Create Component. Otherwise, add this snippet to your configuration:

   "dev.discovery.Discovery_23": {
        "announce_interfaces": [
            "eth0"
        ], 
        "id": {
            "template": "cape.dev.discovery"
        }, 
        "scan": true
    }, 

In other news, i'm thinking of a way to handle components (and configuration) via command line tools, so adding components or other individualization of your system doesn't require (the somewhat odd) tkAdmin nor throwing around json snippets.

So, stay tuned or help out, if you can't wait ;)

PS: There's promising, yet uncomitted (had a HDD crash, but can recover ;) news on the py3.x front, too! Sooooon…

PPS: I added lots of documentation (esp. tutorials) today.

New Repo Access System and git introduced \o/

I'm announcing this now, since I fixed the last obvious test phase flaws and adapted our certificates today:

Repo Access

To make sure, everyone can browse, read and download (possibly even review) our code, I installed a very nice new repository management system some weeks ago, which you can access at  https://repos.hackerfleet.org. The system uses  RhodeCode.

Documentation, issue tracking and planning will still happen here in our Trac.

Git

Prior our last Hackathon (Mission Socialbearing), the need for a second version control system became apparent, so i installed and set up git as our secondary VCS.

Commit Access

All (hg+git) commit access is being handled via ssh public keys now. If you'd like to commit code to our official repos, please contact  riot@hackerfleet.org with your request.

Cheers, riot

An expedition to Denmark

Last week, we returned from our successful expedition to Denmark. Our crew of five furiously sailed from Gelting Mole through the danish south sea to our small, cozy and beautiful mission area.

Openseamap screenshot of Dyvig, our testing area

We fixed a lot of the MS0x00's codebase and made interesting things work:

  • A magnetometer component can now deal with raw data and deliver rather well calibrated compass data
  • A tracking component uses GPS and said compass data to actually move the boat in the right direction
  • We've written a serial probe utility to find out what device is connected to which serial port (we use lots of them ;)
  • The scaffold can finally be initialized from configuration
  • The MSP430's firmware runs as expected:
    • Turning the pump on and off works (the coolant system, too, we'll measure soon)
    • the navigational lights can be turned on and off. Probably dimmable without too much more work.
    • Measuring ADC voltage works, but the sensors are not yet connected
  • cleaned and simplified RPC base (now as planned, more jsonrpc like ;)
  • fixed and cleaned a lot of weird typos/bugs and other lint

Thanks to Martin Ling for many of the above bugfixes and feature submissions!

Sadly our final goal - taking a bathymetry snapshot of the testing area - failed due to an accidentally killed DC-DC regulator :(

And there is still a lot to go! We have a lot more sensors to connect and calibrate, the system as a whole needs improvements and some functional components are outright missing right now. But as you can see, we're advancing at a good pace :)

If you'd like to contribute and help us reach our goal of a reliable, well working robot fleet software system, contact us!

New TkAdmin, Serial driver, NMEA parser

Oh, wow, a lot of pieces finally snap together.

Since revision 36, which was committed today, the system understands and can work with NMEA data gathered via serial line (or whatever source you prefer ;)

In the process, i redesigned and enhanced TkAdmin with a few new perks.

See for yourself:

Even moaar smaller, fscks up wiki homepage, if too large

The design isn't really userfriendly, more programmerfriendly - and i'm improving that every day, too. You can already call component's methods with a dynamic parameter entry dialog, but that one isn't beefed up yet. Probably won't be in a long time because next up, is support for Mapnik and a lot of glue to use the bottle webserver for user interaction.

Thanks:

Debian Logo with Text

Python Logo

No image "kamaelialogo.png" attached to Opensource

OpenCV Logo

OSI Logo

Trac Logo