So I installed my JDM Map Sensor. I made the correct changes to my xml file to run with the new sensor. I've also successfully logged boost with the JDM sensor in Evoscan. My problem is using Evoscan to correctly tune the boost control.

I followed mrfred's directions to change the data xml file in Evoscan but Load Error didn't change to Boost Error. Am I wrong in assuming this? Here's what I followed.

Instructions for EvoScan
Add the following entry to your EvoScan "Data.xml" file:

-----
<DataListItem DataLog="Y" Color="" Display="Boost Error" LogReference="BoostError" RequestID="8A" Eval="0.0241*x-3.087" Unit="psi" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="-5" GaugeMax="5" ChartMin="-5" ChartMax="5" ScalingFactor="1" Notes=""/>
<DataListItem DataLog="Y" Color="" Display="WGDC Correction" LogReference="WGDCCorr" RequestID="8B" Eval="0.5*x-64" Unit="WGDC%" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="-50" GaugeMax="50" ChartMin="-50" ChartMax="50" ScalingFactor="1" Notes=""/>
-----

Save the Data.xml file.
Just reading through this I was expecting to see some new things to log ie.

Boost Error
WGDC Correction

Now I see WGDC Correction but no Boost Error. I noticed that in the "Request" column in Evoscan it says 8A next to Load Error. This is the same "Request" as the Boost Error so that is why I assumed it would just change the name.

Any help would be appreciated.

 

Just to let everyone know, I'm completely new to this stuff. I'm no computer guru and I don't know much about Ecuflash and Evoscan. I've been reading through every Ecuflash thread that pertains to Logging boost and tuning boost. I've been taking baby steps with modifying my rom with Tephra's patches like the v5.10 and Mrfred's for using the JDM Map sensor. I'm still trying to get a good handle on how this all works. I've also made up a word document to create "cliff notes" on all of this stuff to help me better understand it. I know I didn't have to explain myself but I don't want anyone to think that I created this thread without trying some stuff on my own. Most of the guys that are using this stuff have been involved in these threads since early last year so they've had time to soak it all up. I'm trying to play "catch up" with all the new stuff that's been happening since then.

 

Just to summarize what I've actually done to my car, I'll list it.

Modified my ROM to include v5.10. Successfully flashed this and the Evo ran perfect!!
Modified my newly patched ROM to include mrfred's patch to log with the JDM Map Sensor and still have the Evo running perfectly!!

I've also copied and pasted the data from the tables listed in the thread to get me started. I'll try to get a screenshot of what my tables are set to and a screenshot of my logged boost with these settings.

 

Here's how it's set right now.

 

Here's a screenshot of my Boost Log

 

Oh by the way I have a Basic Bolton IX with a GM 3-Port. If anyone sees something out of place let me know.

 

morning bump for the early birds

 

53 views and no comments? Any and all comments welcome. I'm also a little confused about the Alt Map Switching as far as boost is concerned. I only see an Alternate WGDC table. I thought there would be something that looks like "Alternate Baseline Boost" or something like that.

 

evening bump. I would love to slap on my FP Red this weekend but I have to figure out this boost control thing.

 

if I understand your question correctly, youre trying to add "Boost Error" and "WGDC Correction" to your evoscan .xml... And you can see the WGDC Correction, and was expecting load error to change to boost error? Load error does NOT change. You have just added another parameter to log. So you should now have both load error, and Boost Error should be at the bottom of the list.

More importantly, if you are NOT using "direct boost control" you wont need "Boost Error". Direct Boost Control is PSI based, so any error would be corrected in/by PSI. I can tell from your screen shot of your tables that your still using "Load" based control, so you wont need "boost error" till you make the switch!

 

well thanks for trying to help out. I obviously did something wrong when I modified my "Data"xml for Evoscan. As for "Direct Boost Control" I'm not sure what I should be doing to switch to this. I'm having boost problems with 4th and 5th gears. When I hit those gears the boost gauge will hover between 15-17psi and then walks it's way up to almost 25psi. It seems somewhat steady from 1st-3rd but 4th and 5th are my problems. Maybe I'm still using Load based boost control? How do I know for sure?

 

Here's what the Data xml looks like in Notepad. Do I have it copied in there correctly?

 

Morning bump for anyone interested.

 

It appears to be in there properly. Do you have the new patch at the bottom or top? Needs to be at the top! Which version of Evoscan are you using? If youre using 2.5, PM me your e-mail address and I'll try to send you my evoscan .xml. if my comp. permits it. she fiesty. (*****)

Do you have the MUT table in your Ecuflash .xml? You need to have the correct value in the MUT table as well... (I.E.) "request ID= 8A" I dont recall what the values are off hand. I would open up your ROM in Ecuflash and look up 8A/8B in the MUT table and post up the values and see if people can verify them...

What ROM ID? If 88590015, I can send you my .xml for that as well. I pretty much have everything in my .xmls including "direct boost control" and "Tephras v.5.10"

 

I apologize for my ignorance but I'm not sure what patch you're talking about. If you mean the v5.10 patch then yes, it's at the top. If you mean the patch for Evoscan like the one below then No, it's at the bottom.

<DataListItem DataLog="Y" Color="" Display="Boost Error" LogReference="BoostError" RequestID="8A" Eval="0.0241*x-3.087" Unit="psi" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="-5" GaugeMax="5" ChartMin="-5" ChartMax="5" ScalingFactor="1" Notes=""/>
<DataListItem DataLog="Y" Color="" Display="WGDC Correction" LogReference="WGDCCorr" RequestID="8B" Eval="0.5*x-64" Unit="WGDC%" MetricEval="" MetricUnit="" ResponseBytes="1" GaugeMin="-50" GaugeMax="50" ChartMin="-50" ChartMax="50" ScalingFactor="1" Notes=""/>