K.Control having weird values in a MAF cal

jan.vajsejtl · Post by **jan.vajsejtl** » Wed Aug 18, 2010 12:42 pm

Hi,
I am having troubles using a MAF calibration in an FN2.
If I use a MAP calibration, K.Control has value of 0 and the car runs very well. However, when I upload a MAF calibration (new GroupN, only MAF sensor values edited), the K.Control immediately goes to 122 and stays there for ever, it does not change even after an hour of driving. The K.Control=122 means that the ignition is severely retarded and the car does not go and shudders a lot. When I upload my MAP cal again, K.Control goes immediately to 0 and everything is fine again.
Has anyone experienced similar behavior? I am using Flashpro version 1.1.6.2; the car has CAI, RH, exhaust, RRC and IM.
Thanks
Jan

Post by **Spunkster** » Wed Aug 18, 2010 1:23 pm

http://www.hondata.com/forum/viewtopic.php?t=10108

jan.vajsejtl · Post by **jan.vajsejtl** » Wed Aug 18, 2010 1:56 pm

- serial number of your FlashPro: FP-SI-INT-20441
- FlashPro Manager version (not 'the latest'): 1.1.6.2
- the calibration (as an attachment): in TAR
- a datalog of a problem (as an attachment): in TAR
- what sort of vehicle you have: FN2
- what sort of ECU you are using: OEM
- anything about the car which has been modified from stock which may affect the ECU: CAI, RH, exhaust, RRC and IM
- a specific description of the problem:
If I use a MAP calibration, K.Control has value of 0 and the car runs very well. However, when I upload a MAF calibration (new GroupN, only MAF sensor values edited), the K.Control immediately goes to 122 and stays there for ever, it does not change even after an hour of driving. The K.Control=122 means that the ignition is severely retarded and the car does not go and shudders a lot. When I upload my MAP cal again, K.Control goes immediately to 0 and everything is fine again.

Post by **Spunkster** » Wed Aug 18, 2010 3:47 pm

don't compress the files, just attatch them so they can easily be looked at.

jan.vajsejtl · Post by **jan.vajsejtl** » Wed Aug 18, 2010 9:52 pm

see attachments

jan.vajsejtl · Post by **jan.vajsejtl** » Wed Aug 18, 2010 10:03 pm

the Map cal

jan.vajsejtl · Post by **jan.vajsejtl** » Mon Aug 23, 2010 1:24 pm

I tried to "Return ECU to stock" - and here it works fine, the K.Control starts at 55 and slowly descreases during the drive (see datalog attached). Considering all of this, it seems that there is a bug in the FlashPro, it works fine in stock ECU & MAP calibrations, but does not work in MAF calibrations. Any thoughts, Hondata?
Thanks
Jan

Post by **Spunkster** » Mon Aug 23, 2010 2:25 pm

The person that does the software is away for 2 weeks and will have to look at this when he returns.

jan.vajsejtl · Post by **jan.vajsejtl** » Tue Aug 24, 2010 12:10 pm

Fine, tx for the info. I did some more tests and it seems that the "stock fn2 ecu" works fine, however when I touch the cam angles, it stops working - the k.control goes immediately to 122.

jan.vajsejtl · Post by **jan.vajsejtl** » Sun Oct 03, 2010 3:36 am

I have tried the new 1.1.6.3 FP version, however the problem still remains. When I upload a MAF calibration, k.control goes to 121% and the ecu puts significant retard on ignition - see the attached datalog. MAP calibration behaves normally, the k.control is =0%.
Can I hope for resolution of this problem? I would like to use MAF cal for daily driving as the FN2 with MAP cal looses fuel indicator...

jan.vajsejtl · Post by **jan.vajsejtl** » Wed Oct 06, 2010 2:10 pm

Hondata, can you please issue some statement to this problem? Am I the only one experiencing this?

Post by **Hondata** » Thu Oct 07, 2010 7:55 am

You need increase your ignition knock limit values.

jan.vajsejtl · Post by **jan.vajsejtl** » Thu Oct 07, 2010 10:56 am

But can you explain why that only happens in AFM calibrations? Why that also happens in GroupN AFM map? Only stock OEM AFM map behaves correctly!
I do not want to change knock limits and loose knock control that is implemented in the ECU...

civicRSA · Post by **civicRSA** » Sat Oct 09, 2010 11:41 am

I've also noticed this with the FN2's AFM calibration. When using a calibration made in 1.1.5.6 and simply opening it in 1.1.6.3 and saving and uploading the knock control goes to 121% and the ecu retards a lot of timing. What is the reason for this?

jan.vajsejtl · Post by **jan.vajsejtl** » Sun Oct 10, 2010 11:57 pm

Exactly, I started observing this behavior from the version with the new knock control tables - before that, it behaved correctly. However now I am not even able to run the "FN2 GroupN reflash" map as it retards the ignition heavily... Only the "stock equivalent" AFM map is fine but as soon as I change one cam angle (!) the k.control goes crazy.