I'm a willing and eager tester. I don't have two OVMS modules, but I could get another one if you'd like another tester… Nikki. On 14 Oct 2013, at 04:50, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

Robert,

Sorry for the delay in response - I’ve been off grid parenting for the past 24 hours.

I think @Nufkin has done some preparation work, and we have a stub vehicle support file (vehicle_nissanleaf.c), but nothing working yet.

This App shows what can be done:

https://play.google.com/store/apps/details?id=com.Turbo3.Leaf_Spy_Pro

<p8xv6n5_RAmWf7Ep4eAIOqj6vZripkrr9PiegqL_w-2ofBSXUKBkJeLb9tjBj1e4jSY=h310.png> <JcBfvBo5NviN3mdrFw5Hqml-_gBqQUGBfLGHA_9AjQ3pm5nuQVv3SpBlBXHgib0VYr0=h310.png> <n7hlJo_4pxWxvxefz91_lRe2r_QeHLDXtRlYZCW9ZOleyviqUNQODqPfn-L2MzqI9J8=h310.png><q8vJL1pIFDbR0df9VCzJWXW5X7CfsQ-EdtpzzrWQtqYg5A5zPMSStvRYNsy3Kgi3pdE=h310.png>

using just the OBD-II port (I assume all the single master CAN bus, but perhaps also other buses on OBD-II).

I’m very excited by this, and more than willing to help, but I don’t have the car here so am limited in what I can do.

Can you work with @nufkin (and his other half) on this?

You would need some sort of CAN bus decoder (perhaps just an OBD-II dongle, or CAN-USB adaptor), plus an OVMS module and PICKIT for firmware download. If you use MAC OSX, the development environment is simple to setup - for windows there are a few more hoops to jump through. Lastly, a RS232-USB adaptor is useful (but not essential).

Regards, Mark.

On 13 Oct, 2013, at 4:00 pm, Robert Sharpe <robert.sharpe@evergreen-consulting.co.uk> wrote:

...

Hi, < ovmsdev-request@lists.teslaclub.hk>

Is anyone working on Leaf support?

I am interested in helping if I can and have started a discussion at http://openvehicles.com/comment/220#comment-220 to capture were we are with the Leaf.

Regards, Robert Sharpe (Technical Director) 07711 252971 http://www.facebook.com/EvergreenConsultingLtd http://twitter.com/EGCtechnical http://uk.linkedin.com/in/arsharpe

www.evergreen-consulting.co.uk

Your Plugged-in Partner

Support the future and switch to a renewable energy supplier such as Good Energy

Evergreen Consulting is the trading name of Sharpe Consultants Ltd

< /ovmsdev-request@lists.teslaclub.hk>_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

I think the leaf spy app shows what can be done. It only uses standard OBDII, with just one can bus. It could also be using the other non-can OBDII buses, but I doubt it. Shame it is not open source, but the leaf codes are pretty well documented now. Regards, Mark

On 14 Oct, 2013, at 4:00 pm, Nikki Gordon-Bloomfield <nikki@aminorjourney.com> wrote:

Oh yes, there are multiple CAN busses on the LEAF. The standard one, which is where all the data below comes from, an the EV can -- that would require some clever doodads, since both are on the same physical connector -- just different pins.

Nikki.

...

On 14 Oct 2013, at 04:50, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

Robert,

Sorry for the delay in response - I’ve been off grid parenting for the past 24 hours.

I think @Nufkin has done some preparation work, and we have a stub vehicle support file (vehicle_nissanleaf.c), but nothing working yet.

This App shows what can be done:

https://play.google.com/store/apps/details?id=com.Turbo3.Leaf_Spy_Pro

<p8xv6n5_RAmWf7Ep4eAIOqj6vZripkrr9PiegqL_w-2ofBSXUKBkJeLb9tjBj1e4jSY=h310.png> <JcBfvBo5NviN3mdrFw5Hqml-_gBqQUGBfLGHA_9AjQ3pm5nuQVv3SpBlBXHgib0VYr0=h310.png> <n7hlJo_4pxWxvxefz91_lRe2r_QeHLDXtRlYZCW9ZOleyviqUNQODqPfn-L2MzqI9J8=h310.png><q8vJL1pIFDbR0df9VCzJWXW5X7CfsQ-EdtpzzrWQtqYg5A5zPMSStvRYNsy3Kgi3pdE=h310.png>

using just the OBD-II port (I assume all the single master CAN bus, but perhaps also other buses on OBD-II).

I’m very excited by this, and more than willing to help, but I don’t have the car here so am limited in what I can do.

Can you work with @nufkin (and his other half) on this?

You would need some sort of CAN bus decoder (perhaps just an OBD-II dongle, or CAN-USB adaptor), plus an OVMS module and PICKIT for firmware download. If you use MAC OSX, the development environment is simple to setup - for windows there are a few more hoops to jump through. Lastly, a RS232-USB adaptor is useful (but not essential).

Regards, Mark.

...

On 13 Oct, 2013, at 4:00 pm, Robert Sharpe <robert.sharpe@evergreen-consulting.co.uk> wrote:

Hi, < ovmsdev-request@lists.teslaclub.hk>

Is anyone working on Leaf support?

I am interested in helping if I can and have started a discussion at http://openvehicles.com/comment/220#comment-220 to capture were we are with the Leaf.

Regards, Robert Sharpe (Technical Director) 07711 252971 http://www.facebook.com/EvergreenConsultingLtd http://twitter.com/EGCtechnical http://uk.linkedin.com/in/arsharpe

www.evergreen-consulting.co.uk

Your Plugged-in Partner

Support the future and switch to a renewable energy supplier such as Good Energy

Evergreen Consulting is the trading name of Sharpe Consultants Ltd

< /ovmsdev-request@lists.teslaclub.hk>_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

Rob, Mark (C), Nikki, If it helps, I'm happy to provide each of you with OVMS hardware FOC in return for your efforts on the Leaf development :-) Let me know what you need, [http://www.zerocarbonworld.org/images/logo.png] Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org <mailto:kevin.sharpe@zerocarbonworld.org> | www.zerocarbonworld.org<http://www.zerocarbonworld.org/> | twitter.com/zerocarbonworld<http://twitter.com/ZCWcharlie> [http://www.zerocarbonworld.org/images/email-signatures_06.png] Zero Carbon World is a UK Registered Charity #1141347 From: Robert Sharpe <robert.sharpe@evergreen-consulting.co.uk<mailto:robert.sharpe@evergreen-consulting.co.uk>> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Date: Monday, 14 October 2013 13:41 To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Subject: Re: [Ovmsdev] OVMS Leaf Support Hi Mark, This looks very interesting. I am out today but will look in more depth tomorrow. Regards, Rob ---- On Mon, 14 Oct 2013 10:08:41 +0100 Mark Webb-Johnson <mark@webb-johnson.net<mailto:mark@webb-johnson.net>> wrote ---- I think the leaf spy app shows what can be done. It only uses standard OBDII, with just one can bus. It could also be using the other non-can OBDII buses, but I doubt it. Shame it is not open source, but the leaf codes are pretty well documented now. Regards, Mark On 14 Oct, 2013, at 4:00 pm, Nikki Gordon-Bloomfield <nikki@aminorjourney.com<mailto:nikki@aminorjourney.com>> wrote: Oh yes, there are multiple CAN busses on the LEAF. The standard one, which is where all the data below comes from, an the EV can -- that would require some clever doodads, since both are on the same physical connector -- just different pins. Nikki. On 14 Oct 2013, at 04:50, Mark Webb-Johnson <mark@webb-johnson.net<mailto:mark@webb-johnson.net>> wrote: Robert, Sorry for the delay in response - I’ve been off grid parenting for the past 24 hours. I think @Nufkin has done some preparation work, and we have a stub vehicle support file (vehicle_nissanleaf.c), but nothing working yet. This App shows what can be done: https://play.google.com/store/apps/details?id=com.Turbo3.Leaf_Spy_Pro <p8xv6n5_RAmWf7Ep4eAIOqj6vZripkrr9PiegqL_w-2ofBSXUKBkJeLb9tjBj1e4jSY=h310.png> <JcBfvBo5NviN3mdrFw5Hqml-_gBqQUGBfLGHA_9AjQ3pm5nuQVv3SpBlBXHgib0VYr0=h310.png> <n7hlJo_4pxWxvxefz91_lRe2r_QeHLDXtRlYZCW9ZOleyviqUNQODqPfn-L2MzqI9J8=h310.png><q8vJL1pIFDbR0df9VCzJWXW5X7CfsQ-EdtpzzrWQtqYg5A5zPMSStvRYNsy3Kgi3pdE=h310.png> using just the OBD-II port (I assume all the single master CAN bus, but perhaps also other buses on OBD-II). I’m very excited by this, and more than willing to help, but I don’t have the car here so am limited in what I can do. Can you work with @nufkin (and his other half) on this? You would need some sort of CAN bus decoder (perhaps just an OBD-II dongle, or CAN-USB adaptor), plus an OVMS module and PICKIT for firmware download. If you use MAC OSX, the development environment is simple to setup - for windows there are a few more hoops to jump through. Lastly, a RS232-USB adaptor is useful (but not essential). Regards, Mark. On 13 Oct, 2013, at 4:00 pm, Robert Sharpe <robert.sharpe@evergreen-consulting.co.uk<mailto:robert.sharpe@evergreen-consulting.co.uk>> wrote: Hi, < ovmsdev-request@lists.teslaclub.hk<mailto:ovmsdev-request@lists.teslaclub.hk>> Is anyone working on Leaf support? I am interested in helping if I can and have started a discussion at http://openvehicles.com/comment/220#comment-220 to capture were we are with the Leaf. Regards, Robert Sharpe (Technical Director) 07711 252971 http://www.facebook.com/EvergreenConsultingLtd http://twitter.com/EGCtechnical <http://uk.linkedin.com/in/arsharpe>http://uk.linkedin.com/in/arsharpe [Evergreen Consulting] www.evergreen-consulting.co.uk<http://www.evergreen-consulting.co.uk/?utm_source=OVMSdevList&utm_medium=Email&utm_campaign=LeafOVMS> Your Plugged-in Partner Support the future and switch to a renewable energy supplier such as Good Energy<http://www.goodenergy.co.uk/affiliates/evergreen-consulting> Evergreen Consulting is the trading name of Sharpe Consultants Ltd < /ovmsdev-request@lists.teslaclub.hk<mailto:/ovmsdev-request@lists.teslaclub.hk>>_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

Hi Kevin,Thanks a lot for your kind offer.I should set expectations that I am an out of practice and slow coder, but I will do what I can to help.  I can probably help more with test, debug and coordination.So if you are still happy then, as I dont have any OVMS kit, I will need an OVMS and correct cable.Can someone point me to a developer beginner's instructions for what else is required to develop/test, e.g. programmer, sniffer, code repository login, CM procedures, etcIt helps me, and hopefully anyone else working on the project, if we can agree the breakdown of work.  As you may have already seen I have suggested a post for the Leaf development at http://www.openvehicles.com/node/111 Nikki/Mark shall we use that as a way of planning and tracking the work ?Regards,RobOn Oct 14, 2013, at 2.21PM, Nikki Gordon-Bloomfield wrote:Hi Kevin, That's very generous. Happy to test OVMS in my LEAF, so I guess another OVMS kit with a righty cable? Nikki. On 14 Oct 2013, at 13:47, Kevin Sharpe ZCW kevin.sharpe@zerocarbonworld.org> wrote: Rob, Mark (C), Nikki, If it helps, I'm happy to provide each of you with OVMS hardware FOC in return for your efforts on the Leaf development :-) Let me know what you need, Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org | www.zerocarbonworld.org | twitter.com/zerocarbonworld Zero Carbon World is a UK Registered Charity #1141347 From: Robert Sharpe robert.sharpe@evergreen-consulting.co.uk> Reply-To: OVMS Developers ovmsdev@lists.teslaclub.hk> Date: Monday, 14 October 2013 13:41 To: OVMS Developers ovmsdev@lists.teslaclub.hk> Subject: Re: [Ovmsdev] OVMS Leaf Support Hi Mark, This looks very interesting. I am out today but will look in more depth tomorrow. Regards, Rob ---- On Mon, 14 Oct 2013 10:08:41 +0100 Mark Webb-Johnson mark@webb-johnson.net> wrote ---- I think the leaf spy app shows what can be done. It only uses standard OBDII, with just one can bus. It could also be using the other non-can OBDII buses, but I doubt it. Shame it is not open source, but the leaf codes are pretty well documented now. Regards, Mark On 14 Oct, 2013, at 4:00 pm, Nikki Gordon-Bloomfield nikki@aminorjourney.com> wrote: Oh yes, there are multiple CAN busses on the LEAF. The standard one, which is where all the data below comes from, an the EV can -- that would require some clever doodads, since both are on the same physical connector -- just different pins.  Nikki.  On 14 Oct 2013, at 04:50, Mark Webb-Johnson mark@webb-johnson.net> wrote: Robert, Sorry for the delay in response - I’ve been off grid parenting for the past 24 hours. I think @Nufkin has done some preparation work, and we have a stub vehicle support file (vehicle_nissanleaf.c), but nothing working yet. This App shows what can be done: https://play.google.com/store/apps/details?id=com.Turbo3.Leaf_Spy_Pro using just the OBD-II port (I assume all the single master CAN bus, but perhaps also other buses on OBD-II). I’m very excited by this, and more than willing to help, but I don’t have the car here so am limited in what I can do. Can you work with @nufkin (and his other half) on this? You would need some sort of CAN bus decoder (perhaps just an OBD-II dongle, or CAN-USB adaptor), plus an OVMS module and PICKIT for firmware download. If you use MAC OSX, the development environment is simple to setup - for windows there are a few more hoops to jump through. Lastly, a RS232-USB adaptor is useful (but not essential). Regards, Mark. On 13 Oct, 2013, at 4:00 pm, Robert Sharpe robert.sharpe@evergreen-consulting.co.uk> wrote: Hi, ovmsdev-request@lists.teslaclub.hk> Is anyone working on Leaf support? I am interested in helping if I can and have started a discussion at http://openvehicles.com/comment/220#comment-220 to capture were we are with the Leaf. Regards, Robert Sharpe (Technical Director) 07711 252971http://www.facebook.com/EvergreenConsultingLtd http://twitter.com/EGCtechnical http://uk.linkedin.com/in/arsharpe www.evergreen-consulting.co.ukYour Plugged-in PartnerSupport the future and switch to a renewable energy supplier such as Good EnergyEvergreen Consulting is the trading name of Sharpe Consultants Ltd /ovmsdev-request@lists.teslaclub.hk>_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________OvmsDev mailing listOvmsDev@lists.teslaclub.hkhttp://lists.teslaclub.hk/mailman/listinfo/ovmsdev

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@webb-johnson.net>wrote:

Developers guide is here:

https://github.com/markwj/Open-Vehicle-Monitoring-System/blob/master/docs/OV...

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...

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@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@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@webb-johnson.net> wrote: Developers guide is here:

https://github.com/markwj/Open-Vehicle-Monitoring-System/blob/master/docs/OV...

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@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

That's great news. Regards, Rob On 16 Oct 2013, at 06:00, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

...

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.

I think my fishing expedition on the forums may have come up with a bite. A Hong Kong Leaf owner who is willing to help.

I'll let you know how it pans out (over the next couple of days), but if I can get access to a local Leaf, getting the basic support working should be much faster.

Regards, Mark.

On 15 Oct, 2013, at 1:00 pm, Mark Webb-Johnson <mark@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@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@webb-johnson.net> wrote:

...

Developers guide is here:

https://github.com/markwj/Open-Vehicle-Monitoring-System/blob/master/docs/OV...

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@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

Hi Mark,>I think the fastest way to get this done is for me to do it with a local Leaf owner.That sounds like a good idea.>Can someone tell me which CarCAN bus message to look for, which byte(s) to access, and how to convert to percentage SOC?>The document at https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1... suggests ID 5B3 tracks SOH and Gids. But how to convert to percentage SOC?Is @nufkin (Mark C) on this list? He has done some analysis of codes.There is always the authors of the other projects that read Leaf data.Regards,RobOn Oct 16, 2013, at 6.33AM, Mark Webb-Johnson wrote:I think the fastest way to get this done is for me to do it with a local Leaf owner.If I can get basic support working, then perhaps someone else (or others) with better knowledge of the Leaf scene, can take over to get the advanced stuff working.So, I'm going to try to get some Leaf Spy traces, as well as CAN bus logs for parked, charging and driving. Then, get the basic module working with SOC%, GPS location, door status, drive/park and charge monitor.My biggest confusion at the moment is SOC% in the Leaf. There is a lot of talk about gids, etc, but I've never gone into it too deeply.Can someone tell me which CarCAN bus message to look for, which byte(s) to access, and how to convert to percentage SOC?The document at https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1... suggests ID 5B3 tracks SOH and Gids. But how to convert to percentage SOC?Regards, Mark.On 16 Oct, 2013, at 1:03 pm, Evergreen robert.sharpe@evergreen-consulting.co.uk> wrote:That's great news.Regards,RobOn 16 Oct 2013, at 06:00, Mark Webb-Johnson mark@webb-johnson.net> wrote: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.I think my fishing expedition on the forums may have come up with a bite. A Hong Kong Leaf owner who is willing to help.I'll let you know how it pans out (over the next couple of days), but if I can get access to a local Leaf, getting the basic support working should be much faster.Regards, Mark.On 15 Oct, 2013, at 1:00 pm, Mark Webb-Johnson mark@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@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@webb-johnson.net> wrote: Developers guide is here: https://github.com/markwj/Open-Vehicle-Monitoring-System/blob/master/docs/OV... 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 listOvmsDev@lists.teslaclub.hkhttp://lists.teslaclub.hk/mailman/listinfo/ovmsdev__________________________... mailing listOvmsDev@lists.teslaclub.hkhttp://lists.teslaclub.hk/mailman/listinfo/ovmsdev__________________________... mailing listOvmsDev@lists.teslaclub.hkhttp://lists.teslaclub.hk/mailman/listinfo/ovmsdev__________________________... mailing listOvmsDev@lists.teslaclub.hkhttp://lists.teslaclub.hk/mailman/listinfo/ovmsdev

Anyone feeling brave? I’ve just committed a nissan leaf module (set vehicle id to NL) that will monitor the can bus and pickup the SOC%. That is all it does at the moment, but it should work. Regards, Mark. On 16 Oct, 2013, at 2:49 pm, Nikki Gordon-Bloomfield <nikki@littlecollie.com> wrote:

I've already messages mark C. Let's hope he has it :) I know he and his husband have done a lot of logging.

Sent from my iPhone

On 16 Oct 2013, at 07:02, Robert Sharpe <robert.sharpe@evergreen-consulting.co.uk> wrote:

...

Hi Mark,

...

I think the fastest way to get this done is for me to do it with a local Leaf owner. That sounds like a good idea.

...

Can someone tell me which CarCAN bus message to look for, which byte(s) to access, and how to convert to percentage SOC? The document at https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1... suggests ID 5B3 tracks SOH and Gids. But how to convert to percentage SOC?

Is @nufkin (Mark C) on this list? He has done some analysis of codes. There is always the authors of the other projects that read Leaf data.

Regards, Rob

On Oct 16, 2013, at 6.33AM, Mark Webb-Johnson wrote:

I think the fastest way to get this done is for me to do it with a local Leaf owner.

If I can get basic support working, then perhaps someone else (or others) with better knowledge of the Leaf scene, can take over to get the advanced stuff working.

So, I'm going to try to get some Leaf Spy traces, as well as CAN bus logs for parked, charging and driving. Then, get the basic module working with SOC%, GPS location, door status, drive/park and charge monitor.

My biggest confusion at the moment is SOC% in the Leaf. There is a lot of talk about gids, etc, but I've never gone into it too deeply.

Can someone tell me which CarCAN bus message to look for, which byte(s) to access, and how to convert to percentage SOC?

The document at https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1... suggests ID 5B3 tracks SOH and Gids. But how to convert to percentage SOC?

Regards, Mark.

On 16 Oct, 2013, at 1:03 pm, Evergreen <robert.sharpe@evergreen-consulting.co.uk">target="_blank">robert.sharpe@evergreen-consulting.co.uk> wrote:

That's great news.

Regards, Rob

On 16 Oct 2013, at 06:00, Mark Webb-Johnson <mark@webb-johnson.net">target="_blank">mark@webb-johnson.net> wrote:

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.

I think my fishing expedition on the forums may have come up with a bite. A Hong Kong Leaf owner who is willing to help.

I'll let you know how it pans out (over the next couple of days), but if I can get access to a local Leaf, getting the basic support working should be much faster.

Regards, Mark.

On 15 Oct, 2013, at 1:00 pm, Mark Webb-Johnson <mark@webb-johnson.net">target="_blank">mark@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@gmail.com">target="_blank">gbarry42@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@webb-johnson.net">target="_blank">mark@webb-johnson.net> wrote: Developers guide is here:

https://github.com/markwj/Open-Vehicle-Monitoring-System/blob/master/docs/OV...

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@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

---

OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

