[Ovmsdev] OVMS Leaf Support

Tue Oct 15 22:03:58 HKT 2013

CarCAN bus is 512kbps on standard OBD-II pins. An OVMS OBD-II cable should be able to connect.

Here are the parameter check lists, for the virtual vehicle.

I’ve filled in what I know, but really am not familiar with the vehicle.

Can someone more knowledgeable go through this, and fill-in / correct where appropriate?

Regards, Mark.

Development Checklists

You can use these checklists to know what vehicle parameters the OVMS system supports, and how you can map a specific vehicle to these.

Parameter

Purpose

Vehicle Support Notes

Vehicle Identification

car_type

Vehicle type identified

 NL

car_vin

Vehicle VIN

OBD-II PID has this, but messy to get

Parameter

Purpose

Vehicle Support Notes

GPS Status

Vehicle GPS

Does the vehicle have a built-in GPS? If so, complete the following.

 NO. Use OVMS GPS

car_gpslock

Set to record GPS lock

 - 

car_stale_gps

Denotes GPS data staleness

 -

car_latitude

Latitude of the vehicle

 -

car_longitude

Longitude of the vehicle

 -

car_direction

Direction of the vehicle

 -

car_altitude

Altitude of the vehicle

 -

Parameter

Purpose

Vehicle Support Notes

Tire Pressure Monitoring System

TPMS

Does the vehicle have a TPMS? If so, complete the following.

car_stale_tpms

Denotes TPMS data staleness

 OVMS countdown timer on last updated

car_tpms_t

The temperatures of each wheel

 -

car_tpms_p

The pressures of each wheel

 ID 385 (brad370)

Parameter

Purpose

Vehicle Support Notes

Driving Status

car_doors1 [bit7]

Set if the car ignition is ON

 ID 216? (brad370)

car_speed

The speed of the vehicle

 ID 280 B6,B7 (brad370)

car_trip

The vehicle trip counter

 ??

car_odometer

The vehicle odometer

 ID 5C% (CARcan)

Parameter

Purpose

Vehicle Support Notes

Vehicle Environment

car_stale_ambient

Ambient temperature staleness

 OVMS countdown timer on last updated

car_ambient_temp

Ambient temperature

 ID 510 B8 (CARcan)

car_stale_temps

Other Temperature staleness

 OVMS countdown timer on last updated 

car_tpem

Temperature of the PEM

car_tmotor

Temperature of the MOTOR

 ID 551 B1 (brad370)

car_tbattery

Temperature of the BATTERY

car_doors1 [bit 0]

Set if front left door OPEN

 ID 60D (brad370)

car_doors1 [bit 1]

Set if front right door OPEN

 ID 60D (brad370)

car_doors2 [bit 6]

Set if bonnet is OPEN

car_doors2 [bit 7]

Set if trunk is OPEN

 ID 60D (brad370)

car_doors1 [bit 2]

Set if charge port is OPEN

car_doors1 [bit 6]

Set if handbrake is ON

car_doors2 [bit 5]

Set if headlights ON

 ID 358 B8 (brad370)

car_doors3 [bit 1]

Set if vehicle is AWAKE (or if not supported just follow ignition)

car_doors2 [bit 4]

Set if valet mode is ENABLED

car_doors2 [bit 3]

Set if vehicle is LOCKED

 ID 60D (driver+passenger door) 

car_lockstate

4=locked, 5=unlocked (deprecated)

 ID 60D (driver+passenger door)

car_doors4 [bit 2]

Set if alarm SOUNDING

car_time

Time (in seconds)

 internal OVMS counter

car_parktime

Time (seconds) vehicle parked

 count based on ignition state

Parameter

Purpose

Vehicle Support Notes

Battery Status

car_SOC

State of charge percentage

 ID 5B3 contains SOH and Gids, but how to convert to SOC%?

car_idealrange

Ideal range

car_estrange

Estimated range

car_cac100

Calculated Amp Hour capacity

  ID 5B3 contains SOH and Gids, but how to convert to CAC?

Parameter

Purpose

Vehicle Support Notes

Charging Status

car_doors1 [bit 3]

Set if pilot signal ON

car_doors1 [bit 4]

Set if vehicle CHARGING

car_linevoltage

Line voltage while charging

car_chargecurrent

Line current while charging

car_chargemode

Vehicle Mode

car_chargestate

Charging state

car_chargesubstate

Charging sub-state

car_chargelimit

Charge current limit

car_chargeduration

Charge duration (minutes)

car_chargekwh

Charge kWh put into battery

car_chargefull_minsremaining

Mins remaining for full charge

car_chargelimit_minsremaining

Mins remaining for limited charge

car_chargelimit_rangelimit

Desired range for limited charge

car_chargelimit_soclimit

Desired SOC% for limited charge

car_stale_timer

Charge timer staleness

car_timermode

Charge timer mode

car_timerstart

Charge timer schedule

Regards, Mark.

On 15 Oct, 2013, at 1:00 pm, Mark Webb-Johnson <mark at webb-johnson.net> wrote:

> Barry,
> 
> Thanks for the history. I really think we can get what we need from the single car CAN bus.
> 
> I'll extract the relevant sections from the developers guide tonight, and post them here. The first step is to see which of those 'virtual car' pieces of information are available on the car CAN bus, and see if they match-up.
> 
> I really would like to see a dump (and dump) of the car CAN bus, as well as a trace from the leaf spy program. The captioned google docs spreadsheet for leaf can bus messages is quite confusing - it would be good to be able to compare that against what is actually seen on the bus.
> 
> Regards, Mark.
> 
> P.S. I'm trying to find a friendly Leaf owner in Hong Kong to co-operate with this. There are 200+ Leafs here, and no carwings coverage at all, but most are in government service and relatively few in private hands.
> 
> On 15 Oct, 2013, at 11:45 am, Barry Gershenfeld <gbarry42 at gmail.com> wrote:
> 
>> Early development assumed you had to get the EV info from the EV-CAN buss.  Somewhere during the development of Leaf Spy they kept finding desirable info on the car-CAN buss and so eventually determined that all if could be gotten from the car-CAN.  As a bonus, the ELM dongle no longer has to be modified to read the EV buss.
>> 
>> The original reporting efforts started with the "GID" meter, and the early work involved Gary G. building a data recorder as well as a program to analyze the logs.  I'm sure that's precisely what you have in mind as well.  There were downloadable logs--he invited others to install the analyzer and try to find meaningful messages therein.  But as it was early development, they were probably gotten from the EV-CAN.  I don't know if any more recent logs from the car CAN buss are posted.
>> 
>> As a matter of fact, I suspect Gary would be happy to have his analyzing program used.  It would be nice output the data into the same format that it uses.  Or at least write a converter.
>> 
>> I naturally have some interest, being a LEAF owner and PIC hacker.  I'll see if I can make head or tail of the developer's guide.
>> 
>>  * * *
>> 
>> On Mon, Oct 14, 2013 at 7:04 PM, Mark Webb-Johnson <mark at webb-johnson.net> wrote:
>> Developers guide is here:
>> 
>> https://github.com/markwj/Open-Vehicle-Monitoring-System/blob/master/docs/OVMS_Development.pdf?raw=true
>> 
>> I would rather the actual development discussions take place here on this list. A lot of smart people here, with experience getting these vehicle modules working.
>> 
>> The biggest concern for me is whether we can get everything we need off one CAN bus...
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.teslaclub.hk
>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
> 
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.teslaclub.hk/pipermail/ovmsdev/attachments/20131015/b37e98d7/attachment-0001.html>