micro cart dec8 03 micro processor c ontrolled a erial r obotics t eam n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Micro-CART Dec8-03 Micro processor – C ontrolled A erial R obotics T eam PowerPoint Presentation
Download Presentation
Micro-CART Dec8-03 Micro processor – C ontrolled A erial R obotics T eam

Loading in 2 Seconds...

play fullscreen
1 / 62

Micro-CART Dec8-03 Micro processor – C ontrolled A erial R obotics T eam - PowerPoint PPT Presentation


  • 119 Views
  • Uploaded on

Micro-CART Dec8-03 Micro processor – C ontrolled A erial R obotics T eam. Team Members. Team Leaders Jason Funk Karl Svec Client Lockheed Martin Advisor Dr. Greg Smith. Team Members Matt Beecher Andrew Crawford Mike Dent Phong Deo Anthony Nowell Dave Zajicek Yan Zhang

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Micro-CART Dec8-03 Micro processor – C ontrolled A erial R obotics T eam' - gad


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
team members
Team Members
  • Team Leaders
  • Jason Funk
  • Karl Svec
  • Client
  • Lockheed Martin
  • Advisor
  • Dr. Greg Smith
  • Team Members
  • Matt Beecher
  • Andrew Crawford
  • Mike Dent
  • PhongDeo
  • Anthony Nowell
  • Dave Zajicek
  • Yan Zhang
  • Pilot
  • Nicholas Crego
project history1
Project History
  • Beginnings
    • Students wanted to develop a UAV to enter into a competition
    • Accomplishments:
      • Build Chassis
      • Tried different configurations of avionics boxes
      • Built low level software to read sensors
      • Manually flew and took readings
project history2
Project History
  • 3 years ago to 1 year ago
    • 2 students wrote nearly complete versions of avionics software, a ground station, and a simulator
      • Tested the avionics software in the simulator and it worked well
    • Installed avionics software on the system
      • Flight tests resulted in destroyed electronics
        • Determined to be caused by electronics not being electrically isolated from spark plug
project history3
Project History
  • 3 years ago to 1 year ago
    • Replaced nearly all of the electronics on the system
    • AeroEs rebuilt the helicopter and engine
    • Rewrote Ground Station in Java
    • Worked towards completing flight control software
functional system requirements
Functional System Requirements
  • Autonomous flight
  • Visit 4 GPS waypoints
    • Over distance of 3km
    • Fly within 3 meters of waypoint
  • Avoid Fixed Obstacles
    • Fly over them at 50 ft
  • Hover at final waypoint
  • 2 way communication between Ground Station and Helicopter
non functional system requirements
Non-Functional System Requirements
  • Weight less than 14lb
  • Response time less than 1s
work breakdown structure
Work Breakdown Structure
  • Ground Station
  • Mike Dent
  • Dave Zajicek
  • Manual Override
  • Andrew Crawford
  • PhongDeo
  • Yan Zhang
  • Sensors
  • Anthony Nowell
  • Flight Control Software
  • Jason Funk
  • Filtering
  • Karl Svec
  • Matt Beecher
overall team goal
Overall Team Goal
  • Independent autonomous hover on Roll, Pitch, Yaw, Throttle, Collective Servo Channels
    • Complete, test, characterize, filter, and calibrate sensors (Sonar, GPS, Compass, Altimeter, IMU)
    • Complete manual override hardware
    • Fix trimming issues
development cycle
Development Cycle

Design

Implement

Bug Fix

Lab Test

Ground Test

Analyze

Analyze

Flight Test

ground station
Ground Station
  • Purpose
    • Display current status of helicopter
    • Provide interface for setting navigation
    • Provide interface for setting control constants
    • Provide data logging / graphing capability
  • Initial Status
    • Receiving and displayingdata from helicopter
    • Intermittent problems sending data to the helicopter
  • Tasks
    • Fix outstanding communicationissues
    • Add manual trimming
ground station2
Ground Station
  • Communication
    • Manual trimming of servos
    • Packet sending
    • Packet receiving
  • Information handling
    • Data logging
    • Manual / computer control indication
    • New real-time graphing capabilities
ground station3
Ground Station

18

  • Communication
    • Trim packets
      • Trim can be adjusted in real-time from the GS
      • Allows for tuning of servos before and during flight
ground station4
Ground Station

19

  • Communication
    • Packet sending - redundancy option
      • Send up to five identical Trim or PID packets
      • Compensates for possible packet loss/corruption
ground station5
Ground Station

20

  • Communication
    • Packet receiving - frequency option
      • Increase/decrease the rate at which helicopter sends state and dynamic PID packets
      • Allows for better resource management
ground station6
Ground Station

21

  • Information handling
    • Manual / computer control indication
      • Differentiate computer or manual control in logged data
    • New real-time graphing capabilities
      • Uses program called LiveGraph
      • Allows for quick and easy analysis of flight data
ground station7
Ground Station
  • Final Status
    • New Communication, Graphing, & Trim features
      • Fully implemented and tested
      • Verified through ground and flight tests
    • Communication Testing Procedure
      • Initial communication loss: ~60%
      • Adjusted RF modem and serial port settings until best results received (~50% loss)
      • Implemented and tested state packet frequency functionality (now within satisfactory range ~5%)
flight control software

2323

Flight Control Software
  • Purpose
    • Control helicopter movement
  • Initial Status
    • Sends calculated control data to servo controller based on the sensor data it receives.
    • Communication issues exist when receiving data from Ground Station
  • Tasks
    • Fix communication issues
    • Add dynamic trim control
flight control software1

2424

Flight Control Software
  • Task 1: Fix communication issues
    • Implemented dynamic communication frequencies
  • Task 2: Manual Trim Setting
    • Implemented dynamic trim setting