Hi Nikki, On route from China… due here in a few days… will get it to you on the day they clear customs :-) [http://www.zerocarbonworld.org/images/logo.png] Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org <mailto:kevin.sharpe@zerocarbonworld.org> | www.zerocarbonworld.org<http://www.zerocarbonworld.org/> | twitter.com/zerocarbonworld<http://twitter.com/ZCWcharlie> [http://www.zerocarbonworld.org/images/email-signatures_06.png] Zero Carbon World is a UK Registered Charity #1141347 From: Nikki Gordon-Bloomfield <nikki@aminorjourney.com<mailto:nikki@aminorjourney.com>> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Date: Wednesday, 16 October 2013 16:29 To: OVMS Developers <ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Subject: Re: [Ovmsdev] OVMS Leaf Support As soon as I have a spare piece of hardware, I'll give it a go. Kevin? Nikki. On 16 Oct 2013, at 15:31, Mark Webb-Johnson <mark@webb-johnson.net<mailto:mark@webb-johnson.net>> wrote: Anyone feeling brave? I’ve just committed a nissan leaf module (set vehicle id to NL) that will monitor the can bus and pickup the SOC%. That is all it does at the moment, but it should work. Regards, Mark. On 16 Oct, 2013, at 2:49 pm, Nikki Gordon-Bloomfield <nikki@littlecollie.com<mailto:nikki@littlecollie.com>> wrote: I've already messages mark C. Let's hope he has it :) I know he and his husband have done a lot of logging. Sent from my iPhone On 16 Oct 2013, at 07:02, Robert Sharpe <robert.sharpe@evergreen-consulting.co.uk<mailto:robert.sharpe@evergreen-consulting.co.uk>> wrote: Hi Mark,

I think the fastest way to get this done is for me to do it with a local Leaf owner. That sounds like a good idea.

Can someone tell me which CarCAN bus message to look for, which byte(s) to access, and how to convert to percentage SOC? The document at https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1... suggests ID 5B3 tracks SOH and Gids. But how to convert to percentage SOC?

Is @nufkin (Mark C) on this list? He has done some analysis of codes. There is always the authors of the other projects that read Leaf data. Regards, Rob On Oct 16, 2013, at 6.33AM, Mark Webb-Johnson wrote: I think the fastest way to get this done is for me to do it with a local Leaf owner. If I can get basic support working, then perhaps someone else (or others) with better knowledge of the Leaf scene, can take over to get the advanced stuff working. So, I'm going to try to get some Leaf Spy traces, as well as CAN bus logs for parked, charging and driving. Then, get the basic module working with SOC%, GPS location, door status, drive/park and charge monitor. My biggest confusion at the moment is SOC% in the Leaf. There is a lot of talk about gids, etc, but I've never gone into it too deeply. Can someone tell me which CarCAN bus message to look for, which byte(s) to access, and how to convert to percentage SOC? The document at https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1... suggests ID 5B3 tracks SOH and Gids. But how to convert to percentage SOC? Regards, Mark. On 16 Oct, 2013, at 1:03 pm, Evergreen <robert.sharpe@evergreen-consulting.co.uk">target="_blank">robert.sharpe@evergreen-consulting.co.uk<mailto:robert.sharpe@evergreen-consulting.co.uk>> wrote: That's great news. Regards, Rob On 16 Oct 2013, at 06:00, Mark Webb-Johnson <mark@webb-johnson.net">target="_blank">mark@webb-johnson.net<mailto:mark@webb-johnson.net>> wrote: 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. I think my fishing expedition on the forums may have come up with a bite. A Hong Kong Leaf owner who is willing to help. I'll let you know how it pans out (over the next couple of days), but if I can get access to a local Leaf, getting the basic support working should be much faster. Regards, Mark. On 15 Oct, 2013, at 1:00 pm, Mark Webb-Johnson <mark@webb-johnson.net">target="_blank">mark@webb-johnson.net<mailto:mark@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@gmail.com">target="_blank">gbarry42@gmail.com<mailto:gbarry42@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@webb-johnson.net">target="_blank">mark@webb-johnson.net<mailto:mark@webb-johnson.net>> wrote: Developers guide is here: https://github.com/markwj/Open-Vehicle-Monitoring-System/blob/master/docs/OV... 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@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

Hi Mark, Thanks for the update. Good and bad news. For those of us less capable, and only if you think it is worth it, what is the importance of PID polling and how does it affect the development? Regards, Rob ---- On Sat, 19 Oct 2013 16:23:00 +0100 Mark Webb-Johnson <mark@webb-johnson.net> wrote ---- I met up with a local Leaf owner (George) and spent a few hours in the car logging stuff off the main CAN bus. The car is a 2011 model, I think (the VIN model year is U/V, which makes no sense). Good news it that the OVMS cables are fine. The ‘right hand’ ovms obdii cable appears to be the best for the right hand drive nissan leafs. The OBDII connector is under the steering wheel, parallel with the car direction of travel, short side on the left, so using a right-hand cable directs the cable towards the front of the car, which should be easiest for routing. I managed to get quite a few log files, using a standard CAN USB adaptor at 512kbps. Bad news is I am having trouble correlating lots of the messages against the published spreadsheets of Leaf can bus messages. Some messages are partially correct, but many are missing / don’t match up. The car also seems to go to sleep during charging, although the leaf spy could update the SOC ok. The 0x5b3 SOC+GIDS message wasn’t visible on the bus at all. I think we are going to have to use PID polling to get the data we need. Regards, Mark. On 16 Oct, 2013, at 10:31 pm, Mark Webb-Johnson <mark@webb-johnson.net> wrote: Anyone feeling brave? I’ve just committed a nissan leaf module (set vehicle id to NL) that will monitor the can bus and pickup the SOC%. That is all it does at the moment, but it should work. Regards, Mark. On 16 Oct, 2013, at 2:49 pm, Nikki Gordon-Bloomfield <nikki@littlecollie.com> wrote: I've already messages mark C. Let's hope he has it :) I know he and his husband have done a lot of logging. Sent from my iPhone On 16 Oct 2013, at 07:02, Robert Sharpe <robert.sharpe@evergreen-consulting.co.uk> wrote: Hi Mark, >I think the fastest way to get this done is for me to do it with a local Leaf owner. That sounds like a good idea. >Can someone tell me which CarCAN bus message to look for, which byte(s) to access, and how to convert to percentage SOC? >The document at https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1... suggests ID 5B3 tracks SOH and Gids. But how to convert to percentage SOC? Is @nufkin (Mark C) on this list? He has done some analysis of codes. There is always the authors of the other projects that read Leaf data. Regards, Rob On Oct 16, 2013, at 6.33AM, Mark Webb-Johnson wrote: I think the fastest way to get this done is for me to do it with a local Leaf owner. If I can get basic support working, then perhaps someone else (or others) with better knowledge of the Leaf scene, can take over to get the advanced stuff working. So, I'm going to try to get some Leaf Spy traces, as well as CAN bus logs for parked, charging and driving. Then, get the basic module working with SOC%, GPS location, door status, drive/park and charge monitor. My biggest confusion at the moment is SOC% in the Leaf. There is a lot of talk about gids, etc, but I've never gone into it too deeply. Can someone tell me which CarCAN bus message to look for, which byte(s) to access, and how to convert to percentage SOC? The document at https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1... suggests ID 5B3 tracks SOH and Gids. But how to convert to percentage SOC? Regards, Mark. On 16 Oct, 2013, at 1:03 pm, Evergreen <robert.sharpe@evergreen-consulting.co.uk">target="_blank">robert.sharpe@evergreen-consulting.co.uk> wrote: That's great news. Regards, Rob On 16 Oct 2013, at 06:00, Mark Webb-Johnson <mark@webb-johnson.net">target="_blank">mark@webb-johnson.net> wrote: 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. I think my fishing expedition on the forums may have come up with a bite. A Hong Kong Leaf owner who is willing to help. I'll let you know how it pans out (over the next couple of days), but if I can get access to a local Leaf, getting the basic support working should be much faster. Regards, Mark. On 15 Oct, 2013, at 1:00 pm, Mark Webb-Johnson <mark@webb-johnson.net">target="_blank">mark@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@gmail.com">target="_blank">gbarry42@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@webb-johnson.net">target="_blank">mark@webb-johnson.net> wrote: Developers guide is here: https://github.com/markwj/Open-Vehicle-Monitoring-System/blob/master/docs/OV... 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@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

Thanks Mark On 21 Oct 2013, at 02:06, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

Robert,

PID polling vs passive can bus listening.

In general, passive listening is much simpler and easier to develop for without the car. Everything can be done by examining and replaying can bus logs.

PID polling requires active access to the can bus, and is much more intrusive. It is also much harder to test without a physical car.

Regards, Mark.

On 20 Oct, 2013, at 12:23 am, Robert Sharpe <robert.sharpe@evergreen-consulting.co.uk> wrote:

...

Hi Mark,

Thanks for the update.

Good and bad news.

For those of us less capable, and only if you think it is worth it, what is the importance of PID polling and how does it affect the development?

Regards, Rob

---- On Sat, 19 Oct 2013 16:23:00 +0100 Mark Webb-Johnson <mark@webb-johnson.net> wrote ----

I met up with a local Leaf owner (George) and spent a few hours in the car logging stuff off the main CAN bus. The car is a 2011 model, I think (the VIN model year is U/V, which makes no sense).

Good news it that the OVMS cables are fine. The ‘right hand’ ovms obdii cable appears to be the best for the right hand drive nissan leafs. The OBDII connector is under the steering wheel, parallel with the car direction of travel, short side on the left, so using a right-hand cable directs the cable towards the front of the car, which should be easiest for routing.

I managed to get quite a few log files, using a standard CAN USB adaptor at 512kbps.

Bad news is I am having trouble correlating lots of the messages against the published spreadsheets of Leaf can bus messages. Some messages are partially correct, but many are missing / don’t match up. The car also seems to go to sleep during charging, although the leaf spy could update the SOC ok. The 0x5b3 SOC+GIDS message wasn’t visible on the bus at all.

I think we are going to have to use PID polling to get the data we need.

Regards, Mark.

On 16 Oct, 2013, at 10:31 pm, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

...

Anyone feeling brave?

I’ve just committed a nissan leaf module (set vehicle id to NL) that will monitor the can bus and pickup the SOC%. That is all it does at the moment, but it should work.

Regards, Mark.

On 16 Oct, 2013, at 2:49 pm, Nikki Gordon-Bloomfield <nikki@littlecollie.com> wrote:

...

I've already messages mark C. Let's hope he has it :) I know he and his husband have done a lot of logging.

Sent from my iPhone

On 16 Oct 2013, at 07:02, Robert Sharpe <robert.sharpe@evergreen-consulting.co.uk> wrote:

...

Hi Mark,

...

I think the fastest way to get this done is for me to do it with a local Leaf owner. That sounds like a good idea.

...

Can someone tell me which CarCAN bus message to look for, which byte(s) to access, and how to convert to percentage SOC? The document at https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1... suggests ID 5B3 tracks SOH and Gids. But how to convert to percentage SOC?

Is @nufkin (Mark C) on this list? He has done some analysis of codes. There is always the authors of the other projects that read Leaf data.

Regards, Rob

On Oct 16, 2013, at 6.33AM, Mark Webb-Johnson wrote:

I think the fastest way to get this done is for me to do it with a local Leaf owner.

If I can get basic support working, then perhaps someone else (or others) with better knowledge of the Leaf scene, can take over to get the advanced stuff working.

So, I'm going to try to get some Leaf Spy traces, as well as CAN bus logs for parked, charging and driving. Then, get the basic module working with SOC%, GPS location, door status, drive/park and charge monitor.

My biggest confusion at the moment is SOC% in the Leaf. There is a lot of talk about gids, etc, but I've never gone into it too deeply.

Can someone tell me which CarCAN bus message to look for, which byte(s) to access, and how to convert to percentage SOC?

The document at https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1... suggests ID 5B3 tracks SOH and Gids. But how to convert to percentage SOC?

Regards, Mark.

On 16 Oct, 2013, at 1:03 pm, Evergreen <robert.sharpe@evergreen-consulting.co.uk">target="_blank">robert.sharpe@evergreen-consulting.co.uk> wrote:

That's great news.

Regards, Rob

On 16 Oct 2013, at 06:00, Mark Webb-Johnson <mark@webb-johnson.net">target="_blank">mark@webb-johnson.net> wrote:

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.

I think my fishing expedition on the forums may have come up with a bite. A Hong Kong Leaf owner who is willing to help.

I'll let you know how it pans out (over the next couple of days), but if I can get access to a local Leaf, getting the basic support working should be much faster.

Regards, Mark.

On 15 Oct, 2013, at 1:00 pm, Mark Webb-Johnson <mark@webb-johnson.net">target="_blank">mark@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@gmail.com">target="_blank">gbarry42@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@webb-johnson.net">target="_blank">mark@webb-johnson.net> wrote: Developers guide is here:

https://github.com/markwj/Open-Vehicle-Monitoring-System/blob/master/docs/OV...

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@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

---

OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

Hi Mark, Wow great work. For me my current status is Good and frequent access to a Nissan Leaf - YES RS232-to-USB adaptor and laptop (or laptop with RS232 port) - YES OVMS v2 Module - Accepted Kevin's offer of h/w waiting for delivery OVMS v2 OBD-II cable - Accepted Kevin's offer of h/w waiting for delivery PICKIT2 or PICKIT3 programmer - Will order one today (any suggestions to a good source?) Regards, Rob ---- On Tue, 22 Oct 2013 02:11:52 +0100 Mark Webb-Johnson<mark@webb-johnson.net> wrote ---- OK, here's an update... I went through the logs we captured, and had a look at Leaf Spy. I even purchased a copy of Leaf Spy Pro (even though I don't have a Leaf) just as a donation to say thank you to Turbo3 for pushing this approach and working out so much of the mechanics of it. I spent an evening reading through the "Using clone ELM327 Bluetooth OBDII adapter with Leaf" on mynissanleaf.com (all 238 pages of it!), and got a good understanding of the history of where CAN decoding on the Nissan Leaf is, and where it is headed. Bottom line: There are two CAN buses in the Nissan Leaf that are useful to us: the EV CAN bus and the CAR CAN bus. The standard OVMS OBD-II cable connects to the CAR CAN bus. By passive listening on the bus, we can see some EV information, and all of the car information. The EV CAN bus is also available on the OBD-II socket. By passive listening on the bus, we can see all the EV information, but little-to-no car information. OVMS V2 hardware can only connect to one bus. Someone worked out that active requests for information from the controllers (PID polling, as opposed to passive listening) are bridged. You can request information from a controller on the EV CAN bus, via the CAR CAN bus, and the car will bridge the requests between the buses. This appears to work bi-directionally. There is a slight nasty in that if the car is off (asleep), active polling the EV controller causes it to wake up and you can hear a little 12V relay click near the front of the car each time you poll. We don't want to poll too fast when the car is asleep (off) and not charging, to avoid wearing out that relay. The OBD-II connector has 12V power (both switched and non-switched) that we can use for OVMS, powered by an automotive 12V lead acid battery. We do need to take care because apparently that 12V battery is only charged when you drive or once every five days when the car is unplugged (and not at all when the car is plugged in). There is a CAR CAN message to show the 12V battery voltage (and OVMS V2 can also measure directly). There is 'active discussion' in the community on how things like SOC%, battery capacity, ideal and estimated ranges, should be determined. Nissan made a mess of it, and the users are struggling to agree on a uniform approach to a correct way of doing things. I think our plan of attack should be: Use a standard V2 module, with standard OVMS OBD-II cable, to connect to the CAR CAN bus. Use passive CAN listening, for the car information (doors, speed, on/off, etc) as much as possible. Use active CAN polling, bridged to the EV CAN bus, for the EV information that we need. Agree our own user-centric approach of how to represent capacity, SOC, ideal and estimated ranges. It has been quite frustrating looking at the community documentation for CAN bus messages in the Leaf. The documentation doesn't match what I am seeing, and is not at all clear. A lot of people are sharing, but some seem to be holding back and saying things like "here are some clues to what I've found, so go look for it yourself". Some closed source. Not the way I like to do things. There is one very good thread on the active CAN bus polling, here: http://www.mynissanleaf.com/viewtopic.php?f=44&t=11676 A good background read (34 pages) on Leaf CAN bus passive monitoring is here: http://www.mynissanleaf.com/viewtopic.php?f=8&t=4131 and I recommend everyone involved in this to read that thread (only 12 pages) to get a good understanding. There are two spreadsheets tracking Leaf CAN bus messages: https://docs.google.com/spreadsheet/ccc?key=0AuDGAXnbchK0dDc4T05oNE04aVZtUzB6S19DT1RwaHc&authkey=CJi03v4F&hl=en_US&authkey=CJi03v4F#gid=0 https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1... So, what I'm going to do now is to setup a framework in the vehicle_nissanleaf module to do passive listening on the CAR CAN bus, and active polling of the information on the EV CAN bus (bridged via CAR CAN bus). Once the framework is done, I'll test it in the local Hong Kong Leaf, and ask you guys to help. I do need one or two people with the following equipment to help out: Good and frequent access to a Nissan Leaf OVMS v2 Module OVMS v2 OBD-II cable PICKIT2 or PICKIT3 programmer RS232-to-USB adaptor and laptop (or laptop with RS232 port) This is to run the framework in their car, and capture RS232 output from the DIAG port. So, volunteers please. Regards, Mark. On 19 Oct, 2013, at 11:23 pm, Mark Webb-Johnson <mark@webb-johnson.net> wrote: I met up with a local Leaf owner (George) and spent a few hours in the car logging stuff off the main CAN bus. The car is a 2011 model, I think (the VIN model year is U/V, which makes no sense). Good news it that the OVMS cables are fine. The ‘right hand’ ovms obdii cable appears to be the best for the right hand drive nissan leafs. The OBDII connector is under the steering wheel, parallel with the car direction of travel, short side on the left, so using a right-hand cable directs the cable towards the front of the car, which should be easiest for routing. I managed to get quite a few log files, using a standard CAN USB adaptor at 512kbps. Bad news is I am having trouble correlating lots of the messages against the published spreadsheets of Leaf can bus messages. Some messages are partially correct, but many are missing / don’t match up. The car also seems to go to sleep during charging, although the leaf spy could update the SOC ok. The 0x5b3 SOC+GIDS message wasn’t visible on the bus at all. I think we are going to have to use PID polling to get the data we need. Regards, Mark. On 16 Oct, 2013, at 10:31 pm, Mark Webb-Johnson <mark@webb-johnson.net> wrote: Anyone feeling brave? I’ve just committed a nissan leaf module (set vehicle id to NL) that will monitor the can bus and pickup the SOC%. That is all it does at the moment, but it should work. Regards, Mark. On 16 Oct, 2013, at 2:49 pm, Nikki Gordon-Bloomfield <nikki@littlecollie.com> wrote: I've already messages mark C. Let's hope he has it :) I know he and his husband have done a lot of logging. Sent from my iPhone On 16 Oct 2013, at 07:02, Robert Sharpe <robert.sharpe@evergreen-consulting.co.uk> wrote: Hi Mark, >I think the fastest way to get this done is for me to do it with a local Leaf owner. That sounds like a good idea. >Can someone tell me which CarCAN bus message to look for, which byte(s) to access, and how to convert to percentage SOC? >The document at https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1... suggests ID 5B3 tracks SOH and Gids. But how to convert to percentage SOC? Is @nufkin (Mark C) on this list? He has done some analysis of codes. There is always the authors of the other projects that read Leaf data. Regards, Rob On Oct 16, 2013, at 6.33AM, Mark Webb-Johnson wrote: I think the fastest way to get this done is for me to do it with a local Leaf owner. If I can get basic support working, then perhaps someone else (or others) with better knowledge of the Leaf scene, can take over to get the advanced stuff working. So, I'm going to try to get some Leaf Spy traces, as well as CAN bus logs for parked, charging and driving. Then, get the basic module working with SOC%, GPS location, door status, drive/park and charge monitor. My biggest confusion at the moment is SOC% in the Leaf. There is a lot of talk about gids, etc, but I've never gone into it too deeply. Can someone tell me which CarCAN bus message to look for, which byte(s) to access, and how to convert to percentage SOC? The document at https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1... suggests ID 5B3 tracks SOH and Gids. But how to convert to percentage SOC? Regards, Mark. On 16 Oct, 2013, at 1:03 pm, Evergreen <robert.sharpe@evergreen-consulting.co.uk">target="_blank">robert.sharpe@evergreen-consulting.co.uk> wrote: That's great news. Regards, Rob On 16 Oct 2013, at 06:00, Mark Webb-Johnson <mark@webb-johnson.net">target="_blank">mark@webb-johnson.net> wrote: 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. I think my fishing expedition on the forums may have come up with a bite. A Hong Kong Leaf owner who is willing to help. I'll let you know how it pans out (over the next couple of days), but if I can get access to a local Leaf, getting the basic support working should be much faster. Regards, Mark. On 15 Oct, 2013, at 1:00 pm, Mark Webb-Johnson <mark@webb-johnson.net">target="_blank">mark@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@gmail.com">target="_blank">gbarry42@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@webb-johnson.net">target="_blank">mark@webb-johnson.net> wrote: Developers guide is here: https://github.com/markwj/Open-Vehicle-Monitoring-System/blob/master/docs/OV... 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@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

