Bug (?): CAM Angle Table (Lo/Hi) Upload != Download

[taitcw]

- K-Pro S/N: 6430
- KManager version: 1.4.1.0 (WinXP Pro)
- Calibration: N/A
- Datalog of a problem: N/A
- Vehicle: 2002 Honda Integra Type R (JDM K20A)
- ECU: ECUType=3 (PRC ECU?)

Problem:
Set all cells in Low Speed Cam Angle table to 0 (for tuning VTC 0 fuel). Downloaded successfully, test drive and datalog, CAM angle still changes!!!
Download from ECU to see what's going on. Discovered Lo Speed Cam Angle table values DID NOT get updated.

Resolved by setting the bottom right cell to 10 (non-zero angle) and reload. Successful (Download and compare).

However, the same trick does not work on High Speed Cam Angle table. At the end, I had to change a few cells in the last column to non-zero values and re-upload.

Is it just a small glitch??

[Hondata]

Only changed values are uploaded; so this may happen if you upload to an ECU, and then switch to a different ECU without closing KManager. We have changed this for the next release.

[taitcw]

Upgraded KM from 1.4.1.0 to 1.5.1.0.

Scenario:
Start KManager. Open kal, upload.
Closed KManager.
Start KManager, Download from ECU.
Save downloaded kal for comparison (only the lower portion of the table is updated for some reason?).

I am working on the same ECU only.

Again, I needed to modified one cell to non-zero value, then ECU will accept the whole map...

Any idea Hondata??

I am going for a Dyno tune soon (in a few days time), so it would be awesome if you could fix this glitch. Thanks!

Started with this Kal:

Kal04.JPG

Downloaded from ECU:

Kal04 DL.JPG

Modified Kal (see bottom right cell):

Kal05.JPG

ECU accepted the modified Kal.

Update: 1.4.1.0 and 1.5.1.0 behave the same way. This situation only happen when I am uploading a 'VTC0' calibration. Have you tested it Hondata?

[taitcw]

- K-Pro S/N: 6430
- KManager version: 1.5.1.0 (WinXP Pro)
- Calibration: N/A
- Datalog of a problem: N/A
- Vehicle: 2002 Honda Integra Type R (JDM K20A)
- ECU: ECUType=3 (PRC ECU?)

What happened:
Kal from 1.4.1.0, under [Knock/TPS] tab, Scale TPS
Minimum reading: 1.1%
Maximum reading: 102.7%
TPS is correctly scaled to 0% to 100% (as shown under 'Sensors' window and 'Display' window).

Upgraded to 1.5.1.0
Kal has the same min and max TPS values.
Minimum reading: 1.1%
Maximum reading: 102.7%

BUT

TPS is shown -1% when throttle is fully closed!!
(TPS does show as 100% when throttle is fully opened).

I have no way to resolve this, buy I tried to change my minimum reading to 0%. Re-uploaded and TPS shows 0% when throttle is fully closed (as what it should be).

@Hondata, is it possible to fix this minor glitch please?

Thanks.

P.S. Let me know if you need more info.

[Hondata]

Testing and working here - given your other posts, I think you have other problems with the KPro.

Clear security and upload a base (new) calibration again and test again.

[taitcw]

I found it strange too as it was working all fine for every production version prior to 1.5.1.0 (I have not tried 1.4.5.7 and 1.5.0).

I have performed [Erase ECU (Clear Security)].
Ignition off, unplugged ECU for 1+ minute.
Opened a brand new kal (base) with Min and Max TPS as 0% and 100%.
Uploaded (took a bit long which is normal for a fresh upload).
Observed TPS readout Min bounces between 0 and 1%, Max 103%
(Under parameters window TPS min reading is 1.1% and max reading is 102.7%).

Shutdown KManager, and restart application.
Opened my kal with 'correct' TPS scale settings (1.1% and 102.7%) and upload.
Observed TPS readout Min -1% and max reading is 100% (scaled correctly?).

Please advice.

[Spunkster]

Have you tried rescaling the TPS?

http://www.hondata.com/help/kmanager/kn ... =scale+tps

[taitcw]

I have attached some screenshots.

