Let me blow your mind for a minute. All Z4M MAF-based tunes
still use alpha-n. The MAF sensor can't respond quickly enough to rapid changes in airflow, so the ECU momentarily reverts to alpha-n until the MAF can catch up. Unfortunately most tuners don't touch the alpha-n tables with MAF-based tunes, and I would venture to say that most aren't familiar enough with the ECU to understand what it's doing. This leads to the perception of lag with the MAF tune, but in reality it's because the tune isn't optimized. It becomes more apparent with engine modifications.
I wrote a long post about alpha-n vs MAF previously, so I won't fully rehash what I've already said. In summary, MAF is better in most cases. However, a fully optimized alpha-n tune should behave like stock. Many times sensor scaling is misunderstood or ignored, and that leads to some of the problems others have mentioned with alpha-n. I would take an MSS70 alpha-n tune over a MSS54 MAF tune on any naturally aspirated or supercharged setup, due to the MSS70's wideband sensors. While the ECU "guesses" airflow with alpha-n, the MSS70's wideband oxygen sensors will tell you what the actual mixture was. The ECU trims fuel to correct.
Martyn's info is on point. MSS70 does have a built-in baro sensor. Tunes that don't perform as well at altitude are likely suffering due to the ECU operating in a different part of the fueling map which isn't typically tuned at sea level on the dyno. I have not heard of melted pistons in a naturally aspirated S54. The S54 is very robust. You wouldn't believe some of the tunes I've come across... knock thresholds raised to the moon, 16+ deg of ignition timing beyond stock with 98RON tables copied over to 91RON, on cars that are driven hard in the Middle East. I couldn't have come up with a worse tune if I was intentionally trying to blow up an S54, yet the engine endured and still put down fantastic numbers when properly tuned.
maupineda said:
3. Karbonius CSL Airbox (alpha N): it does change the character of the engine, is just more aggressive in general, the throttle transients are more aggressive, and less smooth, and though that may be a mapping thing, I ran epic and Severn tunning maps and both were very similar in terms of delivery. The Severn map was better as it was customized via data logging, so is unfair to compare it to epic's as that was a canned map. However, the car would have hesitations or what I better describe as kangarooing behaviors between 2-3k rpms under mid-low load situations.
The car exhibited a hiccup with both Epic's tune and my tune, which would lead me to believe it was hardware-related, since the airbox was the commonality with both tunes. Most alpha-n Z4Ms don't have hiccups, and it wasn't showing in data logs. MSS70 is sensitive to brake booster faults, and the modifications to support the carbon airboxes can cause hiccups. FWIW, the Epic canned map did cost more than the Severn custom map, and we also provided the MAF-based tune for no additional charge once the car's direction changed.
maupineda said:
I am sure that a MAFless setup could be made just as smooth with enough time and money, the reality is that no one outside Siemens (not even BMW) would have access to all the hundreds of maps that need to be looked at for a seamless implementation. MAF setups play with basics (timing and fueling) and rely on the baseline maps which are factory developed, which means thousands of hours of engine dyno and road driving sessions. No one will ever match or defeat that, period.
As already said, with a CSL Airbox you will have to deal with some compromises.
OEMs don't do nearly the performance calibration work that we're led to believe, and they are bound by emissions standards. I'm fortunate to be one of the few to acquire the official Siemens documentation on MSS70, which is very rare, over 6000 pages long and describes how the ECU works. Additionally, I have a (more common) A2L file which details the addresses of all 8000 parameters in MSS70. I don't think BMW has any one single engineer that is fully familiar with MSS70, because the parameters look like they were decided upon by committee. Some sections that should be minimally relevant are overly complex- like an engineering team was seeking job validation or something to brag about to their customer- while other very important areas are only briefly covered. These files paint an interesting story. Nonetheless, it does take a lot of time to figure out MSS70, even with all the documentation. Much of it is not documented in the way we would like.