Disable high Rev cold start

[Andrew025]

Those of you getting the P050B: in the same/next drive cycle, does it feel like your car is sluggish?
I've noticed consistently after getting the code my car does not accelerate as quickly, even at WOT.
After a drive cycle or two it's back to normal.

If I disable the P050B DTC, would this still happen? If I disable it, does the system still recognize the "fault" but just doesn't generate the code or will it ignore any apparent fault related to that code completely?

[steve99]

Originally Posted by Andrew025

Those of you getting the P050B: in the same/next drive cycle, does it feel like your car is sluggish?
I've noticed consistently after getting the code my car does not accelerate as quickly, even at WOT.
After a drive cycle or two it's back to normal.

If I disable the P050B DTC, would this still happen? If I disable it, does the system still recognize the "fault" but just doesn't generate the code or will it ignore any apparent fault related to that code completely?

Disabling the code should stop the code being logged, stop the cel light and stop any action the ecu may take as a result of the code.

[acj47]

Originally Posted by Foobar

I disabled the DTC for P050B - not sure if I needed to do that one.

I can confirm that disabling this DTC is required, even with editing row 1/2 of the MAF correction tables.

[mid_life_crisis]

Originally Posted by acj47

Thanks - just figured that out. My problem was this tidbit of information: Why is my Tune Calibration ID different from my stock ROM or in OFT/OFM...OFT tunes are generally based on the latest ROM revision for your ROM type...For USA/Canada type = C eg ZA1JB01C...2.0X tunes based on B01 revision

So once I added the two parts of code from the B01 file https://raw.githubusercontent.com/TD...R_ZA1JB01C.xml I then opened up in RomRaider and: success!

Thanks to all who helped!

I get nonsense tables when I try this. Do these tables exist in the definition for automatics? I tried changing the filename to a "D" from a "C" but get a file does not exist message when I tried to download it.

[steve99]

Originally Posted by mid_life_crisis

I get nonsense tables when I try this. Do these tables exist in the definition for automatics? I tried changing the filename to a "D" from a "C" but get a file does not exist message when I tried to download it.

dude cease what you are doing - bricked ecu will result

If you are editing an OFT Tune ALWAYS use the Romraider Definitions provided by the OFT guys on the OFT downloads site ,and you need to use the definitions for your specific ROM type and OFT Tune version. Definitions for V1.5 and V2 OFT tunes are different.
DO NOT use Romraider Definitions from the Github site to edit OFT tunes they are different to the definition on the OFT site.


TIPS on Editing your tunes with RomRaider
http://www.ft86club.com/forums/showthread.php?t=79152

[mid_life_crisis]

Originally Posted by steve99

dude cease what you are doing - bricked ecu will result

If you are editing an OFT Tune ALWAYS use the Romraider Definitions provided by the OFT guys on the OFT downloads site ,and you need to use the definitions for your specific ROM type and OFT Tune version. Definitions for V1.5 and V2 OFT tunes are different.
DO NOT use Romraider Definitions from the Github site to edit OFT tunes they are different to the definition on the OFT site.


TIPS on Editing your tunes with RomRaider
http://www.ft86club.com/forums/showthread.php?t=79152

I copied & pasted the two definitions into the OFT supplied file definitions. When I opened the tune in Romraider the values made no sense. I didn't edit the definition, I edited the download link trying to get one for an automatic that I could copy the two table definitions from, but that didn't work. I'm just trying to add those two tables.

[steve99]

Originally Posted by mid_life_crisis

I copied & pasted the two definitions into the OFT supplied file definitions. When I opened the tune in Romraider the values made no sense. I didn't edit the definition, I edited the download link trying to get one for an automatic that I could copy the two table definitions from, but that didn't work. I'm just trying to add those two tables.

Ok but tread carefully as what you are doing it is verry easy to make an error and mess things up.

the oft defs dont have the maf after start tables in the definitions for roms of any series C D ect.

but the romraider defs do

you need to know your original calid and the cald of your tuned rom structure

to be sure you need a hex editor and search your OFT rom for calid start characters ZA1J their will be three instances first 2 are your original calid third is the actuall calid and structure of rom. Some oft roms are calid hacked some are not, you need to work out what your dealing with. If all three are not same your dealing with a calid hacked rom.

This is a dangereous proceedure , understand what you are doing and be very careful and check your work else ecu will be bricked.

modifying calid or altering defs or using incorrect defs can very easily lead to a bricked ecu.

four guys i know of have bricked ecu doing one of the things above

it can be done but check and re check your work.

once you know what the real structure of the oft rom is say is a B01D then you can grab the B01D romraider def and then change the internal calid to what your original calid is example A01D but you must be sure of both your original calid and what the real structure of the OFT rom is , if in doubt give it a miss as their is no second chance. You will then be able to open your oft rom with your hacked definition that contains the maf after start tables.

alternativly you can do what the other guys did and copy the xml code into your oft def but you stil need to copy this code from the correct romraider def for the structure of your oft rom whick may be different from the file name. you cannot use their examples or xml code as they are on different roms, every rom is dofferent B01C tables sre not in same location as B01D.