Notice, this problem only happens after I upgraded to 1.5.1.0. I simply opened kal (saved by 1.4.1.0), and uploaded to ECU.

DefaultTps.jpg

If I upload the above, my TPS readout when throttle is fully closed is bouncing between 0 and 1%; when throttle is fully open, TPS read 103%.

So I have always scale my TPS using these settings:

ParametersWindow.jpg

It has been working well as TPS readout is 0% and 100% (scaled correctly).

But it is now reading -1% and 100% (KM 1.5.1.0).

I have tried to re-installing KM 1.5.1.0 but it did not help.

[taitcw]

- K-Pro S/N: 6430
- KManager version: 1.5.1.0 (WinXP Pro)
- Calibration: N/A
- Datalog of a problem: See screenshots.
- Vehicle: 2002 Honda Integra Type R (JDM K20A)
- ECU: ECUType=3 (PRC ECU?)

I notice this change, is it a glitch? or is it normal? Has something else changed between 1.4.1.0 and 1.5.1.0???

Datalog of the same journey using KM 1.4.1.0 (same kal). Yesterday.

Datalog1410.jpg

Datalog using KM 1.5.1.0. Today

Datalog1510.jpg

Close up as follow:

Datalog1510_closeup.jpg

Why would the BAT voltage swings like this??? Hardware is the same, the only thing I have changed is KM from 1.4.1.0 to 1.5.1.0.

It reminds me of the A/C clutch not engaging glitch for PRC ECU a while back. Could it be something similar???

@Hondata, any advice?

Thanks.

[taitcw]

- K-Pro S/N: 6430
- KManager version: 1.5.1.0 (WinXP Pro)
- Calibration: N/A
- Datalog of a problem: See screenshots.
- Vehicle: 2002 Honda Integra Type R (JDM K20A)
- ECU: ECUType=3 (PRC ECU?)

This is another thing I have observed from datalogs.

KM 1.4.1.0

AFCMD is pretty much stable @ 14.59:1 (which I believe is the default Target Lambda Limit?)

AFCMD_1410.jpg

KM 1.5.1.0

I have used the default settings.

ParametersWindow_Advanced.png

and this is what I get:

AFCMD_1510.jpg

AFCMD stays @ 14.59:1 during IDLE, but it bounces up and down (can be 15:1) elsewhere. Yes A/F bounces up and down due to that reason...

@Hondata: Could it be another one of those PRC ECU issue?? Any resolution? please?

Edit: AFCMD behaves normally (stays within limit 14.59:1 and does not bounce around) when ECU is placed in Open Loop.

[freezingcoffee]

I have a similar problem, when the throttle plate is closed it shows a -1, I've scaled it multiple times, and even used a different TPS. I plugged in another laptop running an older version of kmanager and it shows 0 when closed.

[sadvtec]

I also show -1 in the new version and am using the billet k-tuned tps. Before the update it showed 0 now shows -1

[Hondata]

Ok, I'm going to combine all your reports into one post.

You are getting many problems which no one else has seen. Go over any recent modifications to your engine, load a new calibration (no one that you have tuned previously), then clear security and upload again.

[rikitaun]

I have a similar problem, when the throttle plate is closed it shows a -1,

+1 with kamanager 1.5, the older version works rigth.

[taitcw]

Ok, I'm going to combine all your reports into one post.

You are getting many problems which no one else has seen. Go over any recent modifications to your engine, load a new calibration (no one that you have tuned previously), then clear security and upload again.

@ Hondata: Thanks for combining all the posts. No modifications have been done to the car for 6 months. The only change that I have made is upgrading KManager from 1.4.1.0 to 1.5.1.0. Also I have already done what you suggested, l created a brand new kal from KM. It still behaves the same. TPS shows -1% when Min Reading is set to 1.1%. AFCMD does not follow Target Lambda limit.

Mine is a JDM with PRC ECU which is slightly different from PRB.

@freezingcoffee: What type of ECU and vehicle are you using?

@sadvtec: What type of ECU and vehicle are you using?

@rikitaun: What type of ECU and vehicle are you using?

I am trying to understand if these issues are only for PRC ECU or all everyone as well??

Thanks everyone.