Thats actually a great idea for all driving conditions once the car is moving past a minimal speed. I'm sure you'll find that the best rev-matched rpm's are close enough together that you can just have one RPM setting somewhere in the middle of the range of all gears.

 

So, in semi Psuedo-code you could put something like this in the NLTS function

Alternatively you could just do

Much simpler, but not nearly as effective.

Then for the Evo X you could just add a throttle=100% in the deepest loop. (not sure how this would work with normal shifting though)

 

i'll look at it for v8+

 

The only thing I worry about is sometimes its not so easy to pick where you want to downshift, but now that I think about it, if we have correct gear/speed ratios set (and it is less important in 5th gear) then you can just multiply that by speed to get the correct RPM.

 

Ive been running V7T5 for the past day and all is well. Alt maps is working, didnt try nlts yet but will. Also need to test valet.

As for everything else I went with Tephras original xml renamed to 706 and used phenem's rom and copied everything over and worked mint.

 

Hey guys,

Good news!

Launch maps work awesome, the alternate maps are working great, and I have yet to test the valet and TPS toggle.

Everything is as is should be now, boost is working, and others have confirmed the USDM version of v7t5 is working 100% for them as well. Just need to confirm a couple last things myself.

I will report back on the valet and TPS toggle activation settings when complete.



~Zach

 

Tephra and Phenem I was actually wondering what would be the cause of Evo Scan logging incorrect values for 2 byte load for the 706 rom ?

I was going to do some logs and started off with a log at idle and noticed my 2 byte load was in the 80's-100's while 1 byte load was in the 30's where it is normally.

Then I decided to do some 3rd gear pulls and see what happened and my load was in the 3000's. Which is obviously wack.

I switched back to 0015 to be sure evo scan was fine and everything was.

 

Actually EVOScan logging is the problem not the ROM. I am having an issue with EVOScan as well right now.

Tephra can you confirm the EVOScan logging XML definition's that need to be added to EVOScan (as described in the first post of the thread).

Also don't use 2 byte load anymore 1 byte is fine (Tephra fixed that).

 

ohh ok I knew at one point it was better to use 2 byte but I have notice my 1 byte being pretty much the same. So its fine then seeing 1 byte worked fine with the v7 rom.

 

How do you log the 1-byte load in evoscan?? I have 94170015

 

Its all the same as before, you guys just need to make sure that your MUT locations are correct if you have modified them at all. Tephra shifted some things from the original XML I (and others) had distributed. Might be best to just start with a fresh copy of the Evoscan XML and add things as necessary. For me that wound up being easier and cleaning things up with the newest version of the evoscan XML.

Load is always "better" to log as Tephra's 1-byte if it is properly set up. It is less "accurate" but allows for more resolution (IE more other items to be logged in the same amount of time). However, it is not the same thing as logging some of the other load functions which are not as good, because they are calculated or have a ceiling of 255.

 

Yeah, know all of that LOL. Just need to know the MUT address. ;-)

 

I expected you knew

First post, Evoscan XML in big red letters . Missing anything else?

 

Well, I took tried out the v7.5 rom that phemen posted. It started...YAY.

Went for a cruise and got on it, iand the car fell on its face and spitted and sputtered at anything over 1/4 throttle. I compared it to my 9927 rom which runs great, and could not find any differences between the fuel and timing maps, nor any other tables that you would think would effect drivability.

Loaded 9927 back in, and it ran fine.

Any ideas?

 

Do you have a mitsu 3bar MAP or stock?