ScanGaugeII work on 2010?

Don't see any reason why not. You get to choose a 3 character designator for each XGauge you create, if you use a 2 or 3 for the generation you will still have two characters for the gauge name. Or you could make gen2 lower case and gen3 uppercase then you could use all 3 characters for the gauge name.

 

Thanks Tumbleweed. I particularly like your lower case/upper case designation idea (no wasted characters that way). Since I am new to ScanGuage II wondered if there is any risk to using the XGauges that are listed on ScanGauge's web page. There are eight listed for Gen II and twenty seven for Gen III , along with a footnote stating that credit for these goes to members of Prius Chat. I'm certain that experimental codes do carry a degree of risk, but do these particular XGauges carry any risk in causing damage to Gen II or Gen II vehicles?
Asking because I'd rather not take the chance if any of these can cause any problems. Thanks.

Regards,
Dubby

 

All of the ones I use come directly from Adrian Black's spread sheet: https://spreadsheets.google.com/ccc?key=0AiHL0r_2nhUEdF9lVVBxOVNoN3Zva3E0NmdZTUR1eVE&hl=en#gid=5

The spread sheet is for Gen 3, I have not used a ScanGauge for Gen2. I have not had any problems with any of the ones on the spread sheet. I do, however, double check all of the data after I enter it just to be sure I haven't made an error. I don't remember any one reporting an error that caused a problem so I think it's pretty safe.

 

Thanks Vincent! I had created a few of these a little while ago but was waiting for the multi-frame support to be released before updating the spreadsheet. Now we have confirmation it's working on 4.05 I will add them to the sheet.

I wonder if ICE temp is actually the engine block's temperature versus coolant temp?

 

Wow, so 4.05 now has multi-frame support!? I guess I will send in mine to have it upgraded for $25.

 

Spiderman,

Yes, Vincent and Adrian helped me with trying this out on mine. It is interesting to see the HV battery voltage and especially the after boost voltage. It is just as I have read Ken in Japan explain about the MG1 and MG2 voltages, either 500 or 650 volts under different circumstances.

Quite interesting. Now that we know the 4.05 supports multi-frame it would be worth the upgrade.

Dwight

Dwight

 

Hey guys, I added the multiframe XGUAGEs to the spreadsheet along with a few more generic OBD-II ones which may prove interesting. (All untested by me at this point)

(See changelog on the spreadsheet)

https://spreadsheets.google.com/spr...2nhUEdF9lVVBxOVNoN3Zva3E0NmdZTUR1eVE&hl=en_US

 

Adrian,

I tested the engine temperature, etf, that Vincent listed in his spreadsheet. It appears to be a different temperature than the existing coolant temp, fWT. At times, there can be as much as 2 to 3 degrees difference in the two reading when increasing or decreasing from the 195 when the ICE is running continuously. Once up to temp they both read 195.

I also tested one of the Battery temperature sensors, B1F, and this works fine. It is very close to the BtT xgauge but not the same.

Thanks.

Dwight

 

I believe it should be the engine coolant temp. The ZVW35 has some common PIDs with ZVW30.

http://priuschat.com/forums/gen-iii...ion/63088-2010-shop-manual-8.html#post1337998

Repair Manual -> Engine / Hybrid System -> SFI System -> Data List / Active Test.

The maths seems different, so pls help to verify.

Vincent

 

BtT is actually measuring the temp of air entering the HV Bty and B1F is the temp of the sensor placed on top of the bty module. From my observation on Gen1, BtT is usually at a lower temp than all the sensors. The sensor farthest away from BtT will have the highest temp of all the sensors.

Vincent

 

Hi Adrian,

BT1 is at the 1st frame as BtT so don't require 4.05 firmware.

I think BPL is the same as SoC, pls chk. The use of remaining life may confuse with the lifespan of the battery, IMHO.

Regarding the individual wheel speed, have you look at the ABS ECU? There are 2 likely PIDs, 03h or 62h.

	Column 1	Column 2	Column 3	Column 4	Column 5	Column 6	Column 7
