Anyone going to take this info and turn it into a simple product? I see jermyw seems to have got rid of his leaf.JeremyW wrote:CarWings does not have a stop charging message. As far as I can tell, the command from the telematics (EV bus message 56E) is pretty simple and made up of a few bit flags.From the highest bit: idle, VCM wake-up logic line status, remote charge, cc off, cc on, unknown, unknown, 0. The unknowns could be 12v supply voltage voltage ok and "within cell coverage"
Code: Select all
hex binary state 86 10000110 idle 46 01000110 status 4E 01001110 cc on 56 01010110 cc off 66 01100110 remote charge
Since that time I've never seen anything other than these states. You could unplug the TCU and try sending some other things like 0x67: 01100111 and see if that turns it off. However, I doubt Nissan would have left this functionality on the table. The only thing that I think they might have left on the table is the code to change the remote turn on temperature. In the 2013+ models this is a command from the AV unit to the climate control computer. I haven't isolated the message on a 2013 but I suspect it *might* work on a 2011 or 2012.
You might look at EV bus message 1F2. I suspect commanded charge power is in here.
ELM type OBDII adapters only connect to the standard CAR-CAN pins. They have no ability to connect to the EV-CAN unless you rewire them. LeafSpy assumes your OBDII adapter is connected to the CAR-CAN.pncguy wrote:I am working on my LeafSpy Pro setup. I have it all working using an old Google Nexus and the Konnwei KW902 (http://www.amazon.com/gp/product/B00R4R ... ge_o00_s00). This OBD2 reader has an on/off switch, but i don't know how long it will last, so I am thinking of a switched extension cable.
I was looking at the Tonsiki cable (http://www.amazon.com/gp/product/B00UR5 ... ISFXR1Q6M0) but I read the details and saw that it only passes through pins 2, 4, 5, 6, 7, 10, 14, 15, and 16.
I read a nice report here (http://digitalcommons.calpoly.edu/cgi/v ... text=cpesp) that says the EV CAN bus is passed through pins 12 and 13.
Does LeafSpy use the EV CAN bus? (I can't see how it wouldn't!) Does that then mean that I need to find (or make) a switched extension cable that carries pins 12 and 13?
nmgeek wrote:Has someone posted a reasonably comprehensive list of the CAN 'polling' query codes? I'm talking about the parameters for request codes like 797 and 745. I read through the google docs spreadsheet of CAN codes and have gotten through half of the 44 (ouch!) pages of this topic in the forum and have found only a dribbling of these codes (about 7 so far). I'm not sure of the exact terminology for these: polling codes, request/response codes, PIDs (Parameter IDs). So not knowing the official terminology I'm not sure exactly what to search for.
You'll want to pass a filter with "ATCF5B3", "ATCRA5BX" to get battery SOH for example. Buffer Overflow is a limitation of the ELM.bvdb wrote: Here is a snippet of what I get back using the expensive Bluetooth dongle: