ScanGaugeII work on 2010?

Hi Frank,
Thank you for your response.

Following is a log using CANUSB on JP Prius.

[request]
t7E080221375555555555

[response]
t7E88100F6137785A82AE
&h0F means 15 bytes responses including "6137", then the valid number of data is 13 bytes. (A to M on Torque)

[request rest of frames]
t7E083000145555555555

[responses]
t7E88217FA08000000052
t7E8822D3000000000000

So, JP Prius is different from yours.

Ken@Japan

 

Hi Frank,

It is easier to see which bit changes in binary:

0 == &B0000 0000
4 == &B0000 0100
68 == &B0100 0100
70 == &B0100 0110

The bit that determines fuel cut is bit 6 so anything that is 2^6 = 64 and above means fuel cut.

In the Repair Manual, there are another 2 fuel cut description; Idle Fuel Cut & FC TAU which I believe is bit 1 and bit 0 respectively. Idle Fuel Cut = "ON" when throttle valve fully closed and engine speed over 2800 rpm. FC TAU is the fuel cut being performed during very light load to prevent incomplete engine combustion. Bit 2 could be Closed Throttle Position SW which is On when you fully release the accelerator pedal.

	Column 1
0	[TH]XGAUGE[/TH][TH]TXD[/TH][TH]RXF[/TH][TH]RXD[/TH][TH]MTH[/TH][TH]NAM[/TH][TH]Notes[/TH]
1	[TR][TD]Fuel Cut Condition[/TD][TD]07E02137[/TD][TD]010722E80322[/TD][TD]3101[/TD]
2	[TD]000100010000[/TD][TD1]FCc[/TD1][TD]Off/On[/TD][/TR]
3	[TR][TD]Closed Throttle Position SW[/TD][TD]07E02137[/TD][TD]010722E80322[/TD][TD]3501[/TD]
4	[TD]000100010000[/TD][TD1]CTP[/TD1][TD]Off/On[/TD][/TR]
5	[TR][TD]Idle Fuel Cut[/TD][TD]07E02137[/TD][TD]010722E80322[/TD][TD]3601[/TD]
6	[TD]000100010000[/TD][TD1]FCi[/TD1][TD]Off/On[/TD][/TR]
7	[TR][TD]FC TAU[/TD][TD]07E02137[/TD][TD]010722E80322[/TD][TD]3701[/TD]
8	[TD]000100010000[/TD][TD1]FCt[/TD1][TD]Off/On[/TD][/TR]

If you are referring to IG OFF Elapsed Time, it is usually consist of 2 bytes data. Have you checked how accurate is the 1 byte data?

Vincent

 

Actually the SGII average mpg is closer to calculated mpg than Prius displayed mpg. For my car displayed mpg is +5-6% high and SGII mpg is about -2% low. Today I watched your gph versus your Prius iMPG at 60 MPH (cruise) and these two matched more closely at 1.00@60 mpg.

SGII also has a standard XGauge GPH. I also watched GPH versus MPG and these two SGII numbers matched more closely at 1.00@60 mpg.

So it makes a little sense to me that the two Prius ECU parameters would match more closely and the two SGII parameters would match more closely since the two GPH calculations are derived from the iMpg parameters.

It appears to me that both GPH and gph are accurate when used with their respective iMPG parameters. gph works much better than GPH when displaying fuel cutoff. GPH seems to hesitate at about 0.25 GPH before finally dropping to 0.02. On the other hand gph follows the HSI and drops immediately to 0.00 gph when the ICE turns off.

I would still like to see someone with trend capability trend these parameters and gather more data for comparison.

 

Hi Vincent

I am glad you checked and refined my post. I use Excel to process ELM327 raw data so I'm more comfortable working with decimal values rather than binary. However I need (much, much) more time to look at my million of records and confirm your fuel cut assumption for idle and TAU conditions.

For the other parameter 7E0 2137 L, values range from &H00 to &HFC (decimal 252) It is a one byte data because it is not connected at all with 7E0 2137 K neither with 7E0 2137 MN which, by the way, are close to the odometer value (different and a bit larger than DTC Clear run distance).

