Why is this ECU staying in closed loop at WOT?

[Gernby]

I'm doing an eTune for a customer that lives at a high altitude, and am getting strange issues with open / closed loop. I have selected "Use MAP to determine WOT", and have set the WOT determination pressure to 700 mBar or less. I have also set the WOT lambda adjustment values to 12.46 for columns 6-10. When the car is at WOT, the MAP value is about 800 mBar, which I expect should cause open loop with a target AFR of 12.46. However, The ECU stays in closed loop, and applies negative STFT's to maintain an AF in the 13's. Why is it doing this?

Also, is there any way to verify which calibration was used to create a datalog? I had to ask the customer to repeat the set of datalogs once, since I suspected he might not have used the new calibration file I sent, which had adjustments to the WOT determination pressure and target Lambda...

FlashPro SS# = FP-S2K-US-30227
FlashPro Manager = 1.2.8.0

Datalog and calibration are attached.

[Spunkster]

Since you aren't sure if the calibration matches the datalog it's hard for us to look into this as a possible problem. Devise a way to make sure the calibration has been uploaded with the person and then go from there.

[Gernby]

Since you aren't sure if the calibration matches the datalog it's hard for us to look into this as a possible problem. Devise a way to make sure the calibration has been uploaded with the person and then go from there.

I understand your point, but it would not really be possible for me to know for sure that someone else used a calibration I sent. That's why I was hoping that the FlashPro or FlashPro Manager would somehow embed the name of the calibration that was used within the Datalog. Even if I ask him to repeat the datalog for a 3rd time, I still wouldn't know for sure. The datalog that I posted is from the 2nd time that he datalogged them, after I told him that it seemed like he datalogged the wrong calibrations. After I received the second set of datalogs still showing the issue, I emailed him again, and asked if there was any way possible that he might have mixed up the calibrations. He said that he checked the files again, and didn't think it was possible that he mixed them up. I've only sent him 1 set of base calibrations, and a 2nd set of customized calibrations. The file names of the 2nd batch are very different from the base calibrations, so it would have been hard to mix them up anyway, especially twice.

[Hondata]

In the datalog it appears that the WOT compensation tables are around 13.2:1

I would suggest changing something which will give an obvious response on the datalog. eg change the VTEC point, limit the short term trim.

[ajpturbopittsburgh]

In the datalog it appears that the WOT compensation tables are around 13.2:1

I would suggest changing something which will give an obvious response on the datalog. eg change the VTEC point, limit the short term trim.

I know this is an oldie but Hondata when I look at his cal. and the datalog and map trace the datalog the boxes that are highlighted in the low and high WOT adjustment tables show 12.46 like the OP says and not 13.2 like you said. Am I missing something?

[Hondata]

The calibration shows 12.5:1 but the datalog shows 13.2:1 therefore the datalog was not made with that calibration.

[Gernby]

After a 3rd attempt, the datalogs finally showed something I expected to see. I believe the customer needed to improve his file management.

[Hondata]

If there was an easy, robust, way I would link datalogs to calibrations.

[Gernby]

If there was an easy, robust, way I would link datalogs to calibrations.

When I was studying the CAN data to identify all the traffic on the bus for my CAN Dyno, I found that there was some sort of random hash code for each flash that stayed constant all the time UNTIL the next flash, so it seemed to me like you could record that hash code with the calibration at flash time, then record that same hash with each datalog.

I've considered doing that very thing with my CAN Dyno to associate my datalogs so that I can identify which dyno plots came from each FlashPro calibration.

[chneo1982]

Hi Gernby,

I am facing the same problem.

I have set 'MAP WOT determination pressure' to 0.1 bar from 4500rpm to 9000rpm.

But after 4500rpm ECU did not switch over to open loop, it continued trimming fuel to the targeted closed loop AFR at 14.7.

I have read in the help file that changing values (to a leaner AFR) in the WOT lambda adjustment tables can cause the ECU to stay in closed loop. Hondata recommends not to change the values to anything above 12.5 AFR. But the weird thing is, most values in the table are leaner than 12.5.

I do not understand what they mean by 'above 12.5'. Is 12.4 above 12.5 or 12.6 above 12.5? WHich direction do they mean?

I have also adjusted the WOT Lambda target to 12.46 like u did, which is richer than the values in the original WOT table. Since Hondata says changing values to a leaner one will cause the ECU to stay in closed loop, i do not understand y my ECU continues to stay in closed loop since the new values are richer.

Could u advise?

[Gernby]

If the MAP value goes above the WOT determination pressure AND the target value in the WOT labmda adjustment table is numerically higher (leaner) than 12.5, it will remain in closed loop and target that value using LTrim and STrim. That winds up being a very nice feature if your O2 sensor is accurate. Unfortunately, most of the OEM sensors are NOT accurate at all in the richer part of their operating range.

[chneo1982]

I will check my calibrations again and test it again.

Thanks Gernby!

[chneo1982]

My ECU still stays in closed loop. There shouldn't be anything wrong with the calibration.

See below:



I wanted open loop after 4500rpm, therefore for the MAP WOT determination pressure table, i set the MAP to a very low value after 4500rpm onwards.

I have also set values in the WOT Lambda adjustment table at below 12.50 at 4500rpm onwards.

Is there anything wrong with the way i set these values?

My car is a '08 Japanese Civic Type R FD2 and i am using the 'Civic SI RRC 2 reflash injector 310 FD2 hondata type R reflash' calibration.

Can anyone advise me? Thanks in advance!

[Gernby]

You should post your calibration and a datalog showing the issue.

[chneo1982]

THere u go...

Apparently someone else asked the same question more than a year ago.

viewtopic.php?f=27&t=12462