Decyphering iMiEV and iON CAR-CAN message data

[garygid]

Please use this thread to discuss the meaningful data
fields that we are discovering, or investigating.

Please use these conventions in these discussions:

1. The Message ID is always in 3 hex characters, like 5BC
2. Refer to the data bytes as D1, D2, D3, D4, D5, D6, D7, D8
3. Show how to decode and scale the data, if known.
4. By default, D4 means all 8 bits of D4
5. Then, D5[7-4] would be the top 4 bits of D5

List of known values:
Note: A (#) following the description = displayed
on CAN-Do v198 Dashboard.

412:D2 = Speed, in km per hour (#)
412:D3,D4,D5 as ((((D3 * 256) + D4) * 256) + D5) = Odometer, in km (#)

373:D3,D4 as (((D3 * 256) + D4) - 32768) * -0.01 = Pack Amps Out (#)
373:D5,D6 as ((D5 * 256) + D6) * 0.1 = Pack Volts (#)

----------
6E1, 6E2, 6E3, and 6E4 are a secquence that contains
cell voltages (88 voltages) and teperatures (66 of them).
See the details in a later post.

----------

[jjlink]

Here is capture to a .can file this time.
https://www.dropbox.com/s/a83h90quf3rpx ... Do196c.zip

Note: the SoC was at or very near 100% at the start of this trip.

Also a .txt file is also included to verify the data is good.

[garygid]

The bug with displaying the Dashboard while reading
an ".alc" file has been eliminated.

http://www.wwwsite.com/puzzles/cando/CAN-Do-v198.zip

is the updated program.
Enjoy, and any suggestions are welcome.

[garygid]

jjlink,
Nice driving log, just over 6 million Messages,
logging about 31 minutes of driving. Thanks.

I do not yet have a Recipe entry for "SOC", but maybe
you will share Recipes for the any items that you have
found. This is the thread for sharing any such Recipes.

With V198 of CAN-Do ...
Your 6-million message ".can" log file works fine,
and I saved it as an ".alc" file and that works fine also.

I graphed Speed, Pack Amps Out, and Pack Volts, and
it seems to work quite well.

Might 373:D1 be something like the Highest Cell Voltage, and 373:D2
be the Lowest Cell Voltage (either scaled or with an offset?)

You guys are making great progress.
Cheers, Gary

[garygid]

I would like to be able to display the cell voltage,
Min, Average, and Max on the Dashboard.

What CAN Messages and fields do I use for
those, please. I seem to remember that the
temperature information is also available, right?

As I recall, it was a series of messages, with some
index value, but I think that priusfan must have
the exact details now, since his very nice 2nd
app shows all 88 cell voltages.

How many temperatures are reported?

[priusfan]

to get details from batt cells,
this is in frames 6E1, 6E2 , 6E3 & 6E4
D1 is an index from 1 to 12
so, you get arrays with 48 positions
but for each combination, there are 2 values

yes it is tricky

better to open my project (the one for the batt) with b4a or read using VB the module scanner.bas.

[jjlink]

Ok, here is a 1 Hour charge capture. The car was down to 4 bars left when I started the charging cycle. The BMS spent the first 15 minutes planning the charge, then it actually started charging for the next 45 minutes. It created 4,135,275 records in that hour, so Gary you can figure 6 hours at 240v will create something like 24,811,650 records. At the end of the hour capture you should be able to see when I pressed the button on the charge handle and stopped the charge cycle, unplugged the J1772, opened the car door and stopped the capture.

Here is the CAN file:
https://www.dropbox.com/s/rz4y19szmre9v ... 98_1HC.zip

For those that don't realize it you can see the active data logging activity on the ODBlink LED (it flashes) when activating individual devices in the car with nothing else going on. This makes it relatively easy to isolate what device in the car sends what data on the CAN bus. For example you can open the car door and see data on the CAN bus is getting logged. In this way it would be pretty easy to figure out what devices in the car relate to what data is being send on the CAN bus (just by switching things on/off and writing down what you did at that time in the capture.

Since Gary has got the CAN-Do program to the point where any of you could start capturing data with an inexpensive ODBlink device, you may want to try it. I can explain how to capture log files with the CAN-Do program, its not hard to do.

Here are some sources for the OBDLink SX Scan Tool:
http://www.amazon.com/OBDLink-SX-OBD-II ... B004IAGNNG
http://www.scantool.net/obdlink-sx.html

Of course it would be really cool if we could ditch the USB wire and use this BT device with the CAN-Do program:

STN1110 Bluetooth OBD-II Adapter
http://batman.homelinux.com/blog/blueto ... i-adapter/

[garygid]

CAN-Do has an Event Logging feature.

You can set up about 10 Event Messages to insert real-time
into the log data, human readable descriptions of events
that you intend to log. Perhaps "Door Opened", "Headlights On",
or some other events.

While logging, a tap of a number key on the keyboard
will insert the "Event" message into the log data.
This can be helpful when looking for some indication of that
event in the CAN data during later analysis of the log.

Although use of these messages is not perfectly supported
yet, this Event feature worked the last time that I tested it.

[garygid]

As I recall, I think that I raised the number of in-memory
Log Messages from 20 million to 30 million in CAN-Do v199.

In any case, the logging "should" quit gracefully when the
In-Memory Logging limit is reached.

I intend to add a Log-to-File option, rather than just the
current Log-to-Memory function.

There is an option to have CAN-Do begin logging when
the program starts up, but that option is not yet very
useful to you, since the OBDLink Setup scripts are not
yet automated.

[jjlink]

Gary, I'm ready to do the low SoC to full charge log capture sometime in the next three days. Should I wait for the log-to-file feature before doing it?