I am having trouble trying to connect to the ECM with my AutoProm. I'm using an HP Pavilion 1.8GHz, AMD Turion 64 Mobile Processor. The car is an 89 GTA 5-Speed with a stock 305.


I have searched this site, and tried to follow the recommendations from here:
http://www.moates.net/mike/faq.html

I have tried changing latency, disabling checksum, etc. etc. This has not been a fun, easy trip so far.

I was able to connect to just the ALDL connection 1 time for a few minutes, but all of the charts showed zero-(0). The packet error count was going up fast and the actual sample rate (Hz) was bout 62+/- IIRC. It disconnected and I have not been able to reconnect since. I tried hooking up through the ribbon cable to a G1 adapter as well, but can't get the car to even run that way.

I'm new at this...any suggestions or help is appreciated.

 

Still no luck.

Using TunerPro RT. $6E ads file, and a stock trans am m5 bin from moates website. But even leaving my stock chip in and just trying to datalog, I can't connect that way either.

Any suggestions???

 

check your settings in TunerPro, go to "Tools" & then "Preferences"
next click on the ALDL/Emulation tab. see if its set to AutoProm for interface type.
also, put the AutoProm in pass through mode & set the interface to MAX 232 & see if it data logs like that.
try the 3 postion switch in both the open & 10K postions.

 

Thanks for the reply.

When setting it to the MAX 232, it will try and connect for several seconds, and then say connection failed. With it set to AutoProm, it just takes a 1/4 of a second and goes back to red saying ALDL Not connected. Switch in both positions causes the same reaction.

I'll try it again "fresh" and see what happens.

For the one moment it said connected, my computer had full battery. I wonder if that has something to do with it. I'll try it sometime this morning with the battery at full capacity and see what happens. I did try it last night with the battery charging, plugged into outlet...made no difference.



Hopefully today I can get on the phone with Craig or someone to help me sort this out.

 

The two horizontal switches are important. One of them enables and disables "Passthrough" mode. With passthrough mode enabled (switch away from the USB connector), the APU1 acts like a normal, everyday ALDL cable. The device's CPU is bypassed (therefore, TunerPro, etc, will not find the hardware). In this mode, you need to select "MAX232" as the interface type in TunerPRo, and you need to select the proper COM port, as determined by the Device Manager in Windows.

When not in passthrough mode, you need to use "AutoProm" as the interface type for ALDL.

The second switch engages and disengages 10K of resistence between pins A & B on the ALDL port. Your '89 requires the 10K to be engaged.

 

So I take it I should be able to datalog in both bypass (MAX232 setting) and in AutoProm mode. MAX232 setting inside switch toward the inside and outside switch toward the outside...or...AutoProm setting both switches toward the inside.

I think I'm clear on that, and was doing that correctly.
In the MAX232 setting I have the COM Port set to 5, and my Device Manager for the port is set to COM5.

With the above, I get the results mentioned in previous thread. Bypass mode it says connection failed. AutoProm mode it immediately responds with a red ALDL not connected.

Port Settings:
Bits per second - 9600
Data bits - 8
Parity - None
Stop Bits - 1
Flow Control - None

Receive and transmit I have tried 4092 and 64
Latency I have tried 1, 5, & 16


I will try again of course.

 

Let's simplify. Work only in passthrough for now.

The outer horizontal switch, I believe, is passthrough mode. It should be away from the USB connector.

The inner switch controls 10K. I don't remember which side is which, so you'll need to experiment.

