sparks454

iTrader: (1)

I just made the 2 transistor cable and still am not getting any data showing using tunerproRT. I'm running the '87 165 ecm with ARAP 6E bin. I have the definition set to 165 6E in tunerpro and have tried 8Hz, 10, and 11 hz in the setup. The car runs so it seems the chip is programmed right. and I have the cable hooked to the ecm w/ ground to A, pwr to B, and data to E. It works with my old 1 transistor cable and winaldl. Using a meter on the female end of the DB9 connector, between grn and pin 2 the voltage jumps back and forth quickly between about .1V and 1V. Between grn and pin 3 the voltage jumps between .4V and .8V.
It appears that there is data being sent...correct???

NOTE: I don't have pins 1,4 and 6 and then pins 7 and 8 jumped together like in the diagram. Does this need to be done???I didn't do it because my windaldl 160 cable does not have this done either...



Any other ideas would be helpful. I have tried connecting about 10 times by different methods. ie. unplug db9 from laptop and boot tunerpro, etc.....

Thanks.

sparks454

iTrader: (1)

??

RBob

iTrader: (1)

Pin B of the ALDL connector only has a 10K pullup to 5 volts. Try hooking that wire of the 2-transistor portion directly to 12 volts (and disconnect it from pin B).

RBob.

SBNova

I cant say wether those jumpers are required, but I have them and my cable works. If the schematic says put them in they probably need to be there.

Ditto on the 12v thing, I put on a "lighter" plug and plug mine into the lighter socket in my car for the cables power supply. I know mine wont work without it.

sparks454

iTrader: (1)

I'll give the 12V thing a try right now and if that doesn't work I'll jumper those pins that show jumpers.

thanks,
Chris

sparks454

iTrader: (1)

The 12v directly to the battery did not work so I solder in jumpers.

thanks,
Chris

sparks454

iTrader: (1)

No luck using the 12V thing or soldering the jumpers. I opened winaldl and there was data flying across only the top 4/5 rows of the raw data screen but no sensor data..

With tunerpro, if I select 165 160 baud.ads and check the 160 baud box and hit connect, it connects immediately but the sensor data shown is garbage. If I select the 165 6E.ads def. file I get not connected no matter what I try. Without the key on it shows not connected pretty quick after pushing connect to ecm. With the key on it looks like it tries to connect for maybe 2-3 seconds or so...

Not sure where to go from here, but by opening winaldl the data going across only a portion of the screen is 100% faster than it used to be.

Any bios setting that needs changed???????

jwscab

i just tried tunerpro the other day, with the 6E ads file, in my 87 camaro, running 32B, seemed to work fine, so this is a follow up to your original questions regarding 32B vs 6E, etc.

I use an aldl converter based on schematics on andrew mattai's (sp?) website, using a max233(like 232, but less wiring).

I initially had trouble with tunerpro, but I had the wrong com port selected, so make sure that is correct. otherwise, i grabbed the 6E ads file that was included with the download, connected eveything thing up, and i have to admit, it took a couple tries to connect, but it did, and i got valid data. I left it at 10Hz also.

be sure to power your circuit from 12v, a cig lighter is good, like others mentioned, and the only other thing I would say is to make sure nothing else is really running in the background on your laptop.

if that all doesn't work, i think you need to just step back, and start from scratch, but don't give up, it will work!

sparks454

iTrader: (1)

I'll give it a couple more times, but I'm growing weary...Let me know how you tried to connect,ie. pushing connect to ecm over and over, or unpluggin the cable and relaunching tunerpro and plugging cable back in etc...I think that would be helpful.

Thanks

jwscab

uh, lets see.......i had the aldl cable plugged in, car off. plugged in the laptop, both the serial cable, and the inverter/power supply. I power both the serial adapter and the laptop from the cig lighter, using a splitter. 10K resistor in place(I just have a switch), data pin E.

then I started the car.

i fired up tunerpro, and went to hit the connect button. i tried that a couple times, each time it did not connect. I figured all the settings had to be right, but i needed to check the com ports. I quick went to device manager to verify com 4, and then went to preferences in tunerpro and set to com 4. i then tried to connect a couple of times, then it worked. I had it hangafter a few minutes and not read data, so I exited the program, then started it again, and hit the connect button, and it connected.

so what you've said you've done should have worked. I would also suggest you try craig moates software ecm852, at www.moates.net, and see what that does. for that program, just make sure you select the right ecm(165) doesn't care which mask you have(32B, 6E)

other than that, it has to be one of two things. either the laptop is doing something funny, or your cable is faulty. i would try and maybe try another laptop?

sparks454

iTrader: (1)

Another laptop is out of the question. I remember seeing on Craig's site that the ECM852 software does not work on windows 2000 which is what is on my laptop. I did load it and tried to connect with it, but it says no link up. I use this laptop for work. I dunno... I use comport 2 which is the rs232 port. It's the same as the com port used for winaldl on this pc.

I guess I have to start at looking at the cable then...

Thanks,
Chris

Cobra289

Chris (Sparks)

If you try first WINALDL and you get connected and after that you try TunerPro you will get problems. Once the port is activated by one software, it will never be released for the other.
So try to reboot first to get rid of the claim of the com port.

