[MeeGo-ivi] IVI Car-Systems APIs
jeremiah.foster at pelagicore.com
Fri Aug 5 10:48:25 UTC 2011
On Fri, Aug 5, 2011 at 12:56 AM, Romain KUNTZ <rkuntz at us.toyota-itc.com>wrote:
> On Aug 4, 2011, at 2:21, Jeremiah Foster wrote:
> > On Wed, Aug 3, 2011 at 5:35 PM, Jussi Vänskä <jussi.vanska at nomovok.com>
> > On 08/03/2011 06:01 PM, Jeremiah Foster wrote:
> >> for tier 1 developers
> >> - Qt API
> >> This excludes ECU to ECU communication. Tier 1's would likely never
> accept this.
> > Nor will any legislator approve MeeGo based systems to be used in any
> sort of safety critical or even safety aware systems. Crafting an API for
> automotive control systems is not the issue here, as the software stack
> won't get certificated for use in safety critical systems.
> > Really? What gives you that impression? Ford uses SYNC from Microsoft,
> that is on the road already. Do you feel MeeGo IVI is not intended to be a
> commercial OS in a head unit? What is its niche then?
> Ford SYNC is not about safety. I think you can forget about any safety
> critical-related things from MeeGo IVI. Getting information from the various
> bus is fine, but internode communication or talking to ECU won't certainly
> happen from the head-unit. I highly doubt that car manufacturers would allow
My understanding is that in some specific instances the Head Unit will
indeed need to talk to the vehicle. I'm not pointing to safety critical
systems here however, but pointing out in a rather general way that the Qt
API is likely way to abstracted from the vehicle's controls to be enough to
fulfill requirements, including OEM and Tier 1 requirements. I worry that
limiting MeeGo IVI to only Qt APIs will likely make it not suitable for a
production Head Unit which makes the entire MeeGo IVI enterprise less
Why would people invest time and energy in something that wasn't going to be
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the MeeGo-ivi