Hey guys I’ve been having trouble with getting this cable to work and thought maybe one of you could give me some help. Sorry if this kinda long but I figured the more info I could give would make things easier. The car is a ’95 Z28 w/ a 383 and most of the bolt-on’s. I’m using a cable and adapter that I got from AKM Cables. I can’t get it to talk to the PCM in the car with Freescan or DataMaster.

First off I have tried this with 2 computers with the exact same results. One was a laptop with a USB adapter and Win, ME, and the other is my older desktop with a serial port setup as Com 2 and Win 98. I get an "Adapter OK" error 1 ("usually bad connection from adapter to PCM or incorrect version") when I hit the test com button in DM's record window. Well, I'm using version EE 3.4.1 which should be correct for 94-95 LT1's. I also had the vehicle selection on F-body (Although I did try the others with no change). I have used TTS's ALDL test program that I downloaded separately, and it says that the adapter passed all tests but won't tell me anything other than that. When I try the Record or Monitor buttons It just recycles seemingly indefinitely. I have checked the cable (after the box) that Andrew made with an ohm meter and show cont. between pin 9 on the ALDL and the 5 pin on the RS232 (the is the green wire), and between pin 5 on the ALDL and pin 1 on the RS232 (white wire). The red and black wires are not connected. I think all this is right if memory serves. I have looked at the car's ALDL connector and it looks OK. I also pulled it out slightly and checked for broken wires. There were none that I could see.

Is there some setting(s) that I have missed within DataMaster that could fix my prob. Could there be something wrong the adapter itself? Or the car's ALDL harness? Any help or suggestions would be appreciated.

Thanks in advance!!

Joey


------------------
'85 Z28
383,700r4 w/B stall, 3.42 w/Powertrax

 

Make sure you have the irda turned off on the laptops. The irda uses the only available uart so it needs to be disabled in order for the back serial com connection to work.

Other then that one of those should work. Freescan needs to be set to Force Data (or something like that on the right side of the display).

Hal

 

Have you tried the Hyperterm test?

 

Dr. Mudge is right. This can help you figure a lot of things out. This may seem like a lot if you aren't used to working with computers, but it is really pretty simple. Just read through it slowly the first time. Go to Start/Programs/Accessories/Communications/HyperTerminal.

If you can't find HyperTerminal on your computer, you can download it here:
http://www.hilgraeve.com/htpe/download.html

Then...
Start HyperTerminal, and name the session anything (session name is insignificant), then:

Select "Connect using: Direct to COM1 (Assuming your serial port is COM1)",
Set BPS to "9600"
Set Data Bits to "8"
Set Parity to "None"
Stop bits to "1"
Set Flow Control to "none"
and then hit OK.

