Man Pages and 2.0 Preparation

I finally finished the man pages for the scripts and programs in MCI. Together with the improved installation instructions for the mote host it should now be a little easier to figure out how to setup this part of the testbed.

Anyway, it has all been pushed it to the remote-mci-1.x branch, which I also finally merged back into my trunk. I haven't decided whether it is worth creating a 1.x branch for SVN; time will tell. However, Rosta mentioned during our talk today that some fixes from his side might be expected in the future and I have some things I would like to fix myself to make 1.x more robust.

In other news, preparation for 2.0 will start to take place and today's chat was a step in that direction. We discussed what the focus should be, and went into detail with a few of the bigger task ahead, such as the administrator interface. To help with this preparation, I made some changes to the wiki to introduce a better framework for the enhancement proposals inspired by TinyOS' TEPs and Python's PEPs. The REP structure is still very informal and simple, since it is still not clear to what extent this will be used. Some work remains to convert the old design documents to the new structure.

User Manual with Screenshots and 1.x Branch

Wow, it is nice to see that the announcement of the 1.0 release on wsnblog.com inspired a lot of people to visit the project page and have a closer look. This is all really encouraging so today I have made some screenshots to try to exemplify what Re-Mote has to offer from the users' point of view. Most of the screenshots have also been integrated into the user manual, which now presents itself much more visually appealing.

I would also like to announce the creation of a new branch for remote-mci-1.x, which already have one embarrassing fix of a typo in the code for setting up the baud rate for the dig528-2 platform. It slipped through because the dig528-2 UDEV rule had the same typo, making it all work perfectly until the rule file was fixed right before the release. Although the fix was easy, it raises the question if it would not be better to also make platform specific UDEV scripts responsible for specifying the baud rate. Something to consider for the upcoming planing of the next release ...

Re-Mote Testbed Framework v1.0

With the dust settling after some last minute hectic renaming and reorganization taking place it is time to celebrate. Finally it's here: version 1.0 has been released and is ready to be deployed at a testbed near you!

This release is the first featuring code development in collaboration between DIKU and CIT. It brings many enhancements mainly to the mote control infrastructure, which has been made more portable and configurable and updated to use UDEV for mote device discovery. The major contribution of this release is the support for MicaZ and Tmote Sky in addition to the original DIG528-2 platform.

While most of the effort has gone into the darker sides of the testbed framework, users of the Re-Mote Control Client will find that upgrading from the preview builds will bring a few nice enhancements, such as improved support for the different mote platforms.