Difference between revisions of "Infotainment System"
Steve Cable (Talk | contribs) (→Architecture) |
Steve Cable (Talk | contribs) (→Architecture) |
||
| Line 24: | Line 24: | ||
== Architecture == | == Architecture == | ||
| − | [[File:Infotainment genr functional diagram.jpg | + | <html> |
| + | <div style="float:right; max-width:50%;"> | ||
| + | </html> | ||
| + | [[File:Infotainment genr functional diagram.jpg]] | ||
| + | <html> | ||
| + | </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. | 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:42, 23 May 2019
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
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.
