garygid
Posts: 187
Joined: Fri Oct 05, 2012 10:19 am
Location: Laguna Hills, CA 92653
Contact: Website

Re: Decyphering iMiEV and iON CAR-CAN message data

Fri Nov 09, 2012 7:29 am

MLucas wrote:For me, I'm not using the OBDLink SX and using the LeafCan, instead with a Dell Duo convertable running Windows 8. I compared my logs with jjlink and they do look similiar with the same type of messages coming through. I analyzed my data for a pattern and it looks like there are common lengths of messages with mostly the same data. The messages with a length of 5 or what would come through the port as a DLC 2 are all 10100. There is one length of 6 in my data, 346271. The next length of 7 are all 3250100. Then come the 17 character length messages, 21000000000000000 and 41850000000000000. The rest are all the 19 character length messages.


What format data is your LeafCan sending?

What program are you using on Win8 to capture the data?

Since each message that you describe is in the hex-text format
of MMMD1D2D3D4D5D6D7D8 then all of your messages should
be of odd length, with three MsgID hex digits and 2xN hex characters
for the N bytes of data. Of course, this is just counting the visible
characters, and ignoring any line-feed or carriage-return.

So, it looks like the one 6-character message is an error of
some sort.

I do not understand your "DLC 2" description of the 5-character
10100 message, which would be a MsgID of hex 101 with one data
byte of 0x00 (zero).

But, it does appear that you are capturing data.

If this data is punctuated with a line-feed character,
that is the OBDLink format, and you should be able
to use CAN-Do to capture the data, and it will add
time-stamps, insert Date-Time pseudo-messages,
and count any even-length message as an error,
instead of including it in the logged messages.

The latest version of CAN-Do is v205, which should
give you a message at the end of the capture with
the total number of errors, and the Max Bytes Used
in the Comm buffer.

Cheers, Gary

Have you tried to get this data into CAN-Do?
LEAF owner, EV supporter

jjlink
Site Moderator
Posts: 393
Joined: Sun Sep 11, 2011 8:26 am
Location: San Francisco Bay Area, CA

Re: Decyphering iMiEV and iON CAR-CAN message data

Fri Nov 09, 2012 8:39 am

Here is this mornings test capture with CAN-Do v205:

Image
Capture by JJLINK, on Flickr
John - 2012 Silver i-MiEV SE model, Jan 19th, 2012 w/OpenEvse, caniOn,& OVMS.

garygid
Posts: 187
Joined: Fri Oct 05, 2012 10:19 am
Location: Laguna Hills, CA 92653
Contact: Website

Re: Decyphering iMiEV and iON CAR-CAN message data

Fri Nov 09, 2012 11:18 pm

I guess that we should make a capture with RealTerm,
read that file into CAN-Do, and see if we get the same
kind of data-length errors.
LEAF owner, EV supporter

jjlink
Site Moderator
Posts: 393
Joined: Sun Sep 11, 2011 8:26 am
Location: San Francisco Bay Area, CA

Re: Decyphering iMiEV and iON CAR-CAN message data

Sat Nov 10, 2012 11:40 am

Gary, I checked and its getting errors in RealTerm. I see the red Error light come while capturing.

I used COM27:

It was initially set up 115,200 baud, 8,N,1.

The "Serial Enumerator" was NOT checked.

Buffer size is 4096.

Latency is at 1, is that to low a setting?

with these commands sent to it:
stsbr 500000
500000 (reconnect at 500000)
ATSP6
ATE0
ATH1
ATL0
ATS0
ATCAF0
ATMA

I loaded into CanDo:

Image
RT-Capture1 by JJLINK, on Flickr

Image
RT-Capture1a by JJLINK, on Flickr

The log file is here:
https://www.dropbox.com/s/xj5pa75wglprn ... pture1.zip

Any Ideas?

Thanks
John - 2012 Silver i-MiEV SE model, Jan 19th, 2012 w/OpenEvse, caniOn,& OVMS.

garygid
Posts: 187
Joined: Fri Oct 05, 2012 10:19 am
Location: Laguna Hills, CA 92653
Contact: Website

Re: Decyphering iMiEV and iON CAR-CAN message data

Sat Nov 10, 2012 5:58 pm

Try latency of 4.
LEAF owner, EV supporter

MLucas
Posts: 833
Joined: Thu Jun 07, 2012 8:52 am
Location: Niagara on the Lake, Ontario, Canada

Re: Decyphering iMiEV and iON CAR-CAN message data

Sun Nov 11, 2012 10:07 am

