Difference between revisions of "Infotainment System"

(Architecture)
 
(36 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
<html>
 
<html>
<div style="width:42%; float:right; margin:0 0 1em 1em;">
+
<iframe width="560" height="315" src="https://www.youtube.com/embed/cI14t-jA3wM?rel=0" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
<img src="../images/infotainment_home_ex.jpg" style="margin-bottom:1em;" class="img-responsive">
+
<br />
+
</div>
+
 
</html>
 
</html>
 +
 
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.  
 
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.  
  
Line 14: Line 12:
  
 
<gallery>
 
<gallery>
File:home_1b.jpg
+
[[File:home_1b.jpg|thumb|framed]]
 
File:home_2.jpg
 
File:home_2.jpg
 
File:gps_full.jpg
 
File:gps_full.jpg
Line 23: Line 21:
 
</gallery>
 
</gallery>
  
 
+
;[[Infotainment_System_-_Technical_Overview|Technical Overview]]
 
+
;[[Infotainment System - Skins|Skins]]
== Architecture ==
+
<html>
+
<div style="float:right; max-width:50%;">
+
<img src="../images/infotainment_genr_functional_diagram.jpg" style="margin-bottom:1em; margin-left:1em;" class="img-responsive">
+
</div>
+
</html>
+
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. The host script is the beating heart of the Infotainment system--for any of the other parts to work, this must be running.
+
 
+
=== 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.
+

Latest revision as of 16:02, 13 May 2022

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)
Technical Overview
Skins