Kpro still stuck at 5500rpm..

[evil R34]

Had my kpro tuned and was running fine, just needed to log on and turn on closed loop in parameters. When i uploaded the map with my originial calibration the rev limiter changed to 5500 rpm. I searched how to undo it and I did the uninstall/reinstall of kamanger.

I cleared the ECU then uploaded the original calibration again and still got the same issues. When i first got this ECU tuned the tuner encountered the same problem but he said it was faulty soldering which he then fixed. But now im having the same issue again but only since i accessed the ECU.

Any suggestions? Much appreciated.

[will88]

I had the same issue with the limiter stuck at 5500rpm, took the same steps as you, what fixed the problem for me is uninstall your version of kpro and use the newest update and reupload your map and see how that goes.

[Mr.Brightside]

yeah, you need to apply the update

[evil R34]

i downloaded the newest kmanager yesterday arvo and deleted the old one and uploaded the map again same problem :/

[evil R34]

WE FIXED IT!!!! Just donwloaded the V3.0 for the new kpro and that fixed it.

[Benson]

WE FIXED IT!!!! Just donwloaded the V3.0 for the new kpro and that fixed it.

Awesome! Glad it all worked out

[EG5]

WE FIXED IT!!!! Just donwloaded the V3.0 for the new kpro and that fixed it.

Finally you sorted it out

[bigjo5]

i just happened to get the same problem, but when uploading my map using the new 3.0 it would not start so i uploaded it again with the old version and it works but still cuts at 5500rpm

[TODA AU]

i just happened to get the same problem, but when uploading my map using the new 3.0 it would not start so i uploaded it again with the old version and it works but still cuts at 5500rpm

You'll need to erase the ECU 1st then reload your map using 3.0

[zco]

where do you download the kmanager 3.0 software ?

[TODA AU]

where do you download the kmanager 3.0 software ?

Hondata website, or click update in K-Manager.

[zco]

Thanks Adrian,

im asking for a friend, i dont actually have the issue myself. we checked on hondata website and it seems like the file was named v1.5 or something..
hence why i asked

so can it be safely said that this issue has a fix ?