Was able to get out and do some preliminary dyno testing. Granted, the car has only 200 miles on it. So much more will come. Testing was done on ~94 octane with carbon filters removed. After the stock runs in 4th and 5th gear I did a few Stage 1 tuned runs just for comparison. While the car makes more power in 5th on the dyno it hits the 155mph speed limiter at around 6200rpm. In 5th gear on the dyno the DCT also decided to lower its torque targets in the 4500rpm range.

Since I mainly just wanted to get some baseline figures I didn't spend too much time digging in to what is going on there. But I saw similar behavior in our N55 DCT 135i before we were able to resolve it on the tuning end.

Net/net happy with the figures. Next up I'll do some VBOX runs and work on stronger tune development as my schedule permits.

At least it's a good answer but don't we want to see what this thing does right of the showroom floor?

There are plenty of 100% stock runs. I was more interested in a realistic baseline to use as an evaluation for future tuning performance. Since I run ~93 octane most of the time along with the carbon filter delete no reason not to get them included in the baseline.

There are plenty of 100% stock runs. I was more interested in a realistic baseline to use as an evaluation for future tuning performance. Since I run ~93 octane most of the time along with the carbon filter delete no reason not to get them included in the baseline.

I've seen baselines vary quite a bit so I was curious what the Specialty Z Dynojet would say.

A 566 wheel baseline with charcoal delete and ~94 is pretty crazy.

Any idea why there is a torque spike down low which gives a big torque peak?

That is awesome!!! Burger Motorsports FTMFW. I cant wait until the new M4 comes out. I'm over my 335 and ordered a 14 991S, but looking forward to the M4 tuning. I will always direct potential customers to you. Best of luck.

the real 1/4 mile is, 11.49@126.72, so the vbox reads high. by the way i sold my vbox after 2days from buying it, it's not accurate

Actually, it's spot on perfect. This is what the VBOX recorded during that 11.49@126.67 run.. 11.52@126.72. The thing is you need to use the right site to interpret the VBOX file. You can't just go off a photo of the VBOX or the iPhone app because they read absolute traps rather than an average of the last 60'. So you get traps about 1mph inflated. You need this verified file from vboxtools.com to get a realistic trap. I just didn't bother posting it above as we're so early in testing.

Now note at the track slope is only -.189%. The program allows up to a -1% slope for a valid 1/4 mile time. So if you test in a non-level surface then you can easily get a better time. Not to mention you can test in optimal conditions where no real track would ever be open. So take VBOX times with a grain of salt but if they post a verified file like this then it's as close to legit as it can be outside of a real timeslip.