K-Pro loses connection when Datalog Recording
K-Pro loses connection when Datalog Recording
I just got k-pro about 3 weeks ago and I never have a problem with connectivity. But what is happening is I am OK as long as I am datalogging without recording. But once I start recording, I lose connection and it goes off-line. I only seem to go off-line when I to a WOT run. If I drive normal its OK. So I have to try like 4 times before i can get it to record the WOT run. Any ideas what is worng? Thanks
some of my customers have the same problems even with the new sheilded cable coming in the kpro box. before that cable, hondata had a custom cable made with an enourmous choke on it. this is what i have and it never disconnects. however, i have no idea the size of the choke or where to get it. there is likely an answer in a previous post or club rsx forum.
More input in hopes of helping to find a solution:
Using a newer laptop (<2yr old Dell D600), I cannot record more than a few seconds of full throttle data and often lose connection even under part throttle cruise. This has been the case with several Kpro modified ECUs and various USB cables. This weekend I finally used a customer's laptop to finish tuning his car so I could log full dyno runs - his worked much better, but would lose connection at full throttle on occasion.
Today I recalled that my early experiences tuning Kpro systems went flawlessly, so I connected my old (>5yr old Thinkpad) to a Kpro in a Lotus Elise for tuning. It data logged everything perfectly - even with a very cheap 12+ ft long non-shielded (choked) USB cable. This has to be a "worst case scenerio" - a K20 mounted in a non-Honda chassis with a modified harness, supercharged with unknown spark plugs, a terrible extra long USB cable, etc.
Things the same: ECU, CABLE, Laptop OS, Kmanager software version, and calibration file.
Things different: Laptop MFG, processor speed, memory, etc., and USB 1.0 vs. 2.0
Maybe this will shed light on the issues - we may be looking in the wrong direction.
Using a newer laptop (<2yr old Dell D600), I cannot record more than a few seconds of full throttle data and often lose connection even under part throttle cruise. This has been the case with several Kpro modified ECUs and various USB cables. This weekend I finally used a customer's laptop to finish tuning his car so I could log full dyno runs - his worked much better, but would lose connection at full throttle on occasion.
Today I recalled that my early experiences tuning Kpro systems went flawlessly, so I connected my old (>5yr old Thinkpad) to a Kpro in a Lotus Elise for tuning. It data logged everything perfectly - even with a very cheap 12+ ft long non-shielded (choked) USB cable. This has to be a "worst case scenerio" - a K20 mounted in a non-Honda chassis with a modified harness, supercharged with unknown spark plugs, a terrible extra long USB cable, etc.
Things the same: ECU, CABLE, Laptop OS, Kmanager software version, and calibration file.
Things different: Laptop MFG, processor speed, memory, etc., and USB 1.0 vs. 2.0
Maybe this will shed light on the issues - we may be looking in the wrong direction.
I've had 3 different laptops/brands connected to my kpro with different processor/speed & USB 1.0/2.0 without problems.Dynotuner wrote:More input in hopes of helping to find a solution:
Using a newer laptop (<2yr old Dell D600), I cannot record more than a few seconds of full throttle data and often lose connection even under part throttle cruise. This has been the case with several Kpro modified ECUs and various USB cables. This weekend I finally used a customer's laptop to finish tuning his car so I could log full dyno runs - his worked much better, but would lose connection at full throttle on occasion.
Today I recalled that my early experiences tuning Kpro systems went flawlessly, so I connected my old (>5yr old Thinkpad) to a Kpro in a Lotus Elise for tuning. It data logged everything perfectly - even with a very cheap 12+ ft long non-shielded (choked) USB cable. This has to be a "worst case scenerio" - a K20 mounted in a non-Honda chassis with a modified harness, supercharged with unknown spark plugs, a terrible extra long USB cable, etc.
Things the same: ECU, CABLE, Laptop OS, Kmanager software version, and calibration file.
Things different: Laptop MFG, processor speed, memory, etc., and USB 1.0 vs. 2.0
Maybe this will shed light on the issues - we may be looking in the wrong direction.
Brands are: Dell Inspiron 4150, IBM T22, HP/Compaq.
The common factor is the Greddy kit. In the past we've found that the kit included non-resistor spark plugs, but it could be that there is something else in the kit which creates a bad ground or inteference. We've asked Greddy for the installation instructions & kit contents, and are looking for a local vehicle with the Greddy turbo kit to look at here.
Hondata
I have a similar problem.
Within seconds of me starting the car Kmanager goes offline. If I unplug the usb cable and then reconnect it it shows online for a few seconds before going back offline.I updated the software yesterday and it seems to be worse.
About to try another laptop
Lotus Exige
k24 motor
Jackson Racing supercharger
everything else is unkown as the car arrived here on a trailer and was built by the owner
Within seconds of me starting the car Kmanager goes offline. If I unplug the usb cable and then reconnect it it shows online for a few seconds before going back offline.I updated the software yesterday and it seems to be worse.
About to try another laptop
Lotus Exige
k24 motor
Jackson Racing supercharger
everything else is unkown as the car arrived here on a trailer and was built by the owner