garygid wrote:
MLucas wrote:For me, I'm not using the OBDLink SX and using the LeafCan, instead with a Dell Duo convertable running Windows 8. I compared my logs with jjlink and they do look similiar with the same type of messages coming through. I analyzed my data for a pattern and it looks like there are common lengths of messages with mostly the same data. The messages with a length of 5 or what would come through the port as a DLC 2 are all 10100. There is one length of 6 in my data, 346271. The next length of 7 are all 3250100. Then come the 17 character length messages, 21000000000000000 and 41850000000000000. The rest are all the 19 character length messages.


What format data is your LeafCan sending?

What program are you using on Win8 to capture the data?

....

The latest version of CAN-Do is v205, which should
give you a message at the end of the capture with
the total number of errors, and the Max Bytes Used
in the Comm buffer.

Cheers, Gary

Have you tried to get this data into CAN-Do?


Q1. I'm not sure the format, I just matched what you were sending in your Can-Spy program and this is the result.

Q2. RealTerm

Q3. No, I have not yet run Can-Do on this data. Is there a newer Recipe file?

Like Dylan...I went electric.

  • Purchased: June 29th, 2012
  • Mileage on June 29th, 2013 - 25,431 km / 15,802 miles
  • Mileage on June 29th, 2014 - 51,286 km / 32,616 miles

List of Oil Spills: http://en.wikipedia.org/wiki/List_of_oil_spills

garygid
Posts: 187
Joined: Fri Oct 05, 2012 10:19 am
Location: Laguna Hills, CA 92653
Contact: Website

Re: Decyphering iMiEV and iON CAR-CAN message data

Sun Nov 11, 2012 1:59 pm

Are you sending Ascii Hex characters, two per byte, or
are you sending binary bytes, one per data byte?

I send 11 binary bytes, three for the Sync and MsgID,
and always 8 bytes for the data, since I pad the data
out to 8 bytes, if needed, with 0xFF bytes.

That does not match what you are showing for
the messages. You show variable length, no Sync
byte, and no Data Length value (a nibble that I send).

LeafCAN sends different log data than the GID-Meter
sends. It sends Hex-character messages similar to
what you are sending, but LeafCAN adds two
checksum bytes, right?

Or am I totally confused (again)?
LEAF owner, EV supporter

jjlink
Site Moderator
Posts: 393
Joined: Sun Sep 11, 2011 8:26 am
Location: San Francisco Bay Area, CA

Re: Decyphering iMiEV and iON CAR-CAN message data

Sun Nov 11, 2012 5:50 pm

garygid wrote:Try latency of 4.



I'm still seeing the errors. :(
John - 2012 Silver i-MiEV SE model, Jan 19th, 2012 w/OpenEvse, caniOn,& OVMS.

FiddlerJohn
Posts: 240
Joined: Sat Jan 07, 2012 9:51 pm
Location: Bowie, Maryland

Re: Decyphering iMiEV and iON CAR-CAN message data

Tue Nov 13, 2012 3:45 pm

I am impressed. This group is making great progress, and I want to help.

I have the premium i-MiEV with 10200 happy miles, an OBDLink SX, and a dual core Intel T3400 2.17 GHz Acer Aspire Laptop with 4GB RAM and 32 bit Vista7.

I currently have two issues:
1. The OBDLink connects thru the USB to blink the OBDLink yellow light, but the OBDwiz application never connects to the OBD ECU CAN Bus. The Automatic Protocol setup checks all rates including 500 kBaud at 29 bits but never connects -- NO DATA.

2. Running CAN-DO gives:
"Component "MSCOMM32.OCX" or one of its dependencies not correctly registered: a file is missing or invalid"
garygid wrote:... remove the "-99" from the file name and usually replace the standard file in C:\windows\system32\
Enjoy, Gary
Removing "-99" and rebooting produced the same results.

Any suggestions?


I intend to delete the current "MSCOMM32.OCX" from the C:\windows\system32\ and add the new one (without the -99) again.

priusfan
Posts: 193
Joined: Mon Oct 08, 2012 7:39 am
Location: France

Re: Decyphering iMiEV and iON CAR-CAN message data

Wed Nov 14, 2012 4:08 am

1) Do NOT use OBDwiz , this app is not appropriate for electric cars.

2) about mscomm32.ocx, do not delete it, maybe rename it with a suffix like .ocx_old, so you can get it back if necessary.

but FIRST, follow this : method

Return to “Instruments - Radio/USB/Nav - CAN - Climate Controls - Remote”