My Nissan Leaf Forum

I just added the Logging Port to my SOC-Meter, and tried to
do some Logging. I got strange results:
(I might have "broken" either CAN-Do receiving, or the SOC-Meter Log-sending.)

I am using SOC-Meter F1.08 and CAN-Do version 1.5.0
An earlier version of CAN-Do (like 1.4.4) might not be broken.

What versions are you using?

I will describe what I got:
With the LEAF ON and READY, but still in Park,

With the "Show Counts" checkbox checked, the wider pink field goes white
and shows message counts, updating about every 200 messages.

However, I got only about 200 additional messages every 10 or 20 seconds,
and a lot of activity in the shorter yellow field. It indicates status, and
I will look up what the numbers mean.

Then, when I "Stopped Input", and went to the Filters screen and
click "Get Msg IDs" (near the left, at the top), I get strange message IDs,
not the ones that I normally get.

So, it APPEARS that either CAN-Do is broken, or the SOC-Meter firmware is broken.

Try CAN-Do around version 1.44 and see if that works.
Based on your tests, I will look for a broken CAN-Do first.
More info later.

I just tried V1.41 (because I already had it downloaded), and it works somewhat better. I don't see any more of the weird corrupted packets, but it seems to be missing a lot of data. And when I display the dashboard, the only valid item displayed is the number of fuel bars.

Should bother I trying again with 1.4.4?

I think you can use CAN-Do 1.4.2 to see a bit more (RPM), if you wish.
However, I think CAN-Do 1.4.4 and on might be broken (for Comm-In Logging).

So, the recent 1.5.0, and the previous versions after 1.4.2, have broken Comm
message reading and I am fixing it now, and I will test it soon, then
put a new version 1.5.1 on-line, and post here. (about another hour or two)

Sorry for the inconvenience, Gary

I just tested with my latest version 1.5.1 of CAN-Do, found at:
http://www.wwwsite.com/puzzles/cando/
I tested Logging messages from the SOC-Meter's Logging Port.
There were some bugs in the version 1.5.0 of CAN-Do.

The Logging Port on the SOC-Meter ver F1.08 seems to work fine with CAN-Do
only IF you use a GOOD USB-to-RS232 cable, but NOT if you use a POOR one.

Using a POOR USB-to-RS232 cable, I got what looked like "garbage" messages.
Also, I "received" only about 100 messages in 15 seconds, not the normal
message rate that is more lke 500 messages per second!

So, make sure you get a "good" USB-to-RS232 adapter.
Those with the latest FTDI chip MIGHT be the better ones.

-------------- What is GOOD? ----------------
No, I have not tested any of these.
However, I would try #4 first (or #2), I think.

1. This "Windows 7 Compatible USB Serial Adapter FTDI Chip
RS232 DB-9 920K with TX/RX LED" MIGHT be good, but it
only has a short cable, and has female attachment hardware.

$18 at Amazon:
http://www.amazon.com/Windows-Compatibl ... 244&sr=8-2

2. This "36inch FTDI USB to Serial Cable for MA PC Linux with Windows Certified Drivers" has a 3-foot cable and appears to have the male attachment hardware (desired).

$19 at Amazon:
http://www.amazon.com/36inch-Serial-Win ... 244&sr=8-6

3. This "6ft. USB to RS232 Converter for Windows 7 (32/64bit) FTDI CHIP RX/TX LED" has a 6-foot cable, but has the female attachment hardware that might not mate well with the SOC-Meter's Logging Port mounting hardware.

$20 at Amazon:
http://www.amazon.com/6ft-RS232-Convert ... 244&sr=8-7

4. This has a 10-foot cable and has the male attachment hardware (that we desire): "USB to RS232 Serial DB9 Cable Adapter FTDI Chipset 10 Feet Supports Windows 7 64bit"

$25 at Amazon:
http://www.amazon.com/Serial-Adapter-Ch ... 44&sr=8-14

5. For those wanting to do 3 or 4-bus CAN logging, this "4 Port RS232 FT4232HL Professional USB to Serial Adapter with TX/RX LED and COM Retention FTDI Chip & Fast 920K Per Port Transfer Speed Certified Microsoft Windows 7 and 2008 Driver Included (32/64-Bit)" might be quite good.

$45 at Amazon:
http://www.amazon.com/FT4232HL-Professi ... 244&sr=8-5

-----

Gary,
I tried the 1.5.1, and it's still not logging properly for me.

1) I'm using a "good" serial adapter with FTDI chip
2) To test for data corruption, I wrote a program to dump the raw logging data to a file.
Next, I wrote another program to decode the raw data that I logged to the file.
There were no lost bytes or data corruption, the data decoded 100% error free.

I want to make sure that there's no discrepancy between the format that I'm outputting and what
CAN-Do expects. Could you please send me a log file of the raw data that's received on the serial port
by CAN-Do?

I've sent you an email with my data dumping utility, in case you don't have something convenient to use.

I would really like to get my hardware working with CAN-Do instead of writing a new program.
Thanks!
Sam

Email your raw log to me first.

I do not yet have a function to make a raw log file, but I can add one to CAN-Do, and add a function to read a raw log as well.

I will help you get this going.
See my PM.

I didn't receive a PM from you, but I just emailed the raw log.

The sync byte is not correct.

53 xor LL xor DH => sync byte

where the MsgID is HLL and the data-count is D

You are doing
53 xor LL xor 0H, then adding the D later.

Otherwise, looks good.

I had a feeling it was just a small discrepancy in format...
yes, I was doing MsgLo XOR MsgHi XOR 53h for the sync byte.
Good sleuthing.

I made the change in my code, and it talks to CAN-Do perfectly now! Thanks for the help.
It's easier to figure out the CAN messages when there's instant feedback on the live bus.
I spent several hours staring at my message logs yesterday, but wasn't able to glean anything new yet.

One thing I just noticed. The regen bargraph goes positive when I put the car in reverse, so the value that's displayed there is probably related to direction of current flow in the motor, rather than what's going in/out of the pack.

Also, I was looking into D4 of 50A as a candidate for temperature in C, but it looks too high ... my car was cold this morning, and it was 62F outside, but the temp was translating to about 82F.

Had the car L2-charged overnight (in early to late morning), perhaps to 100%?

If so, warming internally to 80ºF is not impossible.

Or, maybe charger or coolant temperature?

I will look at D4 of 50A