Rob, If you are not developing code then a PICKIT2 is easier. The original is here: http://www.amazon.co.uk/Microchip-PG164120-Programmer-Pickit-2/dp/B0040ZRGCQ... but as it is 'open source', there are lots of much cheaper clones. For example: http://www.fasttech.com/products/0/10000018/1002200-pickit-2-compatible-prog... Personally, I'd go with the clone. Regards, Mark. On 22 Oct, 2013, at 2:32 pm, Robert Sharpe <robert.sharpe@evergreen-consulting.co.uk> wrote:

Hi Mark,

Wow great work.

For me my current status is

Good and frequent access to a Nissan Leaf - YES RS232-to-USB adaptor and laptop (or laptop with RS232 port) - YES

OVMS v2 Module - Accepted Kevin's offer of h/w waiting for delivery OVMS v2 OBD-II cable - Accepted Kevin's offer of h/w waiting for delivery

PICKIT2 or PICKIT3 programmer - Will order one today (any suggestions to a good source?)

Regards, Rob

---- On Tue, 22 Oct 2013 02:11:52 +0100 Mark Webb-Johnson<mark@webb-johnson.net> wrote ----

OK, here's an update...

I went through the logs we captured, and had a look at Leaf Spy. I even purchased a copy of Leaf Spy Pro (even though I don't have a Leaf) just as a donation to say thank you to Turbo3 for pushing this approach and working out so much of the mechanics of it.

I spent an evening reading through the "Using clone ELM327 Bluetooth OBDII adapter with Leaf" on mynissanleaf.com (all 238 pages of it!), and got a good understanding of the history of where CAN decoding on the Nissan Leaf is, and where it is headed.

Bottom line:

There are two CAN buses in the Nissan Leaf that are useful to us: the EV CAN bus and the CAR CAN bus. The standard OVMS OBD-II cable connects to the CAR CAN bus. By passive listening on the bus, we can see some EV information, and all of the car information. The EV CAN bus is also available on the OBD-II socket. By passive listening on the bus, we can see all the EV information, but little-to-no car information. OVMS V2 hardware can only connect to one bus. Someone worked out that active requests for information from the controllers (PID polling, as opposed to passive listening) are bridged. You can request information from a controller on the EV CAN bus, via the CAR CAN bus, and the car will bridge the requests between the buses. This appears to work bi-directionally. There is a slight nasty in that if the car is off (asleep), active polling the EV controller causes it to wake up and you can hear a little 12V relay click near the front of the car each time you poll. We don't want to poll too fast when the car is asleep (off) and not charging, to avoid wearing out that relay. The OBD-II connector has 12V power (both switched and non-switched) that we can use for OVMS, powered by an automotive 12V lead acid battery. We do need to take care because apparently that 12V battery is only charged when you drive or once every five days when the car is unplugged (and not at all when the car is plugged in). There is a CAR CAN message to show the 12V battery voltage (and OVMS V2 can also measure directly). There is 'active discussion' in the community on how things like SOC%, battery capacity, ideal and estimated ranges, should be determined. Nissan made a mess of it, and the users are struggling to agree on a uniform approach to a correct way of doing things.

I think our plan of attack should be:

Use a standard V2 module, with standard OVMS OBD-II cable, to connect to the CAR CAN bus. Use passive CAN listening, for the car information (doors, speed, on/off, etc) as much as possible. Use active CAN polling, bridged to the EV CAN bus, for the EV information that we need. Agree our own user-centric approach of how to represent capacity, SOC, ideal and estimated ranges.

It has been quite frustrating looking at the community documentation for CAN bus messages in the Leaf. The documentation doesn't match what I am seeing, and is not at all clear. A lot of people are sharing, but some seem to be holding back and saying things like "here are some clues to what I've found, so go look for it yourself". Some closed source. Not the way I like to do things.

There is one very good thread on the active CAN bus polling, here:

http://www.mynissanleaf.com/viewtopic.php?f=44&t=11676

A good background read (34 pages) on Leaf CAN bus passive monitoring is here:

http://www.mynissanleaf.com/viewtopic.php?f=8&t=4131

and I recommend everyone involved in this to read that thread (only 12 pages) to get a good understanding.

There are two spreadsheets tracking Leaf CAN bus messages:

https://docs.google.com/spreadsheet/ccc?key=0AuDGAXnbchK0dDc4T05oNE04aVZtUzB...

https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1...

So, what I'm going to do now is to setup a framework in the vehicle_nissanleaf module to do passive listening on the CAR CAN bus, and active polling of the information on the EV CAN bus (bridged via CAR CAN bus). Once the framework is done, I'll test it in the local Hong Kong Leaf, and ask you guys to help.

I do need one or two people with the following equipment to help out:

Good and frequent access to a Nissan Leaf OVMS v2 Module OVMS v2 OBD-II cable PICKIT2 or PICKIT3 programmer RS232-to-USB adaptor and laptop (or laptop with RS232 port)

This is to run the framework in their car, and capture RS232 output from the DIAG port.

So, volunteers please.

Regards, Mark.

On 19 Oct, 2013, at 11:23 pm, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

...

I met up with a local Leaf owner (George) and spent a few hours in the car logging stuff off the main CAN bus. The car is a 2011 model, I think (the VIN model year is U/V, which makes no sense).

Good news it that the OVMS cables are fine. The ‘right hand’ ovms obdii cable appears to be the best for the right hand drive nissan leafs. The OBDII connector is under the steering wheel, parallel with the car direction of travel, short side on the left, so using a right-hand cable directs the cable towards the front of the car, which should be easiest for routing.

I managed to get quite a few log files, using a standard CAN USB adaptor at 512kbps.

Bad news is I am having trouble correlating lots of the messages against the published spreadsheets of Leaf can bus messages. Some messages are partially correct, but many are missing / don’t match up. The car also seems to go to sleep during charging, although the leaf spy could update the SOC ok. The 0x5b3 SOC+GIDS message wasn’t visible on the bus at all.

I think we are going to have to use PID polling to get the data we need.

Regards, Mark.

On 16 Oct, 2013, at 10:31 pm, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

...

Anyone feeling brave?

I’ve just committed a nissan leaf module (set vehicle id to NL) that will monitor the can bus and pickup the SOC%. That is all it does at the moment, but it should work.

Regards, Mark.

On 16 Oct, 2013, at 2:49 pm, Nikki Gordon-Bloomfield <nikki@littlecollie.com> wrote:

...

I've already messages mark C. Let's hope he has it :) I know he and his husband have done a lot of logging.

Sent from my iPhone

On 16 Oct 2013, at 07:02, Robert Sharpe <robert.sharpe@evergreen-consulting.co.uk> wrote:

...

Hi Mark,

...

I think the fastest way to get this done is for me to do it with a local Leaf owner. That sounds like a good idea.

...

Can someone tell me which CarCAN bus message to look for, which byte(s) to access, and how to convert to percentage SOC? The document at https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1... suggests ID 5B3 tracks SOH and Gids. But how to convert to percentage SOC?

Is @nufkin (Mark C) on this list? He has done some analysis of codes. There is always the authors of the other projects that read Leaf data.

Regards, Rob

On Oct 16, 2013, at 6.33AM, Mark Webb-Johnson wrote:

I think the fastest way to get this done is for me to do it with a local Leaf owner.

If I can get basic support working, then perhaps someone else (or others) with better knowledge of the Leaf scene, can take over to get the advanced stuff working.

So, I'm going to try to get some Leaf Spy traces, as well as CAN bus logs for parked, charging and driving. Then, get the basic module working with SOC%, GPS location, door status, drive/park and charge monitor.

My biggest confusion at the moment is SOC% in the Leaf. There is a lot of talk about gids, etc, but I've never gone into it too deeply.

Can someone tell me which CarCAN bus message to look for, which byte(s) to access, and how to convert to percentage SOC?

The document at https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1... suggests ID 5B3 tracks SOH and Gids. But how to convert to percentage SOC?

Regards, Mark.

On 16 Oct, 2013, at 1:03 pm, Evergreen <robert.sharpe@evergreen-consulting.co.uk">target="_blank">robert.sharpe@evergreen-consulting.co.uk> wrote:

That's great news.

Regards, Rob

On 16 Oct 2013, at 06:00, Mark Webb-Johnson <mark@webb-johnson.net">target="_blank">mark@webb-johnson.net> wrote:

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.

I think my fishing expedition on the forums may have come up with a bite. A Hong Kong Leaf owner who is willing to help.

I'll let you know how it pans out (over the next couple of days), but if I can get access to a local Leaf, getting the basic support working should be much faster.

Regards, Mark.

On 15 Oct, 2013, at 1:00 pm, Mark Webb-Johnson <mark@webb-johnson.net">target="_blank">mark@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@gmail.com">target="_blank">gbarry42@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@webb-johnson.net">target="_blank">mark@webb-johnson.net> wrote: Developers guide is here:

https://github.com/markwj/Open-Vehicle-Monitoring-System/blob/master/docs/OV...

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@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

---

OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

I have an ICD-2. Is the PIC operated at 5V, or 3? I don't think I've found any board info, or I could answer that myself. For the 12 V battery in the LEAF, it's a more accurate thing to say that the battery may be charged any time the traction battery comes on line. There are relays that disconnect the pack entirely. (You're a musician, Nikki--you may recognize the LEAF's "relay song"). They say the LEAF will power up automatically every 5 days to maintain the 12V, but this behavior is bypassed if the J1772 is attached. So, there's the cause of that problem. I have also successfully done the charge-1hr-per-day thing, although I wasn't really away long enough to matter. I looked to see what OVMS sells for and noticed it's in Pounds, which made me wonder if shipping to the States would be messy. Also, it said, "out of stock." But more importantly, it made me wonder if the firmware in a US LEAF might be different? Might explain why you can't get your logs to jive with Leaf Spy. On Tue, Oct 22, 2013 at 2:29 PM, Tom Saxton <tom@idleloop.com> wrote:

I'm not able to program the V2 board with the PICkit2 unless the board plugged into the car to get 12V power, so I'd recommend the PICKit3, which I'm assuming doesn't have this issue.

I need to either build a cable to power the OVMS from a power supply or order the PICKit3 from Fasttech. For now, my laptop is living in the Roadster's passenger seat while I've been doing some work on the charge time predictor.

Tom

From: Mark Webb-Johnson <mark@webb-johnson.net> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Date: Monday, October 21, 2013 11:42 PM

To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Subject: Re: [Ovmsdev] OVMS Leaf Support

Rob,

If you are not developing code then a PICKIT2 is easier.

The original is here:

http://www.amazon.co.uk/Microchip-PG164120-Programmer-Pickit-2/dp/B0040ZRGCQ...

but as it is 'open source', there are lots of much cheaper clones. For example:

http://www.fasttech.com/products/0/10000018/1002200-pickit-2-compatible-prog...

Personally, I'd go with the clone.

Regards, Mark.

On 22 Oct, 2013, at 2:32 pm, Robert Sharpe < robert.sharpe@evergreen-consulting.co.uk> wrote:

Hi Mark,

Wow great work.

For me my current status is

Good and frequent access to a Nissan Leaf - YES RS232-to-USB adaptor and laptop (or laptop with RS232 port) - YES

OVMS v2 Module - Accepted Kevin's offer of h/w waiting for delivery OVMS v2 OBD-II cable - Accepted Kevin's offer of h/w waiting for delivery

PICKIT2 or PICKIT3 programmer - Will order one today (any suggestions to a good source?)

Regards, Rob

---- On Tue, 22 Oct 2013 02:11:52 +0100 *Mark Webb-Johnson< mark@webb-johnson.net>* wrote ----

OK, here's an update...

I went through the logs we captured, and had a look at Leaf Spy. I even purchased a copy of Leaf Spy Pro (even though I don't have a Leaf) just as a donation to say thank you to Turbo3 for pushing this approach and working out so much of the mechanics of it.

I spent an evening reading through the "Using clone ELM327 Bluetooth OBDII adapter with Leaf" on mynissanleaf.com<http://www.mynissanleaf.com/viewtopic.php?f=44&t=12098> (all 238 pages of it!), and got a good understanding of the history of where CAN decoding on the Nissan Leaf is, and where it is headed.

Bottom line:

- There are two CAN buses in the Nissan Leaf that are useful to us: the EV CAN bus and the CAR CAN bus. - The standard OVMS OBD-II cable connects to the CAR CAN bus. By passive listening on the bus, we can see some EV information, and all of the car information. - The EV CAN bus is also available on the OBD-II socket. By passive listening on the bus, we can see all the EV information, but little-to-no car information. - OVMS V2 hardware can only connect to one bus. - Someone worked out that active requests for information from the controllers (PID polling, as opposed to passive listening) are bridged. You can request information from a controller on the EV CAN bus, via the CAR CAN bus, and the car will bridge the requests between the buses. This appears to work bi-directionally. - There is a slight nasty in that if the car is off (asleep), active polling the EV controller causes it to wake up and you can hear a little 12V relay click near the front of the car each time you poll. We don't want to poll too fast when the car is asleep (off) and not charging, to avoid wearing out that relay. - The OBD-II connector has 12V power (both switched and non-switched) that we can use for OVMS, powered by an automotive 12V lead acid battery. We do need to take care because apparently that 12V battery is only charged when you drive or once every five days when the car is unplugged (and not at all when the car is plugged in). There is a CAR CAN message to show the 12V battery voltage (and OVMS V2 can also measure directly). - There is 'active discussion' in the community on how things like SOC%, battery capacity, ideal and estimated ranges, should be determined. Nissan made a mess of it, and the users are struggling to agree on a uniform approach to a correct way of doing things.

I think our plan of attack should be:

1. Use a standard V2 module, with standard OVMS OBD-II cable, to connect to the CAR CAN bus. 2. Use passive CAN listening, for the car information (doors, speed, on/off, etc) as much as possible. 3. Use active CAN polling, bridged to the EV CAN bus, for the EV information that we need. 4. Agree our own user-centric approach of how to represent capacity, SOC, ideal and estimated ranges.

It has been quite frustrating looking at the community documentation for CAN bus messages in the Leaf. The documentation doesn't match what I am seeing, and is not at all clear. A lot of people are sharing, but some seem to be holding back and saying things like "here are some clues to what I've found, so go look for it yourself". Some closed source. Not the way I like to do things.

There is one very good thread on the active CAN bus polling, here:

http://www.mynissanleaf.com/viewtopic.php?f=44&t=11676

A good background read (34 pages) on Leaf CAN bus passive monitoring is here:

http://www.mynissanleaf.com/viewtopic.php?f=8&t=4131

and I recommend everyone involved in this to read that thread (only 12 pages) to get a good understanding.

There are two spreadsheets tracking Leaf CAN bus messages:

https://docs.google.com/spreadsheet/ccc?key=0AuDGAXnbchK0dDc4T05oNE04aVZtUzB...

https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1...

So, what I'm going to do now is to setup a framework in the vehicle_nissanleaf module to do passive listening on the CAR CAN bus, and active polling of the information on the EV CAN bus (bridged via CAR CAN bus). Once the framework is done, I'll test it in the local Hong Kong Leaf, and ask you guys to help.

I do need one or two people with the following equipment to help out:

Good and frequent access to a Nissan Leaf OVMS v2 Module OVMS v2 OBD-II cable PICKIT2 or PICKIT3 programmer RS232-to-USB adaptor and laptop (or laptop with RS232 port)

This is to run the framework in their car, and capture RS232 output from the DIAG port.

So, volunteers please.

Regards, Mark.

On 19 Oct, 2013, at 11:23 pm, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

I met up with a local Leaf owner (George) and spent a few hours in the car logging stuff off the main CAN bus. The car is a 2011 model, I think (the VIN model year is U/V, which makes no sense).

Good news it that the OVMS cables are fine. The ‘right hand’ ovms obdii cable appears to be the best for the right hand drive nissan leafs. The OBDII connector is under the steering wheel, parallel with the car direction of travel, short side on the left, so using a right-hand cable directs the cable towards the front of the car, which should be easiest for routing.

I managed to get quite a few log files, using a standard CAN USB adaptor at 512kbps.

Bad news is I am having trouble correlating lots of the messages against the published spreadsheets of Leaf can bus messages. Some messages are partially correct, but many are missing / don’t match up. The car also seems to go to sleep during charging, although the leaf spy could update the SOC ok. The 0x5b3 SOC+GIDS message wasn’t visible on the bus at all.

I think we are going to have to use PID polling to get the data we need.

Regards, Mark.

On 16 Oct, 2013, at 10:31 pm, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

Anyone feeling brave?

I’ve just committed a nissan leaf module (set vehicle id to NL) that will monitor the can bus and pickup the SOC%. That is all it does at the moment, but it should work.

Regards, Mark.

On 16 Oct, 2013, at 2:49 pm, Nikki Gordon-Bloomfield < nikki@littlecollie.com> wrote:

I've already messages mark C. Let's hope he has it :) I know he and his husband have done a lot of logging.

Sent from my iPhone

On 16 Oct 2013, at 07:02, Robert Sharpe < robert.sharpe@evergreen-consulting.co.uk> wrote:

Hi Mark,

...

I think the fastest way to get this done is for me to do it with a local Leaf owner. That sounds like a good idea.

...

Can someone tell me which CarCAN bus message to look for, which byte(s) to access, and how to convert to percentage SOC? The document at https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1... suggests ID 5B3 tracks SOH and Gids. But how to convert to percentage SOC?

Is @nufkin (Mark C) on this list? He has done some analysis of codes. There is always the authors of the other projects that read Leaf data.

Regards, Rob

On Oct 16, 2013, at 6.33AM, Mark Webb-Johnson wrote:

I think the fastest way to get this done is for me to do it with a local Leaf owner.

If I can get basic support working, then perhaps someone else (or others) with better knowledge of the Leaf scene, can take over to get the advanced stuff working.

So, I'm going to try to get some Leaf Spy traces, as well as CAN bus logs for parked, charging and driving. Then, get the basic module working with SOC%, GPS location, door status, drive/park and charge monitor.

My biggest confusion at the moment is SOC% in the Leaf. There is a lot of talk about gids, etc, but I've never gone into it too deeply.

Can someone tell me which CarCAN bus message to look for, which byte(s) to access, and how to convert to percentage SOC?

The document at https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1... ID 5B3 tracks SOH and Gids. But how to convert to percentage SOC?

Regards, Mark.

On 16 Oct, 2013, at 1:03 pm, Evergreen <<robert.sharpe@evergreen-consulting.co.uk> robert.sharpe@evergreen-consulting.co.uk">target="_blank">robert.sharpe@evergreen-consulting.co.uk> wrote:

That's great news.

Regards, Rob

On 16 Oct 2013, at 06:00, Mark Webb-Johnson < <mark@webb-johnson.net> mark@webb-johnson.net">target="_blank">mark@webb-johnson.net> wrote:

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.

I think my fishing expedition on the forums may have come up with a bite. A Hong Kong Leaf owner who is willing to help.

I'll let you know how it pans out (over the next couple of days), but if I can get access to a local Leaf, getting the basic support working should be much faster.

Regards, Mark.

On 15 Oct, 2013, at 1:00 pm, Mark Webb-Johnson < <mark@webb-johnson.net> mark@webb-johnson.net">target="_blank">mark@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@gmail.com> gbarry42@gmail.com">target="_blank">gbarry42@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@webb-johnson.net> mark@webb-johnson.net">target="_blank">mark@webb-johnson.net> wrote:

Developers guide is here:

https://github.com/markwj/Open-Vehicle-Monitoring-System/blob/master/docs/OV...

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@lists.teslaclub.hk> OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list <OvmsDev@lists.teslaclub.hk> OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list <OvmsDev@lists.teslaclub.hk> OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list <OvmsDev@lists.teslaclub.hk> OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

Barry, PIC runs at 5V. Regards, Mark. On 23 Oct, 2013, at 6:58 am, Barry Gershenfeld <gbarry42@gmail.com> wrote:

I have an ICD-2. Is the PIC operated at 5V, or 3? I don't think I've found any board info, or I could answer that myself.

For the 12 V battery in the LEAF, it's a more accurate thing to say that the battery may be charged any time the traction battery comes on line. There are relays that disconnect the pack entirely. (You're a musician, Nikki--you may recognize the LEAF's "relay song"). They say the LEAF will power up automatically every 5 days to maintain the 12V, but this behavior is bypassed if the J1772 is attached. So, there's the cause of that problem. I have also successfully done the charge-1hr-per-day thing, although I wasn't really away long enough to matter.

I looked to see what OVMS sells for and noticed it's in Pounds, which made me wonder if shipping to the States would be messy. Also, it said, "out of stock." But more importantly, it made me wonder if the firmware in a US LEAF might be different? Might explain why you can't get your logs to jive with Leaf Spy.

