Dear Grigory and Pavel, At the first time, I supposed user can download Navigation App which has its own DR feature. For this purpose, I think we need to provide some raw data for it.
Even though I'm not an expert for DR, downloadable App is hardly likely to have its own DR functionality. Because it is so vehicle specific, it is hard to make it work well for all cars. It looks natural that DR function works as a built-in middleware component, which is provided by OEM. Also, it seems reasonable that most applications are interested in the location value itself wherever and how it comes from. For the coherence between other device branches, it looks better to provide it by QtLocation. OEM might use their ways to get the most exact location and provide it via QtLocation API. Thus, I agreed that some APIs for DR can be deleted at this time if there is any other opinions. Best regards, Justin -----Original Message----- From: [email protected] [mailto:meego-ivi- [email protected]] On Behalf Of Grigory Abuladze Sent: Friday, July 22, 2011 10:42 PM To: Konopelko, Pavel (P.); [email protected] Subject: Re: [MeeGo-ivi] IVI Car-Systems APIs Pavel 1. >With regard to the "odometry" data, could you please be more specific >about: >- vehicles you are talking about (Ford, GM, VW, BMW, etc. and the >respective platform); >- instance of the CAN bus (powertrain, body, infotainment, diagnostics, >etc.) the information is available on; >- identifiers and the periodicity of the CAN signals? As you may see it is platform/manufacturer specific and source of such information should be appropriate. I could provide answers for few of manufacturer, but I am afraid I am not in position to do it. 2. >When it comes to the processing of sensor data, "the vehicle itself" is >just a combination of its control modules connected via several >networks. The radio or navigation head unit running MeeGo IVI would be >just one of these modules. Different vehicle architectures assign >specific tasks to different modules. In most cases, it is the >navigation head unit that is responsible for the vehicle position >tracking. Again what I am trying to say here - there is no reason to request wheel tic or wheel angle and use them for calculation of "something for GPS dead reckoning". If MeeGo ivi is going to use internal vehicle info for better position estimation (from navigation point of view) - it should ask for already properly "cooked" data. And we know such data is available in the vehicle. Best regards, Grigory Abuladze -----Original Message----- From: Konopelko, Pavel (P.) [mailto:[email protected]] Sent: 22 July 2011 14:06 To: Grigory Abuladze; [email protected] Subject: RE: [MeeGo-ivi] IVI Car-Systems APIs Grigory, Grigory Abuladze wrote on 2011-07-20: > Hi > > With respect to these two > http://lists.meego.com/pipermail/meego-ivi/2011-July/000651.html > http://wiki.meego.com/In-vehicle/Roadmap/API#API_Functional_Gr > oups_and_Functions > > we really don't interested in > >> Steering Wheel Angle Integer (for GPS Dead > Reckoning) Get / Noti > >> Wheel Tick Sensor Compound Left Wheel > Rotation Counter, Right Wheel Rotation Counter (for GPS Dead Reckoning) > > as vehicle has full current "odometry" information on CAN bus > which include > > - incremental displacement in mm > - runover displacement in mm > - heading angle in fraction of degree (which takes into > account possible 4 wheel steering) With regard to the "odometry" data, could you please be more specific about: - vehicles you are talking about (Ford, GM, VW, BMW, etc. and the respective platform); - instance of the CAN bus (powertrain, body, infotainment, diagnostics, etc.) the information is available on; - identifiers and the periodicity of the CAN signals? > This "odomentry" is calculated using all available > information from different vehicle sensors > > - abs tick sensors > - accelerometers > - gyroscopes > > and in some feature use > > - cameras > > Thus we definitely won't be more smart in vehicle movement > calculation (for GPS dead reckoning or what so ever) than > vehicle itself to its XXX stability controls and so on. When it comes to the processing of sensor data, "the vehicle itself" is just a combination of its control modules connected via several networks. The radio or navigation head unit running MeeGo IVI would be just one of these modules. Different vehicle architectures assign specific tasks to different modules. In most cases, it is the navigation head unit that is responsible for the vehicle position tracking. Regards, --Pavel Konopelko > > > Best regards, > > > > Grigory Abuladze > Application Solutions (Electronics and Vision) Limited. > Tel: +44 (0) 1273 409147 > > > > Please consider the environment before printing this document. > > > > This message and any attachments may be confidential and > contain privileged information. > > > > Legal Disclaimer: Any views expressed by the sender of this > message are not necessarily those of Application Solutions > (Electronics and Vision) Limited. and whilst every precaution > has been taken to ensure it is virus free, we accept no > responsibility for any damage which may occur from its use. > Information in this e-mail may be confidential and is for the > use of the intended recipient only, no mistake in > transmission is intended to waive or compromise such > privilege. Please advise the sender if you receive this > e-mail by mistake. > > > > This communication was sent from Application Solutions > (Electronics and Vision) Limited. Registered office: The > Riverside Centre, Railway Lane, Lewes, East Sussex, England, > BN7 2AQ. Company Reg. No. 6437845 > > > > _______________________________________________ MeeGo-ivi mailing list [email protected] http://lists.meego.com/listinfo/meego-ivi _______________________________________________ MeeGo-ivi mailing list [email protected] http://lists.meego.com/listinfo/meego-ivi
