When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
I'm having difficulty with the autotap in connecting to the
vehicle, and getting accurate data.
I have tried following directions
exactly but....For instance, when connection is made, car stopped and at
idle, data shows -7000rpm and 6-7 mph. STFT sometimes show 100% and up to 20 degrees of knock retard. It takes over 1 hour of disconnecting,
reconnection,and restarting the program befor the parameters appear correct,
i.e., correct idle, 0 mph, no knock retard, changing STFT.
Sometimes it asks for VIN... sometimes not, I think when it asks for VIN
that it finally starts to correctly analyze.
It gets stuck in the "checking trouble codes & freeze frame info. also it is not even allowing B2S1 & B2S2 O2 parameters to be selected (not showing up in tables
any remedies?
This is the first time i've heard of something like this occuring with Autotap. Are you using the DOS version or Windows version? Also are you using a DOS window within Windows? Just trying to cover all bases here, but after you have plugged in the cable to both the car and computer you did turn the ignition to the "on" position (without starting) before you initiated the connection sequence within Autotap right?
FYI: I use the DOS version and i boot my laptop up into the "safe mode and command prompt only" option. That way Autotap has full control over all resources.
I'm using the DOS version and a DOS window within windows. is this not right?
I believe I've tried every combo of cable connection, ignition on, engine running, bootup there is.
When I plug in cables, then turn ignition on, then bootup, I lose communication when i start the engine and I have to start all over again.
HELP
Windows could be interfering with the COM port to which Autotap is connected to. Try booting to a DOS prompt by hitting the F8 key when you see the words "Starting Windows......" appear during the boot up process (Win9x OS's). Then go to the Autotap directory and run Autotap. Make sure all cables are pluged in and the ignition is in the "ON" position (not start) and then press the "connect to vehicle" button in Autotap. Once Autotap establishs the connection then you can start the car. This is what i do and i've never had any problems. Try this and see what happens.
I'm using the DOS version and a DOS window within windows. is this not right?
I believe I've tried every combo of cable connection, ignition on, engine running, bootup there is.
When I plug in cables, then turn ignition on, then bootup, I lose communication when i start the engine and I have to start all over again.
HELP
The DOS version will lose communication with the car if you start the car after you have autotap running, i.e., you go from ignition on but motor off to motor on. What you need to do then is remove and then reconnect the plug to the car. When you see wacky values for RPM you know that the plug must be reconnected.
Been there, done it, when this is done, communication is never re-established and i have to ...end task... and start over.
I have an IBM thinkpad running windows 2000
WTF
Any other 'puter guru's out there
How about if I spit in the connectors will that work :mad :mad
Been there, done it, when this is done, communication is never re-established and i have to ...end task... and start over.
I have an IBM thinkpad running windows 2000
That's odd. I'm running Windows 2000 Professional on a Dell, running autotap DOS (v. 2.10) in the regular DOS window, and the reconnect trick works every time. :confused:
Yes, Autotap plugs into the port under the steering wheel. You don't have to drive your car to use Autotap. For instance if you wanted to see what codes were set, if any........but then you can do that with the DIC. Past that though you need to drive around with a few WOT runs to get a good idea of how things are functioning. :cheers:
jawski - Sounds like something that is running in Windows (or gets loaded at boot up) is interferring with your COM port.....possible a mouse or modem. The only thing i can suggest is to try to find out what item(s) are using that COM port and make sure they are not running or disable them if they are. Good Luck!
Autotap cost about $250 (got mine for $215 shipped on a GP 2 years ago) and comes with the cable and the software....which is actually free, as you can download it from their web site. But you need their cable in order to use it outside of DEMO mode.......their little catch 22. :smash:
FINALLY got hooked up, I spit in the connectors..no not really but did find the pin connection under the dash is not the tightest connection. I got communication with engine and autotap program running. Iwas able to get a good run in last night..i'm trying to dial in MAFT at WOT.
Thanks to you guys who said it was a COM port problem.
Its a company laptop and I can't install windows version (company policy:rolleyes: )
I will try to repeat today. wish me luck.
Been there, done it, when this is done, communication is never re-established and i have to ...end task... and start over.
I have an IBM thinkpad running windows 2000
That's odd. I'm running Windows 2000 Professional on a Dell, running autotap DOS (v. 2.10) in the regular DOS window, and the reconnect trick works every time. :confused:
I borrowed a friends autotap, installed the software-V2.10 running in DOS, and it seems to work great. BUT, whenever I try to log a file, it displays "not enough memory".
This is on an old toshiba laptop, 40Mb ram, 300Mb free disk space, Win95.
Rx7Rob - I'm running Win95 on an old Toshiba Satalite(sp) Pro 150(Mhz)MMX pentium with 1.5GB HD and 40MB RAM. I boot mine into DOS using the F8 key when "Starting Windows 95....." appears. This gives you the ability to select how you want to boot up your computer. Then i change to the Autotap directory and run Autotap. Try running it this way and see if you still have problems.