garygid said:
CAN-Do v148 has been posted at
http://www.wwwsite.com/puzzles/cando/" onclick="window.open(this.href);return false;
This versions displays Battery Pack Output (Volts and Amps) on
the CAN-Do Dashboard. It also has a way to speed up the
Dashboard display by processing only 1 of every N messages.
However, you can see (what appears to be) the DC L2 charging amps
almost "steady" at about 8 amps in (for example -8.2), and
the voltage climbing from about 350 to near 400 volts
as the "6-hour" charging Log is read in.
....
Hi Gary,
I implemented a CAN data logger for a iMiEV recently. That was easy - because the manufacturer supplied us with a 'CAN gateway' - a piece of hardware that filtered the data coming out of the Drivetrain bus - and prevented us from writing into the bus. The 'it was easy' was thanks to them supplying us with a CAN Signal Configuration matrix - which told us which CAN ID's contained which messages, and which signals, as well as their data type (motorolla) and the bit locations - lengths, scalings, normalizations etc.! The same kinds of information that your followers will soon be loosing sleep over - trying to discover on their own!
Thus I became familiar with CAN-bus in this context.
I have today downloaded your software, very cool, and am trying to experiment with different byte masks etc. as you all are too.
I just have a couple questions:
1) has anyone done any controlled experiments while logging data from the ODB port, with the hope of 'calibrating' or 'decyphering' the data? for Example, if you think you know which message represents the L2 Amps during a charge - you could simply use a self powered clamp on current transformer attached to a voltmeter while charging, say for 2 minuites after it has stabalized, then you could revisit the data knowing first hand the direct measurement of the Amperage over that conductor. Then you would play with the scaling etc. until the numbers match.
2) has anyone done something like the above - regarding the suspected SOC contained in 5BC? the iMiEV for example, contains their SOC as an 8-bit (not ten) word in their 2nd byte, which you normalize to run from 0 to 250, meaning physical range of -5% (at bit value zero) to +120% (at full 8 bit). So the owner of a LEAF could for example, ignore their warnings and run the batteries to near zero - then begin a 110 VAC charge event (or 220 whatever) monitoring what you think is the SOC signal on the 5BC message - and assume the beginning is zero (or perhaps minus 5 for the iMiEV example!) and allow it to plateau at what should mean full (100% or perhaps 120%). Did someone already do that? like... was that '6 hour charge' constructed in this way? from 'a dead car' to 'a full battery'?
Thanks,