Late to the party -- sorry.
These scans look fine with the exception that the car is just not making the power. The ES power is a calculated value but nevertheless gives a reasonable idea as long as the entire logfile isn't uphill/downhill.
- Max power with the Everest was 125 bhp.
Observations that may help you eliminate areas to look at:
- Max boost 0.97 bar
- Timing at idle around 16° BTDC
- Secondary throttle is operating
- EGR valve is operating
- O2 sensor appears to operate normally
- 1 knock event with no timing retard applied -- minor (I'd ignore)
- Air/fuel ratio 14.7 except under high boost when it drops as per normal
- Coolant and MAT values look fine
I then looked at some individual events more carefully so all of the graphs below have in common:
1. WOT (wide open throttle) as reported by ES
2. 3rd gear only acceleration runs
3. The graphs are 6-7 seconds long
The first graph is with Everest chip and shows left Y-axis as Boost (Solid line), right Y-Axis as RPM (Hashed line) and X-Axis as Time in secs.
Here you can clearly see the RPMs falling back, along with a quite marked variation in boost.
The next graph is the same event (Everest run) with right Y-Axis as Power
This quite clearly shows a substantial variation in power

So to try to see if it was the Everest chip I looked for a similar event with the std chip ES.
The graph below is with std 1499 chip and clearly shows the engine RPM dropping back and the variations in boost. The RPM dropback is much less than on the Everest run and was probably hardly noticeable in driving but nevertheless it is there so logic suggests it is something to do with the car and not the Everest chip.

So what might be causing all this ? The speculation below is worth what you're paying for it:
1. Always worthwhile to check both ends of the engine earth which connects to intake manifold at timing belt end (beneath lifting eye) since all the engine sensors ground via this.
2. Is it possible one or other of the cams is a tooth out from changing the cambelt ? No offence -- I'm just asking.
3. It is possible one or more of the fuel injectors can't keep up but that doesn't make sense since even with the Everest they're only at max doing 80% Duty cycle.
4. A boost leak is possible so see the
excellent WIKI for JonT's method.
5. My real gut instinct is the same as John_W's -- blockage in either precat or exhaust.
Reasons:
- Grandad who builds model aircraft engines and exhausts from bare metal says exhaust condition and design affects power enormously.
- In the graphs the boost is building to max, dropping back, building again, and so on. Exhaust blockage in a normal car reduces power but in a turbo car may also "stall" the turbo which then takes time to spin back up and also to build the pressure in the intake manifold which appears to be what we're seeing.
- There are 0 instances of overboost which one would expect with sticky wastegate, duff boost control valve, so it appears something else is causing the boost falling back.
- In the Std 1499 graph you can clearly see the boost is taking longer to recover as the revs rise.
- Elanscan stops at the O2 sensor so doesn't know what's going on in the exhaust or how fast the turbo is spinning. All ES is telling us is that this is happening but all the rest of the readings look normal to me so it is probably something ES can't see. 2p