On Tue, Oct 22, 2013 at 2:29 PM, Tom Saxton <tom@idleloop.com> wrote: I'm not able to program the V2 board with the PICkit2 unless the board plugged into the car to get 12V power, so I'd recommend the PICKit3, which I'm assuming doesn't have this issue.

I need to either build a cable to power the OVMS from a power supply or order the PICKit3 from Fasttech. For now, my laptop is living in the Roadster's passenger seat while I've been doing some work on the charge time predictor.

Tom

From: Mark Webb-Johnson <mark@webb-johnson.net> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Date: Monday, October 21, 2013 11:42 PM

To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Subject: Re: [Ovmsdev] OVMS Leaf Support

Rob,

If you are not developing code then a PICKIT2 is easier.

The original is here:

http://www.amazon.co.uk/Microchip-PG164120-Programmer-Pickit-2/dp/B0040ZRGCQ...

but as it is 'open source', there are lots of much cheaper clones. For example:

http://www.fasttech.com/products/0/10000018/1002200-pickit-2-compatible-prog...

Personally, I'd go with the clone.

Regards, Mark.

On 22 Oct, 2013, at 2:32 pm, Robert Sharpe <robert.sharpe@evergreen-consulting.co.uk> wrote:

...

Hi Mark,

Wow great work.

For me my current status is

Good and frequent access to a Nissan Leaf - YES RS232-to-USB adaptor and laptop (or laptop with RS232 port) - YES

OVMS v2 Module - Accepted Kevin's offer of h/w waiting for delivery OVMS v2 OBD-II cable - Accepted Kevin's offer of h/w waiting for delivery

PICKIT2 or PICKIT3 programmer - Will order one today (any suggestions to a good source?)

Regards, Rob

---- On Tue, 22 Oct 2013 02:11:52 +0100 Mark Webb-Johnson<mark@webb-johnson.net> wrote ----

OK, here's an update...

I went through the logs we captured, and had a look at Leaf Spy. I even purchased a copy of Leaf Spy Pro (even though I don't have a Leaf) just as a donation to say thank you to Turbo3 for pushing this approach and working out so much of the mechanics of it.

I spent an evening reading through the "Using clone ELM327 Bluetooth OBDII adapter with Leaf" on mynissanleaf.com (all 238 pages of it!), and got a good understanding of the history of where CAN decoding on the Nissan Leaf is, and where it is headed.

Bottom line:

There are two CAN buses in the Nissan Leaf that are useful to us: the EV CAN bus and the CAR CAN bus. The standard OVMS OBD-II cable connects to the CAR CAN bus. By passive listening on the bus, we can see some EV information, and all of the car information. The EV CAN bus is also available on the OBD-II socket. By passive listening on the bus, we can see all the EV information, but little-to-no car information. OVMS V2 hardware can only connect to one bus. Someone worked out that active requests for information from the controllers (PID polling, as opposed to passive listening) are bridged. You can request information from a controller on the EV CAN bus, via the CAR CAN bus, and the car will bridge the requests between the buses. This appears to work bi-directionally. There is a slight nasty in that if the car is off (asleep), active polling the EV controller causes it to wake up and you can hear a little 12V relay click near the front of the car each time you poll. We don't want to poll too fast when the car is asleep (off) and not charging, to avoid wearing out that relay. The OBD-II connector has 12V power (both switched and non-switched) that we can use for OVMS, powered by an automotive 12V lead acid battery. We do need to take care because apparently that 12V battery is only charged when you drive or once every five days when the car is unplugged (and not at all when the car is plugged in). There is a CAR CAN message to show the 12V battery voltage (and OVMS V2 can also measure directly). There is 'active discussion' in the community on how things like SOC%, battery capacity, ideal and estimated ranges, should be determined. Nissan made a mess of it, and the users are struggling to agree on a uniform approach to a correct way of doing things.

I think our plan of attack should be:

Use a standard V2 module, with standard OVMS OBD-II cable, to connect to the CAR CAN bus. Use passive CAN listening, for the car information (doors, speed, on/off, etc) as much as possible. Use active CAN polling, bridged to the EV CAN bus, for the EV information that we need. Agree our own user-centric approach of how to represent capacity, SOC, ideal and estimated ranges.

It has been quite frustrating looking at the community documentation for CAN bus messages in the Leaf. The documentation doesn't match what I am seeing, and is not at all clear. A lot of people are sharing, but some seem to be holding back and saying things like "here are some clues to what I've found, so go look for it yourself". Some closed source. Not the way I like to do things.

There is one very good thread on the active CAN bus polling, here:

http://www.mynissanleaf.com/viewtopic.php?f=44&t=11676

A good background read (34 pages) on Leaf CAN bus passive monitoring is here:

http://www.mynissanleaf.com/viewtopic.php?f=8&t=4131

and I recommend everyone involved in this to read that thread (only 12 pages) to get a good understanding.

There are two spreadsheets tracking Leaf CAN bus messages:

https://docs.google.com/spreadsheet/ccc?key=0AuDGAXnbchK0dDc4T05oNE04aVZtUzB...

https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1...

So, what I'm going to do now is to setup a framework in the vehicle_nissanleaf module to do passive listening on the CAR CAN bus, and active polling of the information on the EV CAN bus (bridged via CAR CAN bus). Once the framework is done, I'll test it in the local Hong Kong Leaf, and ask you guys to help.

I do need one or two people with the following equipment to help out:

Good and frequent access to a Nissan Leaf OVMS v2 Module OVMS v2 OBD-II cable PICKIT2 or PICKIT3 programmer RS232-to-USB adaptor and laptop (or laptop with RS232 port)

This is to run the framework in their car, and capture RS232 output from the DIAG port.

So, volunteers please.

Regards, Mark.

On 19 Oct, 2013, at 11:23 pm, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

...

I met up with a local Leaf owner (George) and spent a few hours in the car logging stuff off the main CAN bus. The car is a 2011 model, I think (the VIN model year is U/V, which makes no sense).

Good news it that the OVMS cables are fine. The ‘right hand’ ovms obdii cable appears to be the best for the right hand drive nissan leafs. The OBDII connector is under the steering wheel, parallel with the car direction of travel, short side on the left, so using a right-hand cable directs the cable towards the front of the car, which should be easiest for routing.

I managed to get quite a few log files, using a standard CAN USB adaptor at 512kbps.

Bad news is I am having trouble correlating lots of the messages against the published spreadsheets of Leaf can bus messages. Some messages are partially correct, but many are missing / don’t match up. The car also seems to go to sleep during charging, although the leaf spy could update the SOC ok. The 0x5b3 SOC+GIDS message wasn’t visible on the bus at all.

I think we are going to have to use PID polling to get the data we need.

Regards, Mark.

On 16 Oct, 2013, at 10:31 pm, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

...

Anyone feeling brave?

I’ve just committed a nissan leaf module (set vehicle id to NL) that will monitor the can bus and pickup the SOC%. That is all it does at the moment, but it should work.

Regards, Mark.

On 16 Oct, 2013, at 2:49 pm, Nikki Gordon-Bloomfield <nikki@littlecollie.com> wrote:

...

I've already messages mark C. Let's hope he has it :) I know he and his husband have done a lot of logging.

Sent from my iPhone

On 16 Oct 2013, at 07:02, Robert Sharpe <robert.sharpe@evergreen-consulting.co.uk> wrote:

...

Hi Mark,

>I think the fastest way to get this done is for me to do it with a local Leaf owner. That sounds like a good idea.

>Can someone tell me which CarCAN bus message to look for, which byte(s) to access, and how to convert to percentage SOC? >The document at https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1... suggests ID 5B3 tracks SOH and Gids. But how to convert to percentage SOC?

Is @nufkin (Mark C) on this list? He has done some analysis of codes. There is always the authors of the other projects that read Leaf data.

Regards, Rob

On Oct 16, 2013, at 6.33AM, Mark Webb-Johnson wrote:

I think the fastest way to get this done is for me to do it with a local Leaf owner.

If I can get basic support working, then perhaps someone else (or others) with better knowledge of the Leaf scene, can take over to get the advanced stuff working.

So, I'm going to try to get some Leaf Spy traces, as well as CAN bus logs for parked, charging and driving. Then, get the basic module working with SOC%, GPS location, door status, drive/park and charge monitor.

My biggest confusion at the moment is SOC% in the Leaf. There is a lot of talk about gids, etc, but I've never gone into it too deeply.

Can someone tell me which CarCAN bus message to look for, which byte(s) to access, and how to convert to percentage SOC?

The document at https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1... suggests ID 5B3 tracks SOH and Gids. But how to convert to percentage SOC?

Regards, Mark.

On 16 Oct, 2013, at 1:03 pm, Evergreen <robert.sharpe@evergreen-consulting.co.uk">target="_blank">robert.sharpe@evergreen-consulting.co.uk> wrote:

That's great news.

Regards, Rob

On 16 Oct 2013, at 06:00, Mark Webb-Johnson <mark@webb-johnson.net">target="_blank">mark@webb-johnson.net> wrote:

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.

I think my fishing expedition on the forums may have come up with a bite. A Hong Kong Leaf owner who is willing to help.

I'll let you know how it pans out (over the next couple of days), but if I can get access to a local Leaf, getting the basic support working should be much faster.

Regards, Mark.

On 15 Oct, 2013, at 1:00 pm, Mark Webb-Johnson <mark@webb-johnson.net">target="_blank">mark@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@gmail.com">target="_blank">gbarry42@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@webb-johnson.net">target="_blank">mark@webb-johnson.net> wrote: Developers guide is here:

https://github.com/markwj/Open-Vehicle-Monitoring-System/blob/master/docs/OV...

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@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

---

OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

Tom, Strange. I checked a few PICKIT2 I have, and they all work. For my original testing, I tried two eBay clones, two fasttech ones, and two little Malaysian thumb-drive sized ones - all were ok. The OVMS board does have a fairly large modem, which complicates things. Maybe just not enough power? Can you try to press the little modem power button on the motherboard, to shut down the modem? See if that makes a difference. Regards, Mark. On 23 Oct, 2013, at 5:29 am, Tom Saxton <tom@idleloop.com> wrote:

I'm not able to program the V2 board with the PICkit2 unless the board plugged into the car to get 12V power, so I'd recommend the PICKit3, which I'm assuming doesn't have this issue.

I need to either build a cable to power the OVMS from a power supply or order the PICKit3 from Fasttech. For now, my laptop is living in the Roadster's passenger seat while I've been doing some work on the charge time predictor.

Tom

From: Mark Webb-Johnson <mark@webb-johnson.net> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Date: Monday, October 21, 2013 11:42 PM To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Subject: Re: [Ovmsdev] OVMS Leaf Support

Rob,

If you are not developing code then a PICKIT2 is easier.

The original is here:

...

http://www.amazon.co.uk/Microchip-PG164120-Programmer-Pickit-2/dp/B0040ZRGCQ...

but as it is 'open source', there are lots of much cheaper clones. For example:

...

http://www.fasttech.com/products/0/10000018/1002200-pickit-2-compatible-prog...

Personally, I'd go with the clone.

Regards, Mark.

On 22 Oct, 2013, at 2:32 pm, Robert Sharpe <robert.sharpe@evergreen-consulting.co.uk> wrote:

...

Hi Mark,

Wow great work.

For me my current status is

...

Good and frequent access to a Nissan Leaf - YES RS232-to-USB adaptor and laptop (or laptop with RS232 port) - YES

OVMS v2 Module - Accepted Kevin's offer of h/w waiting for delivery OVMS v2 OBD-II cable - Accepted Kevin's offer of h/w waiting for delivery

PICKIT2 or PICKIT3 programmer - Will order one today (any suggestions to a good source?)

Regards, Rob

---- On Tue, 22 Oct 2013 02:11:52 +0100 Mark Webb-Johnson<mark@webb-johnson.net> wrote ----

...

OK, here's an update...

I went through the logs we captured, and had a look at Leaf Spy. I even purchased a copy of Leaf Spy Pro (even though I don't have a Leaf) just as a donation to say thank you to Turbo3 for pushing this approach and working out so much of the mechanics of it.

I spent an evening reading through the "Using clone ELM327 Bluetooth OBDII adapter with Leaf" on mynissanleaf.com (all 238 pages of it!), and got a good understanding of the history of where CAN decoding on the Nissan Leaf is, and where it is headed.

Bottom line:

There are two CAN buses in the Nissan Leaf that are useful to us: the EV CAN bus and the CAR CAN bus. The standard OVMS OBD-II cable connects to the CAR CAN bus. By passive listening on the bus, we can see some EV information, and all of the car information. The EV CAN bus is also available on the OBD-II socket. By passive listening on the bus, we can see all the EV information, but little-to-no car information. OVMS V2 hardware can only connect to one bus. Someone worked out that active requests for information from the controllers (PID polling, as opposed to passive listening) are bridged. You can request information from a controller on the EV CAN bus, via the CAR CAN bus, and the car will bridge the requests between the buses. This appears to work bi-directionally. There is a slight nasty in that if the car is off (asleep), active polling the EV controller causes it to wake up and you can hear a little 12V relay click near the front of the car each time you poll. We don't want to poll too fast when the car is asleep (off) and not charging, to avoid wearing out that relay. The OBD-II connector has 12V power (both switched and non-switched) that we can use for OVMS, powered by an automotive 12V lead acid battery. We do need to take care because apparently that 12V battery is only charged when you drive or once every five days when the car is unplugged (and not at all when the car is plugged in). There is a CAR CAN message to show the 12V battery voltage (and OVMS V2 can also measure directly). There is 'active discussion' in the community on how things like SOC%, battery capacity, ideal and estimated ranges, should be determined. Nissan made a mess of it, and the users are struggling to agree on a uniform approach to a correct way of doing things.

I think our plan of attack should be:

Use a standard V2 module, with standard OVMS OBD-II cable, to connect to the CAR CAN bus. Use passive CAN listening, for the car information (doors, speed, on/off, etc) as much as possible. Use active CAN polling, bridged to the EV CAN bus, for the EV information that we need. Agree our own user-centric approach of how to represent capacity, SOC, ideal and estimated ranges.

It has been quite frustrating looking at the community documentation for CAN bus messages in the Leaf. The documentation doesn't match what I am seeing, and is not at all clear. A lot of people are sharing, but some seem to be holding back and saying things like "here are some clues to what I've found, so go look for it yourself". Some closed source. Not the way I like to do things.

There is one very good thread on the active CAN bus polling, here:

...

http://www.mynissanleaf.com/viewtopic.php?f=44&t=11676

A good background read (34 pages) on Leaf CAN bus passive monitoring is here:

...

http://www.mynissanleaf.com/viewtopic.php?f=8&t=4131

and I recommend everyone involved in this to read that thread (only 12 pages) to get a good understanding.

There are two spreadsheets tracking Leaf CAN bus messages:

...

https://docs.google.com/spreadsheet/ccc?key=0AuDGAXnbchK0dDc4T05oNE04aVZtUzB...

https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1...

So, what I'm going to do now is to setup a framework in the vehicle_nissanleaf module to do passive listening on the CAR CAN bus, and active polling of the information on the EV CAN bus (bridged via CAR CAN bus). Once the framework is done, I'll test it in the local Hong Kong Leaf, and ask you guys to help.

I do need one or two people with the following equipment to help out:

...

Good and frequent access to a Nissan Leaf OVMS v2 Module OVMS v2 OBD-II cable PICKIT2 or PICKIT3 programmer RS232-to-USB adaptor and laptop (or laptop with RS232 port)

This is to run the framework in their car, and capture RS232 output from the DIAG port.

So, volunteers please.

Regards, Mark.

On 19 Oct, 2013, at 11:23 pm, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

...

I met up with a local Leaf owner (George) and spent a few hours in the car logging stuff off the main CAN bus. The car is a 2011 model, I think (the VIN model year is U/V, which makes no sense).

Good news it that the OVMS cables are fine. The ‘right hand’ ovms obdii cable appears to be the best for the right hand drive nissan leafs. The OBDII connector is under the steering wheel, parallel with the car direction of travel, short side on the left, so using a right-hand cable directs the cable towards the front of the car, which should be easiest for routing.

I managed to get quite a few log files, using a standard CAN USB adaptor at 512kbps.

Bad news is I am having trouble correlating lots of the messages against the published spreadsheets of Leaf can bus messages. Some messages are partially correct, but many are missing / don’t match up. The car also seems to go to sleep during charging, although the leaf spy could update the SOC ok. The 0x5b3 SOC+GIDS message wasn’t visible on the bus at all.

I think we are going to have to use PID polling to get the data we need.

Regards, Mark.

On 16 Oct, 2013, at 10:31 pm, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

...

Anyone feeling brave?

I’ve just committed a nissan leaf module (set vehicle id to NL) that will monitor the can bus and pickup the SOC%. That is all it does at the moment, but it should work.

Regards, Mark.

On 16 Oct, 2013, at 2:49 pm, Nikki Gordon-Bloomfield <nikki@littlecollie.com> wrote:

...

I've already messages mark C. Let's hope he has it :) I know he and his husband have done a lot of logging.

Sent from my iPhone

On 16 Oct 2013, at 07:02, Robert Sharpe <robert.sharpe@evergreen-consulting.co.uk> wrote:

> Hi Mark, > > >I think the fastest way to get this done is for me to do it with a local Leaf owner. > That sounds like a good idea. > > >Can someone tell me which CarCAN bus message to look for, which byte(s) to access, and how to convert to percentage SOC? > >The document at https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1... suggests ID 5B3 tracks SOH and Gids. But how to convert to percentage SOC? > > Is @nufkin (Mark C) on this list? He has done some analysis of codes. > There is always the authors of the other projects that read Leaf data. > > Regards, > Rob > > > On Oct 16, 2013, at 6.33AM, Mark Webb-Johnson wrote: >> >> I think the fastest way to get this done is for me to do it with a local Leaf owner. >> >> If I can get basic support working, then perhaps someone else (or others) with better knowledge of the Leaf scene, can take over to get the advanced stuff working. >> >> So, I'm going to try to get some Leaf Spy traces, as well as CAN bus logs for parked, charging and driving. Then, get the basic module working with SOC%, GPS location, door status, drive/park and charge monitor. >> >> My biggest confusion at the moment is SOC% in the Leaf. There is a lot of talk about gids, etc, but I've never gone into it too deeply. >> >> Can someone tell me which CarCAN bus message to look for, which byte(s) to access, and how to convert to percentage SOC? >> >> The document at https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1... suggests ID 5B3 tracks SOH and Gids. But how to convert to percentage SOC? >> >> Regards, Mark. >> >> On 16 Oct, 2013, at 1:03 pm, Evergreen <robert.sharpe@evergreen-consulting.co.uk">target="_blank">robert.sharpe@evergreen-consulting.co.uk> wrote: >> >>> That's great news. >>> >>> Regards, >>> Rob >>> >>> On 16 Oct 2013, at 06:00, Mark Webb-Johnson <mark@webb-johnson.net">target="_blank">mark@webb-johnson.net> wrote: >>> >>>> >>>>> 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. >>>> >>>> I think my fishing expedition on the forums may have come up with a bite. A Hong Kong Leaf owner who is willing to help. >>>> >>>> I'll let you know how it pans out (over the next couple of days), but if I can get access to a local Leaf, getting the basic support working should be much faster. >>>> >>>> Regards, Mark. >>>> >>>> On 15 Oct, 2013, at 1:00 pm, Mark Webb-Johnson <mark@webb-johnson.net">target="_blank">mark@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@gmail.com">target="_blank">gbarry42@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@webb-johnson.net">target="_blank">mark@webb-johnson.net> wrote: >>>>>>> Developers guide is here: >>>>>>> >>>>>>>> https://github.com/markwj/Open-Vehicle-Monitoring-System/blob/master/docs/OV... >>>>>>> >>>>>>> >>>>>>> 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@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk >>>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev >>>>> >>>>> _______________________________________________ >>>>> OvmsDev mailing list >>>>> OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk >>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev >>>> >>>> _______________________________________________ >>>> OvmsDev mailing list >>>> OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk >>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev >>> _______________________________________________ >>> OvmsDev mailing list >>> OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk >>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev >> > > > _______________________________________________ > OvmsDev mailing list > OvmsDev@lists.teslaclub.hk > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

Just to follow up on this side-thread... I am able to problem a V2 board with a PICkit 2 programmer. I doesn't work from the USB port on the front of my Mac Pro, but it does work from the Mac Pro when plugged into a powered USB hub or directly from my MacBook Air. Tom From: Matt Beard <matt@beard.tv> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Date: Tuesday, October 22, 2013 at 9:34 PM To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Subject: Re: [Ovmsdev] OVMS Leaf Support I use a PICKIT2 and have had no issues programming the V2 board. Maybe you have a faulty unit, or your USB port can't supply the required power. Matt On Wednesday, October 23, 2013, Mark Webb-Johnson wrote:

Tom,

Strange. I checked a few PICKIT2 I have, and they all work. For my original testing, I tried two eBay clones, two fasttech ones, and two little Malaysian thumb-drive sized ones - all were ok.

The OVMS board does have a fairly large modem, which complicates things. Maybe just not enough power?

