Ralliart TD04 spool-up - the load calculation problem & the solution
#31
#32
Hi folks.
Golden's website now has definitions for "Load Ramp Rate #1 (Load>70)". This is defined for the fave Ralliart ROM IDs.
First post updated with a gratuitous EcuFlash image.
The factory value for this is: 3.53%
I've tested out 7.06% and it helped ChosenLoad keep up with fast-rising load. I'm not sure it was quite enough to handle a 4000rpm throttle-stomp, but very close.
Next time I'm out on track, I'll be trying 8.63%.
Rich
Golden's website now has definitions for "Load Ramp Rate #1 (Load>70)". This is defined for the fave Ralliart ROM IDs.
First post updated with a gratuitous EcuFlash image.
The factory value for this is: 3.53%
I've tested out 7.06% and it helped ChosenLoad keep up with fast-rising load. I'm not sure it was quite enough to handle a 4000rpm throttle-stomp, but very close.
Next time I'm out on track, I'll be trying 8.63%.
Rich
#33
I just want ChosenLoad to be able to keep up with the lower of MAPCalcs or MAFCalcs.
Here's my test of 8.63% from just now... going WOT above 4000rpm in 3rd:
That's what I want to see. I'm leaving mine at 8.63%... seems to do the trick
Rich
Here's my test of 8.63% from just now... going WOT above 4000rpm in 3rd:
That's what I want to see. I'm leaving mine at 8.63%... seems to do the trick
Rich
#37
I tried increasing mine from 5% to finally 25% over the weekend and it seems to help in fixing my lean condition during sudden acceleration.
Not sure if that's too much.. but I try to keep it below "Load Ramp Rate #3" which is set at 30% stock.
I guess what determines the ramp rate will be my setup (turbo, cams) and MIVEC settings.
BTW, Rich is the ChoosenLoad parameter you mentioned the same as Load currently defined in EvoScan?
Not sure if that's too much.. but I try to keep it below "Load Ramp Rate #3" which is set at 30% stock.
I guess what determines the ramp rate will be my setup (turbo, cams) and MIVEC settings.
BTW, Rich is the ChoosenLoad parameter you mentioned the same as Load currently defined in EvoScan?
Last edited by RS200Z; Nov 11, 2012 at 07:25 PM.
#38
#39
I thought "The Chosen One" was in tibet? hmmmmmmm
yeah... a bit off topic
back on topic, these are definitely some sweet developments to come through in RA/SST land this past year!
yeah... a bit off topic
back on topic, these are definitely some sweet developments to come through in RA/SST land this past year!
#42
Were you getting spool-up knock before?
If you look closely at your load vs. boost, you may see that you hit peak load sooner now. That depends on your logging speed, though.
Rich
If you look closely at your load vs. boost, you may see that you hit peak load sooner now. That depends on your logging speed, though.
Rich
#43
I have always gotten spool up knocks before this patch.
I think my logging speed is too slow. What's a good baud rate?
BTW when I lightly tap it (30% throttle) at 3k~ rpm and then let go, the car bogs down (coast) slightly faster than before, did you notice any of this after the patch?
I think my logging speed is too slow. What's a good baud rate?
BTW when I lightly tap it (30% throttle) at 3k~ rpm and then let go, the car bogs down (coast) slightly faster than before, did you notice any of this after the patch?
#44
At 7.06%, I couldn't really feel it at all. 8.63% and it's there very slightly.
Earlier on, I tried a larger number (10.59%), and it was much worse. Throttling off while under light boost induced quite a noticeable decel jerk. The log showed rpm really taking a dip, so it's not our imagination.
Given that your experience matches mine (ie. it wasn't my imagination or a problem with my BOV or something), I'd recommend...
For STREET tune : 7.06%
For TRACK tune: 8.53%
Thoughts?
Rich