Tephra v5.10 94170015 Boost control BUG!
Tephra v5.10 94170015 Boost control BUG!
Figured I'd make it official so more users will see this. Some a bunch of memebers have been having issues with Tephras v5.10 patch when using ECU controlled boost ONLY. So far this is the only bug in the entire patch so if you use a MBC don't get worried.
I am going to the race track on friday and I'm kind of in a pickle. I use the "spray on knock" feature from the patch to activate my alky kit so I can't just go to a stock 94170015 rom for now.
Any idea if this is gonna be time consuming to look over or is there a PROVEN 94170008-94170015 patch that has the 'spray on knock' feature with a fully functioning Boost control setup????
With love and desperation,
Jamie
I am going to the race track on friday and I'm kind of in a pickle. I use the "spray on knock" feature from the patch to activate my alky kit so I can't just go to a stock 94170015 rom for now.
Any idea if this is gonna be time consuming to look over or is there a PROVEN 94170008-94170015 patch that has the 'spray on knock' feature with a fully functioning Boost control setup????
With love and desperation,
Jamie
Well, my issue started when I couldn't get ANY repeatability while dialing in my Base WGDC curve even with NO boost error correction. If I did 3-4 pulls in a row (on the same section on-ramp always test my stuff for consistency) the curves would slowly lower in boost each pull and the curve would start to lose its shape. It seemed that only the upper RPM band seemed to hold its shape but thats because my WGDC above 6300rpm is basciallu 100% WGDC anyways I think.
The big problem a few memebrs have had is the boost error correction seems to not be consistent. When they switched back to a standard ROM the issue was instantly resolved though.
I will be doing 3-4 pulls with the patched rom tonighr and get logs and then do 3-4 pulls with a stock rom to see if my Base WGDC issues are indeed the patch. I hope someone can at least peek in this ROM and see if we're just crazy or there is reason to not rely on it right now. I don't want to waste all week after a long days work trying to dial in my tune only to get to the track and have it all screwy and i wasted over $100 to get there and back for nothing
The big problem a few memebrs have had is the boost error correction seems to not be consistent. When they switched back to a standard ROM the issue was instantly resolved though.
I will be doing 3-4 pulls with the patched rom tonighr and get logs and then do 3-4 pulls with a stock rom to see if my Base WGDC issues are indeed the patch. I hope someone can at least peek in this ROM and see if we're just crazy or there is reason to not rely on it right now. I don't want to waste all week after a long days work trying to dial in my tune only to get to the track and have it all screwy and i wasted over $100 to get there and back for nothing
the forums are the best way to reach him because his PM box is always full. I figured this way other members can chime in if they've had any problems with the boost control tables with this ROM ID patch. No reason to keep a possible error in a patch to myself lol. If there is indeed an issue everyone should get a heads up that their current patch might have an error in it
I am also using v5.10 94170015 and have noticed weird things happening with my boost. I am using a JDM Map for direct boost control with the gm solenoid and have noticed that my first pull after a reflash will always hit the highest boost and each run after will never meet those levels.
Trending Topics
Is it only on the alt maps or on the normal maps as well. I have been dialing in my ingersoll rand solenoid, on the normal boost maps and it seems to respond to changes correctly. This is w/o error correction, because i am still trying to find clarity on error correction adjustments and how to go about dialing it in after reading about it so much lol.
Well, I first noticed this on my alt maps so I decided to get used to dialing in the tables with the standard maps so I wasn't wasting my Alky. Personally, I'm having the same issue with my standard maps too. Just like Silver Evo8 said, first pass would be high, then the next passes would be lower. Usually after the 3rd or 4th pass it seemed to settle in. Only problem is if I dialed it in after the 4th pass, the next time I went to try it in the morning it would overshoot a LOT, like 3psi. Usually the curve was the same but the boost level was evenly raised. I have wasted a ton of passes trying to get this dialed in but I can't even get the base WGDC to be even remotely consistent to want to add the error correction adjustments yet. I don't want my error correction constantly doing large adjustments in one direction at first, then large adjustments in the other direction on the next pull.
Can anyone else confirm my issue by running the car with error correction all set to 0 and datalogging 3 passes back to back, with the first pass being just after the car has fully warmed up and hasn't done any WOT pulls Preferably on the standard maps (Alt Maps too if you want to be my hero,lol)
Can anyone else confirm my issue by running the car with error correction all set to 0 and datalogging 3 passes back to back, with the first pass being just after the car has fully warmed up and hasn't done any WOT pulls Preferably on the standard maps (Alt Maps too if you want to be my hero,lol)
Last edited by Jack_of_Trades; Sep 29, 2008 at 11:39 AM.
Is your coolant fully up to temp when this happens? Or is it always the first WOT pull after a flash?
What is your WGDC at peak boost?
Does the actual logged WGDC change or is it always constant but the actual boost level is different?
What is your WGDC at peak boost?
Does the actual logged WGDC change or is it always constant but the actual boost level is different?
my coolant temps are high enough to allow full boost control, the wgdc logging is exactly what it should be in the table but the boost level changes. I have made runs and then come out the next morning to test it one last time on my way to work and have it overshoot. this was without a reflash in between pulls from the night before
Yeah, the WGDC is always exactly what the table says every pull. Its with the BEC all set to zero's too so it shouldn't change the WGDC anyways. Yeah, its annoying as hell lol.
I could be crazy but I just need to know if its all in my head or not so I dont chase ghosts and waste time tuning this thing only to have to redo it again later.