Can you try to press the little modem power button on the motherboard, to shut down the modem? See if that makes a difference.

Regards, Mark.

On 23 Oct, 2013, at 5:29 am, Tom Saxton <tom@idleloop.com> wrote:

...

I'm not able to program the V2 board with the PICkit2 unless the board plugged into the car to get 12V power, so I'd recommend the PICKit3, which I'm assuming doesn't have this issue.

I need to either build a cable to power the OVMS from a power supply or order the PICKit3 from Fasttech. For now, my laptop is living in the Roadster's passenger seat while I've been doing some work on the charge time predictor.

Tom

From: Mark Webb-Johnson <mark@webb-johnson.net> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Date: Monday, October 21, 2013 11:42 PM To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Subject: Re: [Ovmsdev] OVMS Leaf Support

Rob,

If you are not developing code then a PICKIT2 is easier.

The original is here:

...

http://www.amazon.co.uk/Microchip-PG164120-Programmer-Pickit-2/dp/B0040ZRGCQ /ref=sr_1_4?s=electronics&ie=UTF8&qid=1382423740&sr=1-4&keywords=pickit2

but as it is 'open source', there are lots of much cheaper clones. For example:

...

http://www.fasttech.com/products/0/10000018/1002200-pickit-2-compatible-prog rammerdebugger

Personally, I'd go with the clone.

Regards, Mark.

On 22 Oct, 2013, at 2:32 pm, Robert Sharpe <robert.sharpe@evergreen-consulting.co.uk> wrote:

...

Hi Mark,

Wow great work.

For me my current status is

...

Good and frequent access to a Nissan Leaf - YES RS232-to-USB adaptor and laptop (or laptop with RS232 port) - YES

OVMS v2 Module - Accepted Kevin's offer of h/w waiting for delivery OVMS v2 OBD-II cable - Accepted Kevin's offer of h/w waiting for delivery

PICKIT2 or PICKIT3 programmer - Will order one today (any suggestions to a good source?)

Regards, Rob

---- On Tue, 22 Oct 2013 02:11:52 +0100 Mark Webb-Johnson<mark@webb-johnson.net> wrote ----

...

OK, here's an update...

I went through the logs we captured, and had a look at Leaf Spy. I even purchased a copy of Leaf Spy Pro (even though I don't have a Leaf) just as a donation to say thank you to Turbo3 for pushing this approach and working out so much of the mechanics of it.

I spent an evening reading thro _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

Mark, Regarding the 12V drain. As I understand it, the 12V battery gets charged when the car is plugged in and the main traction battery is getting charged. When the car is plugged in and it is NOT charging, the on-board computer wakes up every n seconds and polls its various systems. Because this uses more power than normal 'standby' mode, it quickly drains the battery. If we assume most owners are not going to leave their cars plugged in for days at a time, the issue should be moot, although it's worth playing on the cautious side. Instances of 12V drainage in LEAFs are almost exclusively related to cars which have sat plugged in at charging stations for extended periods of time, such as when their owners go on holiday. Last time I went abroad, I kept my LEAF plugged in, but did the following: Left the car on the first night without a full charge. I think SOC was about 25% if I remember correctly. Set the car's timer to charge every night while I was away with an 80 percent 'limited' charge profile, starting at midnight, and finishing at half-past midnight. On a standard 16 amp EVSE, this meant that the car slowly charged over the course of the week, getting topped up a little more every night. Because the 12V battery was charged too during that period, I was able to keep it happy also, preventing any horrible 'soft-brick' scenarios. What does this tell us? First, I'm pretty sure the 12V battery DOES get charged when the main traction back gets charged. But when the car is plugged in and not charging, NOTHING gets charged and the 12V battery gets drained at a far faster rate than it would be if it was left alone for a few weeks. But I think it also tells us some other important things. IN most situations, (everyday ones, at least) 12V battery drain shouldn't be a problem. I'm happy to be the Guinea pig for this one when Kevin gets the OVMS hardware through customs. The only risk to the car occurs when the car is parked for long periods without being plugged in -- or when it is plugged in but hasn't charged for x hours/days. A work-around here would be to use the parking timer combined with a 'last-charged' timer. If the timer > 24 hours, per say, could we put the OVMS into some form of low-power mode, so it doesn't poll the car and drain that 12V battery as quickly? I know from my Twizy that the OVMS system really does have a very low power drain, so I'm assuming any massive power drains associated with OVMS come from the car's on-board CAN hardware waking up and communicating with the module? We can use the 12V monitoring system already built into OVMS to set an early-warning alert if voltages start to drop, right? If done correctly, it's possible to keep the car plugged in for long periods of time, without adversely affecting the 12V battery. This is a matter of driver education more than anything else. I also think it's worth noting that many LEAFs which have had 12V battery issues are ones which have either spent a lot of time sitting on dealer lots, or are regularly left for long periods of time. It's my opinion that like any car, the LEAF benefits from being driven daily… ;) As soon as Kevin gets the hardware through customs, I'm willing to give this all a go. But a quick question: can I run OVMS alongside LEAFSpy, using an ODBII splitter? Nikki. P.S. FYI, Nissan has changed the position of the ODB port on the 2013 model year cars. It's now behind a small panel to the right of the driver's right (left in LHD countries) knee. Orientation is also moved too. Here's a photo of new vs old. -- You'll notice the new car has an extra port too. Not sure what it's for… Old port is right under the dash, with the catch-side facing to the driver's left. On 22 Oct 2013, at 02:11, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

OK, here's an update...

I went through the logs we captured, and had a look at Leaf Spy. I even purchased a copy of Leaf Spy Pro (even though I don't have a Leaf) just as a donation to say thank you to Turbo3 for pushing this approach and working out so much of the mechanics of it.

I spent an evening reading through the "Using clone ELM327 Bluetooth OBDII adapter with Leaf" on mynissanleaf.com (all 238 pages of it!), and got a good understanding of the history of where CAN decoding on the Nissan Leaf is, and where it is headed.

Bottom line:

There are two CAN buses in the Nissan Leaf that are useful to us: the EV CAN bus and the CAR CAN bus. The standard OVMS OBD-II cable connects to the CAR CAN bus. By passive listening on the bus, we can see some EV information, and all of the car information. The EV CAN bus is also available on the OBD-II socket. By passive listening on the bus, we can see all the EV information, but little-to-no car information. OVMS V2 hardware can only connect to one bus. Someone worked out that active requests for information from the controllers (PID polling, as opposed to passive listening) are bridged. You can request information from a controller on the EV CAN bus, via the CAR CAN bus, and the car will bridge the requests between the buses. This appears to work bi-directionally. There is a slight nasty in that if the car is off (asleep), active polling the EV controller causes it to wake up and you can hear a little 12V relay click near the front of the car each time you poll. We don't want to poll too fast when the car is asleep (off) and not charging, to avoid wearing out that relay. The OBD-II connector has 12V power (both switched and non-switched) that we can use for OVMS, powered by an automotive 12V lead acid battery. We do need to take care because apparently that 12V battery is only charged when you drive or once every five days when the car is unplugged (and not at all when the car is plugged in). There is a CAR CAN message to show the 12V battery voltage (and OVMS V2 can also measure directly). There is 'active discussion' in the community on how things like SOC%, battery capacity, ideal and estimated ranges, should be determined. Nissan made a mess of it, and the users are struggling to agree on a uniform approach to a correct way of doing things.

I think our plan of attack should be:

Use a standard V2 module, with standard OVMS OBD-II cable, to connect to the CAR CAN bus. Use passive CAN listening, for the car information (doors, speed, on/off, etc) as much as possible. Use active CAN polling, bridged to the EV CAN bus, for the EV information that we need. Agree our own user-centric approach of how to represent capacity, SOC, ideal and estimated ranges.

It has been quite frustrating looking at the community documentation for CAN bus messages in the Leaf. The documentation doesn't match what I am seeing, and is not at all clear. A lot of people are sharing, but some seem to be holding back and saying things like "here are some clues to what I've found, so go look for it yourself". Some closed source. Not the way I like to do things.

There is one very good thread on the active CAN bus polling, here:

http://www.mynissanleaf.com/viewtopic.php?f=44&t=11676

A good background read (34 pages) on Leaf CAN bus passive monitoring is here:

http://www.mynissanleaf.com/viewtopic.php?f=8&t=4131

and I recommend everyone involved in this to read that thread (only 12 pages) to get a good understanding.

There are two spreadsheets tracking Leaf CAN bus messages:

https://docs.google.com/spreadsheet/ccc?key=0AuDGAXnbchK0dDc4T05oNE04aVZtUzB...

https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1...

So, what I'm going to do now is to setup a framework in the vehicle_nissanleaf module to do passive listening on the CAR CAN bus, and active polling of the information on the EV CAN bus (bridged via CAR CAN bus). Once the framework is done, I'll test it in the local Hong Kong Leaf, and ask you guys to help.

I do need one or two people with the following equipment to help out:

Good and frequent access to a Nissan Leaf OVMS v2 Module OVMS v2 OBD-II cable PICKIT2 or PICKIT3 programmer RS232-to-USB adaptor and laptop (or laptop with RS232 port)

This is to run the framework in their car, and capture RS232 output from the DIAG port.

So, volunteers please.

Regards, Mark.

On 19 Oct, 2013, at 11:23 pm, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

...

I met up with a local Leaf owner (George) and spent a few hours in the car logging stuff off the main CAN bus. The car is a 2011 model, I think (the VIN model year is U/V, which makes no sense).

Good news it that the OVMS cables are fine. The ‘right hand’ ovms obdii cable appears to be the best for the right hand drive nissan leafs. The OBDII connector is under the steering wheel, parallel with the car direction of travel, short side on the left, so using a right-hand cable directs the cable towards the front of the car, which should be easiest for routing.

I managed to get quite a few log files, using a standard CAN USB adaptor at 512kbps.

Bad news is I am having trouble correlating lots of the messages against the published spreadsheets of Leaf can bus messages. Some messages are partially correct, but many are missing / don’t match up. The car also seems to go to sleep during charging, although the leaf spy could update the SOC ok. The 0x5b3 SOC+GIDS message wasn’t visible on the bus at all.

I think we are going to have to use PID polling to get the data we need.

Regards, Mark.

On 16 Oct, 2013, at 10:31 pm, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

...

Anyone feeling brave?

I’ve just committed a nissan leaf module (set vehicle id to NL) that will monitor the can bus and pickup the SOC%. That is all it does at the moment, but it should work.

Regards, Mark.

On 16 Oct, 2013, at 2:49 pm, Nikki Gordon-Bloomfield <nikki@littlecollie.com> wrote:

...

I've already messages mark C. Let's hope he has it :) I know he and his husband have done a lot of logging.

Sent from my iPhone

On 16 Oct 2013, at 07:02, Robert Sharpe <robert.sharpe@evergreen-consulting.co.uk> wrote:

...

Hi Mark,

...

I think the fastest way to get this done is for me to do it with a local Leaf owner. That sounds like a good idea.

...

Can someone tell me which CarCAN bus message to look for, which byte(s) to access, and how to convert to percentage SOC? The document at https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1... suggests ID 5B3 tracks SOH and Gids. But how to convert to percentage SOC?

Is @nufkin (Mark C) on this list? He has done some analysis of codes. There is always the authors of the other projects that read Leaf data.

Regards, Rob

On Oct 16, 2013, at 6.33AM, Mark Webb-Johnson wrote:

I think the fastest way to get this done is for me to do it with a local Leaf owner.

If I can get basic support working, then perhaps someone else (or others) with better knowledge of the Leaf scene, can take over to get the advanced stuff working.

So, I'm going to try to get some Leaf Spy traces, as well as CAN bus logs for parked, charging and driving. Then, get the basic module working with SOC%, GPS location, door status, drive/park and charge monitor.

My biggest confusion at the moment is SOC% in the Leaf. There is a lot of talk about gids, etc, but I've never gone into it too deeply.

Can someone tell me which CarCAN bus message to look for, which byte(s) to access, and how to convert to percentage SOC?

The document at https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1... suggests ID 5B3 tracks SOH and Gids. But how to convert to percentage SOC?

Regards, Mark.

On 16 Oct, 2013, at 1:03 pm, Evergreen <robert.sharpe@evergreen-consulting.co.uk">target="_blank">robert.sharpe@evergreen-consulting.co.uk> wrote:

That's great news.

Regards, Rob

On 16 Oct 2013, at 06:00, Mark Webb-Johnson <mark@webb-johnson.net">target="_blank">mark@webb-johnson.net> wrote:

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.

I think my fishing expedition on the forums may have come up with a bite. A Hong Kong Leaf owner who is willing to help.

I'll let you know how it pans out (over the next couple of days), but if I can get access to a local Leaf, getting the basic support working should be much faster.

Regards, Mark.

On 15 Oct, 2013, at 1:00 pm, Mark Webb-Johnson <mark@webb-johnson.net">target="_blank">mark@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@gmail.com">target="_blank">gbarry42@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@webb-johnson.net">target="_blank">mark@webb-johnson.net> wrote: Developers guide is here:

https://github.com/markwj/Open-Vehicle-Monitoring-System/blob/master/docs/OV...

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@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

---

OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

A short update: I’m working on the code to handle the Leaf PID polling via the CAR-to-EV bus bridge. It seems ok, but I’m trying to make it modular as we are now doing this same sort of polling in quite a few vehicle modules and it seems sensible to centralise it (to save code space and complexity). It is tricky, because of the relay issue, as we need to make the polling frequency configurable depending on states. I’m making progress and hope to have something within the coming week. My first version of code is going to output to the DIAG serial port lots of data to tell us what is going on. So, I need testers with a (a) laptop, (b) usb-to-serial converter, (c) Leaf, (d) PICKIT, (e) OVMS module, (f) standard OVMS OBD-II cable. Testing will be flashing the module with a HEX I provide, then putting it in the car and getting a log file of the DIAG port to send me. Regards, Mark. On 22 Oct, 2013, at 9:37 pm, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

Nikki,

Thanks for detailed explanation.

...

could we put the OVMS into some form of low-power mode, so it doesn't poll the car and drain that 12V battery as quickly?

Possibly. We haven’t handled that yet, and our tests with it so far have not been very successful. The biggest power draw is the modem. Best we can do is shut that down and delay-loop-spin if 12V gets to low.

...

We can use the 12V monitoring system already built into OVMS to set an early-warning alert if voltages start to drop, right?

Yes. The leaf also seems to have 12V level in a can bus signal, which shouldn’t need to be calibrated and may give us a better result.

...

But a quick question: can I run OVMS alongside LEAFSpy, using an ODBII splitter?

Hmmm. Without special handling, that would be problematic. We would both end up polling the same things, and one/both of us would get confused.

I should have thought that we can listen on the bus first, and make sure there are no polling signals for N seconds, before we start polling ourselves. Similarly, if we see a polling signal/reply, we can back off. But, one concern is that in my tests last weekend, I tried a CAN bus logger and OBD-II with leaf spy together, but didn’t see much. All I saw were some replies:

1382228933.303 R11 797 02 10 C0 00 00 00 00 00 1382229549.511 R11 797 03 22 12 4E 00 00 00 00 1382229799.599 R11 797 03 22 11 5D 00 00 00 00 1382230050.688 R11 797 03 22 13 2A 00 00 00 00 1382230425.777 R11 797 03 22 12 55 00 00 00 00 1382230869.926 R11 797 03 22 13 04 00 00 00 00

so, it looks like I can see someone else polling (and can back off appropriately), but I don’t think I can listen to their replies as if I was polling myself! That would be cool (so long as leaf spy and ovms were polling for the exact same things), and I don’t see why it wouldn’t work, but I just didn’t see that behaviour when I T’ed the bus last weekend.

Regards, Mark.

On 22 Oct, 2013, at 4:23 pm, Nikki Gordon-Bloomfield <nikki@aminorjourney.com> wrote:

...

Mark,

Regarding the 12V drain. As I understand it, the 12V battery gets charged when the car is plugged in and the main traction battery is getting charged. When the car is plugged in and it is NOT charging, the on-board computer wakes up every n seconds and polls its various systems. Because this uses more power than normal 'standby' mode, it quickly drains the battery. If we assume most owners are not going to leave their cars plugged in for days at a time, the issue should be moot, although it's worth playing on the cautious side.

Instances of 12V drainage in LEAFs are almost exclusively related to cars which have sat plugged in at charging stations for extended periods of time, such as when their owners go on holiday. Last time I went abroad, I kept my LEAF plugged in, but did the following:

Left the car on the first night without a full charge. I think SOC was about 25% if I remember correctly. Set the car's timer to charge every night while I was away with an 80 percent 'limited' charge profile, starting at midnight, and finishing at half-past midnight. On a standard 16 amp EVSE, this meant that the car slowly charged over the course of the week, getting topped up a little more every night. Because the 12V battery was charged too during that period, I was able to keep it happy also, preventing any horrible 'soft-brick' scenarios. What does this tell us? First, I'm pretty sure the 12V battery DOES get charged when the main traction back gets charged. But when the car is plugged in and not charging, NOTHING gets charged and the 12V battery gets drained at a far faster rate than it would be if it was left alone for a few weeks.

But I think it also tells us some other important things.

IN most situations, (everyday ones, at least) 12V battery drain shouldn't be a problem. I'm happy to be the Guinea pig for this one when Kevin gets the OVMS hardware through customs. The only risk to the car occurs when the car is parked for long periods without being plugged in -- or when it is plugged in but hasn't charged for x hours/days. A work-around here would be to use the parking timer combined with a 'last-charged' timer. If the timer > 24 hours, per say, could we put the OVMS into some form of low-power mode, so it doesn't poll the car and drain that 12V battery as quickly? I know from my Twizy that the OVMS system really does have a very low power drain, so I'm assuming any massive power drains associated with OVMS come from the car's on-board CAN hardware waking up and communicating with the module? We can use the 12V monitoring system already built into OVMS to set an early-warning alert if voltages start to drop, right? If done correctly, it's possible to keep the car plugged in for long periods of time, without adversely affecting the 12V battery. This is a matter of driver education more than anything else.

I also think it's worth noting that many LEAFs which have had 12V battery issues are ones which have either spent a lot of time sitting on dealer lots, or are regularly left for long periods of time. It's my opinion that like any car, the LEAF benefits from being driven daily… ;)

As soon as Kevin gets the hardware through customs, I'm willing to give this all a go. But a quick question: can I run OVMS alongside LEAFSpy, using an ODBII splitter?

Nikki.

P.S. FYI, Nissan has changed the position of the ODB port on the 2013 model year cars. It's now behind a small panel to the right of the driver's right (left in LHD countries) knee. Orientation is also moved too. Here's a photo of new vs old.

<IMG_0525.jpeg> -- You'll notice the new car has an extra port too. Not sure what it's for…

<IMG_0528.jpeg> Old port is right under the dash, with the catch-side facing to the driver's left.

On 22 Oct 2013, at 02:11, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

...

OK, here's an update...

