MiEV-CAN

[jjlink]

When logging from the OBDLink SX, or similar, one must use
the Car-Comm channel, since the iMiev has only the Car-CAN bus.

To save to a binary log file, one selects the File Type with the
Radio Buttons nearby.

It gets errors if try to capture CarCom data, oddly enough it does successfully capture something when on Ev-Com.

https://www.dropbox.com/s/oca9q1q7ckxr3sx/CarCan.JPG

These came from the EV-Com capture: https://www.dropbox.com/s/olegcppwh6jd6tq/i-Miev_CanDo_Logs.zip

I'm not seeing the radio button you mention. :?:

 

[priusfan]

in your log, the number of frames seems very low : we should get at least 1600/sec...

hereis another release for android app; it is much more stable and it will create a folder for logging.
the name of this folder is BT_CAN.

 

[garygid]

jjlink,
The data in the log from the EV channel is just garbage data,
from random data matching the normal "Sync" pattern.

I will look at your jpg again:
I see that the Car-Comm baud rate is 115200, not 500000 baud.
If your setup commands for the OBDLiink set up 500000 baud, then
the baud rate for reading the Car-Comm port must also be 500000 baud.

After your setup, where the ONDLink is outputting Log data,
starting to read the Log data with the CAN-Do "Read Comm Input"
button will close the Comm port if it is open, then re-open it at the
specified baud rate, then (hopefully) start to gather data, when it detects
the <lf> character (chr(13)) in the data stream.

So, please try again, on the Car-Comm port only, whch shows the green
(Port Exists) indication in your jpg, but set the baud rate to 500000 there,
unless you are setting your OBDLink to a different baud rate.

Thanks for tryig the test.
Cheers, Gary

 

[garygid]

priusfan,
Please remind me what hardware you are using on the OBD port
to send BT messages to the Android Tablet.

Assuming it is a BT version of the OBDLink SX (which is USB connected)
then check the Car-Comm, and OBDLink on Car-Comm, and get the
Comm Port set to have a green backbround, and the baud rate set to
match your OBDLink device, perhaps 500000.

You should not need to set any other parameters to get CAN-Do to
log data into memory, and look at what is in memory.
While reading, the 3rd field should be showing the number of
messages received, so around 1600 per second if everything is working.

I will try to make a test here with my LEAF.

-------------
In this version v194 of CAN-Do, do not check the Run Dashboard.

In my next version v195, I have added a iMiev dashboard, but with no
data being displayed on the dashboard.

In v197 I will try to add displaying the Odometer data, to see if it works.

Cheers, Gary

 

[garygid]

From the LEAF, doing the Car-Comm (CAR-CAN) at 500000 baud,
it appears that I got MsgIDs, but all the data lengths were zero,
and the data did not make sense.

So, there must be something wrong with my code.
So, wait until I get it to work here with the LEAF, and
I will post another version of CAN-Do.

Thanks, Gary

 

[garygid]

Success:
I found 2 bugs. I was setting N to zero in the wrong place.

Tested v196 of CAN-Do with OBDLink SX at 500000 baud
on the CAR-CAN (Car-Comm Input) port of my LEAF.

It seems to work, get lots of Messages, and I see at least
the Accelerator Pedal Position in the correct place in the data.

So, please get CAN-Do v196 from
http://www.wwwsite.com/puzzles/cando/CAN-Do-v196.zip
and try it out.

Please report your results.

 

[priusfan]

bonjour
I tested v196 with:
interface OBDLINK using USB
laptop running windows XP
see picture

I could connect and use the script

I get some results:

I think the capture is ok.
but I don't understand how the logging is working....
I tried many possibilities but without results.... (nothing is stored on the laptop)

 

[garygid]

After you have the good capture into memory (like I see in your
pictures), then you can save the data (the captured messages)
to a file by going to the Output Logs screen, and writing a Binary Log file,
usually in the All-CAN format by using the default "All" option.

Then, you enter a file path and name, or browse for a name and
folder location, using the ".alc" (all-can) file extension.
Use a file name that will help you remember what you
were logging.

Then, write all the in-memory log entries to the Binary file,
so that the same data can be shared, saved for use later, and
read back into CAN-Do easily at some later time.

Starting to capture new log data clears all the in-memory log
message data when you click the Read Comm button.

Congratulations, you are doing very well.

 

[garygid]

OK, about how many records are we getting per second,
while charging?

While driving, we might get 1600 per second, or about
6 million per hour. The present version of CAN-Do can
hold about 20 million messages in memory, so that
would be around 3 hours of driving, enough for most
driving logs.

However, charging might take 6 to 8 hours.
How many log messages are we likely to get?

Getting a good log of charging a fairly or very low
battery to 100% should help us find some SOC and
"fuel" related values, to let us make a better fuel
gauge. Also, we should be able to find Pack amps
and volts.

