Difference between revisions of "S14: Data Acquisition using CAN bus"
Proj user9 (talk | contribs) (→Parts List & Cost) |
Proj user9 (talk | contribs) (→Schedule) |
||
| Line 41: | Line 41: | ||
| 2/25 | | 2/25 | ||
| 2/29 | | 2/29 | ||
| − | | Order sensors | + | | |
| + | * Order sensors | ||
| + | * System design | ||
| Completed. Waiting for the parts. | | Completed. Waiting for the parts. | ||
|- | |- | ||
| Line 59: | Line 61: | ||
| 3/22 | | 3/22 | ||
| 3/28 | | 3/28 | ||
| − | |||
| | | | ||
| + | * Build MPU-9150 data processing algorithm | ||
| + | * Can use Arduino for debugging platform | ||
|- | |- | ||
! scope="row"| 6 | ! scope="row"| 6 | ||
| Line 92: | Line 95: | ||
| | | | ||
|} | |} | ||
| − | |||
| − | |||
== Parts List & Cost == | == Parts List & Cost == | ||
Revision as of 10:24, 6 March 2014
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.
Project Title
Abstract
Our project is to implement a high speed data acquisition system using CAN and storing the data into the SD card.
Objectives & Introduction
Our idea is to use the on board accelerometer and gyroscope together as a motion/gesture sensor to identify the motion then it will send to the other board via CAN bus. We are planning to use 9 degree of freedom MPU-9150 sensor for doing precise movement tracking. Recognized movement will trigger predefined tasks and transmit to Anroid phone via UART-Bluetooth module. More sensors will also be added to do data acquisition.
Team Members & Responsibilities
- Shweta Bohare
- Mradula Nayak
- Heng Zhang
- Driver Development
- All Team
- FreeRTOS Software Design
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.
| Week# | Start Date | End Date | Task | Actual |
|---|---|---|---|---|
| 1 | 2/25 | 2/29 |
|
Completed. Waiting for the parts. |
| 2 | 3/1 | 3/7 | Interface with sensors | Completed? |
| 4 | 3/15 | 3/21 | Develop CAN communication and SPI microSD I/O | |
| 5 | 3/22 | 3/28 |
| |
| 6 | 3/29 | 4/11 | Test MPU-9150 data processing algorithm | |
| 7 | 4/12 | 4/18 | Design Android App to receive/send signal via Bluetooth | |
| 8 | 4/19 | 4/25 | Implement motion tracking algorithm on ARM-android system | |
| 9 | 4/26 | 5/5 | Testing and remove bugs, further enhancements | |
| 10 | 5/8 | 5/8 | Demo |
Parts List & Cost
| Parts | Cost | Comment |
|---|---|---|
|
SJ One Board[1] |
$80.00 x3 |
Each board uses for different functions |
MPU-9150[2] |
$39.95 x1 |
9 DOF motion sensor |
</tr>
|
BC-127[3] |
$49.95 x1 |
Bluetooth module to UART/SPI |
|
Total Cost |
$$$$$ |
Keep it low |
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
Send me your zipped source code and I will upload this to SourceForge and link it for you.
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.