I went through the logs we captured, and had a look at Leaf Spy. I even purchased a copy of Leaf Spy Pro (even though I don't have a Leaf) just as a donation to say thank you to Turbo3 for pushing this approach and working out so much of the mechanics of it.

I spent an evening reading through the "Using clone ELM327 Bluetooth OBDII adapter with Leaf" on mynissanleaf.com (all 238 pages of it!), and got a good understanding of the history of where CAN decoding on the Nissan Leaf is, and where it is headed.

Bottom line:

There are two CAN buses in the Nissan Leaf that are useful to us: the EV CAN bus and the CAR CAN bus. The standard OVMS OBD-II cable connects to the CAR CAN bus. By passive listening on the bus, we can see some EV information, and all of the car information. The EV CAN bus is also available on the OBD-II socket. By passive listening on the bus, we can see all the EV information, but little-to-no car information. OVMS V2 hardware can only connect to one bus. Someone worked out that active requests for information from the controllers (PID polling, as opposed to passive listening) are bridged. You can request information from a controller on the EV CAN bus, via the CAR CAN bus, and the car will bridge the requests between the buses. This appears to work bi-directionally. There is a slight nasty in that if the car is off (asleep), active polling the EV controller causes it to wake up and you can hear a little 12V relay click near the front of the car each time you poll. We don't want to poll too fast when the car is asleep (off) and not charging, to avoid wearing out that relay. The OBD-II connector has 12V power (both switched and non-switched) that we can use for OVMS, powered by an automotive 12V lead acid battery. We do need to take care because apparently that 12V battery is only charged when you drive or once every five days when the car is unplugged (and not at all when the car is plugged in). There is a CAR CAN message to show the 12V battery voltage (and OVMS V2 can also measure directly). There is 'active discussion' in the community on how things like SOC%, battery capacity, ideal and estimated ranges, should be determined. Nissan made a mess of it, and the users are struggling to agree on a uniform approach to a correct way of doing things.

I think our plan of attack should be:

Use a standard V2 module, with standard OVMS OBD-II cable, to connect to the CAR CAN bus. Use passive CAN listening, for the car information (doors, speed, on/off, etc) as much as possible. Use active CAN polling, bridged to the EV CAN bus, for the EV information that we need. Agree our own user-centric approach of how to represent capacity, SOC, ideal and estimated ranges.

It has been quite frustrating looking at the community documentation for CAN bus messages in the Leaf. The documentation doesn't match what I am seeing, and is not at all clear. A lot of people are sharing, but some seem to be holding back and saying things like "here are some clues to what I've found, so go look for it yourself". Some closed source. Not the way I like to do things.

There is one very good thread on the active CAN bus polling, here:

http://www.mynissanleaf.com/viewtopic.php?f=44&t=11676

A good background read (34 pages) on Leaf CAN bus passive monitoring is here:

http://www.mynissanleaf.com/viewtopic.php?f=8&t=4131

and I recommend everyone involved in this to read that thread (only 12 pages) to get a good understanding.

There are two spreadsheets tracking Leaf CAN bus messages:

https://docs.google.com/spreadsheet/ccc?key=0AuDGAXnbchK0dDc4T05oNE04aVZtUzB...

https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1...

So, what I'm going to do now is to setup a framework in the vehicle_nissanleaf module to do passive listening on the CAR CAN bus, and active polling of the information on the EV CAN bus (bridged via CAR CAN bus). Once the framework is done, I'll test it in the local Hong Kong Leaf, and ask you guys to help.

I do need one or two people with the following equipment to help out:

Good and frequent access to a Nissan Leaf OVMS v2 Module OVMS v2 OBD-II cable PICKIT2 or PICKIT3 programmer RS232-to-USB adaptor and laptop (or laptop with RS232 port)

This is to run the framework in their car, and capture RS232 output from the DIAG port.

So, volunteers please.

Regards, Mark.

On 19 Oct, 2013, at 11:23 pm, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

...

I met up with a local Leaf owner (George) and spent a few hours in the car logging stuff off the main CAN bus. The car is a 2011 model, I think (the VIN model year is U/V, which makes no sense).

Good news it that the OVMS cables are fine. The ‘right hand’ ovms obdii cable appears to be the best for the right hand drive nissan leafs. The OBDII connector is under the steering wheel, parallel with the car direction of travel, short side on the left, so using a right-hand cable directs the cable towards the front of the car, which should be easiest for routing.

I managed to get quite a few log files, using a standard CAN USB adaptor at 512kbps.

Bad news is I am having trouble correlating lots of the messages against the published spreadsheets of Leaf can bus messages. Some messages are partially correct, but many are missing / don’t match up. The car also seems to go to sleep during charging, although the leaf spy could update the SOC ok. The 0x5b3 SOC+GIDS message wasn’t visible on the bus at all.

I think we are going to have to use PID polling to get the data we need.

Regards, Mark.

On 16 Oct, 2013, at 10:31 pm, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

...

Anyone feeling brave?

I’ve just committed a nissan leaf module (set vehicle id to NL) that will monitor the can bus and pickup the SOC%. That is all it does at the moment, but it should work.

Regards, Mark.

On 16 Oct, 2013, at 2:49 pm, Nikki Gordon-Bloomfield <nikki@littlecollie.com> wrote:

...

I've already messages mark C. Let's hope he has it :) I know he and his husband have done a lot of logging.

Sent from my iPhone

On 16 Oct 2013, at 07:02, Robert Sharpe <robert.sharpe@evergreen-consulting.co.uk> wrote:

> Hi Mark, > > >I think the fastest way to get this done is for me to do it with a local Leaf owner. > That sounds like a good idea. > > >Can someone tell me which CarCAN bus message to look for, which byte(s) to access, and how to convert to percentage SOC? > >The document at https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1... suggests ID 5B3 tracks SOH and Gids. But how to convert to percentage SOC? > > Is @nufkin (Mark C) on this list? He has done some analysis of codes. > There is always the authors of the other projects that read Leaf data. > > Regards, > Rob > > > On Oct 16, 2013, at 6.33AM, Mark Webb-Johnson wrote: > > I think the fastest way to get this done is for me to do it with a local Leaf owner. > > If I can get basic support working, then perhaps someone else (or others) with better knowledge of the Leaf scene, can take over to get the advanced stuff working. > > So, I'm going to try to get some Leaf Spy traces, as well as CAN bus logs for parked, charging and driving. Then, get the basic module working with SOC%, GPS location, door status, drive/park and charge monitor. > > My biggest confusion at the moment is SOC% in the Leaf. There is a lot of talk about gids, etc, but I've never gone into it too deeply. > > Can someone tell me which CarCAN bus message to look for, which byte(s) to access, and how to convert to percentage SOC? > > The document at https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1... suggests ID 5B3 tracks SOH and Gids. But how to convert to percentage SOC? > > Regards, Mark. > > On 16 Oct, 2013, at 1:03 pm, Evergreen <robert.sharpe@evergreen-consulting.co.uk">target="_blank">robert.sharpe@evergreen-consulting.co.uk> wrote: > > That's great news. > > Regards, > Rob > > On 16 Oct 2013, at 06:00, Mark Webb-Johnson <mark@webb-johnson.net">target="_blank">mark@webb-johnson.net> wrote: > > > 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. > > I think my fishing expedition on the forums may have come up with a bite. A Hong Kong Leaf owner who is willing to help. > > I'll let you know how it pans out (over the next couple of days), but if I can get access to a local Leaf, getting the basic support working should be much faster. > > Regards, Mark. > > On 15 Oct, 2013, at 1:00 pm, Mark Webb-Johnson <mark@webb-johnson.net">target="_blank">mark@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@gmail.com">target="_blank">gbarry42@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@webb-johnson.net">target="_blank">mark@webb-johnson.net> wrote: > Developers guide is here: > > https://github.com/markwj/Open-Vehicle-Monitoring-System/blob/master/docs/OV... > > 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@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > > _______________________________________________ > OvmsDev mailing list > OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > > _______________________________________________ > OvmsDev mailing list > OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > _______________________________________________ > OvmsDev mailing list > OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > > > > _______________________________________________ > OvmsDev mailing list > OvmsDev@lists.teslaclub.hk > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

Also plan to buy all the OVMS goodies soon, but those will take a few weeks to get in, I think?

If you're in Europe then ZCW have OVMS hardware in the UK; http://shop.zerocarbonworld.org/Open-Vehicles/

The only functions that the TCU/carwings can do is get the following data: # of bars,GOM range, plug/charging status, and estimated charging time invoke the following: charging now or turning on or off climate (which attempts to bring the cabin to 78F via heat or AC). Unlocking doors or other goodies might be something we can do after sniffing the car can bus some more! :-) Jeremy On Wed, Nov 6, 2013 at 12:36 AM, Mark Webb-Johnson <mark@webb-johnson.net>wrote:

Jeremy,

The OBDII port carries pins for both buses. OVMS could be connected to either, although the CAR CAN bus is on the standard OBDII pins for a CAN bus.

My preference is the CAR CAN bus at the moment, because we need stuff on the CAR bus, not just EV (like speed, etc), and standard cables can be used. It seems to have worked out very well for LeafSpy. But, there is no reason the OVMS could not be connected directly to EV bus.

If, as you say, the TCM module is connected to just the EV CAN bus that is very good news. It should just be a matter of listening in on what messages it sends on that bus to understand how it is doing things like locking doors, aircon control, etc. The bridge between EV and CAR buses is bi-directional, so perhaps it is also sending messages over to the CAR bus.

Regards, Mark.

On 6 Nov, 2013, at 2:38 pm, Jeremy Whaling <jeremy.whaling@gmail.com> wrote:

While I don't mind the OBD port route for now, eventually I'd like to have the option to have an OVMS module to drop into place of the original TCM which has connections to the EV can bus (only) and a built in GSM antenna. My USB-CAN came in today, hope to play with it a little bit this weekend.

Also plan to buy all the OVMS goodies soon, but those will take a few weeks to get in, I think?

Jeremy

On Tue, Nov 5, 2013 at 4:45 AM, Mark Webb-Johnson <mark@webb-johnson.net>wrote:

...

A short update:

I’m working on the code to handle the Leaf PID polling via the CAR-to-EV bus bridge. It seems ok, but I’m trying to make it modular as we are now doing this same sort of polling in quite a few vehicle modules and it seems sensible to centralise it (to save code space and complexity). It is tricky, because of the relay issue, as we need to make the polling frequency configurable depending on states.

I’m making progress and hope to have something within the coming week.

My first version of code is going to output to the DIAG serial port lots of data to tell us what is going on. So, I need testers with a (a) laptop, (b) usb-to-serial converter, (c) Leaf, (d) PICKIT, (e) OVMS module, (f) standard OVMS OBD-II cable. Testing will be flashing the module with a HEX I provide, then putting it in the car and getting a log file of the DIAG port to send me.

Regards, Mark.

On 22 Oct, 2013, at 9:37 pm, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

Nikki,

Thanks for detailed explanation.

- could we put the OVMS into some form of low-power mode, so it doesn't poll the car and drain that 12V battery as quickly?

Possibly. We haven’t handled that yet, and our tests with it so far have not been very successful. The biggest power draw is the modem. Best we can do is shut that down and delay-loop-spin if 12V gets to low.

- We can use the 12V monitoring system already built into OVMS to set an early-warning alert if voltages start to drop, right?

Yes. The leaf also seems to have 12V level in a can bus signal, which shouldn’t need to be calibrated and may give us a better result.

But a quick question: can I run OVMS alongside LEAFSpy, using an ODBII splitter?

Hmmm. Without special handling, that would be problematic. We would both end up polling the same things, and one/both of us would get confused.

I should have thought that we can listen on the bus first, and make sure there are no polling signals for N seconds, before we start polling ourselves. Similarly, if we see a polling signal/reply, we can back off. But, one concern is that in my tests last weekend, I tried a CAN bus logger and OBD-II with leaf spy together, but didn’t see much. All I saw were some replies:

1382228933.303 R11 797 02 10 C0 00 00 00 00 00 1382229549.511 R11 797 03 22 12 4E 00 00 00 00 1382229799.599 R11 797 03 22 11 5D 00 00 00 00 1382230050.688 R11 797 03 22 13 2A 00 00 00 00 1382230425.777 R11 797 03 22 12 55 00 00 00 00 1382230869.926 R11 797 03 22 13 04 00 00 00 00

so, it looks like I can see someone else polling (and can back off appropriately), but I don’t think I can listen to their replies as if I was polling myself! That would be cool (so long as leaf spy and ovms were polling for the exact same things), and I don’t see why it wouldn’t work, but I just didn’t see that behaviour when I T’ed the bus last weekend.

Regards, Mark.

On 22 Oct, 2013, at 4:23 pm, Nikki Gordon-Bloomfield < nikki@aminorjourney.com> wrote:

Mark,

Regarding the 12V drain. As I understand it, the 12V battery gets charged when the car is plugged in and the main traction battery is getting charged. When the car is plugged in and it is NOT charging, the on-board computer wakes up every n seconds and polls its various systems. Because this uses more power than normal 'standby' mode, it quickly drains the battery. If we assume most owners are not going to leave their cars plugged in for days at a time, the issue should be moot, although it's worth playing on the cautious side.

Instances of 12V drainage in LEAFs are almost exclusively related to cars which have sat plugged in at charging stations for extended periods of time, such as when their owners go on holiday. Last time I went abroad, I kept my LEAF plugged in, but did the following:

- Left the car on the first night without a full charge. I think SOC was about 25% if I remember correctly. - Set the car's timer to charge every night while I was away with an 80 percent 'limited' charge profile, starting at midnight, and finishing at half-past midnight. - On a standard 16 amp EVSE, this meant that the car slowly charged over the course of the week, getting topped up a little more every night. Because the 12V battery was charged too during that period, I was able to keep it happy also, preventing any horrible 'soft-brick' scenarios.

What does this tell us? First, I'm pretty sure the 12V battery DOES get charged when the main traction back gets charged. But when the car is plugged in and not charging, NOTHING gets charged and the 12V battery gets drained at a far faster rate than it would be if it was left alone for a few weeks.

But I think it also tells us some other important things.

- IN most situations, (everyday ones, at least) 12V battery drain shouldn't be a problem. I'm happy to be the Guinea pig for this one when Kevin gets the OVMS hardware through customs. - The only risk to the car occurs when the car is parked for long periods without being plugged in -- or when it is plugged in but hasn't charged for x hours/days. A work-around here would be to use the parking timer combined with a 'last-charged' timer. If the timer > 24 hours, per say, could we put the OVMS into some form of low-power mode, so it doesn't poll the car and drain that 12V battery as quickly? I know from my Twizy that the OVMS system really does have a very low power drain, so I'm assuming any massive power drains associated with OVMS come from the car's on-board CAN hardware waking up and communicating with the module? - We can use the 12V monitoring system already built into OVMS to set an early-warning alert if voltages start to drop, right? - If done correctly, it's possible to keep the car plugged in for long periods of time, without adversely affecting the 12V battery. This is a matter of driver education more than anything else.

I also think it's worth noting that many LEAFs which have had 12V battery issues are ones which have either spent a lot of time sitting on dealer lots, or are regularly left for long periods of time. It's my opinion that like any car, the LEAF benefits from being driven daily… ;)

As soon as Kevin gets the hardware through customs, I'm willing to give this all a go. But a quick question: can I run OVMS alongside LEAFSpy, using an ODBII splitter?

Nikki.

P.S. FYI, Nissan has changed the position of the ODB port on the 2013 model year cars. It's now behind a small panel to the right of the driver's right (left in LHD countries) knee. Orientation is also moved too. Here's a photo of new vs old.

<IMG_0525.jpeg> -- You'll notice the new car has an extra port too. Not sure what it's for…

<IMG_0528.jpeg> Old port is right under the dash, with the catch-side facing to the driver's left.

On 22 Oct 2013, at 02:11, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

OK, here's an update...

I went through the logs we captured, and had a look at Leaf Spy. I even purchased a copy of Leaf Spy Pro (even though I don't have a Leaf) just as a donation to say thank you to Turbo3 for pushing this approach and working out so much of the mechanics of it.

I spent an evening reading through the "Using clone ELM327 Bluetooth OBDII adapter with Leaf" on mynissanleaf.com<http://www.mynissanleaf.com/viewtopic.php?f=44&t=12098> (all 238 pages of it!), and got a good understanding of the history of where CAN decoding on the Nissan Leaf is, and where it is headed.

Bottom line:

- There are two CAN buses in the Nissan Leaf that are useful to us: the EV CAN bus and the CAR CAN bus. - The standard OVMS OBD-II cable connects to the CAR CAN bus. By passive listening on the bus, we can see some EV information, and all of the car information. - The EV CAN bus is also available on the OBD-II socket. By passive listening on the bus, we can see all the EV information, but little-to-no car information. - OVMS V2 hardware can only connect to one bus. - Someone worked out that active requests for information from the controllers (PID polling, as opposed to passive listening) are bridged. You can request information from a controller on the EV CAN bus, via the CAR CAN bus, and the car will bridge the requests between the buses. This appears to work bi-directionally. - There is a slight nasty in that if the car is off (asleep), active polling the EV controller causes it to wake up and you can hear a little 12V relay click near the front of the car each time you poll. We don't want to poll too fast when the car is asleep (off) and not charging, to avoid wearing out that relay. - The OBD-II connector has 12V power (both switched and non-switched) that we can use for OVMS, powered by an automotive 12V lead acid battery. We do need to take care because apparently that 12V battery is only charged when you drive or once every five days when the car is unplugged (and not at all when the car is plugged in). There is a CAR CAN message to show the 12V battery voltage (and OVMS V2 can also measure directly). - There is 'active discussion' in the community on how things like SOC%, battery capacity, ideal and estimated ranges, should be determined. Nissan made a mess of it, and the users are struggling to agree on a uniform approach to a correct way of doing things.

I think our plan of attack should be:

1. Use a standard V2 module, with standard OVMS OBD-II cable, to connect to the CAR CAN bus. 2. Use passive CAN listening, for the car information (doors, speed, on/off, etc) as much as possible. 3. Use active CAN polling, bridged to the EV CAN bus, for the EV information that we need. 4. Agree our own user-centric approach of how to represent capacity, SOC, ideal and estimated ranges.

It has been quite frustrating looking at the community documentation for CAN bus messages in the Leaf. The documentation doesn't match what I am seeing, and is not at all clear. A lot of people are sharing, but some seem to be holding back and saying things like "here are some clues to what I've found, so go look for it yourself". Some closed source. Not the way I like to do things.

There is one very good thread on the active CAN bus polling, here:

http://www.mynissanleaf.com/viewtopic.php?f=44&t=11676

A good background read (34 pages) on Leaf CAN bus passive monitoring is here:

http://www.mynissanleaf.com/viewtopic.php?f=8&t=4131

and I recommend everyone involved in this to read that thread (only 12 pages) to get a good understanding.

There are two spreadsheets tracking Leaf CAN bus messages:

https://docs.google.com/spreadsheet/ccc?key=0AuDGAXnbchK0dDc4T05oNE04aVZtUzB...

https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1...

So, what I'm going to do now is to setup a framework in the vehicle_nissanleaf module to do passive listening on the CAR CAN bus, and active polling of the information on the EV CAN bus (bridged via CAR CAN bus). Once the framework is done, I'll test it in the local Hong Kong Leaf, and ask you guys to help.

I do need one or two people with the following equipment to help out:

Good and frequent access to a Nissan Leaf OVMS v2 Module OVMS v2 OBD-II cable PICKIT2 or PICKIT3 programmer RS232-to-USB adaptor and laptop (or laptop with RS232 port)

This is to run the framework in their car, and capture RS232 output from the DIAG port.

So, volunteers please.

Regards, Mark.

On 19 Oct, 2013, at 11:23 pm, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

I met up with a local Leaf owner (George) and spent a few hours in the car logging stuff off the main CAN bus. The car is a 2011 model, I think (the VIN model year is U/V, which makes no sense).

Good news it that the OVMS cables are fine. The ‘right hand’ ovms obdii cable appears to be the best for the right hand drive nissan leafs. The OBDII connector is under the steering wheel, parallel with the car direction of travel, short side on the left, so using a right-hand cable directs the cable towards the front of the car, which should be easiest for routing.

I managed to get quite a few log files, using a standard CAN USB adaptor at 512kbps.

Bad news is I am having trouble correlating lots of the messages against the published spreadsheets of Leaf can bus messages. Some messages are partially correct, but many are missing / don’t match up. The car also seems to go to sleep during charging, although the leaf spy could update the SOC ok. The 0x5b3 SOC+GIDS message wasn’t visible on the bus at all.

I think we are going to have to use PID polling to get the data we need.

Regards, Mark.

On 16 Oct, 2013, at 10:31 pm, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

Anyone feeling brave?

I’ve just committed a nissan leaf module (set vehicle id to NL) that will monitor the can bus and pickup the SOC%. That is all it does at the moment, but it should work.

Regards, Mark.

On 16 Oct, 2013, at 2:49 pm, Nikki Gordon-Bloomfield < nikki@littlecollie.com> wrote:

I've already messages mark C. Let's hope he has it :) I know he and his husband have done a lot of logging.

Sent from my iPhone

On 16 Oct 2013, at 07:02, Robert Sharpe < robert.sharpe@evergreen-consulting.co.uk> wrote:

Hi Mark,

...

I think the fastest way to get this done is for me to do it with a local Leaf owner. That sounds like a good idea.

...

Can someone tell me which CarCAN bus message to look for, which byte(s) to access, and how to convert to percentage SOC? The document at https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1... suggests ID 5B3 tracks SOH and Gids. But how to convert to percentage SOC?

Is @nufkin (Mark C) on this list? He has done some analysis of codes. There is always the authors of the other projects that read Leaf data.

Regards, Rob

On Oct 16, 2013, at 6.33AM, Mark Webb-Johnson wrote:

I think the fastest way to get this done is for me to do it with a local Leaf owner.

If I can get basic support working, then perhaps someone else (or others) with better knowledge of the Leaf scene, can take over to get the advanced stuff working.

So, I'm going to try to get some Leaf Spy traces, as well as CAN bus logs for parked, charging and driving. Then, get the basic module working with SOC%, GPS location, door status, drive/park and charge monitor.

My biggest confusion at the moment is SOC% in the Leaf. There is a lot of talk about gids, etc, but I've never gone into it too deeply.

Can someone tell me which CarCAN bus message to look for, which byte(s) to access, and how to convert to percentage SOC?

The document at https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1... ID 5B3 tracks SOH and Gids. But how to convert to percentage SOC?

Regards, Mark.

On 16 Oct, 2013, at 1:03 pm, Evergreen < robert.sharpe@evergreen-consulting.co.uk">target="_blank">robert.sharpe@evergreen-consulting.co.uk<robert.sharpe@evergreen-consulting.co.uk>> wrote:

That's great news.

Regards, Rob

On 16 Oct 2013, at 06:00, Mark Webb-Johnson < mark@webb-johnson.net">target="_blank">mark@webb-johnson.net<mark@webb-johnson.net>> wrote:

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.

I think my fishing expedition on the forums may have come up with a bite. A Hong Kong Leaf owner who is willing to help.

I'll let you know how it pans out (over the next couple of days), but if I can get access to a local Leaf, getting the basic support working should be much faster.

