Dear Josef,
I've updated IVI API pages. Please find the link below.
http://wiki.meego.com/In-
vehicle/Roadmap/API#API_Functional_Groups_and_Functions
1) Updated functions which you mentioned
Oil Temperature, Driving Mode, Generated Car Sound Mode.
For the other options, I'm not sure how to provide APIs exactly.
I hope someone would complete it later.
2) Deleted functions below.
Running Status | Compass Status Enum --> Duplicated with Qt Mobility /
QtSensors
Running Status | GPS Data - Date, Time --> Duplicated with Qt Mobility /
QtLocation
Running Status | GPS Data - Position --> Duplicated with Qt Mobility /
QtLocation
Some cars provide these information via vehicle bus. On even that case,
developer should map that information to the existing APIs.
I think we have to align with the other device branches.
3) Divided Sections
I agreed that application developer should not need to know the below.
A the same time, vehicle communication module developer should be able to
know which APIs the vehicle messages are mapped to.
In addition, we have to share the common part with the other device
projects as much as possible.
I think many part of Multimedia and Communication will be shared with
Mobility.
We need to find there is any IVI exclusive functionality.
Your comments are definitely helpful. I hope your continuous interest and
advice.
Best regards,
Justin
-----Original Message-----
From: Josef Raschen [mailto:***@googlemail.com]
Sent: Saturday, June 25, 2011 12:37 AM
To: "�����(Justin Park)"; meego-***@meego.com
Subject: Re: [MeeGo-ivi] List of Vehicle Functions
Hi Justin,
Post by Josef Raschen- light sensors
: It seems to be the same with 'Exterior Brightness'. It's for controlling
head lights or cluster light automatically.
If it's a different one, could you explain it in detail for its purpose?
You are right. I just overlooked it when reading your list. Sorry.
Post by Josef Raschen- parking sensors (and camera(s)?)
: I thought that it can be mapped with 'Obstacle Distance'. The sensors
located near rear bumpers can work to help parking also.
I have no idea that IVI need to have any API for cameras. Could you give
me some examples?
It was just an idea, because I think that MeeGo IVI API should support
camera images in some way (e.g. rear-view camera). But I do not know if
there are any plans about this.
Post by Josef Raschen- park heater
: Does it need to be added separately? In my opinion, it looks an
application feature combining 'Heater' or 'Seat Heater' with parking status.
Not separately but I think for programming the parking heater ECU by using
the infotainment it may need some additional options. Date/time of start
(or weekday for periodically activation) and duration for example.
Post by Josef Raschen- car-setup: suspension, steering, engine/gearbox
(Comfort/Auto/Sport/Eco/Manual)
: I might read that some high-end cars support similar features.
Those cars allow driver to select driving modes, and it affects on gear
shifting and suspensions.
I think that it can be added on personalization group as 'driving mode'
as like below
Personalization | Driving Mode | Enum | Comfort, Auto, Sport, Eco,
manual | Get, Noti, Set
Sounds good. The manual setting may also need an integer value.
Post by Josef Raschen- sound generator settings for electric vehicles
: It's interesting function.
I read that EV should generate car sound(noise) for pedestrians' safety
and satisfying drivers' emotion.
For second one, I guess that EV may provide this features. Is it
sufficient to define it as below?
Electric Vehicle(Personalization?)| Generated Car Sound Mode | Enum |
Normal, Quiet, Sportive | Get, Noti, Set
I think this should work. You could perhaps add an 'Off' option, even
though it probably wont be used due to safety reasons.
Post by Josef RaschenThe other topics...
- functions for telephone/handsfree
- functions for handling Radio/TV
- functions for handling CD/DVD-Changer
- handling portable media devices
- HomeLink
I agree that these topics also should be discussed by IVI WG.
But currently I'd like to focus on vehicle network functionality first.
In some cases, telephony can be provided by the other module and IVI access
it via vehicle network.
Anyhow the above functionalities usually seems to be the applications of
IVI itself.
So, it's better to consider first what features are possible when providing
APIs for the other applications.
For example, if the Navigation application provide API to set the
destination up, the other application may allow many useful use cases.
If I understand the intention of the IVI API it should not only include
functionality of the vehicle network. But it may be useful to divide the
API in serveral parts e.g.
- Car-Systems (basically the network functions you want to focus on)
- Multimedia (audio/video/radio/tv/...)
- Communication (handsfree/...)
- Sensors/Navigation (location/orientation/speed/...)
- ...
The classification of the functions should be done considering the
application programmers point of view. The programmer does not want to know
if a function is implemented using the vehicle network or by another IVI
program.
I hope I could help you with my little knowledge about automotive systems.
Josef
Post by Josef RaschenDear Josef,
Thank you for your feedback. Please review my answers.
- engine oil temperature
: I missed it. I'll add it.
- light sensors
: It seems to be the same with 'Exterior Brightness'. It's for controlling
head lights or cluster light automatically.
If it's a different one, could you explain it in detail for its purpose?
- parking sensors (and camera(s)?)
: I thought that it can be mapped with 'Obstacle Distance'. The sensors
located near rear bumpers can work to help parking also.
I have no idea that IVI need to have any API for cameras. Could you give
me some examples?
- park heater
: Does it need to be added separately? In my opinion, it looks an
application feature combining 'Heater' or 'Seat Heater' with parking status.
- car-setup: suspension, steering, engine/gearbox
(Comfort/Auto/Sport/Eco/Manual)
: I might read that some high-end cars support similar features.
Those cars allow driver to select driving modes, and it affects on gear
shifting and suspensions.
I think that it can be added on personalization group as 'driving mode'
as like below
Personalization | Driving Mode | Enum | Comfort, Auto, Sport, Eco,
manual | Get, Noti, Set
- sound generator settings for electric vehicles
: It's interesting function.
I read that EV should generate car sound(noise) for pedestrians' safety
and satisfying drivers' emotion.
For second one, I guess that EV may provide this features. Is it
sufficient to define it as below?
Electric Vehicle(Personalization?)| Generated Car Sound Mode | Enum |
Normal, Quiet, Sportive | Get, Noti, Set
The other topics...
- functions for telephone/handsfree
- functions for handling Radio/TV
- functions for handling CD/DVD-Changer
- handling portable media devices
- HomeLink
I agree that these topics also should be discussed by IVI WG.
But currently I'd like to focus on vehicle network functionality first.
In some cases, telephony can be provided by the other module and IVI access
it via vehicle network.
Anyhow the above functionalities usually seems to be the applications of
IVI itself.
So, it's better to consider first what features are possible when providing
APIs for the other applications.
For example, if the Navigation application provide API to set the
destination up, the other application may allow many useful use cases.
Best regards,
Justin
-----Original Message-----
Sent: Thursday, June 23, 2011 10:39 PM
Subject: Re: [MeeGo-ivi] List of Vehicle Functions
- engine oil temperature
- light sensors
- parking sensors (and camera(s)?)
- park heater
- car-setup: suspension, steering, engine/gearbox
(Comfort/Auto/Sport/Eco/Manual)
- functions for telephone/handsfree
- functions for handling Radio/TV
- functions for handling CD/DVD-Changer
- handling portable media devices
- sound generator settings for electric vehicles
- HomeLink
Josef Raschen
Post by =?ks_c_5601-1987?B?udrBvryxKEp1c3RpbiBQYXJrKQ==?=Hello, IVI members,
I��ve summarized and arranged vehicle functions related to vehicle
network.
Post by =?ks_c_5601-1987?B?udrBvryxKEp1c3RpbiBQYXJrKQ==?=Thanks to Joel, I could change my excel sheet to wiki xhtml.
I added my work on the existing API page. Please find the below link.
http://wiki.meego.com/In-
vehicle/Roadmap/API#API_Functional_Groups_and_Functions
Post by =?ks_c_5601-1987?B?udrBvryxKEp1c3RpbiBQYXJrKQ==?=I��m not sure that it��s the proper location. If there is more proper
location, please let me know.
I tried to summarized all possible functionalities except diagnostics.
Any ideas or comments are very welcome.
I hope that it��ll be helpful.
Best regards,
Justin
--------------------------------------------------------------
Justin(Jong-Seon)Park
AOP Gr.,S/W platformLab.,
LGElectronicsInc.
221YangJae-Dong,Seocho-Gu,Seoul137-130,Korea
Phone:+82-2-526-4183
Fax:+82-2-6912-6355
_______________________________________________
MeeGo-ivi mailing list
http://lists.meego.com/listinfo/meego-ivi
_______________________________________________
MeeGo-ivi mailing list
http://lists.meego.com/listinfo/meego-ivi