Difference between revisions of "F17: Tata Nano"
Proj user8 (talk | contribs) (→Project Schedule) |
Proj user8 (talk | contribs) (→Project Schedule) |
||
Line 91: | Line 91: | ||
| | | | ||
* Agree on control system architecture | * Agree on control system architecture | ||
+ | * Design the mechanical structure of the car | ||
*<font color="green">Research and study various LCD modules</font> | *<font color="green">Research and study various LCD modules</font> | ||
*<font color="green">Start Basic Android Application development</font> | *<font color="green">Start Basic Android Application development</font> | ||
Line 102: | Line 103: | ||
| 10/17/2016 | | 10/17/2016 | ||
| | | | ||
+ | * Build the mechanical structure of the car | ||
*<font color="blue">Interface servo motor and ESC to the SJone board</font> | *<font color="blue">Interface servo motor and ESC to the SJone board</font> | ||
*<font color="CARROT">Interface GPS and Compass sensor to the micrcontroller</font> | *<font color="CARROT">Interface GPS and Compass sensor to the micrcontroller</font> | ||
Line 112: | Line 114: | ||
*<font color="clouds">Design the barebones basic functionality of the algorithm. Create a skeleton code.</font> | *<font color="clouds">Design the barebones basic functionality of the algorithm. Create a skeleton code.</font> | ||
*<font color="blue">Design software filter to filter CAN messages required for motor controller.</font> | *<font color="blue">Design software filter to filter CAN messages required for motor controller.</font> | ||
− | |||
| Completed | | Completed | ||
|- | |- | ||
Line 119: | Line 120: | ||
| 10/24/2016 | | 10/24/2016 | ||
| | | | ||
− | * | + | * Making tentative DBC file containing communication messages of the entire system |
+ | * Mounted all boards on the car | ||
* Interface all nodes over Can bus and coordinate order and status message transfers between Master and Nodes. PCAN interface should be built to view & test CAN messages via Busmaster. | * Interface all nodes over Can bus and coordinate order and status message transfers between Master and Nodes. PCAN interface should be built to view & test CAN messages via Busmaster. | ||
− | *<font color="blue"> | + | *<font color="clouds">Decide on the CAN ids and the priorities of the CAN messaged for various nodes.</font> |
+ | *<font color="blue">Study and research about motor feedback RPM sensor.</font> | ||
*<font color="blue">Read the CAN messages to display on the LCD connected to the SJ One board.</font> | *<font color="blue">Read the CAN messages to display on the LCD connected to the SJ One board.</font> | ||
*<font color="clouds">Set up CAN communication between the sensor,motor and the master. Test for correct data transmission.</font> | *<font color="clouds">Set up CAN communication between the sensor,motor and the master. Test for correct data transmission.</font> | ||
+ | | Completed | ||
+ | |- | ||
+ | ! scope="row"| 7 | ||
+ | | 10/24/2016 | ||
+ | | 10/31/2016 | ||
+ | | | ||
+ | * Integrate all hardware to the RC car, including power supplies from batteries. Test self powered prototype with the goal of controlling forward, reverse, left and right with start/stop command from the phone app. Test & fix basic integration bugs. | ||
*<font color="orange">Interface back sensor and test all the sensors together. | *<font color="orange">Interface back sensor and test all the sensors together. | ||
*<font color="orange">Debug and fix any issues.</font> | *<font color="orange">Debug and fix any issues.</font> | ||
Line 129: | Line 139: | ||
*<font color="orange">Integrate sensors with other nodes via CAN and test the sensor values while the car is on the move.</font> | *<font color="orange">Integrate sensors with other nodes via CAN and test the sensor values while the car is on the move.</font> | ||
*<font color="orange">The master should have reliable data from sensors by now.</font> | *<font color="orange">The master should have reliable data from sensors by now.</font> | ||
− | |||
*<font color="blue">Send signals to the motor controller from another CAN Node to control speed and steering using CAN interface.</font> | *<font color="blue">Send signals to the motor controller from another CAN Node to control speed and steering using CAN interface.</font> | ||
*<font color="blue">Creating necessary display messages and graphics related to the I/O modules.</font> | *<font color="blue">Creating necessary display messages and graphics related to the I/O modules.</font> | ||
*<font color="clouds">Design the algorithm to process the data received from the sensors and motors by the master.</font> | *<font color="clouds">Design the algorithm to process the data received from the sensors and motors by the master.</font> | ||
*<font color="green">Integrate Google Map, Get Longitude and Latitude data from the position where Marker is placed, Get important data of other nodes from CAN bus.</font> | *<font color="green">Integrate Google Map, Get Longitude and Latitude data from the position where Marker is placed, Get important data of other nodes from CAN bus.</font> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
*<font color="blue">Integrating and testing motor & I/O controller with other nodes.</font> | *<font color="blue">Integrating and testing motor & I/O controller with other nodes.</font> | ||
*<font color="clouds">Extend the algorithm to control the motors along with the obstacle information received from the sensors.</font> | *<font color="clouds">Extend the algorithm to control the motors along with the obstacle information received from the sensors.</font> |
Revision as of 23:38, 24 October 2017
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.
PAGE UNDER CONSTRUCTION
Tata Nano
Self-Navigation Vehicle Project
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
- Master Controller
- Manan Mehta
- Shivam Chauhan
- Geographical Controller
- Kalki Kapoor
- Aditya Deshmukh
- Communication Bridge + Android Application + LCD
- Ashish Lele
- Venkat Raja
- Motor and I/O Controller
- Aditya Choudari
- Shashank Iyer
- Sensor Controller
- Pushpender Singh
- Hugo Quiroz
- Module Level Testing
- Manan Mehta
- Shashank Iyer
Project Schedule
Legend: Motor & I/O Controller , Master Controller , Communication Bridge Controller, Geographical Controller, Sensor Controller , Team Goal
Week# | Start Date | End Date | Task | Status |
---|---|---|---|---|
1 | 09/12/2016 | 09/19/2016 |
|
Completed |
2 | 09/19/2016 | 09/26/2016 |
|
Completed |
3 | 09/26/2016 | 10/03/2016 |
|
Completed |
4 | 10/03/2016 | 10/10/2016 |
|
Completed |
5 | 10/10/2016 | 10/17/2016 |
|
Completed |
6 | 10/17/2016 | 10/24/2016 |
|
Completed |
7 | 10/24/2016 | 10/31/2016 |
|
|
8 | 11/30/2016 | 11/7/2016 |
|
|
9 | 11/7/2016 | 11/14/2016 |
|
|
10 | 11/14/2016 | 11/21/2016 |
|
|
11 | 11/21/2016 | 11/28/2016 |
|
|
12 | 11/22/2016 | 11/28/2016 |
|
|
13 | 11/29/2016 |
|
- |
Parts List & Cost
Item# | Part Desciption | Vendor | Qty | Cost |
---|---|---|---|---|
1 | RC Car - Traxxas 1/10 Slash 2WD | Amazon | 1 | $189.95 |
2 | Traxxas 2872X 5000mAh 11.1V 3S 25C LiPo Battery | Amazon | 1 | $56.99 |
3 | Traxxas 7600mAh 7.4V 2-Cell 25C LiPo Battery | Amazon | 1 | $70.99 |
4 | Traxxas 2970 EZ-Peak Plus 4-Amp NiMH/LiPo Fast Charger | Amazon | 1 | $35.99 |
5 | Bluetooth Module HC-05 | Amazon | 1 | $8.99 |
6 | 4D systems 32u LCD | 4D systems | 1 | $41.55 |
7 | LV Maxsonar EZ0 Ultrasonic sensors | Robotshop | 5 | $124.75 |
8 | LIDAR Sensor | Robotshop | 1 | $190 |
9 | Ultimate GPS breakout | Adafruit | 1 | $49.95 |
10 | CAN tranceivers | Microchip Samples | 10 | Free |
11 | SJOne Boards | Provided by Preet | 5 | $400.0 |
DBC File Link
https://gitlab.com/shivam5594/Autonomous-car/blob/embedded/common_dbc/243.dbc
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.