UCSD TIES Lakeside Environmental Monitoring

1
UCSD TIESLakeside Environmental Monitoring

• Winter 2006
• Client Proposal Presentation
• February 7, 2006
• Project Lead Stephen Bak

2
Agenda

• Statement of Intent
• WQ Research and Assessment
• User-Interface Plans
• Structural Development
• Hardware Development
• Summary

3
Intent of Presentation

• Outline initial status
• Present quarter progress
• State intended goals and deliverables
• Receive client recommendations and approval.

4
Water Quality Research and Assessment

• Team members
• Fabiola Hatley
• Meng Chou
• Sam Hwang
• Evan Sharbrough

5
WQ Sub-Team Goals

• To provide the hardware/software team with a set
  of reliable data to serve as a basis for
  comparison
• To continue studying the current chemical and
  physical status of the water in Lakeside
• To ascertain possible sources of pollution found
  at Lakeside

6
WQ Testing Schedule

• Goal To explore the water upstream from Lakeside
  
• Tasks
• Jan 21st- 1st visit
• Jan 28th- 2nd visit
• Feb 11th- app. with Robin to pick new
  site 6
• Feb 18th- 3rd visit
• Feb 25th- 4th visit
• Mar 4th- 5th visit

7
New Test Site

• The San Diego watershed is one of 11 in Southern
  California
• Stream from El Capitan Reservoir will be
  investigated

Picture 1. San Diego Watershed Network
http//map.sdsu.edu/group2001/group3/san_diego_dat
a.htm

• Site 6 will be picked strategically
• -Area around new site is primarily
  agricultural
• -Old dairy farm is nearby

Picture 2. Water Management http//www.sdcwa.org/m
anage/reservoirs-map.phtml
8
User Interface Development

• Stephen Frost

9
Last Quarter

• Four interfaces defined
• Office
• SWAMP current (Excel), eventual automated
• Education
• Public
• Research begun on what should be included in each
• Implications of certain design decisions on
  usability, ease of maintenance

10
Vandalism Defense

• New and novel things tend to get vandalized more.
  Make the equipment look somewhat aged, and blend
  it in.
• Things that may be being watched do not tend to
  be vandalized as much.
• Appearance of surveillance
• e.g. a fake camera.
• Increase traffic and social activity in the area,
  if possible
• build a trail nearby
• open space.

11
Design Choices and Usability

• Accessibility and procedure for remote system
• Maintenance
• Calibration
• Server and web site
• Reliability
• Maintainability

12
Office Server

• Provide
• File services to other office computers
• Database for storage of WQ data
• Web server for interface to any web browser, with
  authentication
• Streaming to hosted public and educational sites
• Data backup

13
Plan for the Quarter

• Week 5
• Office interface revision 2 weeks
• SWAMP bug Jim Dodson interface leads w/ State
  of Calif. 2 weeks
• Server hardware and software spec 1 week
• Week 6
• Education interface prototype research and sketch
  3 weeks
• Week 7
• Public interface research and sketch

14
Plan for the Quarter

• Week 8
• Server setup and initial configuration for remote
  access, development (tentative) 1 week
• Office interface nuts-and-bolts assembly 2
  weeks
• Week 9
• Wrap up of all trails of research and
  development, noting states 2 weeks
• Catch unfinished processes that may become
  misguided 2 weeks
• Week 10
• Writing continuation report, presenting quarter
  progress to client 1 week

15
Structural Development

• Scott Maghy
• Tim Chow
• Jeanie Kwok

16
Fall Quarter Results

• Basic enclosure and conduit models were
  developed
• Theoretical placement of the system
• Solar panel and antenna mounting ideas

17
Progress to Date

• Review of previous designs
• Analyzed structural design at Santa Margarita
  Ecological Reserve
• Cost analysis of various enclosure and conduit
  options
• Brainstorm new ideas and improvements to
  structural designs

18
Enclosure Improvements

• Option 1
• Purchase enclosure from a home improvement store
  (i.e. Home Depot)
• PROS
• saves time
• cheap (depending on model)
• electrical/circuit breaker boxes run about
  30-40
• only light weatherproofing needed
• moderately durable
• CONS
• significant sizing modifications needed
• lock system

19
Enclosure Option 2
weatherproof seal
lock

• Improve the Fall 2005 model.
• PROS
• possibly cheaper
• exact dimensions
• can tailor it to whatever specifications needed
• lockable
• weatherproof
• CONS
• requires more building time

fixtures for components
battery box (separate)
20
Cost Comparison

• Buy
• 30-50 for a general enclosure
• 100-200 for a high quality,
• specific equipment enclosure
• Build
• 30
• Possibility of acquiring donation/scrap materials

21
Goals for the Quarter

• 1. Deliver completely finished, detailed models
  on the enclosure and conduits.
• 2. Have all materials purchased for the
  construction and installation of the enclosure
  and conduits.
• 3. Begin construction if possible.
• 4. Submit a detailed model of the solar panel
  mountings and how the entire system (enclosure,
  conduits, panels) will fit together.
• 5. Buy materials necessary.

22
Hardware Development

• Electrical Engineers
• Daniel Leu
• Daniel Su
• Justin Tse
• Computer Science
• Tony Aung
• Nick True

23
Accomplishments

• Hardware
• Research wireless options
• Calculate power consumption
• Research battery, charge regulator, solar panel
  options
• Software
• LabVIEW training
• Determine programming goals

24
Goals and Deliverables

• Hardware
• Purchase recommended items
• Test and implement items
• Software
• Data storage onto datalogger
• Data transmission
• Overall
• Field test of system with chemical team

25
RF Modem
May be rated using different antennas
26
Power System

• 10 Watt system requirement
• Solar Panel Considerations
• Scenario Full Light, Partial Light, No Light
• Watts Generated gt Watts Consumed
  Flexibility
• Crystal Structure
• Substrate
• Cost
• Charge Regulator Considerations
• Environmental Concern
• Tracking Technology
• Display
• Cost

27
Solar Panels
Mono-Crystal 10-12 Eff. and Multi-Crystal
10-11 Eff.
28
Charge Regulators
MPPT Maximum Power Point Tracker
29
Rechargeable Sealed Lead-Acid Battery
30
Planned Schedule
31
Summary

• New test site, agricultural investigation
• Vandal-proof, yet usable system
• Finalize structural design
• Complete programming and purchasing of all
  hardware components

32
Final Goals

• Fully functioning prototype
• Confirm through field testing
• Can read/store/transmit data
• Operate remotely
• Next Quarter Deploy
• Debug
• Build enclosure and conduits