[MENTION=97435]need-a-cage[/MENTION] that is not actually true.
If there is not a DTC produced by the ECM there is not a software related issue at all. The issue lies in one of the car's mechanical systems. If there were a tuning related issue then there would be a trouble code. We explained the issue with the addition of M100 or MS100 at length with 16sport.
The biggest issue is partly that there is no definitive answer on what the fuel was. Either way the fuel that was introduced was detrimental. If there were an issue with the tune it would have been happening from day one. As you can see if you go through other posts the car ran fine...UNTIL this mystery fuel was introduced. The OP admits that the issue started about 30 minutes AFTER the new fuel was added. The fact that an aftermarket tune for lack of a better term "turns up" all of the performance parameters will only highlight an issue if one exists in a mechanical part or system. To blindly blame the tune because there is no logging is not accurate.
Then to add further insult to injury you reference AFR. EcoBoosts DO NOT operate of recognize Air/Fuel Ratio. That might as well be an encrypted language that the ECM cannot read.
Anyone taking the native values and changing them into something else gives a chance for things to be miscalculated. This is the biggest issues we see with data logging. If someone looks at AFR on a logger, that value is already calculated. But the issue is what conversion are they using? 14.64? 14.08? something else? Now, what about what is in your tank. If they are assuming e10, and you have something more like e6, that instantly makes the applied conversion incorrect. Then, what if they aren't grabbing the right data point from the ECM to log it? What if they are grabbing one with an offset already added in? or a delay? or a commanded vs actual average?
You can see where one simple item like "afr" is all of a sudden riddled with chances of incorrect data being displayed. Now, we haven't even started talking about boost, or any other myriad of items that could be logged. You see, the Data points that almost all dataloggers use are SAE. Now, SAE standards are nice, BUT they are not designed for someone to do calibration from. They are for repair shops to help diagnose issues with vehicles. So, the level of precision, and refresh rate is not what's needed to do proper calibration development. If you are using a data point with a 200ms refresh rate, but the actual value in the ECM refreshes every 8ms, then the ECM is updating 50x more frequently then what you are watching. Again, you start to see where the issues happen and it's easier to understand why we do not treat the EcoBoost like any other engine before it.
Can someone get lucky and eventually end up with a tune that works by looking at the wrong data? Absolutely. Can they repeat those results over and over again without starting from scratch each time? Usually not. And it all stems from having the right knowledge, and data in the first place.
To make it a little easier to picture for most people. If Ford, GM, Chrysler, or any auto manufacturer could spend $30-50 on hardware to datalog and do calibration, why don't they? The answer is simple, you can't, it takes 10's of Thousands of dollars to have the right hardware just for the process to begin.
Sorry for the lengthy post guys, but inaccurate info will only convolute the issue further.