- FlashPro firmware updated to version 122.
- [FN2] Fixed max fields not showing for active tuning.
- [2016-2017 Turbo Civic] Added boost by gear limit table and added support for 5AG-P92 - Malaysia, 5AG-Z82 - Thailand, 5AG-U62 - Indonesia, 5AG-Q71 - Australia
FlashProManager 2.8.4
FlashProManager 2.8.4
V2.8.4 (21 September 2017)
Hondata
Re: FlashProManager 2.8.4
Quick question?
Will knock control default back to 100% after I upload a calibration using this new 2.8.4 software?
I read somewhere that you defaulted it to 56% knock control value after a reflash for a faster dyno tuning.
The reason I asked is prior reflash, k.control is 54%. After reflash a a quick drive it is at 75%
2017 civic 1.5 cvt
100RON Fuel at +6psi tune, bonestock car.
Thank you!
Will knock control default back to 100% after I upload a calibration using this new 2.8.4 software?
I read somewhere that you defaulted it to 56% knock control value after a reflash for a faster dyno tuning.
The reason I asked is prior reflash, k.control is 54%. After reflash a a quick drive it is at 75%
2017 civic 1.5 cvt
100RON Fuel at +6psi tune, bonestock car.
Thank you!
Re: FlashProManager 2.8.4
How much time is expected of driving to go back to 0% at 100 octane fuel?
Re: FlashProManager 2.8.4
Thanks Hondata,
I noticed that when cruising, k.control is steady at 54%
When boosting hard at 20psi(+6psi basemap) map for 2017 civic 1.5cvt, k.control quickly rises to 70% w/o any knock count? Im using 100 RON fuel.
Same fuel i use on my d16 turbo with 450whp no problems.
What seems to be the issue?
Thanks!
Re: FlashProManager 2.8.4
This is normal. Knock control will vary based on engine noise, it does not need to have knock to alter the knock control.
Hondata
Re: FlashProManager 2.8.4
What he wanted to say is that knock control is not 0% on cruse (as it was few versions before) but its 56% even he uses 100 octane fuel.
Re: FlashProManager 2.8.4
knock control will never be 0% on pump gas. probably wouldn't even hit 0% with race gas?
54 is the lowest it will go on 93octane. 100ron = 95.5 octane
Re: FlashProManager 2.8.4
I have in Europe 100 octane gas. It was 0 before.
Re: FlashProManager 2.8.4
Thanks hondata, to sum it up. Here are the outside factors which affect k.control, being all things equal.
1. Fuel octane
2. Ambient air temp / humidity / elevation
3. Engine load/RPM
Did I miss something?
Thanks!
Re: FlashProManager 2.8.4
Active Tuning does not work for the FN2 or I am running in the wrong direction.
https://youtu.be/lKQUORqRif4
Please, if a major feature is released - explain how it must be used. A short 2 minutes screencast will answer a lot of questions...
Screencast-O-Matic is a cool simple tool to create screencast very quick.
And I can also confirm on the FN2 the K.Control will be reset back to 55 % after flashing...
https://youtu.be/lKQUORqRif4
Please, if a major feature is released - explain how it must be used. A short 2 minutes screencast will answer a lot of questions...
Screencast-O-Matic is a cool simple tool to create screencast very quick.
And I can also confirm on the FN2 the K.Control will be reset back to 55 % after flashing...
Re: FlashProManager 2.8.4
There's two aspects here - the active tuning process and viewing the results of active tuning. You can't blanket both with one statement.
First, to download changes from the ECU you need the calibration as saved after an upload. Downloading from the FlashPro is going to get the calibration as saved before the upload, so it will not work.
Next, it does not work from datalogs, but changes are download directly from the ECU.
Yes, a video would help.
First, to download changes from the ECU you need the calibration as saved after an upload. Downloading from the FlashPro is going to get the calibration as saved before the upload, so it will not work.
Next, it does not work from datalogs, but changes are download directly from the ECU.
Yes, a video would help.
Hondata
Re: FlashProManager 2.8.4
The active tuning tables were sucessfully downloaded from FN2 ECU, although some attention is needed to this points:
- Maximum load and Maximum lambda is fixed, unable to change;
- Minimum values could be greater than Maximum values;
- Restrict maximum values to calibration;
Example: When insert Maximum VTC like 300 the value changed to 65 and
the maximum value for the calibration used is 50;