K-pro possibly going bad; hard to diagnose problem..

K-Series Programmable ECU installation questions / support issues
Locked
katman
Posts: 4
Joined: Sun Jul 08, 2007 4:20 pm

K-pro possibly going bad; hard to diagnose problem..

Post by katman »

Hello..

A friend of mine had a K20 swapped into his DC2 integra w/the help of fellow friend Shawn Hillier about 3mo ago. Everything went fine with the swap; car ran great up until the month 4 rolled around. He began to have what looked like to me, ecu trouble...

The main symptoms are:
- check light coming
- 4K redline.

I took a look at it being that I'm a bit of an ECU techy and personally have a K20 EG w/Kpro.

I tried to communicate with the Kpro via laptop and it wasn't working (connecting) either, which I thought was really odd. After trying a couple different things I was able to connect and uploaded a base map with the latest firmware, thinking this would fix the problem, when it didn't. My friend reported the same problem symptoms remained. Also, we werent' able to pull the DT codes when this problem happens...its the weirdest thing.

As a test, I plugged my Kpro into his car and it ran without issue, no check light, no 4K redline, ran totally fine!

I then plugged his Kpro into my EG and instant check engine light + 4K redline. This is what led me to believe something is up with his Kpro.

I took the ecu cover off and inspected the internal boards to see if anything was damaged. It all looked good. I detached the daughterboard and reseated it back in the ecu. This didn't seem to do anything.

We then contacted Shawn to see if he could get it checked out. A fellow named Javier checked it out and ran some tests on it (I'm told the same test that Hondata performs) but they couldn't find any problems. I'm not sure if they tried plugging it into a vehicle because it should duplicate the same problem we're experiencing.

We got the Kpro back last week. I plugged it into my EG and the same problem(s) remain but a DT code now flashes code "6" after about 30 seconds. I believe this is 'ECT Circuit Low Input or ECT Circuit High Input ' if this is the same code found on 96-00 OBD2 ecu's. If this is the problem, would this really cause the ecu to have a 4K redline and not connect??

I'm kind of stuck on ideas.
I'd like to send this ecu in for repairs if possible..

Thanks for any help if any!
6 Zigen
User avatar
Spunkster
Site Admin
Posts: 23878
Joined: Fri Sep 20, 2002 5:06 pm
Location: Hondata

Post by Spunkster »

Can you datalog? Have you tried Clearing Security (online, tools) and then uploading a new calibration (file, new)?
katman
Posts: 4
Joined: Sun Jul 08, 2007 4:20 pm

Post by katman »

Spunkster wrote:Can you datalog? Have you tried Clearing Security (online, tools) and then uploading a new calibration (file, new)?
The Kpro won't communicate with the laptop, altho Windows does make the sound that a connection to the USB port has been made, but Kmanager doesn't talk to the ecu..
6 Zigen
Locked