Difference between revisions of "S14: Asset Management and Location System"
Proj user7 (talk | contribs) (→Schedule) |
Proj user7 (talk | contribs) |
||
| Line 90: | Line 90: | ||
== Parts List & Cost == | == Parts List & Cost == | ||
Give a simple list of the cost of your project broken down by components. Do not write long stories here. | Give a simple list of the cost of your project broken down by components. Do not write long stories here. | ||
| + | |||
| + | * [https://www.sparkfun.com/products/12580 SparkFun Bluetooh Mate Gold] - $64.95 | ||
| + | ** Alternative: [https://www.sparkfun.com/products/12582 SparkFun BlueSMiRF Gold] - $64.95 | ||
== Design & Implementation == | == Design & Implementation == | ||
Revision as of 00:38, 18 April 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.
S14: Asset Management and Location System
Abstract
The ultimate vision of this project is to develop an asset management and location system to compete with The Tile App. There are two major components to the Tile solution: the tracker and the application. The tracker is small low-power embedded system that can be attached to an object. The application is primarily a user interface that provides visual feedback to guide a user to a specified tag.
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
- Akash Ayare
- Pardeep Badhan
- Talha Ilyas
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# | Date | Planned | Actual |
|---|---|---|---|
| 1 | 3/6 | Wiki Project Page Creation, Schedule | Preliminary Scheduling |
| 2 | 3/13 | Research on Bluetooth and Zigbee radio technologies | Comparison on Bluetooth and Zigbee range and power consumption |
| 3 | 3/20 | Order parts (Bluetooth Modules, battery fixtures), research RSSI | Team registered with GitLab. Team trained on Git workflow and branching methodology. |
| 4 | 3/27 | Interface Bluetooth Modules | Researched Class 1 vs Class 2 BT modules. Ordered Class 1 BT version 2 modules. |
| 5 | 4/3 | Achieve basic Bluetooth communication - exchange "hello" messages between modules | Basic connectivity achieved. Perusing data sheet. |
| 6 | 4/10 | Implement RSSI | Start to read RSSI value and adjust other BT settings from PC. |
| 7 | 4/17 | Demonstrate the change in RSSI value with respect to proximity changes | Added a task and command to directly interface BT module from SJSU One board. |
| 8 | 4/24 | Integrate RSSI with visual indicator (e.g. LEDs) and further tweak corresponding proximity values | Completed? Problems Encountered? |
| 9 | 5/1 | Packaging, battery installation, and testing. Possible expansion of feature-set | Completed? Problems Encountered? |
| 10 | 5/8 | Demo | Completed? Problems Encountered? |
Parts List & Cost
Give a simple list of the cost of your project broken down by components. Do not write long stories here.
- SparkFun Bluetooh Mate Gold - $64.95
- Alternative: SparkFun BlueSMiRF Gold - $64.95
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.
