Wouldn't it be so much easier to just be able to enter a target PSI (if you have the JDM MAP) and have the WGDC and BDEL/Correction dynamically adjust to achieve the desired PSI?

Is this even possible, or am I just dreaming?

 

Shell 93. I'm a little dumbfounded too ... AFR is around 11.8:1 at peak and 11.2:1 at 7200.

I know that's causing the spike. As I mentioned earlier, I had an issue with dropping below -20 desired and the TBEC table wouldn't catch back up. Now that I've got it working, I can zero out the -20 cell and fix the issue ... but, on the other hand ... it's not knocking, so there really isn't a problem. It's just not ideal. I'll work on it this weekend I guess.

Well, that is pretty obvious. But, what is the problem with my situation? I know it's not reaching desired load, but it's not a big deal. Is there something negative that will happen if the TBEC corrects up too high?

You know ... if I were smart I would have realized that I could re-scale the error values. I've wanted more fine control and I don't like the scale .. I just didn't think to change it! That said, I've tried larger correction values on the stock scaling and I saw over correction and a wavy boost curve.

 

Just trying to help.

 

Should be possible. I'm trying to work it out.

 

I know, and I appreciate it. Didn't mean to come off harsh.

 

I'm fairly experienced with ECUFlash/EvoScan. I've got a JDM MAP (thanks mrfred) sensor and have been tuning for a while, but for the life of me I can't get Load Error to log in EvoScan.

I've made the changes listed to my ROM in ECUFlash, flashed the modified ROM to my ECU, and changed the EvoScan data file. But when I try to log "Load Error" in Evoscan I get "Illegal expression in Data.xml".

Here is a copy/paste from my data.xml. What am I missing?

<DataListItem DataLog="Y" Color="" Display="Load Error" LogReference="LoadError" RequestID="8A" Eval="5/8*(x/4-32)" Unit="%" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="-100" GaugeMax="100" ChartMin="-100" ChartMax="100" ScalingFactor="1" Notes=""/>

The eval expression looks right to me, and obviously others have gotten this to work. This is EvoScan v0.99. Maybe you guys can see something I don't. Thanks!

 

Yeah, this would be great. it would be awesome to have even a 2D map with rpm values and then enter the desired boost level in the other column. I'm sure that this can't happen but it would make boost control so much easier
ed

 

So we dont have to change all the maps anymore??

 

Look at the new DataListItem code Mrfred posted in the first post. I had the same issue with .99. The new code works.

 

I am running the boost settings that you see in the attachment. The TBEC table is stock. The car boosts to 22 psi and holds boost to 19 psi by redline. What should I expect if I change the WGDC Correction #1 from the current 10 to 3 or 4? Must I change the TBEC table as well? Or can I keep it stock? Will my boost go higher or lower?

 

Another thing I noticed is that there is no mention in the updated instructions of changing the address in MUT8B. So should we change the address to 6EE3 or not?

 

For USDM Evo IX, 0x6EE3 will get inserted into MUT 8A. If you changed MUT 8B because of my first instructions, then put it back to stock. The stock value is 0x6B41.

 

I believe I changed mine back to stock, but I can't be certain. Would you mind posting the XML for that address?

 

here it is

<table name="MUT8B" category="MUT" address="3F0B2" type="1D" level="1" scaling="Hex16"/>

 

Could someone please answer my question in post 100?