mrfred

iTrader: (50)

One of the advantages of using Excel is that I can plot the BWGDC and target load data from the tables in the ECU. Here are the 2nd and 4th gear logs vs rpm.

accident

iTrader: (60)

I'm using v0.99 and I did this in notepad and I can get it to read on the realtime screen but when I go to review a log it doesn't show up. I was wondering did I do something wrong or forget to change something else?
thanks,
ed

TouringBubble

iTrader: (2)

I haven't been able to get EvoScan to graph a modified file. It's a common problem.

Chamama

Anybody have any luck logging accurate WGDC with the JDM dual solenoid setup?
I used the formula depicted here but got weird readings

Any help much appreciated!

mrfred

iTrader: (50)

What is the ROM ID for your Evo?

Chamama

ROM ID 88570008

mrfred

iTrader: (50)

I'll try to take a look at it this weekend. You could try PMing jcsbanks too. He had a FQ360 and may have disassembled that part of the ECU already.

cij911

iTrader: (14)

Sorry for such a noob question, but in evoscan v2.5, my WGDC shows 85 (which is what I have set the MWGDC to), LoadError is logged at 19.84 across the entire WOT pull, and WGDCCorr shows 16 ?? I have the TBEC set to 0 throughout, what does the WGDCCorr = 16 mean and why does evoscan think my load error is just 19.84?? Thanks

mrfred

iTrader: (50)

The ECU cannot detect a load error of more/less than +/- 20. WGDCCorr should be zero if you have the right side of the TBEC table zeroed out. Did you change the MUT address to point to WGDCCorr?

cij911

iTrader: (14)

MrFred -- I have not changed any MUT address. I just zero'd out the TBEC table, but it appears to be finding some other source for WGDCCorr (is that the same as TBEC) ?? Also, how can I see what my actual WGDC is vs. MWGDC ? Thanks

tephra

iTrader: (6)

load error and wgdccorrection are "new" MUT requests, ie if you havn't changed your MUT table to set them up then logging them will produce garbage.

mrfred

iTrader: (50)

There are some notes in one of my threads about how to log WGDC Correction and load error. I think its called "boost control mods". WGDCCorr is a bit different than TBEC. The ECU compares actual load (or boost) to the target load (or boost) a few times per second, and if the target boost continues to remain above/below the target boost, the ECU will keep subtracting/adding more and more WGDC correction in an effort to hit the target value. The amount it subtracts/adds each time is the TBEC value. the ongoing sum is the WGDC Correction.