Difference between revisions of "Infotainment System"

Revision as of 22:33, 23 May 2019 (view source) Steve Cable (Talk | contribs) (→‎Architecture) ← Older edit		Revision as of 22:33, 23 May 2019 (view source) Steve Cable (Talk | contribs) (→‎Architecture) Newer edit →
Line 24:		Line 24:
	== Architecture ==		== Architecture ==
−	[[:File:/../images/infotainment_genr_functional_diagram.jpg|right|100px|caption]]	+	[[File:images/infotainment_genr_functional_diagram.jpg|right|100px|caption]]
	At it's core, the Infotainment System can be logically broken down into three parts: the host script, the audio handler(s), and display/input pages.		At it's core, the Infotainment System can be logically broken down into three parts: the host script, the audio handler(s), and display/input pages.

---

Revision as of 22:33, 23 May 2019

NADS has developed an extensible architecture to model interactive displays in simulator vehicles. These displays support touch screens, and the application logs the user’s interaction data synchronized with the miniSim data acquisition system.

Applications include infotainment systems and instrument panel displays. The standard system available with miniSim models a typical OEM infotainment system including the following functionality:

• Radio (requires internet connection)
• MP3 playback
• Navigation (NADS Springfield map only)
• Platform Independent (iOS, Android, Windows, Raspberry Pi)

• 
• 
• 
• 
• 
• 
• 

Architecture

At it's core, the Infotainment System can be logically broken down into three parts: the host script, the audio handler(s), and display/input pages.

Host script

This is blah blah

Audio handler(s)

By default, a single audio page (infotainment_audio.htm) is included. This page can handle 3 channels of stereo playback:

• Media playback
• Alert playback (temporarily mutes media playback on play)
• Notify playback

Display/input pages

This is where it gets interesting.