Type: Posts; User: DCAFS
Search: Search took 0.01 seconds.
Man.....your throttle plate is oscillating from 3K to 4.8K like an early generation piggyback tune.
Timing is way low as well.
I would say you are oveboosting at those throttle closure points...
12-03-2013, 09:26 PM
Could be.......I didn't change them drastically. Basically dropped them down by about 50 in the selected rows where I think boost is being reported back to the DME by the piggy during the timing...
12-03-2013, 09:20 PM
I just tried this table adjustment tonight while running on a regular Procede piggy.
My Timing was dropping down to 3-4 degrees on heavy WOT load as soon as I hit max boost.
I modified my...
11-28-2013, 10:27 AM
That's very interesting!
I hope others are able to replicate these results.
In the OFT/Pro-tuner setup there are three separate Torque/Load tables. Does Cobb have the same number of tables or...
Like Terry says.....it's anyones guess.
In my case it looks very much like classic knock retard rather than torque intervention.
I had a closer look at the procede's ignition map in that...
Here is the identical datalog I spoke of earlier except I applied throttle more gradually.
At the same boost point (16 psi) and same rpm, timing stays nice and smooth and only drops to 7 degrees...
There are a lot of missing pieces so it's hard to understand the mechanics of what is going on.
But this was an interesting exercise.
I have to agree with Lulz in that it...
I am not running the OFT currently.....went back to just the procede.....but regardless same behaviour in both platforms.
Here is a datalog where timing drops to 3.5 degrees just after full...
So where do you think the DME goes to get a timing value of 3-4 degrees at high load boost onset?
Is there a specific timing table or is it just the main ignition table...
Holy moly that was fast........
I don't think I even finished posting and you already replied! :laughing-rofl:
But that was exactly what I wanted to know. It's possible to change those values...
Does anyone know under what conditions the DME defaults to the ignition failsafe table?
I notice on some logs that timing can fall as low as 3-4 degrees at boost onset at low to midrange rpms and...
I dunno.....maybe it's just me.....but your trims may be less negative with the updated map, but there seems to be more of a spread between the two banks than before?
What nozzles are you using...
Uh huh......I see a little less torque reduction 5300 rpm and higher in that table.
Worth a shot - but does anyone know how this factor works? Has anyone used this in a Cobb scenario successfuly?
Stack Cobb with Procede? Is that what you mean.....because I still need the piggy to control the meth system.
Remember....Procede is still controlling the WGDC's when stacked.
Well....this was a good idea but it didn't work at all :(
Once the car warmed up I only got to half throttle and the car began to surge and the dash lit up like christmas.....the gas pedal did...
Sounds interesting.....thanks Josh!
I had a quick look at the torque/load limit tables using the comparison tool in tunerpro just now and will try this out later today.
You may be right in...
Haha.....we're just lazy lazy.
Here is my modified stage 1 OTF bin file and the original.xdf file it was married with. The bin is adjusted to stack with a piggy in order to run meth.
More load in the upper rpms and more...
It's already set to 3.00 straight out of the box :(
No lulz......the problem seems to be that the boost target it too low. I have no problem hitting the current target - in fact procede stack exceeds it by 1 psi.
Also it's my understanding that...
Here are my Procede PID settings.....the Proportional factor = 0.4 so increasing it to 0.5 will get to target faster then?
And here is a datalog showing boost setpoint only.
So just a follow up on boost control and stacking.
As Josh indicated Procede will control the WGDC's under all stacked circumstances so no point in massaging the flash wgdc tables.
OMG....I feel so stupid!
So you are saying that all this time I have been spending on upping the flash boost setpoints can easily be solved by simply using the user adjustable boost tables in the...
Yes you mentioned previously that a stacked Procede will control the WG duty cycle - I understand that part, but I had the impression that the boost targets were still defined by the flash rather...
Josh.....are you currently running a stacked setup?
Results 1 to 25 of 203