Quote:
Originally Posted by DallasBoosted
The boost mean abs drops below req boost somewhat. I know I could go and pull out or add wdgc (same way to fix overshoots which I have done) but why doesn't it learn? Those tables should be auto-adjusting to a certain extent. I had a Profec on my Eclipse GSX in 1997 that could boost target perfectly. :P Why do we have to fiddle with it based on logs to get it to work in 2013?
|
The main thing is the Profec is targeting boost, while the DME does not. The other problem is more of a slight confusion in the naming of some of the tables. We really should have called them Load/Boost Ceilings, not Load/Boost Targets. The DME tries to get close to the load and boost requests, but its normally never going to hit them exactly.
Carl's main issues have to do with very high altitude and I've recently found some new things relating to that. At this point, its on the list. While I am concerned with offering these tables as they will almost certainly overspin the turbos, I'll get them added... I just don't have a date right now.
To your other questions:
(1)The FlexFuel sensor is a bit more than just adding an input to the DME. Its possible that this could come at some point, but if we simply feed the signal to the DME, we would need to do massive changes to pretty much every piece of logic. The code simply doesn't exist in stock form from BMW, which means it would need to be written.
(2)Changing the strategy of the DME to be boost targeting would again be a huge undertaking and would require extensive testing. I see this as being unlikely, but I won't completely rule it out.
(3)External WGs are still on the horizon, but with the new options that have been surfacing lately, we should be able to do some testing on this front soon.
I always have a long list of tasks, but don't worry guys, I'll get to them all.
-Josh