Upload failed error

iwilson · Post by **iwilson** » Mon Oct 10, 2005 5:34 am

I purchased a K-Pro a couple of weeks ago. All was fine, new map uploaded made a few adjustments to the VTEC window no problem, until last Thursday... The primary O2 sensor had been throwing a P0134 code from time to time and I decided to disable the code (as I understand this is now a known issue and will be fixed in later version). I also did a datalog run with the ECU placed into open loop to see how good the part throttle mapping was and to keep an eye on the O2 sensor. Job done, I then changed the map back to closed loop and attempted to upload it but got an Upload failed error message. After many attempts I purchased a new cable still no luck. I clamped a ferrite magnet to the cable and no change. Uninstalled K-Manager (+ cleared the registry) and the USB drivers and loaded an earlier version no change. I?m able to datalog with no problem ? but not with earlier versions (garbage readings) which is consistent with versions prior to 1.2.07 not being able to datalog a map uploaded with version 1.2.07. I have also checked the board installation and the patch wiring on the underside of the ECU everything appears to be fine. The USB connector is well protected with insulation tape from grounding on the ECU case and the ground on the intake manifold was moved to the recommended position many months ago. Attempting to download from the ECU seems to proceed normally but the map is a bunch of gibberish. See attached a couple of screenshots. The rubbish in the tables is the result of a previous download.

The engine runs fine and all the sensors would appear to be operating normally according to the datalogging (including the primary O2 sensor).

The problem I have is the car is due to be loaded onto a ship for transport to the States next Monday where it will be driven on a 5,000 mile road trip across the US. I would rather not try anything to drastic at the moment to solve it as the car must be drivable until it gets to the States. But given the distance the car will be traveling I would prefer not to be running in open-loop for 5,000 miles!

I?m attaching a short datalog and the current calibration.

The car is a Lotus Elise with a K20a (JDM) and PRB ECU. This is not a new install and the wiring is fine to the best of my knowledge. The VTEC oil pressure sensor has been installed. The car has run faultlessly with a K100 for sometime prior to the purchase of the K-Pro and I've done over a thousand miles since the K-pro was installed again without any problems other than the intermittent P0134. The laptop has no problem connecting to the ECU and I?ve seen no dropouts or other glitches while connected even for extended periods of time (I've swapped to other USB ports with no change). Any attempt to upload to the ECU including different maps produces the upload failed error within a couple of seconds. The LED?s on the board are displaying correctly and there have been no errors displayed in the error window.

I?d appreciate some guidance on the best way forward at this point. I did find one other thread with someone who experienced the same problem which seems to have been resolved now by Hondata.

Post by **Spunkster** » Mon Oct 10, 2005 9:52 am

Try clearing security then uploading the calibration again. We do not recommend ever downloading the calibration from the ecu as this will fail most of the time.

iwilson · Post by **iwilson** » Mon Oct 10, 2005 11:18 am

Spunkster wrote:Try clearing security then uploading the calibration again. We do not recommend ever downloading the calibration from the ecu as this will fail most of the time.

Thanks, I have tried clearing security but get a clear security failed message - same thing if I try to set security. I only attempted to download the map to see if it was able to do so. I have never tried to upload a downloaded map. As you can see by the screenshots it appears to be able to access the ECU, but is unable to make any changes to the map or retrieve a usuable copy of it.

Post by **Spunkster** » Mon Oct 10, 2005 11:54 am

There is more thna likely a problem with the ecu preparation...a bad solder joint or wire. Who did the ecu preparation?

Only other posibility is that the K-Pro has been damaged by faulty wiring.

iwilson · Post by **iwilson** » Mon Oct 10, 2005 12:27 pm

Spunkster wrote:There is more thna likely a problem with the ecu preparation...a bad solder joint or wire. Who did the ecu preparation?

Only other posibility is that the K-Pro has been damaged by faulty wiring.

UK dealer did the K100 install, I installed the K-Pro. I was a Radio tech in a previous life and the K-Pro is a pretty simple install - there were no dramas and all the pins are in good shape and are in the right place (including the single pin marked with the x and tick. The screw was not overtightened - used thread lock. I have gone as far as checking for continuity between all the K-Pro pins and the board (no problem). Likewise the patch wiring underneath the board is sound. The board worked perfectly (not just for datalogging but also for uploading) for two weeks so I doubt it's the install. The K100 was in for many months so it's not the patch wiring (which meters out in any case).

Post by **Hondata** » Tue Oct 11, 2005 1:29 pm

The first step it to get clear security to work - it is pointless continuing if this step fails.

If clear security doesn't work then the only way to diagnose where the problem lies is to swap ECUs and/or the KPro.

iwilson · Post by **iwilson** » Tue Oct 11, 2005 1:48 pm

Hondata wrote:The first step it to get clear security to work - it is pointless continuing if this step fails.

If clear security doesn't work then the only way to diagnose where the problem lies is to swap ECUs and/or the KPro.

Just to close this one, I've spoken with Hondata and I can confirm their reputation for customer service is deserved. A way forward has been sorted out.