You can type here any text you want

DirectScan problems - need help ASAP: Hardware Timedout!

Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

SignUp Now!

J Banning

Quench my thirst with C16
Joined
May 25, 2001
Messages
2,032
I was experiencing some DirectScan problems at the track last night that I've never had before. I had the following error on all four of my runs. I was not able to record any data. :( ...

Hardware Timedout!
Retry? YES|NO



The DirectScan manual says the following...

"Hardware Timedout! Retry? or DirectScan hardware NOT found!
Occurs while the DirectScanis in Realtime mode. This message indicates that the hardware module is no longer detected by the program. This could be the result of the key in the off position, any of the cables becoming disconnected, or power loss to the car. Please check all connections and ensure that the key is in the ON position."



This is what I did/checked:
- I checked all the connections, and even reconnected everything. I have a spacer set up so the cable doesn't ride up too far on the ECM board.
- I reset the ECM (twice)
- I removed the hardware module and ribbon cable from under the dash and laid it out on the floor.
- I started DirectScan BEFORE starting the car.
- I'd hit the spacebar to start recording after my burnout. When I'd hit it after going through the traps is when I noticed the error.

After all this, the problems still persisted. Everything worked fine BEFORE I started logging data. After hitting the space bar it looks like it would only record 5 seconds or so of data. To the best of my knowledge the car was not experiencing "power loss" (as mentioned in manual)... it ran 11.00's at 120mph.

What's up???
 
Banning,

Was having the same problem with mine. CHECKED everything and could never figure out what the deal is. Mine would do the hardware timeout probably every 20 seconds or so. Car would also act up approx. every third WOT blast or so with the DS on. I finally ditched it in favor of a FJO wideband. If you are running ME-R (like me), then wide band is the way to go. Steve Y told me what the DC%'s are on each TW, so I set my sensors w/ the DS or Scanmaster, then just adjust fuel with the WB.

Sorry I couldn't be of much help, you culd try calling Chu Eng. or Conley's.
 
The only times I've gotten that message were when a cable was off. I did see one printer cable that had a bad connection inside after lots of flopping around in a car, so maybe try a new printer cable?
 
If you have been using DS for a long time and this problem just now occoured, you need to recheck that cable connection. If thats not the problem, contact Chu as your box may have gone bad.

Bob
 
Same thing here man :( Thank god for Scanmaster and an EGT guage. I was really lookin forward to havin the data to go home and look at too!:mad:
 
I have a whole other unit that I can swap in place piece by piece. That should tell me what's wrong. Thanks for the help.
 
Since I switch laptops, I've been suffering from the same problem. I even tried connecting the parallel port dongle, and changing BIOS settings without any luck. I also partitioned the drive so that I can boot directly into DOS, but that was no help either.
I'm wondering if that aluminum foil noise shield would help.
 
I would try the usual suspects. I woudl however take a pencil eraser, run it over the contacts on both sides of the ecm. Make sure the ecm is not plugged in and is grounded before doing this. Also do the samw with all connectors and cable connectors. When doing connectors, inster the eraser and pull out straight. Do it a couple of times. Ensure that all connections are tight and secure. Even with this every once in a while I get it but doing all the above regularly it is very rare anymore. Also check the ribbon cable for any kinks or loose connectors. I have had to replace them on some one elses DS.
 
Back
Top