Unknown reason for boost cut in high gear at 5000 rpm

[tekstil]

Looking at the pictures I'm assuming you are running stock turbo with stock AANABY file. MAP limit for 5000rpm is 270 so you are not hitting that. As I wrote before I had exact same issue at 5200rpm when N75 dropped to zero and then after a second came back up, just like your log file. 5200rpm MAP limit is 263kpa so nowhere near hitting that.
If you look at the base WGDC pilot map and open it in graph mode you can see that it starts to climb up at 4500rpm and reaching its peak at 5000rpm falling down afterwards. I don't think such a "hill" is needed in that area, I would smooth it out from 4000 to 6000rpm to test it out, and afterwards you can add little bit duty cycle back if you see that you are losing boost in that area. You can smooth out the initial turbo overshoot at 3200rpm by lowering duty cycle at 3000rpm. If I remember correctly N75 was at 100% almost all the logs I had with this issue so I think that N75 just crashes for some reason.

Also if you are going to play with this ECU more seriously I'd strongly recommend to use Megalogviewer HD for viewing logs. Way better to read, configure, add graphs and so on, matrix tables etc so for example you can create "VE table" in there and see instantly where you need to make adjustments. It's paid version though but IIRC one payment got you 3 keys, so you can share the costs with other people.

[-ice-]

Agree. Additionally I recommend to avoid calibrating a big difference between requested boost and actual boost (simply to avoid the ECU to become suspicious).

This N75=0 thing is clearly that the ECU detected a fault, I think its not a bug in prjmod. Many people including me had this behaviour and it went away with tuning the boost/N75/thresholds right and of course have intact knock detection.


Way better to read, configure, add graphs and so on, matrix tables etc so for example you can create "VE table" in there and see instantly where you need to make adjustments.

Thats interesting. WinLog should also have such Matrix mode, but never tried it out. Can you show some screenshots of Megalogviewer?

BR

[fivebanger12453]

Thank you guys for your input again!
I was very busy, so had no time to answer...

I'm already using MegaLogViewer for ME7 stuff.

I will upgrad my S2 with a modified K24-7000 which is rated for 360hp. So there will be some mapping needed in the near future.

I'm interested in how to create the VE table in MegaLogViewer. I notice a lag in low rpm range and I think it is due to lean mixture. My wideband O2 shows lean in that range. What would be your suggestions?

[tekstil]

VE table, using same axis as in Tunerpro. You need to have your wideband logging AFR in Winlog to use delta function. In this example it is setup in such way that negative values show areas, where fuel should be removed (ideally, in reality it all depends on various factors etc and you actually have to check whole log to confirm necessary adjustments in specific areas). Also you need to use different custom data filters in conjunction with this.