flight control software2

2525

Flight Control Software
  • Final Status
    • Communication to and from the ground station is far more reliable
    • Able to dynamically update trim
    • Able to dynamically update communications frequencies
sensors
Sensors

26

  • Purpose
    • Provides the flight control software information about the helicopter’s position and orientation
  • Initial Status
    • IMU
      • Working
    • Altimeter
      • Microcontroller code was about half-written
      • Flight control code not started
      • Untested breadboard prototype
sensors1
Sensors

27

  • Initial Status
    • Compass
      • Code believed to be near complete
      • Not calibrated
      • Crashing flight control software
    • Sonar
      • Code believed to be near complete
      • Not calibrated
      • Not tested
    • GPS
      • No support for GPS module in flight control software
sensors altimeter
Sensors - Altimeter

28

  • What was done
    • Software design
    • Initial flight control code
    • Began testing hardware
sensors compass
Sensors - Compass

29

  • What was done
    • Resolved flight control instabilities
    • Calibrated in software (without engine noise)
sensors sonar
Sensors - Sonar

34

  • What was done
    • Calibrated in hardware
    • Bug fixing
slide37
GPS
  • Not able to fix onto satellites
  • Gets a fix when plugged into a laptop computer
  • Magnetic interference with compass
sensors2
Sensors

38

  • Final Status
    • Altimeter
      • Breadboard prototype nearly verified
      • Software is about half-implemented
    • Compass
      • Works in-lab
      • Suffers from magnetic interference from engine
    • Sonar
      • Reliable from 6 inches to about 18 feet (as opposed to the 20 foot specification)
    • GPS
      • Not reliable when used with helicopter SBC
filtering
Filtering
  • Purpose
    • Remove unwanted noise from sensor data
  • Initial Status
    • Some work had been done with RC, moving average, and Kalman filters
    • Performance was unsatisfactory, nothing actually implemented in code
  • Tasks
    • Select a practical filtering model
    • Design and implement filter code
    • Characterize sensor data
    • Calculate filter parameters
filtering1
Filtering
  • Selecting a filtering model
    • Initially considered Kalman filter
      • Delivers very good performance and is the filter of choice for UAVs
      • Developing a process model for a helicopter is very difficult
    • Eventually decided on digital Butterworth filter
      • Well understood
      • Easy to implement in software
      • Computationally less expensive than alternatives (e.g. FIR filter)
slide45

Filtering

  • Filter Coefficients can vary with system changes
    • Store in XML file, parse at initialization
  • XML parser modified to read array of values
    • Tested by creating sample XML file, reading array of values and checking output with file
filtering2
Filtering

46

  • Final Status
    • ButterworthFilter class has been tested for correctness
    • IMU, Sonar, and Compass data have been characterized
    • Filters for the IMU, Sonar, and Compass are implemented in the flight control software
manual override
Manual Override

47

  • Purpose
    • Switch between manual and computer control
  • Initial Status
    • Hardware designed, built, and tested for single servo channel
      • Later Flight Test results in relay chatter
  • Tasks
    • Build circuits for remaining servo channels
initial manual override
Initial Manual Override

48

  • Design
    • Hardware used was RCATS relay for each servo channel
  • Tasks
    • Built for Pitch and Roll channels
  • Problems
    • Chatter causing undesired switch
      • Noise on PWM Control Signal
revised manual override
Revised Manual Override

50

  • Design
    • ElectroDynamics manual override switch
      • Multiple NASA successful missions
  • Status
    • Hardware installed and tested for Roll and Pitch servo channels
  • Tasks
    • Implement for all servo channels independently
revised manual override1
Revised Manual Override

51

6V DC

Servo

Servo Controller

Spektrum Receiver

revised manual override2
Revised Manual Override

52

  • Watchdog
    • Needs pulse signal < 2s between edges
  • Pontech SV203 Servo Controller output
flight test results1
Flight Test Results
  • First Flight Test (April 19th 2008)
    • Achieved 3 second autonomous hover on roll servo channel with excessive drifting
  • Second Flight Test (September 20th 2008)
    • Chatter on manual overrides resulted in an unstable system - Unable to fly
    • Pilot determined the helicopter was mechanically unstable
flight test results2
Flight Test Results
  • Third Flight Test (October 16th 2008)
    • Achieved >30 second hover on roll servo channel with slight drifting
    • Chatter on manual overrides prevented testing of pitch servo channel
  • Final Flight Test (November 21st 2008)
    • Hover on roll and pitch servo channels
    • Compass not reliable enough to attempt yaw servo channel
conclusions1
Conclusions
  • Made significant progress on autonomous hover
    • Fell short of initial goal of autonomous hover on all 5 servos
      • Two servos require the altimeter to be functional
  • Introduce filtering into the system on IMU, Sonar, and Compass
  • Advanced Sonar and Compass functionality
conclusions2
Conclusions
  • Many enhancements to Ground Station
    • Graphing, Data Logging, Communications
  • Increased communication reliability between Ground Station and Flight Control software
lessons learned
Lessons Learned
  • Noise, Noise, Noise
    • Lab tests cannot prove a working system
  • Cannot be over-specialized with such a complex system
  • Prioritize tasks based on goals
the future
The Future
  • Achieve Full Independent Servo Channel Hover
    • Complete Sensors/Filtering
      • Altimeter
    • Remove Drift from Hover
      • GPS
    • Hover on 3 remaining servo channels
  • Achieve Full Hover
    • Couple servo channels
  • Movement and Navigation
demonstration
Demonstration

http://www.public.iastate.edu/~karlsvec/filedump/Videos/MicroCART%20Flight%20Test%2011-21-2008.avi