Difference between revisions of "Infotainment System"

Revision as of 23:00, 23 May 2019 (view source) Steve Cable (Talk | contribs) (→‎Architecture) ← Older edit		Revision as of 23:02, 23 May 2019 (view source) Steve Cable (Talk | contribs) Newer edit →
Line 44:		Line 44:
	=== Display/input pages ===		=== Display/input pages ===
	This is where it gets interesting.		This is where it gets interesting.
		+
		+	== UDP Stream Input ==
		+
		+	== UDP Stream Output ==

---

Revision as of 23:02, 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, instrument panel displays, heads-up displays (HUDs), etc.

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

The core of the Infotainment system is written in Node.js. It establishes an Express web server, then uses Socket.IO to manage connections to different control and/or display surfaces. Because display, audio and control surfaces are coded as web pages served up by the Express server, the Infotainment system creates a device-agnostic ecosystem, where any number of devices on any combination of platforms can participate (assuming they support a semi-modern browser).

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.

UDP Stream Input

UDP Stream Output