NefMoto

I'm thinking this can be fixed using KFLDRL? (non stock exhaust)

This only happens in higher gears where it takes longer to climb up the revs.

Any suggestions?

...and yes, I know I'm pulling timing

Cheers guys

log link (wouldn't let me upload) -> http://s000.tinyupload.com/?file_id=05959996654525825869 (http://s000.tinyupload.com/?file_id=05959996654525825869)

(https://i.ibb.co/89CNXV7/boost.gif)

Why are you taking a screenshot? Just use file->export.

Might want to dial back Q2

Thank you, I didnt know you could do that!  :o

I'll dial it back and re-log.

Any other suggestions?

Just realised that I'm only overshooting on boost and not on load.

Its like boost and load de-sync at 3000 revs until 4000, see pics.


Whats causing this drop notch at 3500?  ???

I was thinking of just filling KFLDRL with 90s after 3000 onwards as to force the correct flow by 'numbing' the PID?

The pid cares about boost, not load.

covered in the wiki. VVT


No. You can reduce the slope of KFLDRL near the top (which would require increasing the slope elsewhere) but flattening it doesn't make much sense. If you are going to play DRL games, best to switch to IMX boost precontrol entirely.

Failing that, just numb Q2.

Okay, so the PID controls boost alone, I know there is ALOT of factors that controls the boost/load relationship so I'm not gonna go there just now. ;D

It had crossed my mind it could be the VVT causing the notch but the whole time fnwue≈0 (0.04 max) and intake cam shaft angle is only ever -/+ 1 away from 0 so surely it isn't VVT ???
 

There are other factors, you'd have to trace the FR to track them all down, but in general its IAT and VVT.

Finally sorted it! ::)

This is my way of fixing it, a bit of a hack but safe if respected.

I just set everything in KFLDRL after 3750 (where oscillations start) to 90 (this is whatever waste gate u want for desired boost).
Because the linearization map is the final "filter" for the PIDs, you render every "PID" (WG) outcome to your given set values in KFLDRL, like an override  ;D

Kinda semi-open loop, let the PID deal with spool and peak boost then KFLDRLs control overrides the dumb PID.  ;D
Because of this I had to numb KFDLULS as I did throw a P1555 code = limp mode.

You have gotta be careful you don't mess up partial throttle so a good map blend and logging helps.

It's not a fix. Youre totally ruined part throttle with that

I never drive over 3500 in partial throttle and below that part of the map is stock.

Not just that but he's ruined the entire point of the PID. altitude variance, temp variance, humidity variance... all of it will not be handled, and eventually he may throw a code.

Why not just numb Q2 like we told you to?

Not ideal, I know lol  ;D I'll give it one last try messing with the PID, Q2, okay.

You are the dumb one, not the PID.

Sorry mate didnt mean to offend any me7 purists out there.  ;D

PID tuning is testing at the best if times, just happy to have smooth power again.

No, it is not "testing at the best of times".
That's the difference between copy-paste monkeys and people who understand how things work.

Someone who understands how the PID works can have it adjusted in 4-5 pulls. Someone who is a monkey that just mashes buttons can do it all day and get nowhere.
Goes without saying for a LOT of other concepts too.

Absolutely nothing to do with ME7 here. Just total lack of basic knowledge in control systems.
There are plenty of books and online resources that explain exactly how a PID works, how to tune it from scratch etc. Hell even the FR briefly explains it.

It's pure math.

I've done a fair bit of research on the subject and have a solid understanding in PIDs, I'm just not spending anymore time - tried for about 18 months already - tuning it.

With regard to copy and paste monkeys, believe me mate you're preaching to the choir, I've got over 1GB of logs so please know I've put work in!

Yet I probably would have it behaving as needed in max 2 hours on your car...

It's exactly what I am talking about. You are randomly modifying things without understanding of the system. Of course you're never going to get anywhere with it. You can probably spend all eternity on it - there are too many variables to get right randomly.
But calling it dumb makes you look... well... dumb :P

Pretty sure you don't have a "solid understanding", otherwise we would not be having this discussion.

just edit KFLDIMX properly and you will have stable control without problems