Now anything you type will be sent out the serial port. The cable’s converter circuit will echo back anything that is sent to it (it doesn't need to be connected to the car). So whatever you type will be sent out the serial port, and if everything is working properly, it will be echoed back by the converter circuit and printed in the HyperTerminal window. If you don't see what you are typing appear in the HyperTerminal window, the PC isn't communicating with the cable.

If Hyperterminal echoes characters both with and without the cable, then the "local echo" is on and needs to be turned off to properly perform this test. To turn it off, in Hyperterminal go to: File->Properties, click on the "Settings" tab, then click on the "ASCII Setup" button, and deselect "Echo typed characters locally".

If the characters you type don't appear in the HyperTerminal window, you have one of the following problems:

The port isn't configured correctly (wrong COM port, etc.)

The port isn't working or another program is using the port. Infrared ports can cause conflicts. To disable infrared ports, go to "Control Panel\System\Device Manager". Other software that uses the serial port can cause problems. For example, PDA & phone synchronizers, etc. which are running in the background can cause problems. Make sure none of this software is running.

The cable's converter isn't working correctly. This is probably the least likely problem. Check all cable connections, etc. To verify that your serial port is working properly, you can perform the hyperterminal test using a short lenth of wire instead of the cable itself. Short pins 2 & 3 on your serial port. Be careful NOT to short any other pins. Pin 3 is the "out" line, and pin 2 is the "in" line. A properly working converter will echo pin 3 back into pin 2, and HyperTerminal will then print the character on the screen. If you short pins 2 & 3, everything that goes out pin 3 simply goes right back in pin 2. So, if you get no characters when typing with the pins shorted, something is either wrong with your serial port or configuration.

FreeScan has default settings that sometimes cause problems for new users. Before you can see any data using FreeScan, you have to do the following:
Select the proper COM port (Usually this is COM1).
Select "Interact" as the operational mode.
Select "GM 1994 Camaro..." or the appropriate vehicle under "Vehicle Make and Comments".
Hit "Start" under "Communications with ECU".
If the Bytes Sent & Bytes Received counters don't start incrementing automatically, hit the force data button until they start to count.

------------------
'94 White Z, A4 2.73s, 1/4th 13.5 @102.3, 1/8th 8.7 @81.6, 60ft 1.97sec
Mods etc. - Mac headers, 3" cutout, Moroso CAI
E.T.F.A. Message Board * (above times are before headers)

[This message has been edited by SteveR (edited August 21, 2002).]

 

Sounds like the adapter is just fine and the problem is iether the cable to the ALDL connector or the connector on the vehicle.

FYI, the ALDL test and the Datamaster "Test COM" both do the same thing that the hyperterm echo test does (plus a lot more), so you probably dont need to run that test.

You might try going by your local 'Autozone' type shop and see if their free scan test will read out the codes.

Also note that not all USB adapters will work with Datamaster or support the 8192 baud rate that the GM PCMs operate at (ask me how I know...) The Belkin F5U103 does work well, tho.

Read the troubleshooting document in the datamaster on-line help, and check the AKM website for serial port troubleshooting information.

HTH,

Gary

 

Thanks for all the replies!

Hal-
When I used the laptop I disabled the IR thing on it before running DM. I think I did it right. I went into the Windows "Control Panel" and checked the box to disable. Then the device had a slash through it in the device manager, but the same probs exist with the desktop.

Dr. Mudge & SteveR-
I have not run the hyperterminal test, but am willing to if you think It will show anything new. I'll try it tonight or this weekend.

Rufus-
I tend to agree on the adapter being OK since the other tests passed.

I did go to Autozone. Their scanner did not pick-up any TC's, but went through all the motions- lights flashing, etc. Would it let you know if the ALDL wasn't working?

Right now I would be happy just to get DM to work with my desktop and a standard serial port. Then I'll play with the usb adapter/laptop issues.

If the serial port is setup wrong what should I look for? Since the "Adapter ok can't communicate with PCM" message comes up I think I'm using the right com port(2). What other serial port settings could cause this error? Could the BPS, data bits, etc. do this?

Thanks Guys! Sorry about my ignorance.

Joey

 

Assuming your running Windows (probably doesn't work on 3.1x, or 95 without osr patch) and the car is running I would say to find a auto store with a good return policy on a scanner. If that works then its got to be the cable.

Hal

 

IF you are connected to the Modem or IR port, they will often echo back the characters sent out, the same as the serial port. - thus it will look like all is working even tho it is not!

Go into windows control panel - System - Hardware - Device Manager and examine the settings under the "Ports" catagory. You should see a listing for "communication Port" (there may be several). You should be able to see what each port is and make a determination of which to use.

Also, you can just try selecting them each in Datamaster, and see if if things start working (use "Monitor" mode)!

Gary

------------------
1984 Volvo "sleeper" with
94 LT1 A4

 

Actually Hal just testing the ALDL port won't really tell you if there is a problem with the cable. The most common problem by far is port configuration problems. Selecting the wrong COM port, having another program which occupies the COM port, etc., etc..

Joey, if you want some help troubleshooting it with HyperTerminal, shoot me an e-mail. It really isn't as involved as it seems from the instructions I gave above, and it can help you determine the problem pretty fast.

steve@wotelectronics.com

 

There are some timing settings that you can adjust in Datamaster that will allow it to communicate with the car better. There is a screen called "Setup Serial Communication Timing" it is under the "Options, Advanced" tab of the Autolog window. Try lowering the "ALDL Link Timing" value.



------------------
Chad Beebe
'97 T/A WS6 M6 Dark Metallic Green
CC 306 cam and some other stuff.
My Car

12.762@109.13 with 1.828 60'
Best 60' 1.816

 

Hey Steve, what is the maximum # of captures per second?

 

Thanks for the help guys. I'm gonna play with this thing some more tomorrow or Sunday and I'll let you know.

Steve- Thanks, if I have any probs. with hyperterm I will definately shooy you an email.

Joey