feb 2007wsn training: intro to wsn & mote kits1 introduction wireless sensor networks and...

Feb 2007WSN Training: Intro to WSN & Mote Kits 1

Introduction Wireless Sensor Networks and Crossbow’s Hardware Products

Topics Crossbow Background & the WSN

Market End-user Benefits/Motivation MoteWorks and Wireless Products

Overview

WSN Training: Intro to WSN & Mote Kits 2 Feb 2007

San Jose Headquarters

Corporate Overview

Global Leader in Sensory Systems Founded 1995 MEMS-Based Inertial Systems Wireless Sensor Networking

125 Employees World Wide

$25M in Venture Capital Cisco Systems, Intel Corporation Morgenthaler Ventures, Paladin Capital


CrossbowUnited States

Switzerland

Japan

China

DistributorsMost European Countries

Key Asian Markets

Crossbow Corporate Overview -- Worldwide Locations


Sensor Systems for Avionics and Land Vehicles First Silicon MEMS IMU/Gyro System First MEMS Gyro FAA certification

Another Side of Crossbow – Inertial Systems

Eclipse 500

Virgin Atlantic Global Flyer


WSN Market Overview – “The Next Tier of the Internet"

Year

Availa

bili

ty o

f co

mp

uti

ng

InteractivityProductivity

Mainframe

Workstation

Number CrunchingData Storage

Connectivity withPhysical World

Personal Computer

Cellular phone


WSN Industries

Research,Education

Industrial Automation

Building Automation

Mobile Asset Management

EnvironmentMonitoring

Physical Security



Topics Crossbow Background & the WSN Market End-user Benefits/Motivation MoteWorks and Wireless Products Overview


Why Deploy Wireless Sensor Networks?

Across the various industries and markets, the benefits of

wireless sensor networks can be grouped into three areas

1. Lower the cost of wiring or deploy “off-the-grid”

2. Build sensing networks for ad-hoc infrastructure

3. Enable new sensor applications where wiring is not possible


Benefits/Motivation

Lower cost of wiring Retrofit of existing systems No power or IT infrastructure Intrinsically safe apps


Benefits/Motivation (cont’d)

Sensing networks for ad-hoc infrastructure

Start small and scale up Incremental improvement of operations Temporary monitoring or site auditing


Benefits/Motivation (cont’d)

New applications where sensors have not been used before

Mobile equipment/people Rapidly changing environment Below ground / covert sensors Atmospheric monitoring


XAV (Crossbow Aerial Vehicle) for Really Difficult Locations

XAV

Ground Station PC

R/C Transmitter

High Gain Wi-Fi


XAV Flight Test Data: 3D and 2D Position

A separate training class on the XAV is available. Visit our website or see Susan Lee for details


Wireless Sensor Network – Architecture

Processor-Radio-Data Logger“Mote”

Sensor cluster or interface

card

Crossbow’s Focus



Topics Crossbow & The WSN Market End-user Benefits/Motivations MoteWorks and Wireless Products Overview


Crossbow Solution

Design Engineering Services, Support and Training

Software Platform

HardwarePlatform


Software Platform -- MoteWorks™

Hardware Platform

Database

Mote Network Tier

SW Development Tools

TinyOS

XMesh

XOtap

Server Tier

Gateway Server SW(“XServe”)

XMesh

XOtap XML

Database

Custom

Serial Forwarder

Client Tier

Monitoring &Management

MoteView

Data Visualization

Analysis

Management

Configuration


Design Engineering Services

Hardware Platform

Processor/Radio Boards

OEM Modules Sensor Boards Gateway Boards

Evaluation &

Development Kits


Basic Anatomy of a Sensor Node


“What Type of Mote Do I Have?” (Review)

Look at the number on the label with units in MHz or GHz

MICA2 433 MHz

MICA2 915 MHz

MICAz 2.4 GHz


MICA2 and MICAz Wireless Modules

Logger Flash

ATMega128LcontrollerAnalog I/ODigital I/O

FSK, Freq. Tunable Radio

51-Pin

Exp

ansio

n C

on

nec

tor

