Difference between revisions of "F17: Viserion"

From Embedded Systems Learning Academy
Jump to: navigation, search
(→‎Schedule)
Line 40: Line 40:
 
! scope="col"| End Date
 
! scope="col"| End Date
 
! scope="col"| Task
 
! scope="col"| Task
 +
! scope="col"| Actual Completion Date / Notes
 
! scope="col"| Status
 
! scope="col"| Status
 
|-
 
|-
Line 50: Line 51:
 
*<font color="black"> Setup Git and slack accounts and verify that access is provided to all the team mates.
 
*<font color="black"> Setup Git and slack accounts and verify that access is provided to all the team mates.
 
| Done
 
| Done
 +
|
 
|-
 
|-
 
! scope="row" | 2
 
! scope="row" | 2
Line 64: Line 66:
 
*<font color="purple"> Study Android application software and approaches from previous projects and document the required features being provided by the application.
 
*<font color="purple"> Study Android application software and approaches from previous projects and document the required features being provided by the application.
 
*<font color="black"> Order finalized Components.</font>
 
*<font color="black"> Order finalized Components.</font>
−
| Done
+
| Done on time except
 +
*<font color="grey">PCB design was changed to only one PCB that will gather all controllers and have Can Bus on it.
 +
|
  
 
|-
 
|-
Line 79: Line 83:
 
*<font color="orange"> Interface all three front sonic sensor to the sensor controller. Apply filtering to get reliable data and send data to Master Controller.  
 
*<font color="orange"> Interface all three front sonic sensor to the sensor controller. Apply filtering to get reliable data and send data to Master Controller.  
 
*<font color="purple">Document Android approaches and decide on how to design the app and fix the protocol to exchange data with Bluetooth module.
 
*<font color="purple">Document Android approaches and decide on how to design the app and fix the protocol to exchange data with Bluetooth module.
−
| Done
+
| Done on time except
 +
*<font color="grey">Basic PCB design is done
 +
*<font color="orange"> Filtering was not applied at this time
 +
|
  
 
|-
 
|-
Line 92: Line 99:
 
*<font color="clouds">Test can bus communication by mounting master, sensor and motor modules and transmitting master related commands.</font>
 
*<font color="clouds">Test can bus communication by mounting master, sensor and motor modules and transmitting master related commands.</font>
 
*<font color="black">Mount the parts on off shelf PCB for Demo 1 and verify the wiring connections and verify that CAR is ready for the demo, </font>
 
*<font color="black">Mount the parts on off shelf PCB for Demo 1 and verify the wiring connections and verify that CAR is ready for the demo, </font>
 +
|
 
|
 
|
  
Line 105: Line 113:
 
*<font color="black"> Car should now move without hitting "any" obstacle when powered on. Car should be able to take a reverse if required.
 
*<font color="black"> Car should now move without hitting "any" obstacle when powered on. Car should be able to take a reverse if required.
 
</font>
 
</font>
 +
|
 +
*<font color="orange"> Back sensor was not yet interfaced. Filtering applied for front sensors.
 
|
 
|
  
Line 117: Line 127:
 
*<font color="purple">Design basic Android application UI, which can verify that the communication with BT module was successful or not </font>
 
*<font color="purple">Design basic Android application UI, which can verify that the communication with BT module was successful or not </font>
 
*<font color="black"> Fetch current longitude and latitude values from GPS modules via BT app and send all the checkpoints to the destination via BT app and BT module to master and verify the link between GPS/Compass, master and BT module and Application is working as expected.</font>
 
*<font color="black"> Fetch current longitude and latitude values from GPS modules via BT app and send all the checkpoints to the destination via BT app and BT module to master and verify the link between GPS/Compass, master and BT module and Application is working as expected.</font>
 +
|
 +
*<font color="grey">PCB design not finished yet.
 +
*<font color="orange"> Back sensor interfaced.
 
|
 
|
  
Line 128: Line 141:
 
*<font color="black"> If the link between Geo, BT, master and Motor module is working, perform outdoor system testing. </font>
 
*<font color="black"> If the link between Geo, BT, master and Motor module is working, perform outdoor system testing. </font>
 
|  
 
|  
 +
*<font color="grey">PCB design finished and main PCB board ordered
 +
*<font color="orange"> Still waiting for sensor mounts 3D printing to be finished.
 +
|
  
 
|-
 
|-
Line 136: Line 152:
 
