Version 1.2.1.1 bug
Version 1.2.1.1 bug
I just realised that the OBDII disable feature does not work properly on 1.2.1.1. I have double checked with 1.2.0.7 and everything was fine. More specifically, when I disable the OBDII in a rom and save it, when I reopen it the OBDII is still checked. I am not attaching the calibration as you can reproduce the problem with any calibration.
Ps: Is it normal for a car without a catalyst and OBDII unchecked, to not complete readiness tests? (catalyst and O2 sensor)?
Ps: Is it normal for a car without a catalyst and OBDII unchecked, to not complete readiness tests? (catalyst and O2 sensor)?
OK. For calibration you can use anyone you like, say a dyno tuned calibration for a stock RSX-S. Then go to 'misc' and uncheck the OBDII functionality. Then save the .kal with any name you like. Reopen it and go to the 'misc' tab. I find the OBDII functionality enabled again although I saved the .kal with OBDII disabled. This would never happen with 1.2.0.7.
I also uploaded a Hondata dyno tuned calibration with OBDII disabled in a car without a cat. After a while, I got cel #67 although I had OBDII disabled. I have done this many times with 1.2.0.7. The only difference is the K-Manager version and the fact that the last car I uploaded the .kal (which resulted in code #67) was a '05 Euro CTR. All the other cars I have tried are '01-'04 Euro CTR's.
I also uploaded a Hondata dyno tuned calibration with OBDII disabled in a car without a cat. After a while, I got cel #67 although I had OBDII disabled. I have done this many times with 1.2.0.7. The only difference is the K-Manager version and the fact that the last car I uploaded the .kal (which resulted in code #67) was a '05 Euro CTR. All the other cars I have tried are '01-'04 Euro CTR's.
i have noticed with the things disabled for obd2 and the o2 sensors
in older versions ltrim doenst respond at all and a af gauge wouldnt work (it would peg out)
now with the new version and same parameters disabled everything works now l trim and my af guage
is this a bug or was it redesinged to work that way
in older versions ltrim doenst respond at all and a af gauge wouldnt work (it would peg out)
now with the new version and same parameters disabled everything works now l trim and my af guage
is this a bug or was it redesinged to work that way
I do not have access to any cars other than Euro CTRs. However, even when I open a new PRB calibration in my laptop, disable OBDII, save it, and then reopen it, the OBDII is again checked. THis is all I can test for other than PRA calibrations.
Now on PRAs, I disable OBDII, I upload the calibration to an ECU and after a while I get a CEL 67. I check the calibration and the OBDII is again checked. Although I uploaded it when I unchecked OBDII, I still get the CEL. I reverted to 1.2.0.7 and all problems disappear.
Now on PRAs, I disable OBDII, I upload the calibration to an ECU and after a while I get a CEL 67. I check the calibration and the OBDII is again checked. Although I uploaded it when I unchecked OBDII, I still get the CEL. I reverted to 1.2.0.7 and all problems disappear.