Antenna

MMCX connector

LE

Ds

Serial ID

FCC/ARIB certified

Logger Flash

ATMega128LcontrollerAnalog I/ODigital I/O

DSSS, 802.15.4 Radio

51-Pin

Exp

ansio

n C

on

nec

tor

Antenna

MMCX connector

LE

Ds

Serial ID

MICAz(MPR2400)

MICA2(MPR400, MPR410, MPR420)


MICAz and MICA2 Core Hardware Components

Platform MICAz MICA2 Information

Microprocessor

ATmega128L ATmega128L http://www.atmel.com

Radio CC2420(2.4 GHz)

CC1000(433 MHz, 868/916 MHz)

http://www.chipcon.com/

External Serial Flash

AT45DB041512 Kbyte

AT45DB041512 Kbyte

http://www.atmel.comThe serial flash can be used for over-the-air-programming (OTAP) and/or data logging

Unique ID (integrated circuit)

DS2401P64-bit

DS2401P64-bit

http://www.maxim-ic.com/This chip contains a unique 64 bit identifier.

51-Pin expansion connector

Yes, except for OEM modules

Yes, except for OEM modules

This connector brings out most of the ATmega128L signal

http://www.atmel.com/

http://www.atmel.com/

http://www.maxim-ic.com/


Atmega128 Resources (1 of 2)

Resource Value Information

Program Memory (Flash Memory)

128K BytesThis memory stores the application code. It is programmed through an MIB base station or using OTAP. When reprogrammed, the entire memory is erased except for the boot code section.

SRAM 4K BytesThis memory section is used to store user application parameters, XMesh variables and TinyOS variables. It also contains the stack.

EEPROM 4K BytesThis memory is used to store persistent values such as mote_id, radio frequency, etc.

Timers4 Timers, two 8 bit, two 16 bit

TIMER0: (8 bit) is used by TinyOS and is available to the user only through the standard TinyOS clock services.TIMER1: (16 bit) is available to the userTIMER2: (8 bit) is only available to the user on the MICA2. For MICAz it is used by the TinyOS radio stack and cannot by used otherwise.TIMER3: (16bit) is available to the user.

SPI Bus1, but not available

The SPI bus is reserved exclusively for the radio interface and is not available for user applications. The SPI bus is also used during reprogramming by the MIB units.

I2C Bus 1 This is a standard serial interface to many sensors


Atmega128 Resources (2 of 2)

Resource Value Information

UART 2

The processor has two UARTs that can be run in either an asynchronous or synchronous mode. UART0 is used for base station communication. UART1 is available to users. The control pins for this uart are shared with the serial flash.

ADC 8 channels

There is a 10 bit ADC available for users. On MICA2 one channel is allocated for the radio’s RSSI. The ADC inputs are also used for JTAG so users should try to use other ADC inputs if possible if they wish to use the JTAG capability.

GPIOThere are many general purpose I/O lines available. Some of these support additional functionality (see ATmega128 manual)

External Clock (High Speed)

7.3228 MHz

This crystal speed is chosen to generate correct UART baud rates (57.6K baud). It is only needed for base station Motes that communicate over the UART or other user applications that communicate to external serial devices. Normally a non-base station mote is fuse programmed to use an internal 8 MHz clock as this clock has a faster start-up time and reduces the overall power consumption for a low-power mesh. The high speed clock is off when the MICA is sleeping.

External Clock(Low Speed)

32 kHzThis clock is used for TinyOS timing (TIMER0). It is always running even when the mote is sleeping as it’s used to wake-up the mote after the required sleep interval.


Atmega128 Fuses

What are fuses? Programmable settings to put the ATMega128L processor into different modes of operation For complete discussion of the fuses see

http://www.atmel.com/dyn/resources/prod_documents/2467s.pdf.

There are 3 types of fuses that MoteWorks users should be aware1. Atmega103 compatibility fuse

2. JTAG fuse

3. XMesh operationsSee Appendix C of the XMesh User’s Manual for further reference

http://www.atmel.com/dyn/resources/prod_documents/2467s.pdf