Regards, Mark.

On 15 Oct, 2013, at 1:00 pm, Mark Webb-Johnson < mark@webb-johnson.net">target="_blank">mark@webb-johnson.net<mark@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@gmail.com">target="_blank">gbarry42@gmail.com<gbarry42@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@webb-johnson.net">target="_blank">mark@webb-johnson.net<mark@webb-johnson.net>

...

wrote:

Developers guide is here:

https://github.com/markwj/Open-Vehicle-Monitoring-System/blob/master/docs/OV...

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@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk<OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk<OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk<OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk<OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

Jeremy, Do you think we can halt the charging using some other message? Can we communicate with the on-board charger? I’d assume it’s on the EV CAN bus? Nikki. On 20 Nov 2013, at 09:06, Jeremy Whaling <jeremy.whaling@gmail.com> wrote:

Hi all! Attached is a text file containing a recording of the EV can bus data during a remote request for status/SOC. The first message from 68C is only seen once. Unfortunately sending the message from my PCAN tool had no effect. Will try to get more data over the weekend.

Jeremy

On Wed, Nov 6, 2013 at 1:22 AM, Jeremy Whaling <jeremy.whaling@gmail.com> wrote: The only functions that the TCU/carwings can do is get the following data: # of bars,GOM range, plug/charging status, and estimated charging time invoke the following: charging now or turning on or off climate (which attempts to bring the cabin to 78F via heat or AC).

Unlocking doors or other goodies might be something we can do after sniffing the car can bus some more! :-)

Jeremy

On Wed, Nov 6, 2013 at 12:36 AM, Mark Webb-Johnson <mark@webb-johnson.net> wrote: Jeremy,

The OBDII port carries pins for both buses. OVMS could be connected to either, although the CAR CAN bus is on the standard OBDII pins for a CAN bus.

My preference is the CAR CAN bus at the moment, because we need stuff on the CAR bus, not just EV (like speed, etc), and standard cables can be used. It seems to have worked out very well for LeafSpy. But, there is no reason the OVMS could not be connected directly to EV bus.

If, as you say, the TCM module is connected to just the EV CAN bus that is very good news. It should just be a matter of listening in on what messages it sends on that bus to understand how it is doing things like locking doors, aircon control, etc. The bridge between EV and CAR buses is bi-directional, so perhaps it is also sending messages over to the CAR bus.

Regards, Mark.

On 6 Nov, 2013, at 2:38 pm, Jeremy Whaling <jeremy.whaling@gmail.com> wrote:

...

While I don't mind the OBD port route for now, eventually I'd like to have the option to have an OVMS module to drop into place of the original TCM which has connections to the EV can bus (only) and a built in GSM antenna. My USB-CAN came in today, hope to play with it a little bit this weekend.

Also plan to buy all the OVMS goodies soon, but those will take a few weeks to get in, I think?

Jeremy

On Tue, Nov 5, 2013 at 4:45 AM, Mark Webb-Johnson <mark@webb-johnson.net> wrote: A short update:

I’m working on the code to handle the Leaf PID polling via the CAR-to-EV bus bridge. It seems ok, but I’m trying to make it modular as we are now doing this same sort of polling in quite a few vehicle modules and it seems sensible to centralise it (to save code space and complexity). It is tricky, because of the relay issue, as we need to make the polling frequency configurable depending on states.

I’m making progress and hope to have something within the coming week.

My first version of code is going to output to the DIAG serial port lots of data to tell us what is going on. So, I need testers with a (a) laptop, (b) usb-to-serial converter, (c) Leaf, (d) PICKIT, (e) OVMS module, (f) standard OVMS OBD-II cable. Testing will be flashing the module with a HEX I provide, then putting it in the car and getting a log file of the DIAG port to send me.

Regards, Mark.

On 22 Oct, 2013, at 9:37 pm, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

...

Nikki,

Thanks for detailed explanation.

...

could we put the OVMS into some form of low-power mode, so it doesn't poll the car and drain that 12V battery as quickly?

Possibly. We haven’t handled that yet, and our tests with it so far have not been very successful. The biggest power draw is the modem. Best we can do is shut that down and delay-loop-spin if 12V gets to low.

...

We can use the 12V monitoring system already built into OVMS to set an early-warning alert if voltages start to drop, right?

Yes. The leaf also seems to have 12V level in a can bus signal, which shouldn’t need to be calibrated and may give us a better result.

...

But a quick question: can I run OVMS alongside LEAFSpy, using an ODBII splitter?

Hmmm. Without special handling, that would be problematic. We would both end up polling the same things, and one/both of us would get confused.

I should have thought that we can listen on the bus first, and make sure there are no polling signals for N seconds, before we start polling ourselves. Similarly, if we see a polling signal/reply, we can back off. But, one concern is that in my tests last weekend, I tried a CAN bus logger and OBD-II with leaf spy together, but didn’t see much. All I saw were some replies:

1382228933.303 R11 797 02 10 C0 00 00 00 00 00 1382229549.511 R11 797 03 22 12 4E 00 00 00 00 1382229799.599 R11 797 03 22 11 5D 00 00 00 00 1382230050.688 R11 797 03 22 13 2A 00 00 00 00 1382230425.777 R11 797 03 22 12 55 00 00 00 00 1382230869.926 R11 797 03 22 13 04 00 00 00 00

so, it looks like I can see someone else polling (and can back off appropriately), but I don’t think I can listen to their replies as if I was polling myself! That would be cool (so long as leaf spy and ovms were polling for the exact same things), and I don’t see why it wouldn’t work, but I just didn’t see that behaviour when I T’ed the bus last weekend.

Regards, Mark.

On 22 Oct, 2013, at 4:23 pm, Nikki Gordon-Bloomfield <nikki@aminorjourney.com> wrote:

...

Mark,

Regarding the 12V drain. As I understand it, the 12V battery gets charged when the car is plugged in and the main traction battery is getting charged. When the car is plugged in and it is NOT charging, the on-board computer wakes up every n seconds and polls its various systems. Because this uses more power than normal 'standby' mode, it quickly drains the battery. If we assume most owners are not going to leave their cars plugged in for days at a time, the issue should be moot, although it's worth playing on the cautious side.

Instances of 12V drainage in LEAFs are almost exclusively related to cars which have sat plugged in at charging stations for extended periods of time, such as when their owners go on holiday. Last time I went abroad, I kept my LEAF plugged in, but did the following:

Left the car on the first night without a full charge. I think SOC was about 25% if I remember correctly. Set the car's timer to charge every night while I was away with an 80 percent 'limited' charge profile, starting at midnight, and finishing at half-past midnight. On a standard 16 amp EVSE, this meant that the car slowly charged over the course of the week, getting topped up a little more every night. Because the 12V battery was charged too during that period, I was able to keep it happy also, preventing any horrible 'soft-brick' scenarios. What does this tell us? First, I'm pretty sure the 12V battery DOES get charged when the main traction back gets charged. But when the car is plugged in and not charging, NOTHING gets charged and the 12V battery gets drained at a far faster rate than it would be if it was left alone for a few weeks.

But I think it also tells us some other important things.

IN most situations, (everyday ones, at least) 12V battery drain shouldn't be a problem. I'm happy to be the Guinea pig for this one when Kevin gets the OVMS hardware through customs. The only risk to the car occurs when the car is parked for long periods without being plugged in -- or when it is plugged in but hasn't charged for x hours/days. A work-around here would be to use the parking timer combined with a 'last-charged' timer. If the timer > 24 hours, per say, could we put the OVMS into some form of low-power mode, so it doesn't poll the car and drain that 12V battery as quickly? I know from my Twizy that the OVMS system really does have a very low power drain, so I'm assuming any massive power drains associated with OVMS come from the car's on-board CAN hardware waking up and communicating with the module? We can use the 12V monitoring system already built into OVMS to set an early-warning alert if voltages start to drop, right? If done correctly, it's possible to keep the car plugged in for long periods of time, without adversely affecting the 12V battery. This is a matter of driver education more than anything else.

I also think it's worth noting that many LEAFs which have had 12V battery issues are ones which have either spent a lot of time sitting on dealer lots, or are regularly left for long periods of time. It's my opinion that like any car, the LEAF benefits from being driven daily… ;)

As soon as Kevin gets the hardware through customs, I'm willing to give this all a go. But a quick question: can I run OVMS alongside LEAFSpy, using an ODBII splitter?

Nikki.

P.S. FYI, Nissan has changed the position of the ODB port on the 2013 model year cars. It's now behind a small panel to the right of the driver's right (left in LHD countries) knee. Orientation is also moved too. Here's a photo of new vs old.

<IMG_0525.jpeg> -- You'll notice the new car has an extra port too. Not sure what it's for…

<IMG_0528.jpeg> Old port is right under the dash, with the catch-side facing to the driver's left.

On 22 Oct 2013, at 02:11, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

...

OK, here's an update...

I went through the logs we captured, and had a look at Leaf Spy. I even purchased a copy of Leaf Spy Pro (even though I don't have a Leaf) just as a donation to say thank you to Turbo3 for pushing this approach and working out so much of the mechanics of it.

I spent an evening reading through the "Using clone ELM327 Bluetooth OBDII adapter with Leaf" on mynissanleaf.com (all 238 pages of it!), and got a good understanding of the history of where CAN decoding on the Nissan Leaf is, and where it is headed.

Bottom line:

There are two CAN buses in the Nissan Leaf that are useful to us: the EV CAN bus and the CAR CAN bus. The standard OVMS OBD-II cable connects to the CAR CAN bus. By passive listening on the bus, we can see some EV information, and all of the car information. The EV CAN bus is also available on the OBD-II socket. By passive listening on the bus, we can see all the EV information, but little-to-no car information. OVMS V2 hardware can only connect to one bus. Someone worked out that active requests for information from the controllers (PID polling, as opposed to passive listening) are bridged. You can request information from a controller on the EV CAN bus, via the CAR CAN bus, and the car will bridge the requests between the buses. This appears to work bi-directionally. There is a slight nasty in that if the car is off (asleep), active polling the EV controller causes it to wake up and you can hear a little 12V relay click near the front of the car each time you poll. We don't want to poll too fast when the car is asleep (off) and not charging, to avoid wearing out that relay. The OBD-II connector has 12V power (both switched and non-switched) that we can use for OVMS, powered by an automotive 12V lead acid battery. We do need to take care because apparently that 12V battery is only charged when you drive or once every five days when the car is unplugged (and not at all when the car is plugged in). There is a CAR CAN message to show the 12V battery voltage (and OVMS V2 can also measure directly). There is 'active discussion' in the community on how things like SOC%, battery capacity, ideal and estimated ranges, should be determined. Nissan made a mess of it, and the users are struggling to agree on a uniform approach to a correct way of doing things.

I think our plan of attack should be:

Use a standard V2 module, with standard OVMS OBD-II cable, to connect to the CAR CAN bus. Use passive CAN listening, for the car information (doors, speed, on/off, etc) as much as possible. Use active CAN polling, bridged to the EV CAN bus, for the EV information that we need. Agree our own user-centric approach of how to represent capacity, SOC, ideal and estimated ranges.

It has been quite frustrating looking at the community documentation for CAN bus messages in the Leaf. The documentation doesn't match what I am seeing, and is not at all clear. A lot of people are sharing, but some seem to be holding back and saying things like "here are some clues to what I've found, so go look for it yourself". Some closed source. Not the way I like to do things.

There is one very good thread on the active CAN bus polling, here:

http://www.mynissanleaf.com/viewtopic.php?f=44&t=11676

A good background read (34 pages) on Leaf CAN bus passive monitoring is here:

http://www.mynissanleaf.com/viewtopic.php?f=8&t=4131

and I recommend everyone involved in this to read that thread (only 12 pages) to get a good understanding.

There are two spreadsheets tracking Leaf CAN bus messages:

https://docs.google.com/spreadsheet/ccc?key=0AuDGAXnbchK0dDc4T05oNE04aVZtUzB...

https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1...

So, what I'm going to do now is to setup a framework in the vehicle_nissanleaf module to do passive listening on the CAR CAN bus, and active polling of the information on the EV CAN bus (bridged via CAR CAN bus). Once the framework is done, I'll test it in the local Hong Kong Leaf, and ask you guys to help.

I do need one or two people with the following equipment to help out:

Good and frequent access to a Nissan Leaf OVMS v2 Module OVMS v2 OBD-II cable PICKIT2 or PICKIT3 programmer RS232-to-USB adaptor and laptop (or laptop with RS232 port)

This is to run the framework in their car, and capture RS232 output from the DIAG port.

So, volunteers please.

Regards, Mark.

On 19 Oct, 2013, at 11:23 pm, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

...

I met up with a local Leaf owner (George) and spent a few hours in the car logging stuff off the main CAN bus. The car is a 2011 model, I think (the VIN model year is U/V, which makes no sense).

Good news it that the OVMS cables are fine. The ‘right hand’ ovms obdii cable appears to be the best for the right hand drive nissan leafs. The OBDII connector is under the steering wheel, parallel with the car direction of travel, short side on the left, so using a right-hand cable directs the cable towards the front of the car, which should be easiest for routing.

I managed to get quite a few log files, using a standard CAN USB adaptor at 512kbps.

Bad news is I am having trouble correlating lots of the messages against the published spreadsheets of Leaf can bus messages. Some messages are partially correct, but many are missing / don’t match up. The car also seems to go to sleep during charging, although the leaf spy could update the SOC ok. The 0x5b3 SOC+GIDS message wasn’t visible on the bus at all.

I think we are going to have to use PID polling to get the data we need.

Regards, Mark.

On 16 Oct, 2013, at 10:31 pm, Mark Webb-Johnson <mark@webb-johnson.net> wrote:

> > Anyone feeling brave? > > I’ve just committed a nissan leaf module (set vehicle id to NL) that will monitor the can bus and pickup the SOC%. That is all it does at the moment, but it should work. > > Regards, Mark. > > On 16 Oct, 2013, at 2:49 pm, Nikki Gordon-Bloomfield <nikki@littlecollie.com> wrote: > >> I've already messages mark C. Let's hope he has it :) I know he and his husband have done a lot of logging. >> >> Sent from my iPhone >> >> On 16 Oct 2013, at 07:02, Robert Sharpe <robert.sharpe@evergreen-consulting.co.uk> wrote: >> >>> Hi Mark, >>> >>> >I think the fastest way to get this done is for me to do it with a local Leaf owner. >>> That sounds like a good idea. >>> >>> >Can someone tell me which CarCAN bus message to look for, which byte(s) to access, and how to convert to percentage SOC? >>> >The document at https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1... suggests ID 5B3 tracks SOH and Gids. But how to convert to percentage SOC? >>> >>> Is @nufkin (Mark C) on this list? He has done some analysis of codes. >>> There is always the authors of the other projects that read Leaf data. >>> >>> Regards, >>> Rob >>> >>> >>> On Oct 16, 2013, at 6.33AM, Mark Webb-Johnson wrote: >>> >>> I think the fastest way to get this done is for me to do it with a local Leaf owner. >>> >>> If I can get basic support working, then perhaps someone else (or others) with better knowledge of the Leaf scene, can take over to get the advanced stuff working. >>> >>> So, I'm going to try to get some Leaf Spy traces, as well as CAN bus logs for parked, charging and driving. Then, get the basic module working with SOC%, GPS location, door status, drive/park and charge monitor. >>> >>> My biggest confusion at the moment is SOC% in the Leaf. There is a lot of talk about gids, etc, but I've never gone into it too deeply. >>> >>> Can someone tell me which CarCAN bus message to look for, which byte(s) to access, and how to convert to percentage SOC? >>> >>> The document at https://docs.google.com/spreadsheet/ccc?key=0An7gtcYL2Oy0dGRaSWl6VTV2eXBQMy1... suggests ID 5B3 tracks SOH and Gids. But how to convert to percentage SOC? >>> >>> Regards, Mark. >>> >>> On 16 Oct, 2013, at 1:03 pm, Evergreen <robert.sharpe@evergreen-consulting.co.uk">target="_blank">robert.sharpe@evergreen-consulting.co.uk> wrote: >>> >>> That's great news. >>> >>> Regards, >>> Rob >>> >>> On 16 Oct 2013, at 06:00, Mark Webb-Johnson <mark@webb-johnson.net">target="_blank">mark@webb-johnson.net> wrote: >>> >>> >>> 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. >>> >>> I think my fishing expedition on the forums may have come up with a bite. A Hong Kong Leaf owner who is willing to help. >>> >>> I'll let you know how it pans out (over the next couple of days), but if I can get access to a local Leaf, getting the basic support working should be much faster. >>> >>> Regards, Mark. >>> >>> On 15 Oct, 2013, at 1:00 pm, Mark Webb-Johnson <mark@webb-johnson.net">target="_blank">mark@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@gmail.com">target="_blank">gbarry42@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@webb-johnson.net">target="_blank">mark@webb-johnson.net> wrote: >>> Developers guide is here: >>> >>> https://github.com/markwj/Open-Vehicle-Monitoring-System/blob/master/docs/OV... >>> >>> 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@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk >>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev >>> >>> _______________________________________________ >>> OvmsDev mailing list >>> OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk >>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev >>> >>> _______________________________________________ >>> OvmsDev mailing list >>> OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk >>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev >>> _______________________________________________ >>> OvmsDev mailing list >>> OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk >>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev >>> >>> >>> >>> _______________________________________________ >>> OvmsDev mailing list >>> OvmsDev@lists.teslaclub.hk >>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev >> >> _______________________________________________ >> OvmsDev mailing list >> OvmsDev@lists.teslaclub.hk >> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev > > _______________________________________________ > OvmsDev mailing list > OvmsDev@lists.teslaclub.hk > http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

<remotesocreqevbus.txt>_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