You asked for accuracy and I can draw the relation of SYSTEM OFF Minutes Vs 7E0 2137 L Value for 379 readings. When I say SYSTEM OFF I mean car parked, system off, driver out, car locked. The curve is:



As you can see, accuracy for measuring 10min periods, the value of 7E0 2137 L is very accurate when you add 23.4 minutes up to 42 hours of SYSTEM OFF.

Big hugs from Frank

 

If you never disconnect Aux Battery cable since the collection of your car from your dealer, MN should be close to ODO. If I'm not wrong, this value should be Dist Batt Cable Disconnect. In my C, this value in Techstream is greater than my ODO which I suspect my dealer had reset my ODO before delivery.

Thank you for taking the time to plot the graph! Yes, it is accurate up to 42 hrs but why only 42 hrs? There are many times when people park their car for much longer time.

According to the RM for ZVW35 (can't find the max value in the ZVW30), the max value is 655350 mins. If it were a 1 byte data, then the multiplication factor would have to be 2570. OTOH, if it were 2 bytes data, e.g. KL, then a scale of 10 mins interval seems correct.

Vincent

 

Hi Vincent

Let's look at the 7E0 2137 readings of some points of my graph.



The readings for these points are:



As you can see, K remains zero in all readings. L rises from 48 (for 493minutes) to 252 maximum (2520 minutes = 42 hours) and then it does not change any more.

Big hugs from Frank

 

I'm a new owner of a 2013 PiP, and want to get my data! I didn't get the advanced, so I feel like all my stats are stuck inside the cars computers with no way to get them out (other than pen/paper). I guess I stupidly assumed there would be some easy way to export logs to a USB stick or something (I'm a computer geek).

I'm thinking about finding a bluetooth OBDII reader and hiding a low power computer somewhere in the car that would gather the data I want; then when it sees it is in my house (finds the Wifi access point) it would upload it to a database. I'm mostly interested in watching anything related to EV use vs. Gas use, kWH used, any charging info, etc.

Any suggestions on a good OBDII bluetooth device? This would be my first attempt to do anything with OBDII, but I can handle the computer side of things. Can anyone point me to a list of what data is available from this interface on the PiP specifically? Let me know if I'm going about this the wrong way or re-inventing the wheel. My main goal is external tracking; as I feel like I have plenty of information from the gauges while driving.

Hope I'm not off topic here. This is my first post; and I'm a VERY excited PiP owner, and new member of the community :-D

 

Thanks for posting the numbers. I also noticed TB2 to be higher by 5F (on android torque).

 

So.... Reverse Beep and seatbelt beeps are taken care of.

I saw this:

Current avg. trip MPG 00 800000000000 0000 000000000000 cfe Generic
current FE (same on AVG xgauge)

So the built in AVG gauge is correct? On a recent trip, once I turned the Prius off it said my mpg was 68mpg. The display for AVG on the ScanGauge II was something in the 30's. Motor size is set to 1.8. What am I missing?

Also, my fuel level's seem to swing by 1/2 gallon here and there, is that normal because of the bladder in the fuel tank?

Thanks!

 

There is no bladder in the 3rd Gen gas tanks.

Mike

 

The first tank mpg reading is bogus. After the next fillup follow the SGII instructions for entering info for fillup. Do not enter gallons the first time. After the first couple of fill ups the SG will learn the correct gallons used and then the mpg will be more accurate.

On mine the SGII is about 2% below calculated which is closer than the car's displayed mpg which is about 6% above calculated.

 

Hi Dravor,

There is no bladder. What you are seeing is the movement of the float inside the fuel sender gauge when cornering or driving on a steep slope. This same signal is also sent to the combination meter (fuel gauge bar graph). The difference is that the combination meter uses software application to suppress these deviations.

Vincent

 

Interesting. I'm looking forward to filling up to see what the ScanGauge registers. Doing the numbers I see now, either I did not fill up to the full 11.9 gallons previously, or something wacky is going on. Waiting to see what happens. I'm on the first blip below half way, and the scangauge says I have anywhere from 5.2 to 5.7 gallons left at around 320 miles into the tank. Even at 5.7 gallons left, at 320 miles into the tank it would give me about 51.61mpg, with my gauge showing 57.4. Typically I'm only off about 2-3 mg, so this would be the largest variance yet.

As the weather get's hotter and mpg goes down, does the variance between displayed and computed mpg get bigger as well?

Thanks!

 

BTW, fixed this. Somehow I missed the part on setting fuel to Hybrid, not Gas. I thought that setting was for Diesel/Gas only. That fixed it and mpg avg is now right.

Thanks!

 

Hello,

I am interested in seeing the current (amps) being supplied to the 12V battery by the system while the car is in Ready mode. I have an SGII and I have looked thru the following spreadsheet, but it's not obvious to me which X-Gauge to use.

Google Docs - Online documents, spreadsheets, presentations, surveys, file storage and more

TIA.

 

Here in the Northwest the best gas mileage is during the summer, not the winter. The mpg factory prius gauge is
usually off about 2.5 mpg in the summer, and about 3.5 mpg off in the winter. The scan gauge usually
under reads about 2 mpg. So if the scan gauge is reading 51 mpg I know I am getting much more than
that....

 

Hi srivenkat,

The Aux. battery does not have a current sensor and I've checked the Repair Manual and there is no PID for that. While the car is in Ready mode, all the current is supplied by DC-DC Converter. The DC-DC Converter get its supply from HV battery, MG1/Inverter(HV Charging) and/or MG2/Inverter(Regen). Part of this current is used for charging the Aux. battery and the rest to power the 12V accessories.

If you just want to know the current being supplied to the Aux. battery, you can use an Ammeter.

Vincent

 

I've got a question on C vs F temperature command strings.. In the spreadsheet, it says change the math string to 00010001ffd8 from 00090005ffd8 in order to get degrees Celsius, but this does not make sense..

The formula for converting between C and F is: F = (C * 9 / 5) + 32

The math string is supposed to be composed of 4 bytes of multiplier followed by 4 bytes of divisor and then 4 bytes of add/subtract, so in the 00090005ffd8 string, I see the multiply by 9 and the divide by 5, but why is the add/subtract value the same in both strings? Shouldn't there be a difference of 32 between them?

I believe the F math string is incorrect, and my basis for this is that the Scangauge built-in command for coolant temperature should match the temperature of all the engine components after everything has had a chance to cool off, so for example, the inverter temps and the MG temps should all be the same as the coolant temp after the car has been sitting for a number of hours. In my car, if I select metric units, I get a cWT reading: coolant temp in degrees C, and if I put in the strings for inverter and MG temps and put in the 00010001ffd8 string that the spreadsheet tells you to use for metric, I get readings that match the built-in cWT reported value, so I think the ffd8 offset is correct for Celsius values, but out by 32 degrees for Fahrenheit. Therefore, I believe the math string for Fahrenheit readings should actually be 00090005fff8 (%d8 + %20)..

Does this make sense?

 

Hexadecimal 0xffd8 is -40 in decimal. -40 is a magic number for temperatures - -40°C = -40°F. So I'm betting that many of the car's temperature sensors read 0 at -40; so the raw sensor number is °C above -40°C. Multiply by 9/5, and you get °F above -40°C (or above -40°F); so for either, you subtract 40, and you get degrees relative to 0.

Just as an example, say that the temperature of the coolant is 100°C/212°F. The sensor reading will be 140; the °C math is multiply by 1, divide by 1, and subtract 40, so you get 100°C. The °F math is multiply by 9 (1260), divide by 5 (252), and subtract 40 (212°F). Look, it's magic!

 

No.
The original math is correct.

We know the raw data has -40C offset, therefore the C display value is (raw value) - 40 (0xFFD8).
Then, the MTH for C display is 0001 0001 FFD8 (-40).

To convert the C display value to F display value is...
F = C * 9 / 5 + 32
C = raw - 40
F = (raw - 40) * 9 / 5 + 32
F = raw * 9 / 5 - 40 * 9 / 5 + 32
F = raw * 9 / 5 - 72 + 32
F = raw * 9 / 5 - 40

Then, the MTH for F display is 0009 0005 FFD8 (-40).

Ken@Japan