Hondata

Hi Hondata,
maybe a tip for a new feature in Flashpro: I would found useful if it is possible in the XY Graph to also export (or copy to clipboard) the mean values from which you plot the graph - this would allow to speed up the AFM sensor calibration for us who use AFM (e.g. if you plot AFM.v vs ...

It's better for me as well, thanks!

As CivicRSA says, I do nothing else than what is described above.
1) Take GroupN map, upload - the car works ok.
2) Update 6 cells in "cam angle low" table, upload - the car's k.control goes to 121% immediately after starting up the engine.

I think that this strange behavior was introduced with the ...

Hi, I did the testing and following results came out: stock equivalent calibration and groupN calibration work ok. However, as soon as I change cam angle tables, the symptom comes in again - knock control goes to 121%. I only changed 6 cells in the low cam table from 45* to 40* (cols 8-10, lines ...

I also just tested it with newest version and still having the same problem...

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 ...

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...

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

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 ...

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.

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 ...

the Map cal

see attachments

- 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 ...

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 ...