Jump to content
SAU Community

Recommended Posts

Can the HKS take over O2 correction, using the factory fuel target table (because FCon won't let you enter a target table), with either a wideband or narrowband feedback?

You can set target AFR's with the Fcon and use the wideband input/parameters for O2 correction.

Won't stop the too rich/lean CELs though as the ecu will still receive the signal and crack the sads (not that it will affect the Fcon tune).

Ryan, if the light bothers you that much, remove the bulb and just buy a Cipher cable to check for CELs periodically.

Ryan, if the light bothers you that much, remove the bulb and just buy a Cipher cable to check for CELs periodically.

You want to see 'crack the shits' when he cuts the CEL signal wire. lol.

Take the bulb out and bypass it with a resistor. ;)

Because simply, its the best way for it to run in low load/idle areas of the map. Hot day, cold day, freezing - doesn't matter. Altitude - doesn't matter. It just corrects.

I would like to see what O2 functions the FCon has, and if they are useful. Thats all.

Meh, some scattered self tuning functions from what I have seen, not worth going down that route imo, it's mainly for dumb arse tuners to hack a tune out with before fine tuning from there.

Mine has bugger all dramas with different temps, as the tuner has set up the coolant temp and intake temp corrections fairly well. It is running a bit rich atm but that's due to me being a compulsive modifier, not the tune. ;)

Once set it shouldn't need o2 correction. I haven't run it for years.

You can do correction based on wideband in the fcon, might be worth trying just to see if it clears the code.

I don't see the issue Scotty. So you trust a 10 year old O2 sensor but not a brand new wideband?

And I thought F-Con was supposed to be the bees-knees with no CEL issues...(thought I read that somewhere a year ago).

I hope you get it where you are comfortable driving it around Ryan, CEL or not. Persistance is the key; and if you do find a good solution (with no CEL) you will be a forum hero ;) .

You can set target AFR's with the Fcon and use the wideband input/parameters for O2 correction.

Won't stop the too rich/lean CELs though as the ecu will still receive the signal and crack the sads (not that it will affect the Fcon tune).

I wonder how close the O2 correction on the F-con would be to stock ECU correction? As in, would the ECU see something good/close enough?

Ryan, if the light bothers you that much, remove the bulb and just buy a Cipher cable to check for CELs periodically.

I'll probably end up with the Cipher cable in the new year anyway, easier to sort out than a code reader and more versatile. I just don't want the light firing and masking another issue.

Because simply, its the best way for it to run in low load/idle areas of the map. Hot day, cold day, freezing - doesn't matter. Altitude - doesn't matter. It just corrects.

I would like to see what O2 functions the FCon has, and if they are useful. Thats all.

Target AFR seems to be useful, and easy to implement (which I think was what Scotty was talking about in a backhanded kind of way :P). Whether it'll replicate the stock ECU in the same kind of way I don't know, but I doubt it.

And I thought F-Con was supposed to be the bees-knees with no CEL issues...(thought I read that somewhere a year ago).

I hope you get it where you are comfortable driving it around Ryan, CEL or not. Persistance is the key; and if you do find a good solution (with no CEL) you will be a forum hero ;) .

Yeah its pretty good Leon, more research to clear random codes is required, but other than that it's good. 8k rev limit is a bit high for my liking, but other than that it's got a fair bit of shove. Be interesting to see what it does on the dyno with Scotty's upgraded spring, holding 15PSI not 7...

I wonder how close the O2 correction on the F-con would be to stock ECU correction? As in, would the ECU see something good/close enough?

Target AFR seems to be useful, and easy to implement (which I think was what Scotty was talking about in a backhanded kind of way :P). Whether it'll replicate the stock ECU in the same kind of way I don't know, but I doubt it.

I think you need to research more about o2 feedback.

The widebands play up constantly and require resetting, recal and the sensors require regular replacement. They are in no way reliable enough to use for auto afr targeting, unless you have some way of proving the sensor is accurate, like running twin sensors through some comparison circuit. It's not something a tuner would like to setup either. (hopefully you already know that from speaking to your tuner.)

The Fcon would try and hold a set AFR, as in 14.7 or whatever you target it to hold. The factory ecu wants to see 14 then 15.5, cycling every few seconds. They are in no way similar. Geddit?

Geddit. I still think there must be some way of looping the signal though...

In other news, actuator turned up today Scott, thanks! Will try and fit tonight.

Mmm it needs to go in to stop the boost spiking. Probably better to just put it in and drive it carefully than let the turbo spike to 20PSI for another couple of weeks. Especially when I'm on holidays and will be using it.