http://www.atmel.com/dyn/resources/prod_documents/2467s.pdf


Syntax for UISP to Set and Read Fuses

--<fuse operation> is optional and can be left out. See the next slide for different settings

--rd_fuses lets you read and print to screen the fuse’s states

For more information type uisp –h in a Cygwin window for documentation

MIB Type General Format for the UISP Command Line in CygwinMIB510 uisp -dprog=mib510 -dserial=/dev/ttyS<COM#> -dpart=ATMega128

–-<fuse_operation> –-rd_fuses

MIB520 (Use the higher of the two COM ports)

uisp -dprog=mib520 dserial=/dev/ttyS<COM#+1> -dpart=ATMega128

–-<fuse_operation> –-rd_fuses

MIB600 uisp -dprog=stk500 -dhost=<IP_Addr> -dpart=ATMega128

--<fuse_operation> –-rd_fuses


Important Fuse Operations for XMesh

Example: To make a high power mesh node use the internal oscillator via a MIB510 on COM1

XMesh configuration

wr_fuse_h wr_fuse_l wr_fuse_e Description

XMesh-LP or XMesh-ELP andOTAP disabled

0xd9 0xc4 0xff Internal oscillator (8MHz) enabled.JTAG disabled.

XMesh-LP or XMesh-ELP andOTAP enabled

0xd8 0xc4 0xff Internal oscillator (8 MHz) enabled.JTAG disabled. Bootloader for OTAP

XMesh-HP and OTAP enabled

0xd8 0xff 0xff Bootloader for OTAP

Base Station(XMeshBase)

0xd9 0xff 0xff Enable the use of an external oscillatoruisp -v -dprog=mib510 -dpart=ATmega128 -dserial=/dev/ttyS0

--wr_fuse_h=0xd9 --wr_fuse_l=0xff --wr_fuse_e=0xff --rd_fuses


A Shortcut to Set and Read Fuses

Typing in the long UISP command can be cumbersomeThere is a script called “fuses” in /MoteWorks/tools/bin which

allows the fuses to be read and written easily. (Screen shot below.) You should be able to do this in any directory in a Cygwin window

An even nicer alternative: Use MoteConfig (more later).$ fusesfuses Ver:$Id: fuses,v 1.1.4.1 2006/07/21 15:42:59 mturon Exp $ Usage: fuses [command] [port] [args] read = read fuses clkint = set to internal oscillator clkext = set to external oscillator jtagen = enable JTAG jtagdis = disable JTAG

Command Flag ------- ------------------------------------------------------------ clkext --wr_fuse_l=0xff clkint --wr_fuse_l=0xc4 jtagdis --wr_fuse_h=0xd9 jtagen --wr_fuse_h=0x19 read --rd_fuses


MTS300/310 General Experimental Board

Microphone / Tone DetectorTemperature: Panasonic ERT-J1VR103J

CdSe Photoresistor

Sounder: Ario (centered at 4.5 kHz)

Magnetometer: Honeywell HMC1002 (MTS310CA only)

• Resolution: 134 mGaussAccelerometer: ADI ADXL202 (MTS310CA only)• 2 axis• Resolution: ± 2mG

XSensor App XMesh App Driver directoryXMTS310_XXX_HP

XMTS310_XXX_LP

NotesUse XMeshBase for Mote on gateway board.

Use XMeshBase for Mote on gateway board

Program Name

XSensorMTS310 /opt/MoteWorks/tos/sensorboards/mts310


MTS3x0CA or MTS3x0CB?

Probably most of you have the MTS300CBs and MTS310CBs.

While they are largely identical to the MTS300CA and MTS310CA, there are two ways to distinguish them CBs have a white sticker label on them CBs have a green “jumper” wire soldered on one side of the

board

Take a moment to note which board you have and write that down at the front of your WSN training manual

feb 2007wsn training: intro to wsn & mote kits1 introduction wireless sensor networks and...

Documents

wsn mote kitswsn training

wsn mote kitsfeb

possiblewsn training

wsn market overview

site auditingwsn training

paladin capitalwsn training

sensor systems

gridbuild sensing networks