Introduction

From CSL Wiki

Contents 1 Introduction 2 System Architecture 3 Open Questions 4 Initial thoughts on potential changes

Introduction

There are a number of problems with the hostmote and transceiver code at present that need to be addressed. This code runs on a mote that connects to a Stargate via a serial interface, and maintains wireless connectivity to the rest of the mote network. This device is the gateway between the Stargate and the mote network, and it is hence imperative that it operate stably and reliably. The following are the problems noted that should be addressed.

1. The transceiver mote locks up and ceases responding at random times, after anything from a number of hours to a number of weeks. The cause of failure is unknown
2. JTAG is currently not used with the mote that fails
3. The tiny-os side hostmote code does not have a good seperation of radio specific / radio agnositic code, meaning it contains many #ifdef statements, greatly reducing code clarity, and limiting future extensibility to other radio platforms
4. The code is not well understood or documented

System Architecture

The following diagram shows the relationships between the different software modules.

Open Questions

Initial thoughts on potential changes

This is a list of stuff that Lew and I had wanted to do at some point. --thanos

Mote-side

• Add parametrized interface to hostmote
• Add dynamic priority for clients
• Make transceiver a connector app and modularize the radio usage

PC-side

• Functionalize large chunks of code in motenic_main.c
• Make timers adaptive and configurable through a command device

Both

• Make the protocol running over the serial interface more robust
• Make the implementation of the serial interface protocol more robust