Once we identify these values, I should be able to
make a iMiev mode in my GID-Meter, or an iMiEV
version of the firmware for the unit.

See info about the SOC/GID-Meter at:
www.wwwsite.com/puzzles/socmeter/

However, a nice charging log first, please.
And... more Recipe items for the iMiEV.

 

[sandange]

I can see all that are on this posting, are very advanced in this field and I really do not have the knowledge to contribute to it.
As an average consumer I discovered this booth
(Fleetcarma Energy & Emissions Made Easy)
at the EV convention in Montreal last week

They have a device and service to monitor and record the performance of EV's , Hybrids and more.

http://www.fleetcarma.com/

I thought you might want to evaluate this should it be of relevance to your work here.

 

[garygid]

I got the iMIEV Dashboard in CAN-Do working, displaying
Speed and Odometer from MsgID 0x412.

It works when I read a ".can" file, but not when I read an ".alc" file.

So, it appears that I have a bit more work to do.
Cheers, Gary

 

[priusfan]

bonjour,
here, I am playing with the android app getting info via BT.
there are no more log files, only a small SQLite database.
at the moment there are 3 tables.
one for storing the macadress from the last used device.
one with a record each second; the time stamp is unixtime, some standard infos...
one with a record each kilometer...
maybe later on, other tables : by trip , summaries

this allows to start the application with the graph showing the usage from last strip...

It should be ready within 2 days...

ps to admin :
maybe you could split this thread;
one part for decyphering the data ,
another for using them, logging & / or developping UI

 

[garygid]

I started another thread for discussing the meanings
and decoding of the CAN Message data fields.

I will attempt to keep the first post of that thread
updated with the definition of the "known" data fields.

I also started another thread for Android CAN Monitoring Apps,
since this good work has grown to deserve its own thread.

 

[garygid]

The latest version of Can-Do shows Speed and Odometer,
and the Battery Pack Volts and Amps Out on the Dashboard.

The bug with reading ".alc" log files and using the Dashboard
has been stomped out.

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

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

 

[garygid]

The latest version of CAN-Do is v200, available at:
www.wwwsite.com/puzzles/cando/CAN-Do-v200.zip

The zip file includes an OCX that one can use to allow
CAN-Do to open Comm Ports 17 through 99, i addition
to the normal 1 through 16.

One would remove the "-99" from the file name and
usually replace the standard file in C:\windows\system32\

Enjoy, Gary

 

[garygid]

The latest version of CAN-Do is v202, available at:
http://www.wwwsite.com/puzzles/cando/CAN-Do-v202.zip

The zip file includes an OCX that one can use to allow
CAN-Do to open Comm Ports 17 through 99, in addition
to the normal port numbers of 1 through 16.

One would remove the "-99" from the file name and
usually replace the standard file in C:\windows\system32\

Enjoy, Gary

 

[jjlink]

The latest version of CAN-Do is v202, available at:
http://www.wwwsite.com/puzzles/cando/CAN-Do-v202.zip

The zip file includes an OCX that one can use to allow
CAN-Do to open Comm Ports 17 through 99, in addition
to the normal port numbers of 1 through 16.

One would remove the "-99" from the file name and
usually replace the standard file in C:\windows\system32\

Enjoy, Gary

That file (MSCOMM32.OCX) is in here on my Win7x64 box:

C:\Windows\SysWOW64

 

[garygid]

Win7 also has a Windows\System32 folder.

I have not yet investigated how to do this in Win7,
but maybe you put the new MSCOMM32.OCX in the
System32 folder, or perhaps replace the existing file
in the other folder. Or, maybe the file you see is
an entirely new compilation. Perhaps compare byte
length and the file dates.

I would suggest doing a Byte-comparison of these files.
The original OCX file has the bytes 3D 10 00 in exactly
one place, and the 10 ihex s the max port number.
I replaced the hex 10 with hex 63 (99 decimal).

Please let us know what you discover.

 

[garygid]

Has anybody tried this OBD BT adapter from BrainyDeal:

http://www.amazon.com/gp/product/B008U1MOM8/ref=ox_sc_act_title_1?ie=UTF8&smid=A1BREQ8I6OHSBG

For under $20, it has some good reviews, but apparently not to be
confused with other similar looking units from other Vendors.
Read the 5-star user comments, and watch the video there.

However, according to one source, "ELM327 V1.5" might be a clone.
But, it would be very nice if it was actually a reliable unit, right?

Cheers, Gary

 

[priusfan]

hello
I tested this exact interface (a guy in france got one and he sent it to me for tests).

it is not usable for us.
it is possible to install only one filter (at this time, I use 5 together).


do not leave it on the car: no sleep function, you will drain your battery.


it works perfectly with torque on prius gen3.