[inmn]

I have taken delivery of a new i30cw Diesel Auto (1.6 litre engine),in Victoria, Australia and have connected a Scangauge II to it (I have the SLX model - no trip computer).

The Scangauge II gives erratic readings:
LHK (litres per 100 km) - this should be the current fuel economy (i.e. average of last few seconds) - it alternates between 0 and what appears to be a correct reading. It sits on 0 for about 5-15 seconds and then about 5 seconds on a proper reading. Naturally this seriously impacts the AVG (average fuel economy - l/100km)

This is also occurring for:
LOD - engine Load & LPH - litres per hour.

All other gauge measurements, such as RPM, KPH CWT and MAP all show what appears to be correct measurements continuously
These other measurements DO NOT go to zero for a period before returning to a proper value the way it does for LOD, LPH and LHK).

    * I have tried 2 different fuel options "Diesel A" and "Diesel B"
    * I have tried different "CUTOFF" values and decided to set it to ZERO -> the TPS (Throttle Position Sensor) appears to be accurate, and gives a continuous correct value.

    * I have tried to force it to different modes and it doesn't work at all

    * I have tried setting "RATE" (i.e. sampling rate) to "SLOW" then "FAST" and "NORMAL"


I haven't adjusted the percentage parameter when using the "FILLUP" function, as I have only filled up the tank once. Should I go straight to -35% (as suggested by "ouri30" at: https://i30ownersclub.com/forum/index.php/topic,537.30.html on August 15, 2008).

I have also experienced the thud when the auto was downshifting as reported by user "Bluei30Crdi" regarding his experience with the ScanGaugeII (July 21, 2008)
see:
https://i30ownersclub.com/forum/index.php/topic,537.0.html

I am using what I assume to be the latest firmware version of ScanGauge II, version 3.17 as at July 9, 2010.

[Paolo5]

Hi inmn,

Congratulations on your new car!


I don't know if you have seen this re automatic i30 diesels:-

http://www.scangauge.com.au/support/CompatibleVehicles.shtml

and I don't know if there are incompatibility problems with the auto and the Scangauge 11 above and beyond the abrupt gear changes. Maybe the Australian distributor or Scangauge itself could clear this matter up for you.

I bought a new Scangauge 11 on 25-6-10 and fitted it to my manual diesel.

The Scangauge II gives erratic readings:
LHK (litres per 100 km) - this should be the current fuel economy (i.e. average of last few seconds) - it alternates between 0 and what appears to be a correct reading. It sits on 0 for about 5-15 seconds and then about 5 seconds on a proper reading. Naturally this seriously impacts the AVG (average fuel economy - l/100km) This is also occurring for:
LOD - engine Load & LPH - litres per hour.

 I don't have this problem with mine.

* I have tried 2 different fuel options "Diesel A" and "Diesel B"

I have mine set to "Diesel A"

* I have tried setting "RATE" (i.e. sampling rate) to "SLOW" then "FAST" and "NORMAL"

I have mine set to "FAST".

I am using what I assume to be the latest firmware version of ScanGauge II, version 3.17

Mine is the latest too.

Why don't you fillup and set the SG 11 to -35% at that point and see if things settle?
 
