1 / 17

Indycar Telemetry Data Acquisition Interface

Indycar Telemetry Data Acquisition Interface. University of Waterloo Systems Design SD 542. Danny Ho 97 140232 March 25, 2002. Presentation Summary. Introduction to Telemetry Functional Decomposition Initial Design 1 st Prototype User Feedback & Limitations 2 nd Prototype

sorena
Download Presentation

Indycar Telemetry Data Acquisition Interface

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. Indycar TelemetryData Acquisition Interface University of Waterloo Systems Design SD 542 Danny Ho 97 140232 March 25, 2002

  2. Presentation Summary • Introduction to Telemetry • Functional Decomposition • Initial Design • 1st Prototype • User Feedback & Limitations • 2nd Prototype • Industry Comparison • Conclusions

  3. Objective of Telemetry • Ensure driver safety • Monitor vehicle performance • Use data history to adapt car to track 1st place finish !

  4. The Flow of Data Onboard sensors Radio transmitters Pit lane

  5. Functional Decomposition

  6. Initial Design

  7. Focus of 1st Interface • Functional Visual Basic for Application implementation • Simulate alarm conditions • Provide real-time monitoring scenario

  8. 1st Prototype

  9. User Feedback & Limitations • Alarm salience was adequate • Visual representation did not conform well to mental model • Graphical forms lacked frame of reference (scale) • Certain graphical elements were hard to notice

  10. Final Prototype

  11. Final Prototype

  12. Final Prototype

  13. Industry Comparison

  14. EFI Technologies

  15. PI Research

  16. Conclusions • Proposed system: • offers richer, more iconic representation of data • Provides better cognitive association • Improves upon salience and mental model • Industry systems: • more data intense • data display in the strictest sense • targeted towards expert engineers (experienced!)

  17. Q & A • How critical is alarming? • Shouldn’t experts know what to look at? • Analogical or Iconic? • Is industry software too bland?

More Related