Hello Hondata. I noticed a weird ignition graphing while logging a WOT run. If you look at times 18:347, 23:353, 23:585, 27:186 and 27:369. At the first time stamp the ignition starts at 24 degrees and it dips to 18 degrees like super fast then jumps right back to 22 degrees. It happens again 4 more times. I can feel a slight hesitation when it happens. It's not super obvious but I can definitely feel it and it's a little annoying. If you can take a look at the log to see if anything is off that would be great. Here's the cal also. Thanks guys.
One more thing I'd like to add is this never happened until I lowered my boost control frequency to 38Hz from 50Hz because I needed more resolution in the boost control.
Weird Ignition after shifts in WOT under boost
Weird Ignition after shifts in WOT under boost
You do not have the required permissions to view the files attached to this post.
I don't think it matters what ignition table we're running. I've had this since the day I've owned my FlashPro and just shrugged it off as a weird behavior in the ECU since I could find no parameters that reference it. In all my datalogs it looks like a random 5* ignition retard after a shift... even with warm up ignition enabled. For reference, here's a datalog from a year ago when I was running 32* ignition. Ignore the fact I'm in closed loop at WOT, had a fun time toying with the lambda tables back then (hehe). And then a recent (week old) datalog & calibration that has me running 27-28* ignition. I've commented both datalogs.
I have this happening in e-tunez customer datalogs as well... It's not something that seems to affect N/A tunes negatively since it's so momentary, but I can see it being quite annoying with F/I tunes. I've seen it happening on the low cam as well. I've got dozens of datalogs showing this behavior. Kind of curious where it's coming from...
I have this happening in e-tunez customer datalogs as well... It's not something that seems to affect N/A tunes negatively since it's so momentary, but I can see it being quite annoying with F/I tunes. I've seen it happening on the low cam as well. I've got dozens of datalogs showing this behavior. Kind of curious where it's coming from...
You do not have the required permissions to view the files attached to this post.