Battery ECU from Auto Enginuity

	Column 1	Column 2	Column 3	Column 4	Column 5	Column 6	Column 7	Column 8	Column 9	Column 10
0	Time (mm:ss)	38:59	39:21	39:43	40:05	40:27	40:49	41:10	41:32	41:54
1	IB Main Battery (A)	1.39	1.35	1.60	1.07	33.87	25.11	-11.13	33.5	-4.75
2	Battery Block Max Voltage (V)	15.43	15.41	15.37	15.36	14.52	15.53	16.46	16.37	16.43
3	Maximum Battery Block No (#)	15	1	19	19	1	19	19	19	1
4	Battery Block Min Voltage (V)	15.25	15.24	15.20	15.16	14.65	15.76	16.28	16.18	16.33
5	Minimum Battery Block No (#)	3	3	4	7	7	7	12	7	7
6	Battery Block Voltage 1 (V)	15.40	15.41	15.33	15.31	14.68	15.59	16.41	15.34	16.77
7	Inside Resist 1 (Ohm)	0.022	0.022	0.022	0.022	0.022	0.022	0.022	0.022	0.022
8	Battery Block Voltage 2 (V)	15.33	15.31	15.27	15.27	14.48	14.92	16.38	15.18	16.63
9	Inside Resist 2 (Ohm)	0.022	0.022	0.022	0.022	0.022	0.022	0.022	0.022	0.022
10	Battery Block Voltage 3 (V)	15.27	15.25	15.21	15.19	14.62	15.96	16.18	15.74	16.69
11	Inside Resist 3 (Ohm)	0.023	0.023	0.023	0.023	0.023	0.023	0.023	0.023	0.023
12	Battery Block Voltage 4 (V)	15.27	15.26	15.21	15.21	14.76	15.63	16.35	15.81	16.73
13	Inside Resist 4 (Ohm)	0.022	0.022	0.022	0.022	0.022	0.022	0.022	0.022	0.022
14	Battery Block Voltage 5 (V)	15.27	15.25	15.22	15.20	14.98	16.43	16.18	16.62	16.61
15	Inside Resist 5 (Ohm)	0.022	0.022	0.022	0.022	0.022	0.022	0.022	0.022	0.022
16	Battery Block Voltage 6 (V)	15.33	15.34	15.31	15.26	14.97	16.14	16.33	16.58	16.70
17	Inside Resist 6 (Ohm)	0.022	0.022	0.022	0.022	0.022	0.022	0.022	0.022	0.022
18	Battery Block Voltage 7 (V)	15.27	15.24	15.17	15.20	15.70	15.90	16.17	16.41	16.51
19	Inside Resist 7 (Ohm)	0.021	0.021	0.021	0.021	0.021	0.021	0.021	0.021	0.021
20	Battery Block Voltage 8 (V)	15.28	15.27	15.22	15.22	15.21	16.25	16.21	16.84	16.55
21	Inside Resist 8 (Ohm)	0.023	0.023	0.023	0.023	0.023	0.023	0.023	0.023	0.023
22	Battery Block Voltage 9 (V)	15.29	15.27	15.23	15.22	15.80	15.84	16.23	16.34	16.56
23	Inside Resist 9 (Ohm)	0.023	0.023	0.023	0.023	0.023	0.023	0.023	0.023	0.023
24	Battery Block Voltage 10 (V)	15.30	15.27	15.23	15.23	16.23	15.92	16.25	16.34	16.49
25	Inside Resist 10 (Ohm)	0.023	0.023	0.023	0.023	0.023	0.023	0.023	0.023	0.023
26	Battery Block Voltage 11 (V)	15.32	15.28	15.27	15.07	15.39	16.08	16.47	16.55	16.28
27	Inside Resist 11 (Ohm)	0.024	0.024	0.024	0.024	0.024	0.024	0.024	0.024	0.024
28	Battery Block Voltage 12 (V)	15.29	15.28	15.23	15.06	15.59	16.74	16.40	16.35	16.22
29	Inside Resist 12 (Ohm)	0.022	0.022	0.022	0.022	0.022	0.022	0.022	0.022	0.022
30	Battery Block Voltage 13 (V)	15.31	15.28	15.25	15.15	15.41	15.85	16.40	16.94	16.21
31	Inside Resist 13 (Ohm)	0.022	0.022	0.022	0.022	0.022	0.022	0.022	0.022	0.022
32	Battery Block Voltage 14 (V)	15.30	15.29	15.25	15.08	15.40	15.86	16.38	16.65	16.29
33	Inside Resist 14 (Ohm)	0.023	0.023	0.023	0.023	0.023	0.023	0.023	0.023	0.023
34	Battery Block Voltage 15 (V)	15.41	15.41	15.33	15.25	15.47	15.76	16.39	16.60	16.38
35	Inside Resist 15 (Ohm)	0.023	0.023	0.023	0.023	0.023	0.023	0.023	0.023	0.023
36	Battery Block Voltage 16 (V)	15.30	15.33	15.29	15.16	15.43	15.85	16.28	16.73	16.26
37	Inside Resist 16 (Ohm)	0.022	0.022	0.022	0.022	0.022	0.022	0.022	0.022	0.022
38	Battery Block Voltage 17 (V)	15.32	15.29	15.27	15.21	15.26	15.58	16.44	16.49	16.39
39	Inside Resist 17 (Ohm)	0.021	0.021	0.021	0.021	0.021	0.021	0.021	0.021	0.021
40	Battery Block Voltage 18 (V)	15.39	15.38	15.33	15.27	15.42	15.85	16.48	16.55	16.37
41	Inside Resist 18 (Ohm)	0.021	0.021	0.021	0.021	0.021	0.021	0.021	0.021	0.021
42	Battery Block Voltage 19 (V)	15.43	15.41	15.37	15.33	15.53	15.87	16.45	16.41	16.55
43	Inside Resist 19 (Ohm)	0.022	0.022	0.022	0.022	0.022	0.022	0.022	0.022	0.022
44	Battery Inside Air Temperature (C)	23	22	22	22	22	22	22	22	22
45	Battery Temperature 1 (C)	27	27	27	27	27	27	27	27	27
46	Battery Temperature 2 (C)	30	30	30	30	30	30	30	30	30
47	Battery Temperature 3 (C)	31	31	31	31	31	31	31	31	31
48	Battery Temperature 4 (C)	26	26	26	26	26	27	27	27	27
49	CCTL (Bit)	1	1	1	1	1	1	1	1	1
50	Cooling Fan HI (Bit)	0	0	0	0	0	0	0	0	0
51	Cooling Fan LO (Bit)	0	0	0	0	0	0	0	0	0
52	Cooling Fan MID (Bit)	0	0	0	0	0	0	0	0	0
53	Delta SOC (%)	20	20	20	20	20	20	20	20	20
54	ECU Code (ASCII)	255	255	255	255	255	255	255	255	255
55	EQC0 Front Relay (Bit)	0	0	0	0	0	0	0	0	0
56	EQTR Charge Start Signal (Bit)	0	0	0	0	0	0	0	0	0
57	Normal Status (Bit)	1	1	1	1	1	1	1	1	1
58	Onboard Charge Status (Bit)	0	0	0	0	0	0	0	0	0
59	Outer Charge Status (Bit)	0	0	0	0	0	0	0	0	0
60	Pre Onboard Charge Status (Bit)	0	0	0	0	0	0	0	0	0
61	SBLW Fan Stop Request (Bit)	0	0	0	0	0	0	0	0	0
62	The Number Of Stored DTCs (#)	0	0	0	0	0	0	0	0	0
63	VMF Fan Voltage (V)	0	0	0	0	0	0	0	0	0
64	WIN (Kw)	-20	-20	-20	-20	-20	-20	-20	-20	-20

Removed range text; ordered so battery modules are paired; formatted for trailing zeros.

I've highlighted the same values reported by the Graham miniscanner. The Graham scanner also reports the highest battery temperature but this may be calculated from the four values. The miniscanner can also read up to three, stored DTC and clear them as needed.

Bob Wilson

 

Exactly! Each data value is polled from the ECU by Auto Enginuity and reflects the value found when polled. In actuality, there is a time-stamp for each field but I left only the first time-stamp for each set of data.

BTW, I've been experimenting with how to display the data in a way that maximizes understanding. I'm done with changing table formats for now. But you are absolutely correct that there are race conditions between the different values.

Bob Wilson

 

I had the same problem with the Graham scanner. The polling interval is about 120 ms. but stuff happens a lot faster. So I adopted the practice of only using data where two points are within 10% of each other. Otherwise you get too many outliers and they'll drive the data nuts.

That is on my list but Saturday, I got my solder, OBD connector. I'm going to add a couple of cheap, push buttons and using that connector, verify we can read out the two-code flashes (Thanks Patrick.)

The one thing that has me scratchin' my head is MG1 torque is nearly random. I suspect they have a data conversion error so I'm starting to look at it much closer.

I still don't feel good about how to get it synced with the car correctly. I've had occasions where it just stopped polling too. I would not call AE a solid piece of work. So far:

• ISO9141-2 - vehicle type interface
• OBD-II compliant - initialization type, but I still get spiked codes on the ABS. The other initialization types didn't throw the codes but they also were less reliable in data recording. I had tried KWP2000 but it was unreliable. At least it didn't throw false codes on the ECUs.

I'm finding the best approach:

1. Plug in the OBD interface
2. Plug in the laptop and get it fired up and the application
3. Turn the car to IGN (no need to start or READY)
4. After the first sync
5. Pull down "Vehicle" and "disconnect"
6. Pause while it does it
7. Pull down "Vehicle" and "connect"

It seems going from "disconnect" to "connect" lets the software properly initialize the OBD module and sync the software. Then it seems to be a whole lot more reliable.

In recording the data, less is more. You'll still have race conditions and have to throw out data that is not part of stable operation.

GOOD LUCK!
Bob Wilson

 

I was looking at the battery voltages this weekend and SOC. I noticed that doing a forced charge leads to some peculiar data. The AE SOC values per module were above 80% but didn't quite follow the voltages. It almost looked like the dV drop of NiMH batteries but the drop was excessive. Later, I noticed the SOC display was higher than the actual SOC based upon voltage in the modules. It was very strange.

So last night, I put the car in "R" with the rear wheels against a curb. I was able to bring the module voltages to more normal levels and the operator SOC and battery levels seemed more 'normal.'

I'm planning to do more stuff in this area in the future.

All in all, the Graham Miniscanner is a more solid, plug-and-play, product. The AE is still a little too flaky for me to feel confident. It has more data points but . . .

Bob Wilson

 

Exactly! I still have the original CSV file but it is nearly useless for practical analysis:

• first row titles - columns 1, 3, 5 . . . have "Time" text; columns 2, 4, 6 . . . have data element text. This title text line is great and a significant improvement over the Graham Miniscannner
• second row - blank line
• subsequent rows - columns 1, 3, 5 ... have time values and columns 2, 4, 6 . . . have data values

So the first step is to transpose the data so the first column holds the title text in each row. Since I only need one time-stamp for each group of data, I removed all but the first. This leaves a spreadsheet that looks like the data table posted. But the order is as originally recorded.

So I sort and group the data so the module-pair voltages and internal resistence are together and a couple of other order changes to help make sense of the data. This is not how the data elements were originally read but it makes practical analysis possible.

Bob Wilson

 

Great charts!

I too have noticed intermittent data dropouts in some of my studies. I'll be starting a thread on MG1 shortly. What is disappointing is the vendor doesn't seem to have a clue about Prius values and seems distinctly uninterested in addressing my documented concerns.

I notice they provided a programming document for the ProLine and I'm thinking a Java based, Prius specific alternative might make a lot of sense. Java to be operating system independent but 'reverse engineer' the OBD protocol(s). This might give us some relief.

Bob Wilson