Vigilant Sensing Technology

1
Vigilant Sensing Technology

• VST1000 Remote Sensing System
• Preliminary Design Review
• Development Team Patrick Hauser
• Joel Keesecker
• Mark Kien

2
Review Outline

• Project Objectives
• Motivation
• System Module Descriptions
• Division of Labor
• Condensed Schedule
• Risks Mitigation
• Questions

3
Project/System Objectives

• Seamless turnkey operation
• Broadband pipeline for expandability
• Selection of narrowband sensors
• Clandestine packaging of remote units

4
Motivations

• Provide generic, economical remote sensing
  ability for use in public safety and medical
  environments.
• Use non-dedicated lines to communicate with the
  sensors in the field.

5
System Level Diagram
6
System Modules

• Master Control Unit
• RF Remote Sensing Unit
• Power Line Remote Sensing Unit
• PC Interface

7
System Interfaces
8
Master Control Unit (MCU)
9
MCU Basic Functions

• LCD Sensor data, errors, and status
• Status LEDs Tx, Rx, Power, Error
• Liaison between Remote Unit and Host PC
• Store data when com link is lost (100 Recs)
• Error monitoring and detection routines

10
MCU Module Interfaces
11
MCU Microcontroller Requirements

• Single Board Microcontroller
• Memory to support the following
• Buffering and storage of sensor data (record size
  TBA).
• Operating firmware (code size TBA).
• Ports 1-GPSI, 2-RS232, 16-GPIO
• Speed to support data movement.

12
MCU Power Line Modem Requirements

• Support serial high speed data 14Mbps
• Provide P/S for MCU or use single supply
• FCC approved for industrial use
• Small and easy to assimilate into MCU

13
MCU RF Modem Requirements

• 2.4 GHz FCC Unlicensed Band Operation
• Support serial high speed data 250Kbps
• Single power supply
• Small and easy to assimilate into MCU

14
MCU Power Supply Requirements

• Highly efficient design switching
• Will supply all modules with specific needs
• Strive for single supply solution
• High likelihood for final design group build

15
Remote Sensor Unit (RSU)
16
RSU Basic Functions

• Monitor sensors, send data when critical
  threshold is reached
• Format and communicate sensor data to MCU
• Respond to commands from MCU
• Status LEDs Tx, Rx, Power, Error, Low Battery
• Report RSSI to monitor link quality
• Custom PCB
• Unique ID for each sensor

17
Sensors

• Original Idea Radiation Detection
• Possible Sensors
• Temperature
• Wireless Signal Detection
• Possibly ADL5500
• Motion
• Air Quality (eg. Clean Room)
• Board capable of supporting a variety of sensors

18
RSU Interfaces
19
RSU Microcontroller Requirements

• Same architecture for both boards
• (TI / Freescale / Atmel)
• Low power consumption
• At least 2 channel 8-bit onboard ADC
• Onboard UART
• Real time clock
• Ports 1 GPSI/RS-232/RS-485, 8-16 GPIO, ICSP/ISP

20
RSU Power line Sensor

• GPSI Interface to power line transceiver
• Possibly using Asoka PL80-9105-001
• If broadband power line communication proves to
  difficult fall back to narrowband.
• AC-DC switching power supply

21
RSU Wireless Sensor

• 2.4 GHz wireless communication
• Using Xbee or RS-232 Wireless Modem
• Battery, Charger, and monitor
• 9-12 V Lithium-ion Battery
• Charger Purchased or own design
• DC-DC switching power supply
• Low standby power consumption

22
PC Interface
23
GUI/Host PC Basic Functions

• Interface through RS232 to the MCU
• View historic and real time sensor data
• Control data acquisition
• Store data to database
• Monitor sensor status (RSSI, Battery life)
• Error monitoring and detection routines

24
GUI Data Viewer

• Table of detects
• Detailed info of selected detect
• Detailed info on most recent detect
• Get Detect from wireless device
• Get Detect from power line device

25
(No Transcript)
26
GUI Sensor Information

• Battery power (wireless device)
• Sensor unit RSSI
• Number of sensors on power line unit
• Number of sensors on wireless unit
• ID mapping
• ID number and corresponding sensor

27
(No Transcript)
28
Host PC RS232 Communication

• Script to read and write to port
• On read, update database
• Communicates with master controller
• Continuous/Scheduled update
• Fetch data upon GUI request

29
GUI - If Time Permits

• Website
• Data viewing only
• Way to view data from anywhere
• Historical Info
• Plot user defined historical data
• Scatter or bar graph depending on data
• Ex. Temperature over time
• Ex. Number of Motion detects/day over 1 week

30
Division of Labor
31
Condensed Schedule
32
Risks Mitigation

• Noisy lines could make power line communications
  difficult
• Down grade to narrow band modems or drop Power
  Line Modem option altogether.
• Part availability
• Address part concerns well in advance of need
• Resources limited
• Reduce scope and/or leverage additional dev.
  tools.

33
Questions / Suggestions