Yeah its pretty good Leon, more research to clear random codes is required, but other than that it's good. 8k rev limit is a bit high for my liking, but other than that it's got a fair bit of shove. Be interesting to see what it does on the dyno with Scotty's upgraded spring, holding 15PSI not 7...

8K a bit high? (understatement much, lol). Is that an easy figure for your tuner to set?

I would think you'd have about 2,500 rpm of 'not a lot happening' with the standard turbo.

8k is the lowest rev limit on an Fcon V-Pro

:O Ok-doky then. I guess that's why it's called the 'Pro'.

Is 8K safe for an unopened VQ25? Or should I say, safe for an extended operating life?

I still hit the limiter thanks to the auto not shifting at wot, soft limit is set at 7k, hard limit is 7,600. I don't know what Cam is on about... possibly a hard cut backup?

8k is the lowest rev limit on an Fcon V-Pro

mine shifts at 7200rpm consistantly dont hit the cut....... not sure what the cut is though might have to try that LOL

Installed the rear sway bar and raised the front by 75mm (thank god.. lol)

Ran out of time to do the front sway bar links, so I'll ask the shop to do whilst they push in the bushes tomorrow.

Got home late thanks to the wonderful folks at Adelaide Metro but still managed to remove the top half of the intake, jack the car up and onto jack stands, remove the front wheels so I can put the good ones back on and drain all the coolant out.

Hopefully I'll get home early tomorrow and get the radiator out. Think there should be more room for the thermostat once the radiator and clutch fan are out.

The coolant thermostat? It's just three bolts, no need to remove the radiator or fan.

With the o2 issue, I seem to remember Jaycar having a kit to combat this very problem. Perhaps you could look into it?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



  • Similar Content

  • Latest Posts

    • Yeah, that's fine**. But the numbers you came up with are just wrong. Try it for yourself. Put in any voltage from the possible range and see what result you get. You get nonsense. ** When I say "fine", I mean, it's still shit. The very simple linear formula (slope & intercept) is shit for a sensor with a non-linear response. This is the curve, from your data above. Look at the CURVE! It's only really linear between about 30 and 90 °C. And if you used only that range to define a curve, it would be great. But you would go more and more wrong as you went to higher temps. And that is why the slope & intercept found when you use 50 and 150 as the end points is so bad halfway between those points. The real curve is a long way below the linear curve which just zips straight between the end points, like this one. You could probably use the same slope and a lower intercept, to move that straight line down, and spread the error out. But you would 5-10°C off in a lot of places. You'd need to say what temperature range you really wanted to be most right - say, 100 to 130, and plop the line closest to teh real curve in that region, which would make it quite wrong down at the lower temperatures. Let me just say that HPTuners are not being realistic in only allowing for a simple linear curve. 
    • I feel I should re-iterate. The above picture is the only option available in the software and the blurb from HP Tuners I quoted earlier is the only way to add data to it and that's the description they offer as to how to figure it out. The only fields available is the blank box after (Input/ ) and the box right before = Output. Those are the only numbers that can be entered.
    • No, your formula is arse backwards. Mine is totally different to yours, and is the one I said was bang on at 50 and 150. I'll put your data into Excel (actually it already is, chart it and fit a linear fit to it, aiming to make it evenly wrong across the whole span. But not now. Other things to do first.
    • God damnit. The only option I actually have in the software is the one that is screenshotted. I am glad that I at least got it right... for those two points. Would it actually change anything if I chose/used 80C and 120C as the two points instead? My brain wants to imagine the formula put into HPtuners would be the same equation, otherwise none of this makes sense to me, unless: 1) The formula you put into VCM Scanner/HPTuners is always linear 2) The two points/input pairs are only arbitrary to choose (as the documentation implies) IF the actual scaling of the sensor is linear. then 3) If the scaling is not linear, the two points you choose matter a great deal, because the formula will draw a line between those two points only.
    • Nah, that is hella wrong. If I do a simple linear between 150°C (0.407v) and 50°C (2.98v) I get the formula Temperature = -38.8651*voltage + 165.8181 It is perfectly correct at 50 and 150, but it is as much as 20° out in the region of 110°C, because the actual data is significantly non-linear there. It is no more than 4° out down at the lowest temperatures, but is is seriously shit almost everywhere. I cannot believe that the instruction is to do a 2 point linear fit. I would say the method I used previously would have to be better.
×
×
  • Create New...