Page 2 of 2

Posted: Tue Apr 21, 2009 11:47 am
by chrisfjr83
Why is this not a stickie???

Posted: Mon May 18, 2009 2:40 am
by sass
Before leaving the version 1.3.6.

I have tested some non-convenience with version 1.3.5.4
It was installed at three prb ecu and a one prc-023.
In the first case installation of PRB ECU was successful and the calibration go from desktop without problems.
In the other two PRB had problems sending the calibration and not writing in their ecu. Does not writing PARAMETERS TO k-manager. Solution to this problem is only function erase ECU Then the upload was ok.

Since PRC-023 which was installed in the body of EK solutions to this problem with erase functoin ECU did not help.

It was to change the wiring swap scheme.


Image

Decisions found only removing the wire from connector CONTROL alternator because previous uploading produced with the included charge lamp on the display. Then alternators connector put in place and made the engine start.
All work as expected.
Question to hondata?
Upload B10 When alt-l has a power that comes with the scoreboard lights charge. It makes sense to remove a wire from the B10 ECU.
Then the wire lamp charge scheme will look like in the B series, or a combination of S2000.

If turning off the B10 is not possible, I can suggest here that alternative compounds.

Image
Sorry for my bad english.

Posted: Mon May 18, 2009 10:40 am
by Hondata
The diagram looks old. The o2 heater needs to be switched ignition.

http://www.hondata.com/images/k20awiring.gif

Posted: Mon May 18, 2009 11:06 pm
by sass
Hondata wrote:The diagram looks old. The o2 heater needs to be switched ignition.

http://www.hondata.com/images/k20awiring.gif
Thanks for your answer.
But I more interested in dagram of connection lamp charge to ECM connect B10 Alt-I. It right printed in your diagram at http://www.hondata.com/images/k20awiring.gif ?

Posted: Fri May 22, 2009 12:36 am
by fvang
After switching over to the this version, I have notice a problem.

When accelerating or decelerating, there seems to be a lag.

The datalog shows that around the threshold of closed loop to open loop, the fuel get reduced. It seems to happen 87kpa -> 84kpa.

See the attached datalog (15.5s-16s).

From the 1.3.4 version, I did not see this. Is there some behavior that is happening with the fuel when it is at the threshold?

Posted: Fri May 22, 2009 7:06 am
by Hondata
The change is from open loop to closed loop. In closed loop the target AF is around stoichiometric. In open loop it is around 0.85 - so there is a -15% change in fuel from the open to closed loop change. Additionally, in closed loop the last fuel trim is applied - which is -14%, so in total there is a change of almost 30% fuel. Once in closed loop the ECU trims the short term adjustment back to around 0%.
The problem is the -15% short term trim being applied before you go into open loop. You need more fuel tuning from 1000-3000 rpm and light load.

Posted: Fri May 22, 2009 4:48 pm
by fvang
Although I will try your suggestion, I find it odd that the previous version did not behave the same way. I felt this lag the very day I uploaded with this new version.

I have uploaded another datalog.

This time it shows that there is some fuel decrease even though the short trim is small. It has both accel and decel points. See at 3.5s. It gives short trim of -3% yet there is a 30% fued difference.

Please see the attached datalog.

Posted: Sat May 23, 2009 10:07 am
by Hondata
In any case the short term fuel trim is very high - it needs to be fixed. There also is a problem with the cam control.

Posted: Wed Jul 22, 2009 6:12 pm
by Blackcoupe
Looking for some clarification. Recently installed Kpro, info is below:

06 Acura RSX-S
Serial # 6872
Kmanager 1.3.5.4

I'm getting an intermitant error message while datalogging. The message is as follows:

"The ECU is currently datalogging to on-board memory. Please switch off or disable on-board datalogging before datalogging from Kmanager."

On-board data logging is disabled and I'm running the stock 05Z1 CAI Kal.

Any thoughts?

Posted: Thu Jul 23, 2009 8:11 am
by Hondata
The message means the KPro reports that it is datalogging. How long does it take before you get this message?

Posted: Thu Jul 23, 2009 9:37 am
by Blackcoupe
It appears once in a while, normally a couple of minutes into a datalog. If I click ok on the window I can resume a new datalog with no interruptions. Onboard datalogging is disaled, so not sure why I'm getting this message. There are a couple of others users on clubrsx that are experiencing the same problem as well.