(I don't know what fuel tank capacity Ouri30 used when setting up his SG. Rumour has it that an i30tank will hold 62 litres filled to the brim, which is where I fill mine.) I set mine to 62 litres. I will find out at my next fillup how accurate the -35% is with 62 litres set as the tank's capacity with my SC11.

All the best in getting to the bottom of this. I am really happy with my SC11

Cheers,
Paolo5

[inmn]

I spoke to the Australian distributor and he specifically told me about the issue with the automatic transmission. I had hoped that because it was an earlier version of ScanGauge from nearly 2 years ago and that the i30 auto-diesel available in Australia might have had subtle updates that this issue would not re-occur. There was a promise of the 30-day money back guarantee which I will take up unless I can quickly find a solution.

I love the idea of the ScanGauge II device and want to see it working properly. I will try the -35% thing on the next fill up and see how it goes.

thanks for the reply.

[inmn]

I emailed the company I purchased if from and they in-turn emailed the manufacturers in the US.

They suggested doing a reset, and changing the "FUEL TYPE" to "GAS"  

seems very counter-intuitive, but I tried it and it appears to work. I had to set "CUTOFF" to zero as the LPH (litres per hour) and LHK (litres per 100km) where higher when I took my foot off the accelerator. Once I did that it gives continuous readings, that appear to correctly correspond to current fuel use (LPH and LHK). I also set "RATE" to "FAST"

I only took it on a 20km drive (in the country) gently rolling hills, I didn't get any thuds from the auto-transmission. There was hardly any flat section of road.

I won't have the car for a couple of days now, so I won't be able to do more testing. I would be more happy if I get to try it out over a range of different measurements (in the GAUGE function), for a longer drive, especially on some flat roads.

Also the LOD reading is still erratic, going from zero to a value around 70-80, but this is insignificant if all else is working. I also tried to set "FUEL" to "DIESEL A" and it operated as it did previously, with periods of Zero readings, changing "FUEL" back to "GAS" again fixed this.

all in all it appears to be pretty good, I just need to get it fully accurate and this will only happen after a few fill-ups.

It seems pretty counter-intuitive to set it to "gas", but it works much better. I am interested to know why selecting this as the fuel makes it work.

[Paolo5]

Hi inmn,
I too wonder why the new "gas" setting seems to have corrected things. For that matter, I wonder what the settings, Diesel a, Diesel b, Hybrid etc. actually do to the calibration of the SC and how they were ascertained in the software development process.

It is great that the auto-transmission "thud" also seems to have vanished. Did the Scangauge people say that this problem has been rectified for your application with the 3.17 software? If not, this thudding would be a dealbreaker for me with an auto i-30.

Good luck. Keep us informed....

On another SC note, I have lately setup a few new gauges (using the Xgauge facility) that I can monitor whilst driving.
*Litres used per day
*KM travelled per day
*Litres left in tank
*Time travelled on tank

I have said it before...what a great gizmo!

[inmn]

I had a longer drive later on (70km), which included some flat country roads. This time I noticed the issue of incorrect readings when taking my foot off the accelerator at over about 50 km/h. Under 50km/h LPH and LHK (litres per hour and litres per 100km) both go down when you take your foot off the pedal, but over about 50, it increases, showing for example higher fuel consumption rate when going down a hill than when traveling at steady speed on a flat section. Does anyone know how the "CUTOFF" function works? I have it at zero after changing it from the default (neither worked) should I try a much higher value. I tested the various other gauges, and only "LOD" engine load still gives erratic readings, but as I mentioned before, that doesn't concern me, all other gauges appear to be working correctly (except for the coasting issue for LPH and LPK). TPS (throttle position) appears to be very accurate, I think it is used for the "CUTOFF" function.

The "thud" in the transmission has not come back at all, which is very good news, but you never know, the situation could be different in suburban / peak hour stop-start driving. I live in the country so do hardly any suburban / peak-hour driving, except when I drive to Melbourne a couple of times a month.

Paolo5, I would be interested in the other gauges you have set up using the Xgauge facility, let us know what codes you need to set them up, and if anyone can tell me what the various "FUEL" settings actually do I would be very interested in an explanation.

[Paolo5]

Hi inmn,
If you refer to the small blue book that should have come with your SC entitled "Installation and Operation", the relevant section on the setting up of other gauges is outlined on pages 28 and 29. It will all make sense to you after you read it a few times.

Each gauge takes a minute or so to program once you figure out what you want to show up and what you will call it (so that you will recognise the 3-figure name once you are back in the GAUGE section).

For example, if you want to have a gauge that registers the Time travel Total on a Tank you need to need get into the XGauge section and allocate this new gauge a number between 1 and 24. Then press EDIT.
Then enter-
*54_ "and "OK" on the TXD screen (5 is for time and 4 is for Tank Trip)
*800000000000" and "OK" on the RXF screen (8 tells the SC that this is a Trip Gauge)
*and then give it a name eg. TTT
*hit the "SAVE" button.

Then (using the above example) when you are in the gauge section and you scroll down to TTT you will have a register of the Total Time that you have travelled on the current Tank.
It really is that simple.

All the best,
Paolo5

P.S. In my appplication, I didn't alter the Cutoff setting from the default.

[Lorian]

Shamlessly stolen:

"The CUTOFF was a last minute addition to the ScanGaugeII. Some vehicles will report when they shut off fuel flow during coasting with the engine in gear. The same signal also indicates when the vehicle is enriching the fuel mixture during hard acceleration. If the throttle position is below the CUTOFF value when this signal is received, the ScanGaugeII assumes it means 0 fuel flow. Above this it means enriched flow. Normally you should not have to change this. If your TPS is above this level when you are coasting with your foot off the accelerator, you would need to raise it. If you set it to 0, this detection is turned off."

It is described in the latest version of the handbook too IIRC.

[marvy]

I emailed the company I purchased if from and they in-turn emailed the manufacturers in the US.

They suggested doing a reset, and changing the "FUEL TYPE" to "GAS"  

seems very counter-intuitive, but I tried it and it appears to work. I had to set "CUTOFF" to zero as the LPH (litres per hour) and LHK (litres per 100km) where higher when I took my foot off the accelerator. Once I did that it gives continuous readings, that appear to correctly correspond to current fuel use (LPH and LHK). I also set "RATE" to "FAST"

I only took it on a 20km drive (in the country) gently rolling hills, I didn't get any thuds from the auto-transmission. There was hardly any flat section of road.

I won't have the car for a couple of days now, so I won't be able to do more testing. I would be more happy if I get to try it out over a range of different measurements (in the GAUGE function), for a longer drive, especially on some flat roads.

Also the LOD reading is still erratic, going from zero to a value around 70-80, but this is insignificant if all else is working. I also tried to set "FUEL" to "DIESEL A" and it operated as it did previously, with periods of Zero readings, changing "FUEL" back to "GAS" again fixed this.

all in all it appears to be pretty good, I just need to get it fully accurate and this will only happen after a few fill-ups.

It seems pretty counter-intuitive to set it to "gas", but it works much better. I am interested to know why selecting this as the fuel makes it work.

Hi Inim,

I have also mailed the manufacturer about the problem. Basically the "GAS" or "DieselA" or "DieselB" change the way the scangauge reads the fuel consumption. When it's set to "Diesel A", it uses the "LOD" data which is wrong when the A/C is off. Switching to GAS would most likely use another set of data which won't be as accurate as LOD if load was working right but should be better then nothing.

With respect to the clunk in the transmission, I am glad to hear that it's not happening... and here is why. The port that the scangauge plus into is basically the vehicle network. In the i30, all of the car components talk to each other over this vehicle network. This includes, the engine, the transmission, the instrumentation, alarm, ignition, traction control, ESP, air bags etc etc. If your getting clunks in your transmission, it would indicate to me that the scangauge is interfering with this vehicle network. This would be BAD in my book especially when you consider what else could be getting stuffed around that you don't know about!

[inmn]

The port that the scangauge plus into is basically the vehicle network. In the i30, all of the car components talk to each other over this vehicle network. This includes, the engine, the transmission, the instrumentation, alarm, ignition, traction control, ESP, air bags etc etc. If your getting clunks in your transmission, it would indicate to me that the scangauge is interfering with this vehicle network. This would be BAD in my book especially when you consider what else could be getting stuffed around that you don't know about!

Wouldn't that be the same for all modern cars?
I thought that the idea of the scangauge was that it is just a passive device that reads the signals. Obviously OBDII interface implementations differ slightly between car-makers and Scangauge has to try and cater for a wider coverage as possible. Perhaps there are other pins on the interface that do have an effect on various systems that are connected electronically. I don't know how many of the pins are actually used, but the socket does have quite a few.

[marvy]

Wouldn't that be the same for all modern cars?
I thought that the idea of the scangauge was that it is just a passive device that reads the signals. Obviously OBDII interface implementations differ slightly between car-makers and Scangauge has to try and cater for a wider coverage as possible. Perhaps there are other pins on the interface that do have an effect on various systems that are connected electronically. I don't know how many of the pins are actually used, but the socket does have quite a few.

The scangauge is not passive as it actually talks on the network. It sends a query to the ECU to get the information it needs. I am not saying that the scangauge will disrupt the network, it most cars it seems to get a long just fine with everything else. I am saying that if I had a car that the auto started going weird (limp home mode??) when the scangauge is plugged in, I would be worried. To me, it would indicate that the scangauge is disrupting the network somehow and this could be dangerous.

[marvy]

Also the LOD reading is still erratic, going from zero to a value around 70-80, but this is insignificant if all else is working. I also tried to set "FUEL" to "DIESEL A" and it operated as it did previously, with periods of Zero readings, changing "FUEL" back to "GAS" again fixed this.

Just a quick note, the load should drop to zero when ever you are coasting in gear and the engine is not at idle. This is because there is zero fuel flow so the LOD shows 0. When switching to "GAS" this doesn't happen which is wrong.

For fun, listen to your engine when you coast down a hill in gear, the familiar "diesel rattle" will stop as there is no fuel being combusted. Touching the throttle will start it up again instantly.

[inmn]

Just a quick note, the load should drop to zero when ever you are coasting in gear and the engine is not at idle. This is because there is zero fuel flow so the LOD shows 0. When switching to "GAS" this doesn't happen which is wrong.

Can anyone with a Scangauge that is working confirm this: Does it show 0 for LHK (Litres per 100km) or 9999 MPG  (or LPH or GPH at zero) when coasting in gear and engine is not at idle?

[Lorian]

Can anyone with a Scangauge that is working confirm this: Does it show 0 for LHK (Litres per 100km) or 9999 MPG  (or LPH or GPH at zero) when coasting in gear and engine is not at idle?

It does on mine. 9999MPG, its what I hope to see as much as possible. It works exactly as you'd expect it to. As soon as I accelrate it changes, and as soon as the engine hits idle (or close to it) it changes too. On engine-deceleration I always get 9999MPG.

Keep in mind I have a U2 engine which probably has later engine management code though, might not be relevant.

[Lorian]

I double checked my setting when I went out tonight. My engine type is set to "Diesela".

My cutoff is set to 24 which IIRC is the default, and works OK.

My scanguage firmware is 3.17

[inmn]

Thanks Lorian for letting me know that on coasting that no fuel is being consumed (unless at idle revs)

The specs for the 1.6 litre common rail turbo diesel for the Australian market is:
85 kW @ 4000 rpm 255 Nm @ 1900 – 2750 rpm
which I assume is the "U2" version of the engine. The build date of my car is mid-May 2010.

I would guess the issue is the automatic transmission, looking back on what Marvy said, I could speculate that there is a lot of communication, i.e.  signals to control the automatic transmission that ultimately interferes with ScanGauge II's operation in reporting instantaneous fuel consumption (i.e. LPH, GPH, LHK and MPG). Looks like most posters to the i30ownersclub forum are enthusiasts who don't mind changing their own gears because of the obvious benefits, it would probably have been worth it to pay for my wife to have a few lessons driving a manual car, the savings in term of up front costs and on-going fuel savings would have been worthwhile.

I have given up using "GAS" as the fuel, I tried the others as well (LPG an HYBRID), I was annoyed by the higher fuel consumption on coasting, and have reverted back to "Diesel A", even though you have periods of zero readings. When it is non-zero, it appears more accurate than the readings of the "GAS" mode. I do hope ScanGauge comes up with a fix in the next version.

Also as a reference, what LPH or GPH do you get at idle, i.e. for a fully warmed up engine, no headlights, no a/c, just a minimum of accessories running?

[Paolo5]

I just checked my CUTOFF setting and it is set to 10.

[Lorian]

Also as a reference, what LPH or GPH do you get at idle, i.e. for a fully warmed up engine, no headlights, no a/c, just a minimum of accessories running?

Its not somthing I focus on, so will have to check that for you later.
I think all i30's todate with the automatic gearbox are U rather than U2 spec engines. This might have changed recently, but I doubt it.

[Lorian]

I just checked my CUTOFF setting and it is set to 10.

According to other discussions on the wen It should be set to at least the the value of the throttle position sensor, when you are not pressing the pedal, plus 4. But like I said It works fine on mine set to 24.