Power Meter Presentation

1,036 views

Published on

Published in: Education, Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,036
On SlideShare
0
From Embeds
0
Number of Embeds
135
Actions
Shares
0
Downloads
14
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Power Meter Presentation

  1. 1. Team 3 Power Meter<br />James Aitkenhead, Nicole Ogden, Matt Quantz<br />
  2. 2. The Product<br />Targets customers who want to monitor energy statistics with an easy-to-use graphical interface<br />Our widget will help you to be more aware of your energy usage, saving you time and money<br />
  3. 3. Mechanical Design<br />
  4. 4. Mechanical Design<br />
  5. 5. Project Management<br />We used a combination of traditional and agile project management.<br />It would be very hard to manage a project that has never been done before using a strictly traditional approach (hard to estimate task durations)<br />
  6. 6. Resource Scoping<br />FPGA<br />Different versions of Nios II<br />Software<br />IP Blocks<br />Internal Power Supply<br />Outsourcing Consultants<br />Other items considered for design<br />
  7. 7. Code Repository<br />Used TortoiseSVN for Project Version Control<br />Directory Structure:<br />C Code<br />C Scripts<br />C Test<br />RTL Code<br />RTL Scripts<br />RTL Test<br />Documentation<br />This Directory Structure Supports Reusability<br />
  8. 8. Code Reviews<br />We did not implement formal code reviews<br />We collaborated between team members for writing and testing code<br />
  9. 9. Benefits of RTL and C Coding Guidelines<br />Makes Code More Readable<br />Makes Code More Reusable<br />Makes Code More Portable<br />Increases Productivity of Code Reviews<br />Allows Auto-Documentation (Doxygen)<br />
  10. 10. IP Design and Reuse<br />IP Component Reuse saves time in a project<br />Component Reusability should be paramount in a design<br />Reusability brings the product to market faster<br />
  11. 11. Hardware to Software Interface<br />A register map is a listing of all the memory registers used in the project, and their address<br />The register map is used by everyone from design to layout to verification engineers<br />This makes it important to create the map early in the project<br />The register map can be created manually, or there is software available to automate the process<br />
  12. 12. Functional Verification<br />Direct testing was used<br />Code Coverage was 100%<br />
  13. 13. Cost Estimate (Break-Even Cost)<br />
  14. 14. Lessons Learned<br />Don’t wait until the last minute to add documentation<br />Read the datasheets for little “Easter eggs” which could delay<br /> progress<br />Divide tasks more evenly between team members<br />
  15. 15. Roadblocks<br />We struggled to re-create last quarter’s touch screen interface<br />We struggled to learn how to use all the project tracking tools effectively<br />We struggled with the opto-isolator interface between the MCP3909 and the FPGA<br />The SPI interface was odd to work with<br />
  16. 16. Conclusions<br />We successfully interfaced with the MCP3909 Evaluation Board<br />We successfully displayed the measured data on the 16x2 character LCD<br />This was a fun project with numerous practical applications<br />With more time, we would implement a wireless data transfer, uploading the data to the Internet, or both<br />Also with more time we were going to try to implement Ethernet to connect the device to the internet and communicate to websites like: “Google Powermeter,” and “Microsoft hohm;” to relay instant power usage for our area.<br />

×