0	XGauge	TXD	RXF	RXD	MTH	NAM	Notes
1	Front Right wheel speed	07B02103	02B804610503	2808	?		MPH
2	Front Right wheel speed	07B02162	02B804610562	2808	?		MPH

Vincent

 

I suggest you send your inquiry to Linear Logic first, they might give you a free upgrade! Bob Wilson and cwerdna get theirs upgraded FOC.

Vincent

 

Adrian/Vincent, does the new SG firmware also allow changing the headlight auto-off setting, or does that require something different from the multi-frame support?

 

Hi macman408,

It is different from multi-frame since the Protocol Control Information + Data are less than 8 bytes.

PCI = 06 (not shown)
Data = 3B 15 00 00 00 00

I think there are 2 problems:

1) TXD can only take up to 7 bytes, 07 50 40 3B 15 00 00.

2) To save user the trouble of entering the PCI byte, SGII will automatically insert it for you based on your TXD data. So, even if TXD can be extended to accept 2 more bytes, the Identifier would still be wrong.

07 50 07 40 3B 15 00 00 00 00 => 7 bytes Data

The correct msg. should look like this:

07 50 40 06 3B 15 00 00 00 00 => 6 bytes Data

I suspect 750 is the Gateway ECU (?) and 40 is the Body ECU (?).

It is unlikely for LL to change the algorithm to allow manual entering of PCI as that would mean all previous Xgauge will have to be re-coded. So it seems Techstream is the only way to do it.

Vincent

 

I agree that 750 is the Gateway and 40 is the Body. 40 is the Gen2 Body address on the KWP (SIL) bus, and I guess they converted to CAN usage by using the gateway.

The ELM would appear to have the same problem with devices addressed via the gateway.

 

Vincent,

I configured the other two battery temperature sensors last night. Driving to work this morning, I saw the following:

BtT = 85 F
B1T = 95 F
B2T = 100F
B3T = 95 F

It looks like the B2T is the highest reading.

Dwight

 

Vincent,

Out of curiosity as to where the three temperature sensors were mounted on the battery, I looked it up in the Gen III Repair Manual. They do not show the sensors in the drawings but they do show up in the electrical diagram for the battery. It shows three sensors, one for inlet air temp and only two others for battery temps.

B1F and B3F seem to report the same temp or maybe one degree difference. B2F is normally 5 to 10 degrees higher than 1 or 3.

The BtT, which you said was the inlet air temp from the blower motor, is usually about 5 to 10 degrees lower than B1F or B3F which would make sense.

Any ideas?

Dwight

 

I don't have the Gen III Repair Manual but the NCF someone posted did show the sensors.



I don't know whether B2T should be the highest temp. My Gen I is usually B1T the highest and B4T the lowest. I suggest you check with another Gen III user.

Vincent

 

Vincent,

I went back and looked at the overall electrical drawing for the 2010 Prius. It shows four thermistors labeled TC0, TB0, TB1 and TB2. They are not identified as to their function.

I went back to the Repair Manual electrical drawing for the HV battery and it has these labeled:

TC0 = Intake Air Temperature Sensor
TB0 = Battery Temperature Sensor
TB2 = Battery Temperature Sensor

I noticed for the first time that there is a dotted line between TB0 and TB2 meaning that TB1 is not shown for simplicity. So there are three battery temperature sensors as you stated.

I will wait for another Gen III owner to list their readings for comparison.

Thanks,

Dwight

 

From the spreadsheet, most of the PIDs for HV CPU seems to be from 61h to 98h. I believe there are still a lot of PIDs not discovered yet. If you can get me the PID maps, I can help to generate more PIDs to test.

	Column 1	Column 2	Column 3	Column 4	Column 5	Column 6	Column 7
0	XGauge	TXD	RXF	RXD	MTH	NAM	Notes
1	PID map for Block 60h (1st word)	07E22160	02EA14610560	2810	000100010000	601	Hex.
2	PID map for Block 60h (2nd word)	07E22160	02EA14610560	3810	000100010000	602	Hex.
3	PID map for Block 80h (1st word)	07E22180	02EA14610580	2810	000100010000	801	Hex.
4	PID map for Block 80h (2nd word)	07E22180	02EA14610580	3810	000100010000	802	Hex.

Vincent