Difference between revisions of "F16: The-Nine"
Proj user8 (talk | contribs) (→Obstacle Detection Systems) |
Proj user8 (talk | contribs) (Ultrasonic testing) |
||
| Line 353: | Line 353: | ||
Include sub-sections that list out a problem and solution, such as: | Include sub-sections that list out a problem and solution, such as: | ||
| + | |||
| + | ==== Ultrasonic sensors ==== | ||
| + | |||
| + | ===== RS-232 testing ===== | ||
| + | |||
| + | The MaxBotix LV-MaxSonar-EZ1 (P/N# MB1010) has several interfaces used to indicate the distance to an obstacle that it has sensed. One of the simplest is a RS-232 output which is enabled by grounding the BW pin or leaving it unconnected (floating). The output is logic-level compatible with RS-232 (where a logic '1' is 0V and a logic '0' is Vcc) but not voltage-level compatible. MaxBotix designed the RS-232 output like this to allow direct connection to a RS-232 compliant serial port, but it means the logic levels are inverted with respect to the LPC1758 which has no on-chip provisions for inverting the logic level. Therefore an inverter (such as the 74LVC1G04) is required between the TX output of the MB1010 and the LPC1758's UART RX input for proper operation. | ||
=== My Issue #1 === | === My Issue #1 === | ||
Revision as of 18:57, 21 October 2016
Contents
- 1 Project Title
- 2 Abstract
- 3 Objectives & Introduction
- 4 Project Schedule Overview
- 5 Team Members & Responsibilities
- 6 Parts List & Cost
- 7 Bluetooth Communications
- 8 Application & Control Interface
- 9 Obstacle Detection Systems
- 10 Localization and Positioning (GPS)
- 11 Propulsion Systems and Speed Tracking
- 12 Master Control Systems
- 13 Conclusion
- 14 Project Video
- 15 Project Source Code
- 16 References
Project Title
The-Nine: Self Driving 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.
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.
Project Schedule Overview
| Task # | Start Date | End Date | Task Description | Status | Actual End Date |
|---|---|---|---|---|---|
| 1 | 9/14/2016 | 9/20/2016 | Research Project Components and Read Previous Reports | Completed | |
| 2 | 9/21/2016 | 9/27/2016 | Set up Version Control System and Basic Project Documentation | Completed | |
| 3 | 9/28/2016 | 10/04/2016 | Order Project Components and Discuss Project Implementation | Completed | |
| 4 | 10/05/2016 | 10/19/2016 | Individual Prototyping and Module Design | Completed | |
| 5 | 10/20/2016 | 10/27/2016 | Status Update: Demoing first round of Prototyping to the group | In Progress | |
| 6 | 10/28/2016 | 11/18/2016 | Adding a level of complexity to designs: Interfacing Motor, Sensor, GPS, and Bluetooth Modules with the Master Controller over CAN bus | In Progress | |
| 7 | 11/19/2016 | 11/25/2016 | Integration Testing between Modules, System Validation | In Progress | |
| 8 | 11/26/2016 | 12/02/2016 | Overall System Optimization | In Progress | |
| 9 | 12/03/2016 | 12/09/2016 | Finalization, Preparing for Demonstration | In Progress |
Team Members & Responsibilities
Application & Control Interface
- Khalil Estell
Bluetooth Communications
Master Control Systems
- Steven Hwu
- Adam Iglesias
Obstacle Detection Systems
- Charles MacDonald
- John Strube
Localization and Positioning (GPS)
- Sara Sepasian
Propulsion Systems and Speed Tracking
- Derek Tran
- Matthew Boyd
Parts List & Cost
Give a simple list of the cost of your project broken down by components. Do not write long stories here.
| Item # | Part Description | Vendor | QTY | Cost |
|---|---|---|---|---|
| 1 | RC Car | 1 | ||
| 2 | SJSUOne Board | Preet Kang | 1 | $80.00 |
| 3 | HC-06 Bluetooth Module | Amazon | 1 | $8.99 |
Bluetooth Communications
Schedule
| Task # | Start Date | End Date | Task Description | Status | Actual End Date |
|---|---|---|---|---|---|
| 1 | 9/21/2016 | 9/27/2016 | Research Wireless Communication Platforms | Completed | |
| 2 | 9/28/2016 | 10/04/2016 | Learn about the SJSUOne boards Wireless Interface Capability | Completed | |
| 3 | 10/05/2016 | 10/19/2016 | Order Bluetooth Module and Integrate it with SJSUOne board | In Progress | |
| 4 | 10/20/2016 | 10/27/2016 | Status Update: Demoing transmission of psuedo-data with a Mobile Application | In Progress |
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.
Application & Control Interface
Schedule
| Task # | Start Date | End Date | Task Description | Status | Actual End Date |
|---|---|---|---|---|---|
| 1 | 9/21/2016 | 9/27/2016 | |||
| 2 | 9/28/2016 | 10/04/2016 | |||
| 3 | 10/05/2016 | 10/19/2016 | |||
| 4 | 10/20/2016 | 10/27/2016 |
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.
Obstacle Detection Systems
Schedule
| Task # | Start Date | End Date | Task Description | Status | Actual End Date |
|---|---|---|---|---|---|
| 1 | 10/16/2016 | 10/23/2016 | Interface IMU and ultrasonic sensors to board. | In progress | TBD |
| 2 | 10/23/2016 | 10/30/2016 | Develop CAN interface to transmit sensor data. | Assigned | TBD |
| 3 | 10/30/2016 | 11/06/2016 | |||
| 4 | 11/06/2016 | 11/13/2016 |
Design & Implementation
The obstacle detection system covers two areas: detecting obstacles and determining vehicle orientation.
Obstacle detection is performed using ultrasonic sensors placed around the perimeter of the vehicle, concentrated at the front (three sensors) and less so in the back (one sensor) as the vehicle is primarily driven in the forward direction.
Vehicle orientation is accomplished using an inertial measurement unit, which is used to determine the speed and bearing of the vehicle.
Hardware Design
Ultrasonic sensors
Ultrasonic sensors are controlled using GPIO. The sensor consists of a trigger-input signal which causes it to emit sound at a specific frequency, and a echo-output signal which is pulsed when a reflection of the same frequency is received. The echo response is detected by the edge-sensitive GPIO interrupt, and the trigger is produced by a software-generated pulse.
Inertial measurement unit (IMU)
The IMU is a system that contains an accelerometer, magnetometer, and gyroscope. The IMU interfaces to the SJOne board using I2C.
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:
Ultrasonic sensors
RS-232 testing
The MaxBotix LV-MaxSonar-EZ1 (P/N# MB1010) has several interfaces used to indicate the distance to an obstacle that it has sensed. One of the simplest is a RS-232 output which is enabled by grounding the BW pin or leaving it unconnected (floating). The output is logic-level compatible with RS-232 (where a logic '1' is 0V and a logic '0' is Vcc) but not voltage-level compatible. MaxBotix designed the RS-232 output like this to allow direct connection to a RS-232 compliant serial port, but it means the logic levels are inverted with respect to the LPC1758 which has no on-chip provisions for inverting the logic level. Therefore an inverter (such as the 74LVC1G04) is required between the TX output of the MB1010 and the LPC1758's UART RX input for proper operation.
My Issue #1
Discuss the issue and resolution.
Localization and Positioning (GPS)
Schedule
| Task # | Start Date | End Date | Task Description | Status | Actual End Date |
|---|---|---|---|---|---|
| 1 | 9/21/2016 | 9/27/2016 | |||
| 2 | 9/28/2016 | 10/04/2016 | |||
| 3 | 10/05/2016 | 10/19/2016 | |||
| 4 | 10/20/2016 | 10/27/2016 |
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.
Propulsion Systems and Speed Tracking
Schedule
| Task # | Start Date | End Date | Task Description | Status | Actual End Date |
|---|---|---|---|---|---|
| 1 | 9/21/2016 | 9/27/2016 | |||
| 2 | 9/28/2016 | 10/04/2016 | |||
| 3 | 10/05/2016 | 10/19/2016 | |||
| 4 | 10/20/2016 | 10/27/2016 |
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.
Master Control Systems
Schedule
| Task # | Start Date | End Date | Task Description | Status | Actual End Date |
|---|---|---|---|---|---|
| 1 | 9/21/2016 | 9/27/2016 | |||
| 2 | 9/28/2016 | 10/04/2016 | |||
| 3 | 10/05/2016 | 10/19/2016 | |||
| 4 | 10/20/2016 | 10/27/2016 |
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
GitLab
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.
