club.liberty.asn.au

alexeiwoody wrote:If an auto gear box is good enough for Pagani and Ferrari - then it's good enough for me

I love it Alexei!!

If only our autos changed gears like the ferrari and pagani

peadya100 wrote:

alexeiwoody wrote:If an auto gear box is good enough for Pagani and Ferrari - then it's good enough for me

I love it Alexei!!

If only our autos changed gears like the ferrari and pagani

Haha thanks Adam I was partly joking, obviously the ferrari gearboxes are still a heaven and earth difference, but I feel our boxes have also come a long way.

And I know a lot of us auto owners get pretty sick of having to defend our choice (sometimes it wasn't even a choice ), when in reality there's not much of a difference anymore

To answer your question about safe tuning parameters go to romraider.com and read the intro/walkthroughs there, all about scoobaru tuning. If you have even more time, check out Bad Noodle's guide to tuning. That will give you a general idea of how to tune and what the process is like

peadya100 wrote:Not sure if this is the right thread for it, but youve mentioned a few times Ben that you have personal targets of what you consider safe tune levels. I know you said our tuners should be working to those but if we're doing all this logging and monitoring, we should probably have a basic idea of what some safe levels are. Ive tried searching it a few times and failed, so if there is a thread on this already im sorry but cant find it

Surely a question worthy of its own thread!
It was covered in the epic VF46 vs VF52 thread, IIRC.
Every tune I've had has been targeted towards drivability and reliability, so the tuner was tuning for safe AFR's with plenty of headroom...

Basically the limitations are:
- the tuning strategy - how much headroom is built into the tune to keep things safe and sustainable.
- tuned for boost or timing or a combination?

- what sustained boost pressure at which the stock heads are known to lift = >21psi

- the actual or estimated turbo compressor map which describes the actual efficiency envelope of the turbo, e.g. pushed beyond the surge line it making more hot air (detonation promoting) than productive boost.

- the octane rating/detonation resistance of the fuel/fuel combination being used.

- the efficiency of the stock fuel system: pump lines injectors (maybe a safe 180 kw atw)

- the efficiency of the induction and exhaust.

I'm sure some experts can correct me if I misconstrued or missed anything.

Yeah i figured it definitely would have been covered somewhere. I can find the VF46 - VF52 thread.. i was in that one at some stage.. thanks Ben!!

For me personally, i want to focus on monitoring rather than tuning (god knows id stuff that up if i tried it).. so i just want to determine the levels im willing to get tuned to, and convey that to my tuner. And then keep an eye on things to make sure everything stays to those levels

Alexei, i knew you were joking haha
I know owning an auto opens us to ridicule, but as you said sometimes its just not by choice, and for me this being my first auto, living in sydney i just couldnt handle driving manuals in this traffic anymore... secretly i would love another manual though

Hi there mate,

Thanks for the useful info.

I have configured my laptop to log the following values as suggested in your post:

Logging Parameters:
From Torqued Performance:
A/F Correction #1(%)
A/F Learning #1(%)
A/F Sensor #1(AFR)
Engine Load (g/rev)
Engine Speed
Feedback Knock Correction
Fine Learning Knock Correction
IAM
Ignition Total Timing
Injector Duty Cycle
Intake Air Temperature
Manifold Absolute Pressure (PSI)
Manifold Relative Pressure(corrected)(PSI)
Mass Airflow (g/s)
Mass Airflow Sensor Voltage
Throttle Opening Angle(%)
Vehicle Speed (mph)
Optional (but mandatory for health check):
VVT angles (L&R)

VVT specific parameters:
Engine Speed
Vehicle Speed (mph)
VVT angles (L&R)
OCV duty (L&R)
OCV current (L&R)

Is it possible for you to give us an indication on what the max and min values should be for the above mentioned parameters so i get an idea on what's normal and with in limits?

Cheers,

Ras

As usual correct me if I'm wrong here but... It's more for your tuners use, to amend or revise your tune.
For a quick health check, Learning View is useful.
If anomalies are prevalent then peeping the log for certain parameters would be the go.

But IAM should be at 1 (for postFL at least)
VVT angles matching or close to matching across the rev range.
Learnt values not maxed out.

I'm sure our learned members can advise

New info added: correct me if I'm wrong folks

ECU Reset Info:
ECU resetting how to basic mode: remove the battery negative terminal. Pump the brake pedal until the brake lights are extinguished, so eg if the handbrake is on: no brake light on the dash or tail lights.
ECU resetting how to advanced mode:: use an OBDII adapter and app, eg Torque App or Tactrix with Learning View or RomRaider. This is preferable because one can check for any stored diagnostic codes.

ECU resetting when to: whenever you have made a mod that will affect the learnt parameters in your tune.
Examples: changed panel filter type, changed to heavier oil, changed OCV soilenoids, cleaned filthy MAF.
Some cars require an ECU reset after flashing a tune, you can check this by taking a learning view after reflashing.
No learnt parameters equals a reset ECU.

ECU resetting when NOT to: When you have a CEL and no method to read the code. Usually if you have a severe-issue CEL, the car will stay in its limp home mode. Some less severe CELs will reset themselves after a period of time.
If you have a CEL, check it ASAP with an OBDII adapter of some description or find a member or mechanic who can.

After an ECU reset: drive the car gently, off boost, with a mix of traffic and freeway if possible. the the concensus seems to be that 20-30 minutes is enough time for the relearning to become established.

Great, well explained info BBB.
Thanks heaps.

I'm going to update the FAQ soon with a section discussing Tune Scope and Intent for members trying to decide how, what or who to get tuned by.
Let me know if you have any suggestions.

Updated again!
LMK if any info needs clarification or is bogus.
Next up:
Subaru Stutter & Hesitation to be added to issues.
Diagnosis strategy for issues to be explored.

Added a juicy quote from dr20t as its required reading

FYI from Matt: Subaru pre-Can ECUflash procedure (this one for an SG9 Foz) will update with the postFL procedure which is much simpler...

Reflash procedure is similar to yours
Connect green flash connectors under the dash, above the brake pedal(may be hidden)
Turn Ignition to ON and you will hear the radiator fans cycling ON/OFF which confirms the ECU is in flash mode
Test Write to ECU, confirm the first 2 YES/NO's are a YES
Once Test Write is OK, flash on new tune.

Here is the weird bit on this ECU, turn off ignition once new tune is on and safely flashed etc
Turn Ignition back to ON position
Connect with LV to read the ECU and you will notice it has not reset
Reset the ECU
Turn Ign OFF
wait 30 seconds
Turn Ignition back to ON position
Coneect with LV and confirm the LV data has now reset.
Start car
Let it idle for 60 seconds before driving.

^ don't forget to disconnect green flash connectors before driving (not stated in steps above). My understanding is car would be in limp mode if driven with them connected?

Indeed and that would be colossally irritating too

Just wanted to confirm the flash procedure for an 2008 3.0R-B definitely doesn't need any flash connectors? Just the Tactrix 2.0 and IGN on?

Trying to flash a new rom to my car and keep getting the 'Interface close' error. Using ECUFlash v1.44.3721. I can read/log the ECU no problems, just unable to flash to it.

[22:15:54.695] D2UJ001T (217 tables) inheriting 32BITBASE (893 tables)</p>
[22:15:54.726] 1048576 byte image read.</p>
[22:15:54.758] using metadata XML ID D2UJ001T from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/subaru/Liberty 3.0R/D2UJ001T 2008 ADM Liberty 3.0R-B AT.xml</p>
which inherits XML ID 32BITBASE from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/subaru/Bases/32BITBASE.xml</p>
[22:15:54.758] ---notes---</p>
2012/11/30 [Tactrix] Experimental definition from RomRaider.</p>
2012/12/05 [Tactrix] Visually examined tables for obvious errors, but no in-car verification has been done. Standardized file name.</p>
[22:16:32.993] J2534 API Version: 04.04</p>
[22:16:32.993] J2534 DLL Version: 1.00.3721 Jan 9 2013 17:24:59</p>
[22:16:32.993] Device Firmware Version: 1.12.3688</p>
[22:16:32.993] Device Serial Number: TAxwh0Vp</p>
[22:16:39.952] kernel get version</p>
[22:16:40.155] interface close</p>