Difference between revisions of "F16: Autonomous Runaway Alarm Car"

Revision as of 21:13, 20 December 2016

Grading Criteria

Project Title

Abstract

The Autonomous Runaway Alarm Car is a mobile alarm clock designed to really get people out of bed in the morning. When the alarm goes off, the Runaway Alarm Car starts moving and starts playing an annoying sound or song, forcing the user to chase it around to stop it. This car is capable of detecting obstacles and avoiding them.

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.

The objective of this project is to create a car that has the functionalities of an alarm clock and be able to avoid obstacles.

• Set a timer on the board
• Display the timer
• Produce a noise from the buzzer after the timer runs out of time
• Have the car move forward and avoid obstacles using IR sensors when the timer reaches 0
• Turn off the alarm car by pressing a button on the car

Team Members & Responsibilities

• Jonathan Chen
  • Motors and wheels
    • Constructed the car and programmed the board to run the motors
  • Implemented the logic for obstacle avoidance

• Andrew Javier
  • Implemented the timer task
  • Programmed the IR sensor task
  • Programmed the buttons to turn on the alarm car

Schedule

Show a simple table or figures that show your scheduled as planned before you started working on the project. Then in another table column, write down the actual schedule so that readers can see the planned vs. actual goals. The point of the schedule is for readers to assess how to pace themselves if they are doing a similar project.

Parts List & Cost

Design & Implementation

The design section can go over your hardware and software design. Organize this section using sub-sections that go over your design and implementation.

Hardware Design

Discuss your hardware design here. Show detailed schematics, and the interface here.

Figure 1. Hardware Block Diagram: System Overview

Hardware Interface

In this section, you can describe how your hardware communicates, such as which BUSes used. You can discuss your driver implementation here, such that the Software Design section is isolated to talk about high level workings rather than inner working of your project.

SJOne Board

Figure X. SJOne Board

L298N Dual H-Bridge

Figure X. L298N H-Bridge

Figure X. L298N H-Bridge

IR Sensor

Figure X. IR Sensor

Figure X. IR Sensor Block Diagram

Buzzer

Software Design

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.

Figure X. Algorithmic State Machine Chart

Figure X. Task Chart

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.

• ADC through the SJOne board

Testing & Technical Challenges

Describe the challenges of your project. What advise would you give yourself or someone else if your project can be started from scratch again? Make a smooth transition to testing section and described what it took to test your project.

Include sub-sections that list out a problem and solution, such as:

LCD Display

• Problem

Initially, the project called for the implementation of the 1602A v2 LCD Display to be used to display the time. The first issue with the board was the lack of datasheets available for the display. The closest datasheet for this display module was for v1.2, although that datasheet was vague. To minimize the number of pins needed for the LCD display, we decided on using it in 4-bit mode. The datasheet for v1.2 of the display showed that 4-bit mode was possible, but said little about implementation of the mode.

• Solution

As a workaround to this issue and to retain the alarm clock-like functionalities of the project, we decided to use the on board 7-segment display and LEDs to indicate the amount of time left before the alarm goes off. The 7-segment display represents the amount of minutes and the LEDs give an indication of the number of seconds before the alarm goes off. Within the final minute of the countdown before the alarm, the 7-segment display will show the time remaining before the alarm goes off and the car starts moving.

The workaround involves two tasks: one to set the timer and the other to count down to 0. In the timer set task, the user uses Switches 0 and 1 to set the time needed to elapse for the alarm to go off. Switch 0 increments the timer to 1 minute while Switch 1 resets the timer in case the user goes too far. When the user has the desired time set, Switch 2 is pressed which allows the RTOS to context switch to the countdown.

Conclusion

Conclude your project here. You can recap your testing and problems. You should address the "so what" part here to indicate what you ultimately learnt from this project. How has this project increased your knowledge?

Project Video

Upload a video of your project and post the link here.

Project Source Code

• Sourceforge Source Code Link

References

Acknowledgement

This project could not have been completed without the guidance and assistance of the following people:

• Dr. Haluk Ozemek
• Preetpal Kang
• Charles MacDonald
• Praveen Prabhakaran

References Used

List any references used in project.

Datasheets

• L298N H-Bridge
• LCD Screen
• IR Sensor

Links

• Dual H-Bridge Motor Controller Start Guide
• L298N Dual H-Bridge Motor Driver User's Guide

Appendix

You can list the references you used.