GST Motorsports

iTrader: (8)

Thanks, Awesomeness as always.

One more question on boost drop, so when it drops to 0 wgdc for the timer amount, I take it error correction is turned off for that same amount of time as well?

fostytou

iTrader: (15)

A bit late, sure... but I just realized that 2 byte airflow is wrong (as posted) for 88590615.

Set to:
MUT 02 = 6B7E
MUT 03 = 6B7F

Should be:
MUT 02 = 6B9E
MUT 03 = 6B9F

linuxman51

iTrader: (7)

The launch maps are bad ***! after a little bit of tweaking I was able to consistently knock out 1.6's and 1.7 60's last night while I felt out the new clutch.

This is my launch map (suggestions are welcome):


and for comparision, my race/pump mix map (its definitly a work in progress):


I can have ~280-300 load in about a second with the setup like that and the stationary limiter @ 7500. With the regular launch setup, takes about 5 seconds to get to 250ish load.

fostytou

iTrader: (15)

Did you try static/lower values for the launch map? All I had heard before we specifically had the launch map was to drop timing to -5 in the 2-step RPM areas and from ~80-150 load. This just produced knock for me while launching and running at the time, so I didn't keep it.

I imagine smoothing it would help with the knock a bit, but did you try any lower numbers? (the more retard the more expanding gas in the exhaust, etc).

linuxman51

iTrader: (7)

with lower numbers the boost would come on just a hair sooner, but it also produced knock counts. This is phantom knock that the sensor is picking up, but I didn't want to carry that into the run, so I just pulled timing out of my normal map in a couple strategic areas. It was violent tho after 2 seconds with - timing, my neighbors don't care for me anymore.

Its still a bit of a work in progress, i'm having a hard time getting the load to stay inside a +-50 window, I'll probably work on that a bit sunday at IFO.

ixbreaker

iTrader: (3)

^That's funny fostyou, i was about to mention the same about the MUT tables being off in my 15rom. should it be as it is in the 2-byte thread, because i got this instead:
88590015
2byte load
MUT 00 = 8450
MUT 01 = 8451

2byte RPM
MUT 02 = 6B7F
MUT 03 = 6B1F

2byte AirFlow
MUT 04 = 6D85
MUT 05 = 6DA7

should it be like this???
^That's funny fostyou, i was about to mention the same about the MUT tables being off in my 15rom. should it be as it is in the 2-byte thread, because i got this instead:
88590015
2byte load
MUT 00 = 6B42
MUT 01 =6B43

2byte RPM
MUT 02 = 6B1E
MUT 03 = 6B1F

2byte AirFlow
MUT 04 = 6B9E
MUT 05 = 6B9F

phenem

iTrader: (39)

OK I found two issues while driving around today on the 9653 ROM. Those two issue are the WGDC 100% below threshold does not work, it always 0% under that value. Also under deceleration my car is jerking back and forth, the wideband is reading fuel in the 13's for about 8-10 seconds then it goes flat line and the car smooths out.



Here are the logs from the pulls, the first one is a third gear pull and you can see both situations here, no WGDC untill 200% load, then under decel you can see how the wideband is reading, almost like the car is injecting fuel with crazy high timing. The second one is just daily driving so you can see there is no WGDC until 200% or more (which is where my threshold is set).

Log 1

Log 2

Anyone else having this issue?

Any help would be appreciated.

~Zach

phenem

iTrader: (39)

After some thinking and talking with danl we think my issue might have something to do with the p0505 and periphery bit I turned off FCA bit 8. I will switch that back tomorrow and see what happens.

Any idea why that would effect the WGDC mod?

Other than that the only mod that might effect this is the OBDII stuff, if the periphery bit that I will change tomorrow doesn't fix it I will set that back to factory as well and test.

to be continued....

ixbreaker

iTrader: (3)

^ is there a threshold to activate 100% WGDC. eg: you need 100% TPS to to engage this feature...If so, notice you do have 1 data point that reaches 100%WGDC, but since your load jumps from 180 beyond 200%, your WGDC defaults to your settings arcross the remaining RPM range. I'm not sure how 100% TPS is suppose to work. Does anyone out there testing have a log of this feature at work. I'm currently testing the 15rom

phenem

iTrader: (39)

I understood it differently, I thought the idea is supposed to have it be 100% WGDC no matter what TPS (or take a percentage based on the TPS vs. WGDC % table) to improve throttle response during daily driving. That is the way Dave explained it I thought, but I could be wrong.

Having it only active when TPS = 100 would be kind of pointless because stock turbo type applications would reach full boost so fast the BCS will need to kick in and adjust boost almost instantly (as you can see from my maps)

Can someone else confirm which way the logic is supposed to operate?

ixbreaker

iTrader: (3)

^ your reasoning is absolutely correct. But, i'd still like to see a log with this feature active.

fostytou

iTrader: (15)

I think 2 byte load and RPM were intentionally left off (or at least not worried about) since 1 byte load is better and 1 byte RPM suffices... but I could be wrong. The value I posted for airflow is definitely correct. It is from the thread and tested on a lonely highway this morning .


No, I can definitely say that the instant you reach the "min load for boost control value" WGDC goes to 100% until the instant you hit the WGDC 100% below threshold and then it goes to whatever is in your maps.

Here is an example log for you.
http://thefrost.net/randomfiles/tuni...0_02.22.24.csv

There is also a description here:
http://evoecu.logic.net/wiki/TephraMod#Boost_Control

ixbreaker

iTrader: (3)

ahhh i c, wow. So then there is a threshold, eg: min load for full boost control? and according to your log, the WGDC 100% feature is set to ~190 and below correct?

tephra

iTrader: (6)

no TBEC is still allowed - but max upward tbec of %10 should be fine -yeah?

tephra

iTrader: (6)

with WGDC - Fosty is correct.

The stock "min load for boost control" still means you get 0% wgdc up until 80-110 load - as soon as you supasse this then the "100% mod" kicks in.

If you want %100WGDC in lower loads - then drop the stock table down a bit...