Difference between revisions of "F16: Autonomous Nautical System"
(→Autonomous Nautical Systems for Ocean Transit and Survey (ANSOTAS)) |
m (→= Implementation) |
||
| Line 128: | Line 128: | ||
Show your software design. For example, if you are designing an MP3 Player, show the tasks that you are using, and what they are doing at a high level. Do not show the details of the code. For example, do not show exact code, but you may show psuedocode and fragments of code. Keep in mind that you are showing DESIGN of your software, not the inner workings of it. | Show your software design. For example, if you are designing an MP3 Player, show the tasks that you are using, and what they are doing at a high level. Do not show the details of the code. For example, do not show exact code, but you may show psuedocode and fragments of code. Keep in mind that you are showing DESIGN of your software, not the inner workings of it. | ||
| − | + | == Implementation == | |
This section includes implementation, but again, not the details, just the high level. For example, you can list the steps it takes to communicate over a sensor, or the steps needed to write a page of memory onto SPI Flash. You can include sub-sections for each of your component implementation. | This section includes implementation, but again, not the details, just the high level. For example, you can list the steps it takes to communicate over a sensor, or the steps needed to write a page of memory onto SPI Flash. You can include sub-sections for each of your component implementation. | ||
Revision as of 02:32, 21 December 2016
Contents
Grading Criteria
- How well is Software & Hardware Design described?
- How well can this report be used to reproduce this project?
- Code Quality
- Overall Report Quality:
- Software Block Diagrams
- Hardware Block Diagrams
- Schematic Quality
- Quality of technical challenges and solutions adopted.
Autonomous Nautical Systems for Ocean Transit and Survey (ANSOTAS)
Abstract
Constructing an autonomous navigation system responsive to GPS and Tilt Compass feedback to form and track trajectories to a given location. Low power, and observant system.
Objectives & Introduction
Show list of your objectives. This section includes the high level details of your project. You can write about the various sensors or peripherals you used to get your project completed.
Team Members & Responsibilities
- Angel Hernandez-Perez
GPS control
- Fayek Wahhab
Servo control
- Abraham Carrillo
Motor Control
Schedule
Table 1. Schedule
| Week# | Date | Tasks | Actual |
|---|---|---|---|
| 1 | 10/8 | Decide on boat hull based on the amount of devices
we planned to us. Purchased motor, servo, and battery accordingly |
Completed
Brushed DC motor powered by Electronic Speed controller was purchased. |
| 2 | 11/4 | Intercept the pwm signals issued by a remote
control for steering and speed throttling. Decode these signals over time to identify which values produce what kind of effect to the driving system. |
Completed
Using a logic analyzer did not work the way we planned An oscilloscope was used but only to prove that this was not necessary since the motor and servo reacts to PWM as any other motor or servo. |
| 3 | 11/25 | Make separate compass, gps, and pwm tasks | Completed
These tasks are a simple tasks demoing the functionality |
| 4 | 12/02 | Link separate task outputs together using navigation task. | Completed
Debug the steering and motor control commands issued by the state of the navigation task state machine. |
| 5 | 12/16 | Revise gps task to give only needed information and use
all task outputs in the navigation task |
Completed
Buggy and needs to check for invalid information using checksum |
| 6 | 12/20 | Update the wiki page | Completed
Clean up exceptions in the land demo program |
