recent anomaly in engine performance... flashpro bug?

2012+ US/Canadian Civic Si / 2013+ ILX
Post Reply
iketh
Posts: 44
Joined: Sat Apr 12, 2014 7:55 pm

recent anomaly in engine performance... flashpro bug?

Post by iketh »

at exactly 0:20:39.897 of the log, spike in MAP without a change in tpedal or tplate... started about 2 weeks ago and can be felt while driving (almost feels like a misfire) and always occurs at exactly 4100 rpm
Attachments
datalog0001.fpdl
(4.17 MiB) Downloaded 209 times
User avatar
Spunkster
Site Admin
Posts: 22703
Joined: Fri Sep 20, 2002 5:06 pm
Location: Hondata

Re: recent anomaly in engine performance... flashpro bug?

Post by Spunkster »

You have not posted your calibration
User avatar
Hondata
Site Admin
Posts: 10428
Joined: Thu Aug 15, 2002 12:13 pm
Location: Torrance, CA
Contact:

Re: recent anomaly in engine performance... flashpro bug?

Post by Hondata »

Are you sure you have the time in the datalog correct (20:39)? Everything looks ok at that point.
Hondata
iketh
Posts: 44
Joined: Sat Apr 12, 2014 7:55 pm

Re: recent anomaly in engine performance... flashpro bug?

Post by iketh »

20:39.9 spike in map from -6.8 to -5.3"/psi and massive spike in injectors/duty
Attachments
2.43.fpcal
(23.25 KiB) Downloaded 180 times
iketh
Posts: 44
Joined: Sat Apr 12, 2014 7:55 pm

Re: recent anomaly in engine performance... flashpro bug?

Post by iketh »

duty jumps from 30 to 36% and injectors 9.06ms to 10.61ms
User avatar
Hondata
Site Admin
Posts: 10428
Joined: Thu Aug 15, 2002 12:13 pm
Location: Torrance, CA
Contact:

Re: recent anomaly in engine performance... flashpro bug?

Post by Hondata »

This is what I see at 20:39. Everything looks ok.
throttle-dl.png
throttle-dl.png (12.18 KiB) Viewed 7689 times
The only thing I have noticed is that just before (around 20:36) you go from closed loop to open loop, the switch being 80 kPa. Because you have set the WOT compensation tables over 12.5:1, it may do odd things like staying in closed loop - see the help file (do not set the WOT compensation values over 12.5:1).
Hondata
iketh
Posts: 44
Joined: Sat Apr 12, 2014 7:55 pm

Re: recent anomaly in engine performance... flashpro bug?

Post by iketh »

39.9... you're forgetting the .9... look at injectors and map
iketh
Posts: 44
Joined: Sat Apr 12, 2014 7:55 pm

Re: recent anomaly in engine performance... flashpro bug?

Post by iketh »

it doesn't matter what type of tune I use, they all have that 4100rpm hiccup
iketh
Posts: 44
Joined: Sat Apr 12, 2014 7:55 pm

Re: recent anomaly in engine performance... flashpro bug?

Post by iketh »

22:06.195s injector spike from 13.46 to 17.83 again at 4100rpm... that's not ecu doing something weird with closed loop, that's a bug in the hidden fuel tables for AFR tunes (the tune is the same I attached above)
Attachments
datalog0002.fpdl
(2.86 MiB) Downloaded 205 times
User avatar
Hondata
Site Admin
Posts: 10428
Joined: Thu Aug 15, 2002 12:13 pm
Location: Torrance, CA
Contact:

Re: recent anomaly in engine performance... flashpro bug?

Post by Hondata »

As pointed out above, it is because you have changed the WOT compensation tables to values leaner than 12.5:1. The weird injector duration is from the secondary o2 sensor running PRISM as higher load than it was designed for.
Hondata
iketh
Posts: 44
Joined: Sat Apr 12, 2014 7:55 pm

Re: recent anomaly in engine performance... flashpro bug?

Post by iketh »

sigh I already tested that... I will switch back to open loop and upload another log... also for this application 13.44 is the ratio when it remains closed loop not 12.5....
iketh
Posts: 44
Joined: Sat Apr 12, 2014 7:55 pm

Re: recent anomaly in engine performance... flashpro bug?

Post by iketh »

also secondary o2 sensor is disabled
User avatar
Hondata
Site Admin
Posts: 10428
Joined: Thu Aug 15, 2002 12:13 pm
Location: Torrance, CA
Contact:

Re: recent anomaly in engine performance... flashpro bug?

Post by Hondata »

In the first datalog at least, the jump in injector duration at 20:39.9 is from the closed loop to open loop transition at 80 kPa. I don't see any change in MAP.
You need to change the WOT compensation tables so that no values are greater than 12.5:1 It does not matter if in open or closed loop or if the o2 sensors are disabled, WOT compensation table values should not be greater than 12.5:1.
Hondata
Post Reply