Regards,
Cobra289

sparks454

iTrader: (1)

Hey cobra. I have tried that also. I only tried the winaldl once or twice over the course of rebooting and relaunching tunerpro about 40 times now.

I unplugged the cable from the back of the laptop and put a meter on the DB9 connector on the cable. Pins 5 and 2 show 12.2V with the key off. Key on shows toggling between .5 and 5.5V, so it looks like the data is being sent to the pc. Testing pins 5 and 3 there is minimal toggling between .02 and .1V.

Any thoughts on that info. With the key on and connecting to tunerpro I show connected V86.86 on the bottom left of the screen which is bad from what M. Mansur said. With the key off and launching the program there is no error just no hardware or hardware not attached.

Should i see the voltage toggling on pin 2. I think I should being that 2 and the data line are together through a transistor. Correct??

sparks454

iTrader: (1)

Things just keep on gettin worse. I replaced the transistors in the cable. Same thing no data. Tried winaldl again. Works fine...

***Do I need a resistor across A and B even with the 2 transistor cable???????????

Figured I had enough for the night and now the car won't start!!!! It's starting in limp mode. Pulled chip and it verified to buffer. REprogrammed anyway. Same thing....limp home mode....Could something with that damn cable I made fried the computer. The chip veriified o.k. I tried another set of limp home chips. Same results. I did jumper A and B with a paper clip to check for diagnostic code and the SES light flashed one time then paused and flashed twice quickly and stopped and then a couple seconds later repeated. Not sure what that means..ECM and ignition fuses checked out good.

Does anyone wish to buy this t/a..........need some help before I junk it.

Mangus

OK, here we go. Everything laid out (in no particular order, and paying no attention to what you may have already tried):

- For 8192 baud data with a '165, you NEED the 10k between A and B.

- Make sure your cable works as it should (for 8192). To ensure this, download Datamaster's cable test utility and run all the tests.

- If you're absolutely certain your cable works, check it again. (Especially if you can't seem to connect but everyone else using a similar setup can).

- Moates ECM852 works fine in DOS mode regardless of what OS is installed on the HD. I'll say it gain: create a DOS boot diskette, copy ECM852 to it, boot your laptop/PC using the diskette, and launch ECM852 from the command line. If ECM852 can connect but TunerPro can't, you're full of it (Wait, I mean, we can go from there. Did I say that out loud?). If TunerPro doesn't connect, I'm relatively certain a) ECM852 will not, or 2) if ECM852 connects, you're probably just not giving enough connection attempts in TunerPro.

- Make sure TunerPro is configured to use the COM port your cable is communicating with. Make sure the interface type is MAX232/2-Trans.

- If attempting to grab 8192 data, make sure your mask supports it. $32 does not. $32B (I guess?) and $6E (for sure) do.

- Make sure you have the correct datastream definition file for your application. If your setup uses $32B or $6E, the 1227165_6E.ads file will work for both (for 8192 baud). If you're using $6E or $32, 1227165_160.ads will work for both (for 160 baud). If you're using something else, I don't know what you need. Consult some of the other regulars. =)

- 160 baud will *always* show connected when you begin monitoring (since 160 baud doesn't have a "connection" routine. So it doesn't matter whether you are getting "real" data or not, in 160 baud mode (using a 160 baud definition), you'll always see "connected" when you click "begin monitoring". This will change in the next version. I know its misleading.

- TunerPro does not currently support 160 baud data acquisition if using a USB to serial converter (or a Moates USB ALDL interface cable). This will be fixed in 4.0.

- If your car supports 8192 baud or has the ability to with a simple mask change, do it. If you're using $32B or $32, update to $6E. (Optional, but recommended by most).

- If you still are having problems, try a different computer or different cable. Find a friend.

- If you still are having problems, sell your car, learn how to make donuts the old fashioned way, and take that up as your hobby.



- I'm kidding in a lot of places in this post.

MTPFI-MAF

Ok I made the diagram Third Gen Specific

Might help Some one latter so here it is.

sparks454

iTrader: (1)

Thanks for the diagram. That's really helpful. Where can i get the cable test utility???? I am running the 6e bin and the 165. I could not get Moates's software to connect either , but then again i did not have that 10k across A and B.

Back to the limp mode startup now....What could have happened??

SBNova

The reason you only had *some* data in WinALDL was the lack of the 10k. If I scan mine with WinALDL, without the 10k, thats what I get, insert the 10K (while running) and you get the rest of the data almost instantly.

sparks454

iTrader: (1)

I got the cable working with tunerpro now. The issue is the 3rd gear TRUE flag when the key is on. I think this is why it's starting in limp mode, but I am not sure how to correct it...

Cobra289

Hi Chris (Sparks),

NO resistor NO glory.

It will be handy if in addition of the resistor you put a switch.
If you put the switch and after be connected you can switch open the 10K resistor so that you will get a full logging information.
Regards,
Cobra289

67 ss

I have been fighting this 2 transistor cable myself trying to get it to work. I did wire mine to power off the 232 port like the 1 transistor cable will this not work that way?? I used a lab scope to watch signals and everything looks good till I hook the ground to the aldl connector then everything flat lines. Any advice would be appreciated.