K-Pro Communication Issues
Posted: Mon Feb 06, 2023 3:16 pm
Hi All, I've tried searching for this specific issue but my situation doesnt seem to align with anything else I've seen.
Sorry in advance for the length of this post but I wanted to include as much relevant information as possible.
To start, my setup is Kpro V4, PRB ECU, RSX Base 5 Speed -> K20Z3 & 6 Speed Swapped
Had no issues whatsoever with KPro for roughly 3 months or so.
The issue I've been having is an inability to upload tunes, or get any meaningful readings from engine sensors in KManager.
In KManager it says Driver Installed, Online, and Ignition On, so everything looks normal.
Then I'll start the car and the check engine light comes on and it runs very poorly (doesn't usually with my current calibration)
Naturally I'll click "start datalogging" to see what the sensors are reading and check trouble codes, but instead coolant temp reads 310, intake air temp reads 310, MAP reads like 1695, basically junk numbers. When not datalogging they all read 0.
If I try to upload my calibration it says "upload failed". So I went to "update USB drivers" and it says update failed. Same thing happens when I click "test USB".
Strange thing is I was able to download the tune from my ECU, and again KManager reads Online and Ignition On when the key is on, and Ignition Off when the key is off, so it would appear the USB cable is functioning (at least to some degree), but I just can't upload a tune or get any meaningful readings from any engine sensors.
I tried tightening the screws on the KPro daughter board inside the ECU as was recommended for similar issues and I was actually able to communicate with the ECU and the car ran normally again for a day or so, and now its back to behaving as I described before.
I'm not sure if this warrants me sending the ECU back to Hondata or what but I've tried different laptops, I checked the KPro daughter board screws and they're still tight, I've set up the engine ground as Hondata recommends, im running resistor spark plugs, etc.
Hope someone else has had a similar experience and can share what remedied the situation.
Thanks for reading!
Sorry in advance for the length of this post but I wanted to include as much relevant information as possible.
To start, my setup is Kpro V4, PRB ECU, RSX Base 5 Speed -> K20Z3 & 6 Speed Swapped
Had no issues whatsoever with KPro for roughly 3 months or so.
The issue I've been having is an inability to upload tunes, or get any meaningful readings from engine sensors in KManager.
In KManager it says Driver Installed, Online, and Ignition On, so everything looks normal.
Then I'll start the car and the check engine light comes on and it runs very poorly (doesn't usually with my current calibration)
Naturally I'll click "start datalogging" to see what the sensors are reading and check trouble codes, but instead coolant temp reads 310, intake air temp reads 310, MAP reads like 1695, basically junk numbers. When not datalogging they all read 0.
If I try to upload my calibration it says "upload failed". So I went to "update USB drivers" and it says update failed. Same thing happens when I click "test USB".
Strange thing is I was able to download the tune from my ECU, and again KManager reads Online and Ignition On when the key is on, and Ignition Off when the key is off, so it would appear the USB cable is functioning (at least to some degree), but I just can't upload a tune or get any meaningful readings from any engine sensors.
I tried tightening the screws on the KPro daughter board inside the ECU as was recommended for similar issues and I was actually able to communicate with the ECU and the car ran normally again for a day or so, and now its back to behaving as I described before.
I'm not sure if this warrants me sending the ECU back to Hondata or what but I've tried different laptops, I checked the KPro daughter board screws and they're still tight, I've set up the engine ground as Hondata recommends, im running resistor spark plugs, etc.
Hope someone else has had a similar experience and can share what remedied the situation.
Thanks for reading!