Page 1 of 1

Issues after upgraded to 1.1.4.6 beta

Posted: Wed Mar 24, 2010 8:05 am
by chris2000
All cars mentioned below is FD2R.

I was using 1.1.3.4 since its release in January.

Need to help a friend tune and got a basemap that was done on 1.1.4.6 so i had to upgrade my software to 1.1.4.6 beta.

1st car i did was a new flashpro with the 1.1.4.6. Everything went out fine till i run out of injector cycle. So this car now waiting for bigger injectors before the next tune.

A few days later on this Monday, a friend datalogue his car and wanted me to check his tune as it was done last year with a very early Flashpro manager and he felt the car not so smooth now. Took the flashpro unit from him and plug to my laptop and it prompted for firmware upgrade which is normal as the earlier car i did was same.

To my suprise datalog shows that the car was running on 0 map pressure regardless on TPS and rpm. We then connect the flashpro on the obd2 and online the connection and confirm that it only show 0mbar map pressure. 1st thing to mind was a faulty map sensor on the FD2R that only did 55000km. We went and bought a new MAP sensor and install it. Connected the flashpro again to check was to shock to see the NEW MAP sensor still shows 0mbar map pressure.

Thinking it was something wrong we plug the HDS system from Honda to check but no fault code and on the HDS live system also show that the MAP was indeed 0mbar!

My daily car which is an FD2R as well with Flashpro and had been running really well with map created using 1.1.3.4 just a few weeks ago. So decide to connect the flashpro on my car with the new 1.1.4.6 beta to see what happen.

Same firmware upgrade. then connect flashpro to car, start the car then go online to check the condition of my car. It shows 0mbar. I took a short drive and recorded a datalog to show u.

I have not flash my car yet but just merely upgrade firmware and connect to car only. But some how with the new firmware and software version had created a bug and cause the MAP sensor reading going crazy!

I then search for the map that i created using 1.1.3.4 on my laptop and upload/flash again.

Start the car after reflash and BINGO the Map sensor is working again.

I think this is a big bug as it may have able to cause a problem.

Further more i noted after the firmware upgrade and reflash again so that MAP sensor is working, i noted almost everywhere in the cam angle and load point they were leaner and i needed to add 3-6% almost at every partial load point.

Both car same after reflash. need to add fuel.

Will attach the datalogue soon.

Posted: Wed Mar 24, 2010 8:54 am
by chris2000
attach is the datalog of my fd2r with k24 stock block showing map is only reading at 0mbar.

Posted: Wed Mar 24, 2010 10:39 am
by civicRSA
Yes the problem with the map sensor started with the newer releases. You need to open the calibration then save it and upload it to the ecu again, map sensor will now datalog correctly.

With the fuel problem I am not sure.

Posted: Wed Mar 24, 2010 11:46 am
by Gernby
I had a similar problem using calibrations from older versions of FlashPro Mnager causing my air fuel values to go lean. Now I'm just super careful about upgrading FlashPro Manager. I'm going to stick with 1.1.3.4 until the newer version has something I really need.

Posted: Wed Mar 24, 2010 11:50 pm
by soxfan143
The ECU need to be be reflashed with the latest version of FPM and the latest firmware or the older logs will not read properly. Hondata had to rewrite the coding for reading MAP because it wasn't reading above 22psi. All cars you want to read datalogs from will need to be updated to the latest version.

Posted: Thu Mar 25, 2010 10:31 am
by Hondata
With the change in the way the MAP sensor was read you did need to upload the calibration again when updating to 1.1.4.x. I have since changed the software so that V1.1.4.x will datalog the MAP sensor from previous versions.