1 / 26

Team 3: Calvin Cruise

Team 3: Calvin Cruise. Adaptive Cruise Control System ENGR 340 May 1, 2007. Relieving Highway Driving Frustration. Outline. Introduction of Project Current Results Costs Conclusion Questions. Introduction • Results • Costs • Conclusion • Questions. Introduction of project.

enye
Télécharger la présentation

Team 3: Calvin Cruise

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Team 3: Calvin Cruise Adaptive Cruise Control System ENGR 340 May 1, 2007 Relieving Highway Driving Frustration

  2. Outline • Introduction of Project • Current Results • Costs • Conclusion • Questions Introduction • Results • Costs • Conclusion • Questions

  3. Introduction of project

  4. Introduction – The Team Nate Sportel • Erik Barton • Bryan Bandstra • Chris Vonk • Nate Barker Introduction • Results • Costs • Conclusion • Questions

  5. Introduction – Project Overview Design an Adaptive Cruise Control System • Detects the distance and speed of forward vehicles • Changes the cruise speed of the equipped vehicle • Information displayand push buttoninterface Introduction • Results • Costs • Conclusion • Questions

  6. Design Changes • Original Design • Current Design Introduction • Results • Costs • Conclusion • Questions Hardware Driven Controller – VHDL J1850 BUS – Control USB – Comm Touch screen – UI Software Driven Controller – NIOS ADC & DAC – Control RS232 – Comm VGA/LCD – GUI

  7. Current Results

  8. Block Diagram Introduction • Results • Costs • Conclusion • Questions

  9. Completed Components • ADC • Interrupts sytem • DAC • Controls car cruise system Introduction • Results • Costs • Conclusion • Questions

  10. Completed Components Introduction • Results • Costs • Conclusion • Questions

  11. Completed Components Presents: Introduction • Results • Costs • Conclusion • Questions

  12. Introduction • Results • Costs • Conclusion • Questions

  13. Completed Components • Controller • Software – written and tested • Radar • Successfully tested with PC terminal, Vehicle Spy Introduction • Results • Costs • Conclusion • Questions

  14. Completed Components • J1850 • Successfully tested with PC terminal, Vehicle Spy • Interrupts • Handled and functional • LCD Screen • Works on DE2 board • Displays the speed/distance of vehicles ahead • Displays the user set time for following distance • Allows user to change following distance using switches Introduction • Results • Costs • Conclusion • Questions

  15. Completed Components • RS232 • Hardware fully functional • Terminal, neoVI, RXD/TXD, RTS/CTS • neoVI • RAW API opened and communications with external devices (car, radar) • VGA • Can write to screen using hardware • Timer • Timer interrupt functional (at 20 ms) Introduction • Results • Costs • Conclusion • Questions

  16. Work in Progress Components • RS232/neoVI • Communication using software currently unavailable due to a timing issue • VGA • As a SOPC component, can not currently talk with software Introduction • Results • Costs • Conclusion • Questions

  17. Costs

  18. Costs Prototype: • 2 neoVI $3000 • Radar $2200 • DE2 board $500 • PCB $200 • FCC License $60 • LCD/Touchscreen $300 • Connectors/Cables $50 • TOTAL $6310 Introduction • Results • Costs • Conclusion • Questions

  19. Costs Production System: • Processor w/ CAN $400 • Radar $2200 • PCB $200 • Touchscreen $150 • TOTAL $2950 Introduction • Results • Costs • Conclusion • Questions

  20. Conclusion

  21. Conclusion How the Product Could be Improved: • Better processor • No development board • More memory, faster • Implement brakes • Improve range of allowable speeds • Make use of acceleration readings and other vehicle information given to us by the radar Introduction • Results • Costs • Conclusion • Questions

  22. Conclusion How the Product Could be Improved: • Have a CAN input controller to eliminate need for neoVI • Develop stability reading on the car to send yaw • Should allow for better handling of curves, low grade hills Introduction • Results • Costs • Conclusion • Questions

  23. Conclusion Acknowledgements: • JCI • Stew Gray • Mark Michmerhuizen • Sheetal Patel • Intrepid • David Crockett • DaimlerChrysler • Rene Nieuwenhuizen Introduction • Results • Costs • Conclusion • Questions

  24. Conclusion Acknowledgements: • TRW Bill VanderRoest • Calvin College • Professor VanderLeest • Professor Brouwer • Professor Hekman • Bob DeKraker • Chuck Holwerda Introduction • Results • Costs • Conclusion • Questions

  25. Questions?

More Related