Johan Thelin
2011-06-30 08:57:09 UTC
Hello all,
I've taken the liberty of reviewing the suggested APIs at
http://wiki.meego.com/In-vehicle/Roadmap/API . My background from
automotive is powertrain (automatic transmissions and rear wheel drive
systems), and Qt-based embedded development (and a bunch of other
non-related activities).
This is a bit of nit-picking, so please take it for what it is. I did
not want to come as a newcomer and edit the wiki :-)
The specifics:
- Car Information / Engine Type - the list seems a bit limited. What
about gas vehicles, fuel cells, etc.
- Running Status / Transmission Gear Status - what about variable
ratio transmissions, and the position of automatic gear leavers (PNRD)
- Running Status / Wheel Brake - three values represented by a
Boolean, looks like an Enum to me.
- Running Status / Lights Status - what about automatic headlights, do
you want an indicator flashing on/off each time, or do you want an
automatic value there as well, not only on/off
- Running Status / Wheel Tick Sensor - here, it is interesting to know
the source / accuracy. Is it from the front axis, rear axis,
calculated from the RPM + gear or a speed sensor in the gearbox? Here,
sensor failures are commonly replaced with less reliable values in the
drive line logic.
- Personalization / Key ID - is it wise to be able to set this value?
- Personalization / Generated Car Sound Mode - what is this? seems
like something that is implemented in the IVI system from the rpm
value or such, nothing that needs to be handled like this? Also, the
modes seems rather limited, I'd rather pick from a set of "dream
cars".
- Driving Safety / Transaction Control System - what is a transaction
control system? Could be me being out-of-date, or a typo.
- Climate/Environment / HVAC Fan / Target Temperature - the resolution
(1 dgC) seems a bit rough. I believe that my current knob has 0.5 dgC
steps
- Climate/Environment / Air-Recirculation - can be automatic as well.
Regarding the type Composition, I'm not sure that I follow what it is.
I guess that it indicates a key-value collection. For many Composition
types, the number of listed available keys seem a bit limited, e.g.
Personalization / Driver Seat Position (available adjustments),
Driving Safety / Airbag Status (the airbag positions). There are more,
but I'm not sure if I've simply misinterpreted the listed available
keys as *the* available keys, rather than an example of keys.
Finally, we reach the unit management. In some places I see Celsius
and PSI being specified, in others km/mil, litre/gallon, mph/kph are
provided as alternatives. I would suggest that a fixed set of units
are used, but that conversion methods are provided. This way, the car
only has to be able to provide one set of units and the IVI-system can
adapt to driver settings. It would also mean that one could rely on
one-way conversions. There is not need to be able to convert between
all units, only from the defined source unit.
Well, that was my 0.05$. Hope to be able to contribute more!
Best regards,
Johan Thelin M.Sc.E.E.
Senior Software Developer
Pelagicore AB
Ekelundsgatan 4, 6tr, SE-411 18 Gothenburg, Sweden
Mobile: +46 (0)700 900 250
Skype: jothpelagicore
E-Mail: johan.thelin-gfIc91nka+***@public.gmane.org
I've taken the liberty of reviewing the suggested APIs at
http://wiki.meego.com/In-vehicle/Roadmap/API . My background from
automotive is powertrain (automatic transmissions and rear wheel drive
systems), and Qt-based embedded development (and a bunch of other
non-related activities).
This is a bit of nit-picking, so please take it for what it is. I did
not want to come as a newcomer and edit the wiki :-)
The specifics:
- Car Information / Engine Type - the list seems a bit limited. What
about gas vehicles, fuel cells, etc.
- Running Status / Transmission Gear Status - what about variable
ratio transmissions, and the position of automatic gear leavers (PNRD)
- Running Status / Wheel Brake - three values represented by a
Boolean, looks like an Enum to me.
- Running Status / Lights Status - what about automatic headlights, do
you want an indicator flashing on/off each time, or do you want an
automatic value there as well, not only on/off
- Running Status / Wheel Tick Sensor - here, it is interesting to know
the source / accuracy. Is it from the front axis, rear axis,
calculated from the RPM + gear or a speed sensor in the gearbox? Here,
sensor failures are commonly replaced with less reliable values in the
drive line logic.
- Personalization / Key ID - is it wise to be able to set this value?
- Personalization / Generated Car Sound Mode - what is this? seems
like something that is implemented in the IVI system from the rpm
value or such, nothing that needs to be handled like this? Also, the
modes seems rather limited, I'd rather pick from a set of "dream
cars".
- Driving Safety / Transaction Control System - what is a transaction
control system? Could be me being out-of-date, or a typo.
- Climate/Environment / HVAC Fan / Target Temperature - the resolution
(1 dgC) seems a bit rough. I believe that my current knob has 0.5 dgC
steps
- Climate/Environment / Air-Recirculation - can be automatic as well.
Regarding the type Composition, I'm not sure that I follow what it is.
I guess that it indicates a key-value collection. For many Composition
types, the number of listed available keys seem a bit limited, e.g.
Personalization / Driver Seat Position (available adjustments),
Driving Safety / Airbag Status (the airbag positions). There are more,
but I'm not sure if I've simply misinterpreted the listed available
keys as *the* available keys, rather than an example of keys.
Finally, we reach the unit management. In some places I see Celsius
and PSI being specified, in others km/mil, litre/gallon, mph/kph are
provided as alternatives. I would suggest that a fixed set of units
are used, but that conversion methods are provided. This way, the car
only has to be able to provide one set of units and the IVI-system can
adapt to driver settings. It would also mean that one could rely on
one-way conversions. There is not need to be able to convert between
all units, only from the defined source unit.
Well, that was my 0.05$. Hope to be able to contribute more!
Best regards,
Johan Thelin M.Sc.E.E.
Senior Software Developer
Pelagicore AB
Ekelundsgatan 4, 6tr, SE-411 18 Gothenburg, Sweden
Mobile: +46 (0)700 900 250
Skype: jothpelagicore
E-Mail: johan.thelin-gfIc91nka+***@public.gmane.org