- Open TunerPro and load 1227165_6E.ads (this is an '89 TPI, right?).
- Go to preferences and set it to use MAX232 on COM5 for Emu interface. Check that the cable works by using the test button. The COM port may change if you plug into a different USB port.
- Try to connect. if it fails, move the inner switch to the opposite position (thereby engaging the 10K).
- It COULD take a couple of attempts using TunerPro, since TunerPro doesn't do anything intelligent to hit the connection window specific to 6E.

If that works, cool.

 

89 TPI, yes.

When I load or re-load in the 1227165_6E.ads file, if I have the ALDL Dash showing, half the numbers turn beige while the rest stay blue. Just thought I would note that.

Set to MAX 232, COM5
Cable found and functional.
Try to connect:
CONNECTION FAILED
place switch in opposite direction, try again
CONNECTION FAILED.

No here's the catch...at this point if I go back to preferences and TEST for Valid Cable...this time it turns up CABLE NOT FOUND OR FUNCTIONING (8192 baud)

It does this every time...such as I turn off TunerPro RT, turn it back on...re-test, Cable is found and functional....Try to Connect...Connection Failed, re-test cable...NOT FOUND.

OK. Some progress maybe, any ideas...plan of attack?

Thanks

 

OK, this is exactly the same problem as Tim here:
https://www.thirdgen.org/forums/diy-...t-connect.html

In Tim's case, I think it's a problem with the driver for his adapter. In your case, you're not using an adapter.

What OS are you using? For XP or Vista, you need this driver:
http://www.ftdichip.com/Drivers/CDM/...0Certified.zip

 

what messed me up when i tried doing this last week (just started tuning)

is that make sure your cable is hooked up and tunerpro rt is looking for the cable on that specific com port ..

look under device manager for what # port it is (right click my computer / and hit manage) ..

if you cant set tunerpro for that port # then you can change it in the settings

.....................

thats the trouble i went through ..

other than that .. just make sure everything is plugged up, oh and make sure you got a chip in and the ecm fuse is in .. those will stop it from connecting ..

 

OS...Operating System??

Microsoft Windows XP I think is the answer to that question. The current driver, one it came with,is the 2.0.0 driver. I will install that driver as soon as I get my car back up and running...currently getting the starter rebuilt.

Thanks for the help

Adrians, I believe the Comm ports are set up correctly. I'll be sure to check the fuses though, not something I have looked at. Thanks

 

its the fuse on the front left if you feel up under the dash .. its a red 10 amp i believe ..

and i think the one next to the battery is also for the ecm .. not sure though ..

but if you can start your car, then dont even worry about checking the fuses b/c it wouldnt start if the ecm had no power ..

......................

as for the operating system .. i had trouble with my moms new vista laptop .. top of the line (2 month old) sony viao $2200 laptop and it freezes during datalogs sometimes ..

but my moms other laptop with windows xp runs flawlessly, even though its alot slower .. but doesnt freeze ..

 

Updated driver. No change in the MAX232 bypass mode.
I switched it over to AutoProm mode. Started pressing CTRL-F4 several times and about the 10th time it connected like it did before. No data being captured. Packet error count going up about 9 times per second. Sample rate about 9.1 Hz. I disconnected after a while, never able to reconnect.

Fuses are good.

??? What now ???

 

I found these two posts. I will try some things on here I haven't tried before.
If this doesn't work...then I'm pretty much fed up with this unusable $380 worth of emulation/datalogging/chip burning equipment I have. Honestly, I have had this stuff for almost a month now and have not been able to use it.

https://www.thirdgen.org/forums/diy-...et+error+count

https://www.thirdgen.org/forums/diy-...r+count+packet

If I can't get it to work, what are my other datalogging options?

 

Do you have a multimeter? Can you check to ensure that you're seeing 10K of resistence between pins A & B on the ALDL cable? If no 10K is present, one of the horizontal switches is in the wrong position.

Do you have another laptop you can try? Perhaps a friends?

There are a good number of people out there using AutoProms, both on XP and an Vista (I personally have a couple of AutoProms, and a bunch of computers). We need to find out what's different about your steps.

Have you tried calling Craig for support yet? His # is on his web site.

 

This is because you moved the horizontal switch out of bypass mode. In bypass mode, TP has to be set to MAX232 as the type (in which case the "test cable" button will work). Out of bypass mode, TunerPro must be set to "AutoProm" as the interface type.

If TunerPro detects the AutoProm at startup ("AutoProm USB" is lised in the status bar), then you're not in bypass mode, and you need to have the interface type set to AutoProm.

 

Craig hasn't called me back or emailed me back. I'll try again.
I'll try the multimeter thing, and see if I can get another laptop to try.
----------
I moved the switch for the 10K deal. I completely disconnect all when switching over. I have the switches and settings set accordingly. In bypass mode, I can test for function, and its good before trying to connect. After trying to connect...it tests nonfunctional. There is no ability to test for function when in AutoProm mode, so I assume its a moot point when in AutoProm mode. Connection fails either way. It just says connection failed in bypass mode. It just says ALDL not connected in AutoProm mode.

I'm not clueless. As a PE, I write specs, review specs, etc. I know how to follow details and read directions, etc.

 

OK, maybe a step in a positive direction.

Trying again it was a no go in bypass mode.

Tried in autoprom mode, and for some weird reason, I was able to connect a few times like before...pressing connect several times and finally getting it to work like BEFORE...no data captured, all zeros, etc.

I pressed Play Current ALDL Log Session, and it "looks" like I got a second of data, a snapshot of sorts. Here is SOME of the info:

0703 prom ID
Load Variable - 16
Coolant Temp - 281.3
Throttle position - 3.37
Block Learn - 0
Engine Speed - 5325
MAF - 0grams
Start Up Coolant Temp - -37.3degrees

Basically, all the data is screwy, real screwy.

Error codes 45, 43, 34, 32, 23


What might this tell you? I'm going to swap out ECMS with a spare I have and see what happens. Then rehook up the GP1 adapter and run a different bin with both ECMS, and see what happens.

 

That's not valid data. Focus on connecting in passthrough mode. 10k in place, MAX232 selected as the interface type (test using the test button to ensure your cable settings are correct). 1227165_6E.ads file. It might take a couple of tries to connect.

 

Talked to Craig Moates on the phone today (he was very helpful). He walked me through the steps, tested the ALDL cable with some software downloaded from his site, etc. We burned a chip using the Autoprom and an arap.ads bin, and inserted into the ECM using an adapter. Cranked the car up and all was good. Tried to connect...and got the same results in bypass or autoprom mode.

So at this point...it appears I can burn a chip, but have no datalogging capability. I will mess around with the aldl link itself and swap ECMs and then go from there.

This kinda sucks. Maybe I'm destined to use a carburetor.

 

SUCCESS

Swapped to a spare ECM. Works!!

Thanks for all that helped. There seemed to be no sign of the ECM being bad, but the spare fixed whatever issue was there.

 

Fwew! Lucky find. That could have caused even more headache than it already has!

Glad you're up and running.