again it dangereous territory and mistakes will brick your ecu and no one wants to see that


merry christmas

[mid_life_crisis]

Originally Posted by steve99

Ok but tread carefully as what you are doing it is verry easy to make an error and mess things up.

the oft defs dont have the maf after start tables in the definitions for roms of any series C D ect.

but the romraider defs do

you need to know your original calid and the cald of your tuned rom structure

to be sure you need a hex editor and search your OFT rom for calid start characters ZA1J their will be three instances first 2 are your original calid third is the actuall calid and structure of rom. Some oft roms are calid hacked some are not, you need to work out what your dealing with. If all three are not same your dealing with a calid hacked rom.

This is a dangereous proceedure , understand what you are doing and be very careful and check your work else ecu will be bricked.

modifying calid or altering defs or using incorrect defs can very easily lead to a bricked ecu.

four guys i know of have bricked ecu doing one of the things above

it can be done but check and re check your work.

once you know what the real structure of the oft rom is say is a B01D then you can grab the B01D romraider def and then change the internal calid to what your original calid is example A01D but you must be sure of both your original calid and what the real structure of the OFT rom is , if in doubt give it a miss as their is no second chance. You will then be able to open your oft rom with your hacked definition that contains the maf after start tables.

alternativly you can do what the other guys did and copy the xml code into your oft def but you stil need to copy this code from the correct romraider def for the structure of your oft rom whick may be different from the file name. you cannot use their examples or xml code as they are on different roms, every rom is dofferent B01C tables sre not in same location as B01D.

again it dangereous territory and mistakes will brick your ecu and no one wants to see that


merry christmas

I was trying to do that last bit but couldn't find code that worked.
Oh well.

[Tromatic]

I set mine to -8.

Car reported it was 48F out, first start of the day:

From start to end of the "noise": 35 seconds.

From end of the "noise" to reduction to normal idle: 1 minute 15 seconds.

Time from start to the temp reaching "C" (about 130F according to Carista): 4 min 16 seconds. I typically wait for the temp to reach "C" before I move.

I found the timing-induced noise to be greatly reduced at the back of the car, by half at least by as measured by ear.

Don't know why people are complaining about warm-up time.

[elBarto]

Does anyone know what the "Catalyst Warm up Idle" and "non idle" tables are for?



Those are changed from stock, but haven't found out what they do exactly.

[StormMcCloud]

I've literally got no idea what any of this means. Is there any way for you guys to just give us a stage 2 UEL 93 tune with a lowered cold start? The way it is now is way too loud and none of this stuff makes any sense to me.

[Dammod]

Hey guys,

FYI:
Just another way to disable the loud cold start that doesn't involve editing the map:

Originally Posted by Dammod

Hey peeps,

Just a quick tip I thought I would share in-case you didn't know.

I never like starting my car "normally" after it has been standing for a few days. Due to my working environment, the BRZ sometimes stands for a few days depending on how busy I am.

The following procedure will allow the car to crank for however long you want without starting.
It will also stop the car from having that obnoxiously loud - if you have an exhaust - (and sometimes cool) high idle which is primarily used for emissions purposes to warm the cat up.

Step by step:
1. Have your keys in the car and be seated in the drivers seat (obviously).
2. Put your clutch and accelerator pedal to the floor and hold them there.
3. Hold the "Stop Start" button for however long you want the car to crank without starting.
4. Let go of the "Stop Start" button and then the accelerator and clutch.
5. Start the car normally: Clutch in and press "Stop Start"

NOTE: I have not tried this with a "standard" spec non-key-less entry car.
EDIT: Works with STD spec 86 too! (Thanks @Scarl3t !)

Benefits: The longer your car has been standing, the more oil will drain to the sump and away from the components that need it. Depending on how long the car has been standing for, a few revolutions are made with inadequate amounts of lubrication.
By cranking you car for a few seconds, you will get the oil circulating first.
Engine builders usually crank a car a few times before starting a new engine for the first time. In the aeromotive industry as well, it is procedure to crank the engine for x amount of seconds before ignition.

We enable this feature on most cars, especially race cars which tend to stand for a while between races.

The BRZ/86 has this feature build in and already enabled luckily.

http://www.ft86club.com/forums/showp...53&postcount=1

Regards,
Damien

[steve99]

Originally Posted by StormMcCloud

I've literally got no idea what any of this means. Is there any way for you guys to just give us a stage 2 UEL 93 tune with a lowered cold start? The way it is now is way too loud and none of this stuff makes any sense to me.

Its just using romraider to edit tune tables.

what rom are you on ?

[StormMcCloud]

I'm on the Stage 2 UEL tune. (pretty sure the 93 octane one but I'd have to double check the OFT and make sure that's the one I picked)

I realize it is just using romraider but reading all of this and looking at it, it just doesn't make sense to me.

(need sleep will check forum when I wake up)