Octopus_V_2.1

You are here:

Octopus_V_2.1

Categories:

Octopus Dashboard

New Features of Octopus dashboard v.2:

Software-based energy estimation
Support for localization (in progress)
Alert notifications
Channel selection
Temperature, light and humidity sensors connected
General improvement of Application and radio request panels
Support for TinyOS 2.1
Support for Tyndall25 nodes (humidity sensor driver to be implemented)
Support for multi-platform TinyOS nets (e.g. TelosB and Tyndall25 nodes together)
Automatic loading of energy aware components loaded only for the OctopusDashboard application

Downloads

Octopus Dashboard Requirements

TinyOS 2.1 environment running on your machine;
Native platform compilers to use installed in your TinyOS
- for Tyndall25 node see Tyndall_TinyOS user manual;
- for Telos and Mica follow the link

How to install Octopus Dashboard

Copy the OctopusDashboard directory containing motes and java directory in /opt/tinyos-2.x/apps/;
Copy CC2420TransmitC.nc and CC2420TransmitP.nc from energy directory into the folder: /opt/tinyos-2.x/tos/chips/cc2420/transmit/;
Copy LedsC.nc and LedsP.nc from energy directory into the folder: /opt/tinyos-2.x/tos/system/;
Copy PowerCycleC.nc, PowerCycleP.nc from energy directory into the folder: /opt/tinyos-2.x/tos/chips/cc2420/lpl/;
Copy Energy.nc from energy directory into the folder: /opt/tinyos-2.x/tos/interfaces/.

How to run the Octopus Dashboard

1. Compile the node code for the Octopus application for your platform:

cd /opt/tinyos-2.x/apps/OctopusDashboard/motes
make <PLATFORM>

you need to substitute <PLATFORM> with the name of your platform (e.g.: Tyndall25 or telosb).
Each mote of your network must have a distinct ID. For the base station mote the ID must be equal to 0 (others nodes must ownt different IDs). We recommend you use consecutive node ID’s for OctopusDashboard versions 1.3 and later.

2. make <PLATFORM> reinstall,<NODE_ID> <your usual installation options>

<your usual installation options> can be PROGRAMMING_BOARD, SERIALPORT or nothing (depends on the platform to deploy). For instance: “make Tyndall25 reinstall,0 Tynprogbrd,COM2” or “make micaz reinstall,0 mib510,/dev/ttyS0” or “make telosb reinstall,0”

Note: For Tyndall25 it may happen that if you type motelist, your PC does not list any mote. However, this does not prevent uploading the code into the node once you pointed the right port ()

3. Connect the root mote to your PC and switch on all motes.

4. Export the MOTECOM variable in your environment:

export MOTECOM=serial@<SERIALPORT>:<SERIALPORT BAUD RATE>

Note: You need to change <SERIALPORT> and <SERIALPORT BAUD RATE> with your inputs, for example the Tyndall baud rate is 57600; if you are using telosb, you can just write "telosb" instead of the baud rate. SERIALPORT is the serial port device name. Under Windows, if your serial port is COMn:, you must use /dev/ttySn-1 or COMn as the device name. On Linux, the device name is typically /dev/ttySn for a regular serial port and /dev/ttyUSBn or /dev/usb/tts/n for a USB-serial cable (the name depends on the Linux distribution).
Note that the SERIALPORT specified for MOTECOM must be the one used for communicating with a mote over the serial line. On telos and mica motes this is the same port that the mote is programmed from. Other motes, such as Tyndall25, have one port dedicated to programming and another for communication. Just make sure you use the correct one.

5. Compile and run the java application.

cd /opt/tinyos-2.x/apps/OctopusDashboard/java
make
java OctopusGui

Note: Sometimes Octopus starts receiving "bad packets" that are signalled in the terminal or by the red led onto the nodes. This maybe due to a too high node data rate or the base station is connected at a later stage etc. In that case you may reset the node by clicking onto the button provided.