Bump for anymore ideas on how to get this working correctly.

 

Same issue here. Except it was working and now it doesn't want to.

 

Email me your ROM and a log or two and Ill see if it works for me.

Email is in sig.

 

THANK YOU SO MUCH!!!! Email sent!

 

Your welcome. Email'd you.

I figured out his issue.

He had 2byte load improperly configured and its reading totally wrong (ie 2661.875) and since the mapracer uses load to work, it wouldnt work.

I recommend that he just use 1byte load, as he is running V7 and 1byte load is better then 2byte.

 

Wow, that was crazy fast! I don't understand what you are saying about the load being configured wrong though, could you explain that?

I am actually flying out of town in the morning so I won't be able to play with this until I get back next week but I will update this again once I get back to it. Thanks so much Jay!

 

The top axis of the fuel and timing maps (and in many other maps) is the value "load". You use load and rpm to figure out what cells you are in.

Now, you were trying to log "2byte" load, which is an "old" way to log load. You have to configure the MUT table in your ROM for 2byte load to work.

But you dont even need to worry about 2byte load, because now, we have "1byte" load. 1byte load comes with tephra V7. It works better and is easier to configure. All you have to do is make sure the "load factor" is the same in evoscan and in the ROM. In evoscan, on the data item "1byte load", under the area "function", if it says "1.2*x", then "1.2" is your "load factor". So in your ROM, under "2byte to 1byte Load Factor", you need to make that value "1.2".

Now, the ROM and evoscan by default have the load factor at "1.2", so you wont have to change anything untill you exceed that load factor, which happen at 306 load with a 1.2 factor.

Conclusion: Just log 1byte load.

 

Ah! I had the MUT table setup for 2 byte on my old ROM but I never messed with it on v7 and when I made that log I forgot to log 1 byte. I had never even heard about verifying the load factor so obviously I had never checked that before. I can't thank you enough for going out of your way to help me figure this out.

 

No problem.

 

I feel like I'm taking crazy pills!



So I'm back from my trip and started messing with the tune again. I did a third gear pull today logging 1 byte load. I tried to track it with MapTracer but it still didn't do anything. I said screw it, I'll just look at the 1 byte and RPM and see if that works now. I opened the the ignition table in ECUFlash and now the load/RPM headers are all jacked up, even on the ROM. I opened the original V7 ROM I had downloaded and the load/RPM headers are all jacked up there too. They weren't before. This is driving me crazy. Here is a screen shot of what the table looks like directly from the ROM:



Any ideas?

 

Looks like your defs are messed up.

Your defs are here: C:\Program Files (x86)\OpenECU\EcuFlash\rommetadata\mitsubishi\evo

Send me this def and Ill check it :TephraMOD-94170715-v7

That is if your still using 94170015 V7. If you using 9653, send that def.

 

I am still using v7 (94170715). However, I just realized I was opening my ROM with ECUflash 1.29. I just opened it with ECUflash 1.43 and the tables are now correct.

Looking at the log on a spredsheet and comparing it to the tables now makes sense (I imagine because of the 1byte load) and I can manually track the cells being used. I think I am going to give up on MapTracer for now.

 

Cool.

I would use EvoScan (or VDs) data charting. While not as easy as a map tracer, it is much, much better then using a spreadsheet and my preferred way to look at logs