Difference between revisions of "F16: E-Bike"

From Embedded Systems Learning Academy
Jump to: navigation, search
(Schedule)
(Objectives & Introduction)
Line 18: Line 18:
 
== Objectives & Introduction ==
 
== 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.
 
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.
1. Allow a motor to propel a bike forward when a button is pressed
+
<br>
2. Create a battery driven power circuit that can support an embedded system and can be charged without a wall adapter
+
1. Allow a motor to propel a bike forward when a button is pressed <br>
 +
2. Create a battery driven power circuit that can support an embedded system and can be charged without a wall adapter <br>
 
3. Show the user the current status of their battery
 
3. Show the user the current status of their battery
  

Revision as of 00:46, 7 December 2016

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.

E-Bike

Abstract

Electrics bicycles are the future of transportation. Our project helps build on this future by advancing electric bike design. We have two motors on the bike. One generates power to charge an on-board battery, while the other propels the bike forward as requested by user input. This allows the user to reach steady transportation speeds without the need to pedal constantly. A more effective future of transportation based on renewable energy is the way forward for us and the planet.

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.
1. Allow a motor to propel a bike forward when a button is pressed
2. Create a battery driven power circuit that can support an embedded system and can be charged without a wall adapter
3. Show the user the current status of their battery

Team Members & Responsibilities

  • Nicholas Randhawa
    • Power circuit
    • A/D Converter
  • Alejandro Puente
    • Display battery level to external screen over UART
  • Shared Responsibilities
    • Hardware mounting
    • GPIO drivers
    • RTOS tasks to integrate everything

Schedule

Week # Proposed Completion Date Task Status Actual Completion Date
1 10/28 Finalize project idea and determine hardware requirements Completed 10/28
2 11/04 Order parts Completed 11/04
3 11/11 Draw schematics Completed 11/11
4 11/18 Get A/D on LPC working

Output reading to an external screen

A/D Completed

Screen is a WIP

11/18 (A/D)

TBD (Screen)

5 11/25 Get MOSFETs working with motors

Finalize power circuit build

WIP TBD
6 12/02 Create RTOS tasks to integrate A/D with the MOSFETs Completed 11/29
7 12/09 Mount hardware and begin testing Pending TBD
8 12/16 Fix defects, finish report, and clean up code Pending TBD

Parts List & Cost

Give a simple list of the cost of your project broken down by components. Do not write long stories here.

Part # Part Name Quantity Cost ($)
1 Bike 1 Free
2 LCD Screen 1 10
3 36V, 10Ah Rechargable Battery 1 250
4 Push Button 1 Free
5 Speed Controller 1 10
6 SJOne Board 1 80
7 Circuit Case 1 Cost
8 Screen and controller case 1 Cost
9 MOSFET 2 4
10 250W DC Motor 1 50
11 50W AC Generator 1 30
12 Boost Converter 1 10
13 Buck Converter 1 10
14 Terminal Block 2 Cost
15 Resistors 4 Free
16 Diodes 2 Free
17 Nuts 5 Free
18 U-Bracket 2 Cost
19 Small PCB 1 1
20 8mm Motor Arbor Adapter 1 8
21 Skateboard Wheel 1 Free

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.

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.

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.

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.

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:

My Issue #1

Discuss the issue and resolution.

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

References

Acknowledgement

Any acknowledgement that you may wish to provide can be included here.

References Used

List any references used in project.

Appendix

You can list the references you used.