There are three interesting values related to SOC on the Leaf. Gids: Discovered by Gary Giddings, each Gid represents 80 Wh of energy currently in the battery pack. A nominal new packs reads 281 Gids on a full charge and the car stops going at about 6 Gids. 80*(281-6) = 22 kWh of usable charge. Gary Giddings' original SOC meter calculated SOC = Gids/281 So that gives an SOC in energy units like the Roadster's ideal miles, except that the car dies at about 2% SOC. Also, the Gid measurement is temperature dependent, understates charge in hot weather and overstates it in cold weather. The value is not directly readable from the primary CAN bus, but folks have figured out how to query it from there. The implied precision of the measurement is 1/281 = 0.36%, but the accuracy is much worse than that. It's typically shown to 0.1%. Ah: The car's estimate of the pack's capacity in Ah was found on the main bus. As I understand things, it correlates well with Gids but there isn't an accepted standard nominal new pack Ah value. The Leaf Spy app lets users set their Ah value from which another SOC percent is computed, rendering those values unique to each car and thus useless for things like battery capacity studies. True SOC: This is a horrible name for the high precision value that drives the SOC bars in the Leaf. (It's a byte value, so not quite 0.1% precision.) The giant problem with this value is that it's relative to the pack's current estimated pack capacity. So, even after your pack has lost 30% of its capacity, it still charges to 100% of that, shows all 12 SOC bars on the dash and "True SOC" still runs up to 100.0. Personally, I would want OVMS to show: SOC % = Gids/281 SOC Energy = Gids (like ideal miles in the Roadster) Pack Ah treated as CAC is in the Roadster Many, perhaps a majority, of Leaf owners will want to see the "True SOC" because they don't realize how stupid that is until they lose a capacity bar and realize that SOC still goes to 100% even though that doesn't mean the same thing it did when the car was new, so any intuition they've acquired about how much charge it takes to drive from A to B has to be constantly adjusted. Tom From: Mark Webb-Johnson <mark@webb-johnson.net> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Date: Tuesday, October 15, 2013 10:33 PM To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Subject: Re: [Ovmsdev] OVMS Leaf Support My biggest confusion at the moment is SOC% in the Leaf. There is a lot of talk about gids, etc, but I've never gone into it too deeply.

Hi Mark,>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.No problem.  What I was really suggesting was a way of tracking tasks toclarify what needs to be done, who is doing it and its statushelp get engagement from other people that might want to also helpshows general progress to the users/developerslinks to maybe to task specific threadsProbably a better system would be to share a google spreadsheet.Let me know what you think.RobOn Oct 15, 2013, at 3.04AM, Mark Webb-Johnson wrote:Developers guide is here:https://github.com/markwj/Open-Vehicle-Monitoring-System/blob/master/docs/OV... 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 (the car CAN that is on the standard OBD-II pins). Every time this is raised, the response is 'oh, no, you need to see all 4 vehicle buses (and Chademo bus included)'. I don't believe that. In most cases I've seen, the common useful information is gatewayed onto the primary CAN bus used for OBD-II comms - either directly as repeated CAN messages, or indirectly via PID polling. Sure, in an ideal world the OVMS module would support 10 individual CAN buses, the legacy OBD-II buses, plus methane sensors for cabin pollution, but for what we need to do I really don't think it is necessary.I think what the Leaf Spy people have done really shows what is possible with that primary CAN bus. Sure, they could also be accessing the legacy OBD-II buses as well, but I doubt it. We can even see what Leaf Spy is accessing, as they have a trace function:What I will need is an ELM trace to see if I can determine what the problem is.1. Start the app and go to the bottom of the Settings menu (Debug) and check the "Trace ELM" check box, then exit the app. The trace starts on the next app startup.2. Start up the app and let it run for 20 seconds then exit. The "Trace ELM" flag is automatically turned off. A logging message will flash bottom center while logging is active.3. Using the email address in the About screen send me the TRC_******.txt file located in the LEAF_BT_CAN folder.Can someone with that program try it, and send me the trace output?Also, are there any CAN bus dump files out there for the CAR CAN bus? It would be good to see the volume of data, as well as some examples.Later today, I'll prepare a list of what OVMS needs, and let's try to map that to CAR CAN data messages and PID requests. Let's see if this is feasible first.Regards, Mark.On 14 Oct, 2013, at 10:01 pm, Robert Sharpe robert.sharpe@evergreen-consulting.co.uk> wrote:Hi Kevin,Thanks a lot for your kind offer.I should set expectations that I am an out of practice and slow coder, but I will do what I can to help.  I can probably help more with test, debug and coordination.So if you are still happy then, as I dont have any OVMS kit, I will need an OVMS and correct cable.Can someone point me to a developer beginner's instructions for what else is required to develop/test, e.g. programmer, sniffer, code repository login, CM procedures, etcIt helps me, and hopefully anyone else working on the project, if we can agree the breakdown of work.  As you may have already seen I have suggested a post for the Leaf development at http://www.openvehicles.com/node/111 Nikki/Mark shall we use that as a way of planning and tracking the work ?Regards,RobOn Oct 14, 2013, at 2.21PM, Nikki Gordon-Bloomfield wrote:Hi Kevin, That's very generous. Happy to test OVMS in my LEAF, so I guess another OVMS kit with a righty cable? Nikki. On 14 Oct 2013, at 13:47, Kevin Sharpe ZCW kevin.sharpe@zerocarbonworld.org">target="_blank">kevin.sharpe@zerocarbonworld.org> wrote: Rob, Mark (C), Nikki, If it helps, I'm happy to provide each of you with OVMS hardware FOC in return for your efforts on the Leaf development :-) Let me know what you need, Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org | www.zerocarbonworld.org | twitter.com/zerocarbonworld Zero Carbon World is a UK Registered Charity #1141347 From: Robert Sharpe robert.sharpe@evergreen-consulting.co.uk">target="_blank">robert.sharpe@evergreen-consulting.co.uk> Reply-To: OVMS Developers ovmsdev@lists.teslaclub.hk">target="_blank">ovmsdev@lists.teslaclub.hk> Date: Monday, 14 October 2013 13:41 To: OVMS Developers ovmsdev@lists.teslaclub.hk">target="_blank">ovmsdev@lists.teslaclub.hk> Subject: Re: [Ovmsdev] OVMS Leaf Support Hi Mark, This looks very interesting. I am out today but will look in more depth tomorrow. Regards, Rob ---- On Mon, 14 Oct 2013 10:08:41 +0100 Mark Webb-Johnson mark@webb-johnson.net">target="_blank">mark@webb-johnson.net> wrote ---- I think the leaf spy app shows what can be done. It only uses standard OBDII, with just one can bus. It could also be using the other non-can OBDII buses, but I doubt it. Shame it is not open source, but the leaf codes are pretty well documented now. Regards, Mark On 14 Oct, 2013, at 4:00 pm, Nikki Gordon-Bloomfield nikki@aminorjourney.com">target="_blank">nikki@aminorjourney.com> wrote: Oh yes, there are multiple CAN busses on the LEAF. The standard one, which is where all the data below comes from, an the EV can -- that would require some clever doodads, since both are on the same physical connector -- just different pins.  Nikki.  On 14 Oct 2013, at 04:50, Mark Webb-Johnson mark@webb-johnson.net">target="_blank">mark@webb-johnson.net> wrote: Robert, Sorry for the delay in response - I’ve been off grid parenting for the past 24 hours. I think @Nufkin has done some preparation work, and we have a stub vehicle support file (vehicle_nissanleaf.c), but nothing working yet. This App shows what can be done: https://play.google.com/store/apps/details?id=com.Turbo3.Leaf_Spy_Pro using just the OBD-II port (I assume all the single master CAN bus, but perhaps also other buses on OBD-II). I’m very excited by this, and more than willing to help, but I don’t have the car here so am limited in what I can do. Can you work with @nufkin (and his other half) on this? You would need some sort of CAN bus decoder (perhaps just an OBD-II dongle, or CAN-USB adaptor), plus an OVMS module and PICKIT for firmware download. If you use MAC OSX, the development environment is simple to setup - for windows there are a few more hoops to jump through. Lastly, a RS232-USB adaptor is useful (but not essential). Regards, Mark. On 13 Oct, 2013, at 4:00 pm, Robert Sharpe robert.sharpe@evergreen-consulting.co.uk">target="_blank">robert.sharpe@evergreen-consulting.co.uk> wrote: Hi, ovmsdev-request@lists.teslaclub.hk">target="_blank">ovmsdev-request@lists.teslaclub.hk> Is anyone working on Leaf support? I am interested in helping if I can and have started a discussion at http://openvehicles.com/comment/220#comment-220 to capture were we are with the Leaf. Regards, Robert Sharpe (Technical Director) 07711 252971http://www.facebook.com/EvergreenConsultingLtd http://twitter.com/EGCtechnical http://uk.linkedin.com/in/arsharpe www.evergreen-consulting.co.ukYour Plugged-in PartnerSupport the future and switch to a renewable energy supplier such as Good EnergyEvergreen Consulting is the trading name of Sharpe Consultants Ltd /ovmsdev-request@lists.teslaclub.hk">target="_blank">/ovmsdev-request@lists.teslaclub.hk>_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________OvmsDev mailing listOvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hkhttp://lists.teslaclub.hk/mailman/listinfo/ovmsdev__________________________... mailing listOvmsDev@lists.teslaclub.hkhttp://lists.teslaclub.hk/mailman/listinfo/ovmsdev

OVMS hardware is currently in UK customs and should be released this week. Have you obtained the programmer and any other dev tools? On 3 Nov 2013, at 08:53, "Robert Sharpe" <robert.sharpe@evergreen-consulting.co.uk<mailto:robert.sharpe@evergreen-consulting.co.uk>> wrote: Hi Kevin, I am keen to start helping out on the Leaf development. It's been 3 weeks and I just wandered what the progress with the OVMS hardware is ? Regards, Rob ---- On Mon, 14 Oct 2013 15:01:15 +0100 <robert.sharpe@evergreen-consulting.co.uk<mailto:robert.sharpe@evergreen-consulting.co.uk>> wrote ---- Hi Kevin, Thanks a lot for your kind offer. I should set expectations that I am an out of practice and slow coder, but I will do what I can to help. I can probably help more with test, debug and coordination. So if you are still happy then, as I dont have any OVMS kit, I will need an OVMS and correct cable. Can someone point me to a developer beginner's instructions for what else is required to develop/test, e.g. programmer, sniffer, code repository login, CM procedures, etc It helps me, and hopefully anyone else working on the project, if we can agree the breakdown of work. As you may have already seen I have suggested a post for the Leaf development at http://www.openvehicles.com/node/111 Nikki/Mark shall we use that as a way of planning and tracking the work ? Regards, Rob On Oct 14, 2013, at 2.21PM, Nikki Gordon-Bloomfield wrote: Hi Kevin, That's very generous. Happy to test OVMS in my LEAF, so I guess another OVMS kit with a righty cable? Nikki. On 14 Oct 2013, at 13:47, Kevin Sharpe ZCW <kevin.sharpe@zerocarbonworld.org">target="_blank">kevin.sharpe@zerocarbonworld.org<mailto:kevin.sharpe@zerocarbonworld.org>> wrote: Rob, Mark (C), Nikki, If it helps, I'm happy to provide each of you with OVMS hardware FOC in return for your efforts on the Leaf development :-) Let me know what you need, [http://www.zerocarbonworld.org/images/logo.png] Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org <mailto:kevin.sharpe@zerocarbonworld.org> | http://www.zerocarbonworld.org/ | twitter.com/zerocarbonworld<http://twitter.com/ZCWcharlie> [http://www.zerocarbonworld.org/images/email-signatures_06.png] Zero Carbon World is a UK Registered Charity #1141347 From: Robert Sharpe <robert.sharpe@evergreen-consulting.co.uk">target="_blank">robert.sharpe@evergreen-consulting.co.uk<mailto:robert.sharpe@evergreen-consulting.co.uk>> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk">target="_blank">ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Date: Monday, 14 October 2013 13:41 To: OVMS Developers <ovmsdev@lists.teslaclub.hk">target="_blank">ovmsdev@lists.teslaclub.hk<mailto:ovmsdev@lists.teslaclub.hk>> Subject: Re: [Ovmsdev] OVMS Leaf Support Hi Mark, This looks very interesting. I am out today but will look in more depth tomorrow. Regards, Rob ---- On Mon, 14 Oct 2013 10:08:41 +0100 Mark Webb-Johnson <mark@webb-johnson.net">target="_blank">mark@webb-johnson.net<mailto:mark@webb-johnson.net>> wrote ---- I think the leaf spy app shows what can be done. It only uses standard OBDII, with just one can bus. It could also be using the other non-can OBDII buses, but I doubt it. Shame it is not open source, but the leaf codes are pretty well documented now. Regards, Mark On 14 Oct, 2013, at 4:00 pm, Nikki Gordon-Bloomfield <nikki@aminorjourney.com">target="_blank">nikki@aminorjourney.com<mailto:nikki@aminorjourney.com>> wrote: Oh yes, there are multiple CAN busses on the LEAF. The standard one, which is where all the data below comes from, an the EV can -- that would require some clever doodads, since both are on the same physical connector -- just different pins. Nikki. On 14 Oct 2013, at 04:50, Mark Webb-Johnson <mark@webb-johnson.net">target="_blank">mark@webb-johnson.net<mailto:mark@webb-johnson.net>> wrote: Robert, Sorry for the delay in response - I’ve been off grid parenting for the past 24 hours. I think @Nufkin has done some preparation work, and we have a stub vehicle support file (vehicle_nissanleaf.c), but nothing working yet. This App shows what can be done: https://play.google.com/store/apps/details?id=com.Turbo3.Leaf_Spy_Pro using just the OBD-II port (I assume all the single master CAN bus, but perhaps also other buses on OBD-II). I’m very excited by this, and more than willing to help, but I don’t have the car here so am limited in what I can do. Can you work with @nufkin (and his other half) on this? You would need some sort of CAN bus decoder (perhaps just an OBD-II dongle, or CAN-USB adaptor), plus an OVMS module and PICKIT for firmware download. If you use MAC OSX, the development environment is simple to setup - for windows there are a few more hoops to jump through. Lastly, a RS232-USB adaptor is useful (but not essential). Regards, Mark. On 13 Oct, 2013, at 4:00 pm, Robert Sharpe <robert.sharpe@evergreen-consulting.co.uk">target="_blank">robert.sharpe@evergreen-consulting.co.uk<mailto:robert.sharpe@evergreen-consulting.co.uk>> wrote: Hi, < ovmsdev-request@lists.teslaclub.hk">target="_blank">ovmsdev-request@lists.teslaclub.hk<mailto:ovmsdev-request@lists.teslaclub.hk>> Is anyone working on Leaf support? I am interested in helping if I can and have started a discussion at http://openvehicles.com/comment/220#comment-220 to capture were we are with the Leaf. Regards, Robert Sharpe (Technical Director) 07711 252971 http://www.facebook.com/EvergreenConsultingLtd http://twitter.com/EGCtechnical <http://uk.linkedin.com/in/arsharpe>http://uk.linkedin.com/in/arsharpe [Evergreen Consulting] www.evergreen-consulting.co.uk<http://www.evergreen-consulting.co.uk/?utm_source=OVMSdevList&utm_medium=Email&utm_campaign=LeafOVMS> Your Plugged-in Partner Support the future and switch to a renewable energy supplier such as Good Energy<http://www.goodenergy.co.uk/affiliates/evergreen-consulting> Evergreen Consulting is the trading name of Sharpe Consultants Ltd < /ovmsdev-request@lists.teslaclub.hk">target="_blank">/ovmsdev-request@lists.teslaclub.hk<mailto:/ovmsdev-request@lists.teslaclub.hk>>_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk<mailto:OvmsDev@lists.teslaclub.hk> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

Jeremy, We are using the gateway function at the moment, that bridges the CAN and EV buses. Seems to work well - but it only bridges extended PID requests and replies (not most normal passive bus traffic). This allows us to access the EV bus from the CAN bus. Regards, Mark. On 4 Nov, 2013, at 11:09 am, Jeremy Whaling <jeremy.whaling@gmail.com> wrote:

Hi All,

According to the service manual, the current Telematics is located on the EV bus. My can to USB arrives Tuesday, hope to be listening to the TCU can messages soon.

I've attached a page to show what's on the EV and car can busses.

Jeremy

On Sunday, November 3, 2013, Kevin Sharpe ZCW wrote: OVMS hardware is currently in UK customs and should be released this week.

Have you obtained the programmer and any other dev tools?

On 3 Nov 2013, at 08:53, "Robert Sharpe" <robert.sharpe@evergreen-consulting.co.uk> wrote:

...

Hi Kevin,

I am keen to start helping out on the Leaf development. It's been 3 weeks and I just wandered what the progress with the OVMS hardware is ?

Regards, Rob

---- On Mon, 14 Oct 2013 15:01:15 +0100 <robert.sharpe@evergreen-consulting.co.uk> wrote ----

Hi Kevin,

Thanks a lot for your kind offer.

I should set expectations that I am an out of practice and slow coder, but I will do what I can to help. I can probably help more with test, debug and coordination.

So if you are still happy then, as I dont have any OVMS kit, I will need an OVMS and correct cable.

Can someone point me to a developer beginner's instructions for what else is required to develop/test, e.g. programmer, sniffer, code repository login, CM procedures, etc

It helps me, and hopefully anyone else working on the project, if we can agree the breakdown of work. As you may have already seen I have suggested a post for the Leaf development at http://www.openvehicles.com/node/111

Nikki/Mark shall we use that as a way of planning and tracking the work ?

Regards, Rob

On Oct 14, 2013, at 2.21PM, Nikki Gordon-Bloomfield wrote: Hi Kevin,

That's very generous. Happy to test OVMS in my LEAF, so I guess another OVMS kit with a righty cable?

Nikki.

On 14 Oct 2013, at 13:47, Kevin Sharpe ZCW <kevin.sharpe@zerocarbonworld.org">target="_blank">kevin.sharpe@zerocarbonworld.org> wrote:

Rob, Mark (C), Nikki,

If it helps, I'm happy to provide each of you with OVMS hardware FOC in return for your efforts on the Leaf development :-)

Let me know what you need, Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org | http://www.zerocarbonworld.org/ | twitter.com/zerocarbonworld

Zero Carbon World is a UK Registered Charity #1141347 From: Robert Sharpe <robert.sharpe@evergreen-consulting.co.uk">target="_blank">rob _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev <photo.jpg>_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

Thanks Rob ---- On Mon, 04 Nov 2013 14:07:58 +0100 Kevin Sharpe ZCW <kevin.sharpe@zerocarbonworld.org> wrote ---- OVMS kits back in stock in the UK and FOC kits sent to Nikki and Robert to help with Leaf development. http://shop.zerocarbonworld.org/Open-Vehicles/ Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org | http://www.zerocarbonworld.org/ | twitter.com/zerocarbonworld Zero Carbon World is a UK Registered Charity #1141347 From: Robert Sharpe <robert.sharpe@evergreen-consulting.co.uk> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Date: Sunday, 3 November 2013 08:52 To: Ovmsdev <ovmsdev@lists.teslaclub.hk> Subject: Re: [Ovmsdev] OVMS Leaf Support Hi Kevin, I am keen to start helping out on the Leaf development. It's been 3 weeks and I just wandered what the progress with the OVMS hardware is ? Regards, Rob ---- On Mon, 14 Oct 2013 15:01:15 +0100 <robert.sharpe@evergreen-consulting.co.uk> wrote ---- Hi Kevin, Thanks a lot for your kind offer. I should set expectations that I am an out of practice and slow coder, but I will do what I can to help. I can probably help more with test, debug and coordination. So if you are still happy then, as I dont have any OVMS kit, I will need an OVMS and correct cable. Can someone point me to a developer beginner's instructions for what else is required to develop/test, e.g. programmer, sniffer, code repository login, CM procedures, etc It helps me, and hopefully anyone else working on the project, if we can agree the breakdown of work. As you may have already seen I have suggested a post for the Leaf development at http://www.openvehicles.com/node/111 Nikki/Mark shall we use that as a way of planning and tracking the work ? Regards, Rob On Oct 14, 2013, at 2.21PM, Nikki Gordon-Bloomfield wrote: Hi Kevin, That's very generous. Happy to test OVMS in my LEAF, so I guess another OVMS kit with a righty cable? Nikki. On 14 Oct 2013, at 13:47, Kevin Sharpe ZCW <kevin.sharpe@zerocarbonworld.org">target="_blank">kevin.sharpe@zerocarbonworld.org> wrote: Rob, Mark (C), Nikki, If it helps, I'm happy to provide each of you with OVMS hardware FOC in return for your efforts on the Leaf development :-) Let me know what you need, Kevin Sharpe | Founder & Patron Tel: +44 122 566 7544 ext: 800 | Skype: zerocarbonworld kevin.sharpe@zerocarbonworld.org | http://www.zerocarbonworld.org/ | twitter.com/zerocarbonworld Zero Carbon World is a UK Registered Charity #1141347 From: Robert Sharpe <robert.sharpe@evergreen-consulting.co.uk">target="_blank">robert.sharpe@evergreen-consulting.co.uk> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk">target="_blank">ovmsdev@lists.teslaclub.hk> Date: Monday, 14 October 2013 13:41 To: OVMS Developers <ovmsdev@lists.teslaclub.hk">target="_blank">ovmsdev@lists.teslaclub.hk> Subject: Re: [Ovmsdev] OVMS Leaf Support Hi Mark, This looks very interesting. I am out today but will look in more depth tomorrow. Regards, Rob ---- On Mon, 14 Oct 2013 10:08:41 +0100 Mark Webb-Johnson <mark@webb-johnson.net">target="_blank">mark@webb-johnson.net> wrote ---- I think the leaf spy app shows what can be done. It only uses standard OBDII, with just one can bus. It could also be using the other non-can OBDII buses, but I doubt it. Shame it is not open source, but the leaf codes are pretty well documented now. Regards, Mark On 14 Oct, 2013, at 4:00 pm, Nikki Gordon-Bloomfield <nikki@aminorjourney.com">target="_blank">nikki@aminorjourney.com> wrote: Oh yes, there are multiple CAN busses on the LEAF. The standard one, which is where all the data below comes from, an the EV can -- that would require some clever doodads, since both are on the same physical connector -- just different pins. Nikki. On 14 Oct 2013, at 04:50, Mark Webb-Johnson <mark@webb-johnson.net">target="_blank">mark@webb-johnson.net> wrote: Robert, Sorry for the delay in response - I’ve been off grid parenting for the past 24 hours. I think @Nufkin has done some preparation work, and we have a stub vehicle support file (vehicle_nissanleaf.c), but nothing working yet. This App shows what can be done: https://play.google.com/store/apps/details?id=com.Turbo3.Leaf_Spy_Pro using just the OBD-II port (I assume all the single master CAN bus, but perhaps also other buses on OBD-II). I’m very excited by this, and more than willing to help, but I don’t have the car here so am limited in what I can do. Can you work with @nufkin (and his other half) on this? You would need some sort of CAN bus decoder (perhaps just an OBD-II dongle, or CAN-USB adaptor), plus an OVMS module and PICKIT for firmware download. If you use MAC OSX, the development environment is simple to setup - for windows there are a few more hoops to jump through. Lastly, a RS232-USB adaptor is useful (but not essential). Regards, Mark. On 13 Oct, 2013, at 4:00 pm, Robert Sharpe <robert.sharpe@evergreen-consulting.co.uk">target="_blank">robert.sharpe@evergreen-consulting.co.uk> wrote: Hi, < ovmsdev-request@lists.teslaclub.hk">target="_blank">ovmsdev-request@lists.teslaclub.hk> Is anyone working on Leaf support? I am interested in helping if I can and have started a discussion at http://openvehicles.com/comment/220#comment-220 to capture were we are with the Leaf. Regards, Robert Sharpe (Technical Director) 07711 252971 http://www.facebook.com/EvergreenConsultingLtd http://twitter.com/EGCtechnical http://uk.linkedin.com/in/arsharpe www.evergreen-consulting.co.uk Your Plugged-in Partner Support the future and switch to a renewable energy supplier such as Good Energy Evergreen Consulting is the trading name of Sharpe Consultants Ltd < /ovmsdev-request@lists.teslaclub.hk">target="_blank">/ovmsdev-request@lists.teslaclub.hk>_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk">target="_blank">OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev