Ok will try, Thanks. Looked at my map and mine is 15x18 but the conversion map is 20x21 could this be the issue? Just afraid of blowing my engine.

 

Yup, that's what I was on about

As i said, just paste in your axis' and your table.
Overwrite your final rpm/load axis label with the ones on the sheet.

Check your bigmap against your old map and make sure the values are the same for each matching load/rpm column/row.

 

Before Tephra came out with the Launch maps, I was using NLTS as launch control/2-step. It has worked very well for me for that purpose. I use it very seldom for shifting. I have 6k static so that I can feel a bit safer about letting my wife/friends drive it.

I have gotten the new Phenem xml that was posted for 96530706 rom and it works fine now. I was hoping to get a new xml for 96532706 for the live mapping capabilities but I am still running into same issues of the NLTS rpm drop not working. Yes, I have change the setting to uint16 and it does nothing.

I would like to have both Launch maps and NLTS running on the live map rom, so we shall see.

 

Here's a new question for those that are using the v7, how do we tune the maf scaling with maf adder already in it? Are we tuning it the same way we did using, the percentage from the fuel trims? I'm kinda confused and I've spent the day going through the maf scaling threads but saw no answer in terms of the new maf scaling procedure.

 

Any Tephra pro's in the NYC area? If so can you please pm me.

 

Quick V7 question. I'm not seeing how to get the timing and fuel maps and such on the V7 bin file. I see the Mods but nothing pertaining to my tune. I was watching the V5 video and they talked about copy and pasting the xml files into my old bin Rom ID but I didn't think you needed to do that with V7.


BTW I'm a ECU Flash, and Tephra newb, first attempt at this kinda stuff. Hell last week I didn't even know what an unlocker was. So bare with me please.

 

Do we have to go through absolutly everything (every map table) and port it over like before ?

What do i do with the maf scaling as in v5 i have "Airflow/Hz Raw Scaling" and in V7 "MAF Scaling (MAF Adder already included)"



[Edit] Sorted finally found out it's just a matter of changing the table scaling so it's the same for both old and new.

 

hey guys. i'm trying out 96530706 and just had a quick question. i'm running a 05 evo8 ssl and was just doing the inital setup on the new modified rom. i copied the immobilizer code and changed the immobilizer hex to the specified setting for the yr of my car (0x0058). anyway, i noticed that the ECU Internal ID is different. do i leave this alone or change it?

also, i know that the RPM/Speed to Gear table is meant for the 6mt. since i do not run ecu boost i'm assuming this table doesnt apply to me? thanks.

 

The ECU internal ID is left alone, that denotes that it is a 96530006 rom... and correct on the boost table, you only need to adjust that if you are running boost by gear..

 

hey freddie. thx. i just PM'd you before reading this. last night i assumed that i didn't need to touch either tables but i wanted to make double sure.

 

So I have a couple issues. My stationary rev limiter doesn't work.

I don't have a value for NLTS RPM drop (just displays a small gray box) and can not change it. Also, I assume the NTLS Speed and Load thresholds should be adjusted? I mean if I'm reading this right, I'd have to be under 19 mph and 150 load to get NLTS to work on the given settings.

 

just looking at the Non-Continuous Monitor Availability Patch Part 2 in the tephra 7 rom. I noticed that the stock value is 0x6AA1 and says that the Forced PASS Inspection value is 0xEAFF. however, i see EAE5 there as the value. is this a typo?


also, i noticed that the Desired ISCV initial step position with AC *** tables values are different from my 05 rom. i've never really had issues with my idle at all so would it be safe to assume to just copy the settings from my 05 rom to this new tephra 7 rom or should i leave them as is?

thanks fellas.

 

Greetings, 03 Evo migrating from 94170015 v5.10

The "WGDC = 100% below this Load" is not working correctly. So far the WGDC will only go to 100% after it passes the "min load for boost control" value. Let's say this value is a load of 88. I get 0% WGDC from 0-88 load, then 100% WGDC from 89-200 load, then whatever my WGDC table is.

Is this normal? Or do I just have to lower the "min load for boost control" values to say, a load of 10, that way my WGDC is always 100% up to whatever I specify in the " WGDC = 100% below this load"...

I thought the purpose of 100% WGDC below xxx load was exactly that, 100% WGDC from 0-xxx. Or am I missing something?

 

That is 100% the way it is supposed to work, you are missing nothing you explained to yourself exactly the way it is supposed to work.

 

So, are there any benefits to leaving the WG open under the "min load for boost control"?

I figure fuel economy might improve a little bit, with maybe a little bit more low rpm response, at the expense of a slightly laggier boost curve.

Anyone have any data to support which way is better?