MoteNIC: Overview

1
MoteNIC Overview

• Need to interface the motes RF communication
  capabilities with a PC
• Example PC104s and IPAQs use the mote as a
  wireless transceiver for experimental purposes
• Solution Motenic
• Designed and maintained by Jeremy Elson
• A user-space driver
• Resides on top of FUSD (By Jeremy Elson)
• 2 parts
• PC side- moted user-space driver
• Mote side- TRANSCEIVER component

2
MoteNIC Details

• Communication from PClt-gtMote
• Uses serial port
• Uses a simple framing protocol (host-mote)
• Interface
• 2 devices /dev/mote and /dev/mote_tos
• User can open, read and write on the devices the
  same way as with any Unix-like device
• /dev/mote can send and receive messages of
  arbitrary length, /dev/mote_tos is restricted to
  TinyOS messages

3
SensorNIC

• Sensornic interfaces the motes sensors with a PC
• Uses two additional devices, /dev/mote_light and
  /dev/mote_temp
• More can be added
• Basic motenic functionality is still there
• When a user reads from a device, a request is
  sent to the mote to obtain a reading from its
  sensor
• After ADC conversion is done, user gets a reply
  in the form of a 10-bit unsigned int

4
Next step MoteNIC2 (SuperNIC)

• More functionality
• Ability to set the radio TX range, based on
  potentiometer value
• Already implemented
• Ability to turn the radio ON/OFF
• Anything else of interest that can be found on
  the new mote
• Modularity
• Shift design from monolithic to component-based
• Forced by restrictions on the motes code-space
  size