Difference between revisions of "F17: Viserion"

From Embedded Systems Learning Academy
Jump to: navigation, search
(→‎Schedule)
(→‎Schedule)
Line 99: Line 99:
 
*<font color="blue"> Maintain the speed based on feedback for uphill and downhill</font>
 
*<font color="blue"> Maintain the speed based on feedback for uphill and downhill</font>
 
*<font color="blue"> Improve the trajectory of the car using algorithm based on speed and directions</font>
 
*<font color="blue"> Improve the trajectory of the car using algorithm based on speed and directions</font>
−
*<font color="blue"> Interface the LCD with microcontroller and do basic display of text</font>
 
 
*<font color="orange"> Stress test front sensors in different environment conditions indoor, outdoor and compare data. Also change different angles for sensors and find best angles for most reliable data and maximum coverage. </font>
 
*<font color="orange"> Stress test front sensors in different environment conditions indoor, outdoor and compare data. Also change different angles for sensors and find best angles for most reliable data and maximum coverage. </font>
 
*<font color="CARROT">Start development of GPS and Compass modules and document the efforts and ways to test the algorithm.</font>
 
*<font color="CARROT">Start development of GPS and Compass modules and document the efforts and ways to test the algorithm.</font>
Line 124: Line 123:
 
| 11/19/2017
 
| 11/19/2017
 
|
 
|
−
+
*<font color="clouds"> Interface the LCD with micro controller and do basic display of text</font>
−
*<font color="blue"> Display speedometer, destination distance, time to reach and warnings</font>
+
*<font color="clouds"> Display speedometer, longitude and direction values</font>
 
*<font color="orange"> Prepare design and possibly try to finish 3D printing or figure out some other hardware solution for sensor mount for final car design. </font>
 
*<font color="orange"> Prepare design and possibly try to finish 3D printing or figure out some other hardware solution for sensor mount for final car design. </font>
 
*Verify the connections and working of mounted components.
 
*Verify the connections and working of mounted components.
Line 147: Line 146:
 
| 12/01/2017
 
| 12/01/2017
 
|
 
|
 +
 
*Sensors should be mounted, working and tested by now. Work on fine tuning and final SW touch.
 
*Sensors should be mounted, working and tested by now. Work on fine tuning and final SW touch.
 
*Integrate multiple nodes over CAN and perform integration and system testing.
 
*Integrate multiple nodes over CAN and perform integration and system testing.

Revision as of 23:45, 31 October 2017

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.

Viserion Team RC Car

Abstract

This section should be a couple lines to describe what your project does.

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

  • Aakash Menon
  • Ajinkya Mandhre
  • Aniket Dali
  • Dheemanth Bangalore Vishwanatha
  • Jean Madassery
  • Omkar Kale
  • Pratap Kishore Desai
  • Pratap Ramachandran

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.

Legend: Motor & I/O Controller , Master Controller , Communication Bridge Controller, Geographical Controller, Sensor Controller , Team Goal , Team PCB, , Team Android

Week# Start Date End Date Task Status
1 10/09/2017 10/15/2017
  • Research previous projects wiki page, gather useful information.
  • Discus about roles and study data sheet of the required parts and list down minimum two parts for each required function.
  • Setup Git and slack accounts and verify that access is provided to all the team mates.
 Done
2 10/16/2017 10/22/2017
  • Design Hardware layout for the project, schematic shall identify all the modules, ports and the pins interfaced.
  • Design sensor and motor board's schematic in eagle PCB.
  • Design data flow diagram for all the software exchanges between the modules and the master.
  • Complete DBC file based upon the design data flow diagram and share the file via GIT repo.
  • Study about GPS and Compass calibration .
  • Interface motor and drive using Preet's PWM driver API. Find different levels of speed and direction.
  • Interface one sonic sensor to the sensor controller. Receive data and calculate distance. Write send, receive and MIA functions to be able to perform basic CAN communication.
  • Study Android application software and approaches from previous projects and document the required features being provided by the application.
  • Order finalized Components.
 Done