*<font color="blue"> Connect battery output to ADC channel and read back the battery parameters. </font>
 
*<font color="blue"> Connect battery output to ADC channel and read back the battery parameters. </font>
 
*<font color="orange"> Interface Head lights and turn them ON based on light sensor value. </font>
 
*<font color="orange"> Interface Head lights and turn them ON based on light sensor value. </font>
 +
|
 +
*<font color="grey">Sensor breakout PCB design and ordered
 
|
 
|
  
Line 147: Line 165:
 
*<font color="black">Start documenting project report by collaborating artifacts produced during project development. </font>
 
*<font color="black">Start documenting project report by collaborating artifacts produced during project development. </font>
 
*<font color="black">Fix the bugs in system testing. </font>
 
*<font color="black">Fix the bugs in system testing. </font>
 +
|
 
|
 
|
  
Line 157: Line 176:
 
*<font color="black"> Start documenting project report by collaborating artifacts produced during project development.</font>
 
*<font color="black"> Start documenting project report by collaborating artifacts produced during project development.</font>
 
*<font color="black"> Fix the bugs in system testing.</font>
 
*<font color="black"> Fix the bugs in system testing.</font>
 +
|
 
|
 
|
  
Line 167: Line 187:
 
*<font color="black"> Work on unfinished project report documentation.</font>
 
*<font color="black"> Work on unfinished project report documentation.</font>
 
*<font color="black"> Fix the bugs in system testing.</font>
 
*<font color="black"> Fix the bugs in system testing.</font>
 +
|
 
|
 
|
  
Line 178: Line 199:
 
*<font color="black"> Record a video to demonstrate project working and features.</font>
 
*<font color="black"> Record a video to demonstrate project working and features.</font>
 
*<font color="black"> Complete Documentation of wiki page. </font>
 
*<font color="black"> Complete Documentation of wiki page. </font>
 +
|
 
|
 
|
  
Line 187: Line 209:
 
*<font color="black"> Ready for Demo.</font>
 
*<font color="black"> Ready for Demo.</font>
 
|
 
|
−
 
+
|
  
 
|}
 
|}

Revision as of 06:39, 1 December 2017

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 Actual Completion Date / Notes Status
1 10/09/2017 10/15/2017
  • Research previous projects wiki page, gather useful information.
  • Discuss 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 on time except
  • PCB design was changed to only one PCB that will gather all controllers and have Can Bus on it.
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 cycle 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 on time except
  • Basic PCB design is done
  • Filtering was not applied at this time
4 10/30/2017 11/05/2017
  • Interface RPM sensor and measure Speed.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 software modules for 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.
  • Mount the parts on off shelf PCB for Demo 1 and verify the wiring connections and verify that CAR is ready for the demo,
5 11/06/2017 11/12/2017
  • Finish Bearing Angle Calculation.
  • Control the Car's speed on detection of obstacle.
  • 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.
  • Car should now move without hitting "any" obstacle when powered on. Car should be able to take a reverse if required.
  • Back sensor was not yet interfaced. Filtering applied for front sensors.
6 11/13/2017 11/19/2017
  • Interface the LCD with micro controller and do basic display of text
  • Prepare design and possibly try to finish 3D printing or figure out some other hardware solution for sensor mount for final car design.
  • Share Gerber files with the PCB fabrication house and order 2 PCB.
  • Design basic Android application UI, which can verify that the communication with BT module was successful or not
  • Fetch current longitude and latitude values from GPS modules via BT app and send all the checkpoints to the destination via BT app and BT module to master and verify the link between GPS/Compass, master and BT module and Application is working as expected.
  • PCB design not finished yet.
  • Back sensor interfaced.
7 11/20/2017 11/25/2017
  • Display speedometer, longitude and direction values
  • Mount sensors on new/final hardware solution, position them properly and test again received data while car is in move.
  • If the link between Geo, BT, master and Motor module is working, perform outdoor system testing.
  • PCB design finished and main PCB board ordered
  • Still waiting for sensor mounts 3D printing to be finished.
8 11/26/2017 12/01/2017
  • Connect battery output to ADC channel and read back the battery parameters.
  • Interface Head lights and turn them ON based on light sensor value.
  • Sensor breakout PCB design and ordered
9 12/03/2017 12/08/2017
  • Display the battery parameters on LCD.
  • Perform round 1 of system testing.
  • Start documenting project report by collaborating artifacts produced during project development.
  • Fix the bugs in system testing.
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=40363"