- serial number of your FlashPro=FP-SI-INT-20243
- FlashPro Manager version=1.2.2.0
- the calibration=don't have access to the calibration
- a datalog of a problem= attached
- what sort of vehicle you have=Euro CTR FN2
- what sort of ECU you are using=OEM ECU
- anything about the car which has been modified from stock which may affect the ECU=0
- a specific description of the problem=follows
1.When flashpro is connected to the ecu AFR is like fuel maps are but when disconnected then goes lean,when usb cable is connected again AFR returns to normal.
After uploading the calibration 2-3 times then AFR worked properly with flashpro disconnected.
2.After a new calibration uploaded after some changes on mechanical parts of the engine took some datalogs with flaspro connected to the ecu and discovered that parameters were different than original map like V-TEC point [~3400rpm] - Ignition and had many knocks with no knock retard.
When flashpro disconnected v-tec point went back to original calibration which is at 2800rpm can't tell about the knocks and ignition advance.
datalog 1 is the last dyno pull after new calibration uploaded
datalogs 2,3,4 are after few days on a road test
ECU reacts different when connected to Flashpro.
ECU reacts different when connected to Flashpro.
- Attachments
-
- datalog4.fpdl
- (72.1 KiB) Downloaded 199 times
-
- datalog3.fpdl
- (266.34 KiB) Downloaded 208 times
-
- datalog2.fpdl
- (46.25 KiB) Downloaded 190 times
-
- datalog1.fpdl
- (10.58 KiB) Downloaded 215 times
Re: ECU reacts different when connected to Flashpro.
nice help to my problem!Spunkster wrote:http://www.hondata.com/forum/viewtopic.php?f=29&t=10108
thanks for your precious time!
Re: ECU reacts different when connected to Flashpro.
without the calibration it is impossible to speculate. We ask for all this information as it is very important.
Re: ECU reacts different when connected to Flashpro.
Spunkster wrote:without the calibration it is impossible to speculate. We ask for all this information as it is very important.
and how on earth the calibration can help for a problem that it's obvious can't produse it?
how a calibration can react just by connect or disconnect the flashpro to the obd2 and changes AFR or other parameters????
don't have access to the calibration coz my tuner keeps it locked so i can't provide you that info.
if you're rejecting my request for help just because of this then only i can say is that you've found a good excuse to avoid searching for answers for just another possible firmware error-bug or whatever!!
i'll try 1.2.5 to see if these errors occur again!
thanks again for your 'help'.
Re: ECU reacts different when connected to Flashpro.
Typically we look at the calibration to see what error codes are been disabled, what the compensation tables are like, what the shape of the fuel tables is like - anything and everything that can cause a problem.
I'm not sure that I fully understand your problem report. If you plug in the FlashPro, and the AF changes, then it cannot be software, firmware or anything other than a ground current flow.
I'm not sure that I fully understand your problem report. If you plug in the FlashPro, and the AF changes, then it cannot be software, firmware or anything other than a ground current flow.
Hondata
Re: ECU reacts different when connected to Flashpro.
fuel changes was the first issue but solved after calibration uploaded 2-3 times.
recent issue is that v-tec point went to 3400rpm from 2800 when flashpro was connected and went back to 2800 when disconnected!
anyway your answer is more helpfull than previous and i'll see if there are any ground issues.
recent issue is that v-tec point went to 3400rpm from 2800 when flashpro was connected and went back to 2800 when disconnected!
anyway your answer is more helpfull than previous and i'll see if there are any ground issues.
Re: ECU reacts different when connected to Flashpro.
calibration uploaded again after FPM 1.2.5 downloaded.
first datalogs with no issues so maybe its was a 1.2.2 bug
first datalogs with no issues so maybe its was a 1.2.2 bug