3 10/23/2017 29/10/2017
  • Start interfacing received components to respective Nodes and do a superficial testing of components.
  • Design GPS/Compass, Bluetooth and master board's schematic in eagle PCB.
  • Identify and document best approach to calibrate Compass.
  • Experiment on duty suitable for direction and speed of the motors
  • Communicate with Master and set speed and directions.
  • Interface RPM sensor and calculate speed in KPH
  • Interface all three front sonic sensor to the sensor controller. Apply filtering to get reliable data and send data to Master Controller.
  • Document Android approaches and decide on how to design the app and fix the protocol to exchange data with Bluetooth module.
 Done
4 10/30/2017 11/05/2017
  • Maintain the speed based on feedback for uphill and downhill
  • Improve the trajectory of the car using algorithm based on speed and directions
  • Stress test front sensors in different environment conditions indoor, outdoor and compare data. Also change different angles for sensors and find best angles for most reliable data and maximum coverage.
  • Start development of GPS and Compass modules and document the efforts and ways to test the algorithm.
  • Test can bus communication by mounting master, sensor and motor modules and transmitting master related commands.
5 11/06/2017 11/12/2017
  • Finish Bearing Angle Calculation.
  • Mount the parts on off shelf PCB for Demo 1 and verify the wiring connections and verify that CAR is ready for the demo,
  • Develop framework to display data based on messages received from CAN bus
  • Interface back sensor, receive, filter and send data. All sensors should be working properly by now and master should be getting stable values even while car is on the move.
  • Finish development of algorithm for Compass & GPS calibration and verify that the direction obtained from the modules with that of any off shelf smartphone's Compass.
6 11/13/2017 11/19/2017
  • Interface the LCD with micro controller and do basic display of text
  • Display speedometer, longitude and direction values
  • Prepare design and possibly try to finish 3D printing or figure out some other hardware solution for sensor mount for final car design.
  • Verify the connections and working of mounted components.
7 11/20/2017 11/25/2017
  • Connect individual module with master on the physical CAN bus and test the exchanges.
  • Fix the bugs.
  • Verify the accuracy obtained from GPS and compass module with expected accuracy, fix bugs if required.
  • Mount sensors on new/final hardware solution, position them properly and test again received data while car is in move.
  • Test Android Application with dummy data if nodes are not ready.
8 11/26/2017 12/01/2017
  • Sensors should be mounted, working and tested by now. Work on fine tuning and final SW touch.
  • Integrate multiple nodes over CAN and perform integration and system testing.
  • If solution for filtering sensor data is not finalized and made perfect by now, finish it immediately.
  • Fix bugs, if any.
9 12/03/2017 12/08/2017
  • If android application and Bluetooth module exchanges are ready, perform outdoor system testing.
  • Analyze, document the bugs, cross verify the bug.
  • Fix the bugs in individual or integrated software/hardware.
  • Interface Head lights and turn them ON based on light sensor value.
  • Perform integration or unit testing to verify that bug is fixed.
10 12/10/2017 12/12/2017
  • Perform round 2 of system testing.
  • Start documenting project report by collaborating artifacts produced during project development.
  • Fix the bugs in system testing.
11 12/13/2017 12/16/2017
  • Perform round 3 of system testing.
  • Work on unfinished project report documentation.
  • Fix the bugs in system testing.
12 12/17/2017 12/19/2017
  • Perform round 4 of system testing.
  • Fix the bugs in system testing.
  • Record a video to demonstrate project working and features.
  • Complete Documentation of wiki page.
13 12/20/2017
  • Ready for Demo.


Parts List & Cost

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

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:

<Bug/issue name>

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.

Retrieved from "http://socialledge.com/sjsu/index.php?title=F17:_Viserion&oldid=40209"