Thanks,
Michael. Table updated. Nice to have the
v.b.consumption metric (er, so now I need a new example
script!), and apologies on the Twizy spelling.
"OBDII Mappable" is a recognition that not every metric
can be mapped to an OBDII PID. I don't support Strings,
for example, except for the VIN and ECU Name. Also,
items that are numeric values representing a state are,
perhaps, not so useful assuming the OBDII device is a
HUD or something similar. I could be persuaded
otherwise, though there are far easier ways to log such
things. Anyway, Mappable column is whether one can map
the metric to a PID or not. There's no enforcement code
behind it, so it's just a reminder. The overall warning
on metric / PID compatibility is in the Setup section of
the OBDII ECU chapter.
To Geir, I got your
spreadsheet, but on my system the Kia Soul column is
blank (also Leaf and Twizy as expected), but the rest
are fine. I am using LibreOffice... Do I have a file
compatibility problem?
Thanks,
Greg
Michael Balzer wrote:
… and here's the one for the Twizy (note: single 'z').
I've also added my latest addition (v.b.consumption)
and the two ECU flag descriptions, and I've added a
separate sheet for the Twizy specific metrics.
What do you mean by "OBD mappable"?
Regards,
Michael
Am 03.04.2018 um 22:02
schrieb Geir Øyvind Vælidalo:
Greg,
Here’s the updated spreadsheet with
available metrics for the Kia Soul.
Geir
<OVMS Metrics Table.xlsx>
_______________________________________________
OvmsDev mailing list
OvmsDev@lists.openvehicles.com
http://lists.openvehicles.com/mailman/listinfo/ovmsdev
--
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
_______________________________________________
OvmsDev mailing list
OvmsDev@lists.openvehicles.com
http://lists.openvehicles.com/mailman/listinfo/ovmsdev