Ok guys just got my cable today in the mail...I got the new drivers for it all that. Checked in Device Manager to check what Com port....its COM port 6....ok so i go into TunerPro Rt and load my 88.xdf file and 1227730_V6_90-92.ads file. I try the Test for valid cable thing...it only works right after i plug the cable in?....it will for for like idk 30 secs after its plugged it. After a lil while it will say Cable not found.... Is the Com port timing out or something? Either way even when it does say the cable is found i try and connect to the ECM...car is "on" position and it keeps saying connection failed?...im very confused. Ive read posts about this...i made sure i have all the new defitions of everything and the .xdf and .ads files are both corresponding. It would tell me if they arent anyway. Im very confused. Any help would be great.


EDIT: i have the '7730 ECM...its a 3.1l MPFI with SD...I have a newer laptop(maybe a year old) and its running Vista 64bit...i think the vista 64 bit is my problem. I do not have a xp laptop or a computer that i could bring next to my car....if i have to buy a crap computer just to tune my car im going to be pissed...i have a laptop for a reason!

 

I have the same problem alot of the time. Doesnt seem to recognize the cable is connected to the comm port. However i'm still able to connect to ECM even when it says cable not found. So keep trying it and see if it connects back up. Sometimes i need to try several times in a row before it finally connects. Big pain in the *** but its the way it works i guess. Also, does the cable have a 10K resistor switch? Usually switch the 10K resistor on when connecting and switch off once connected.

 

The use of the 10K ohm resistor should only be with the '165 ECM.

I have had difficulties using some of the "1227730" ads files that are on moates, lukily I generally only use $59 and S_AUJP which have great ads/adx files.
You may find that there is a problem with the ads file, and you will need to edit it to connect properly.

If I get a chance, I will try loading an $88 xdf file to my test bench and seeing what it's going to take to get datalogging working, since I do need to figure that out for a friends car anyway, using his TECH1 is getting annoying.

 

it does have the 2 way 10k resistor switch...i got it off of aldlcable.com or something like that...its a nice lil cable...and like six shooter stated i think thats not for the 730 ecm...i do remember reading about that and it mentions trying it in different states on the instructions...but ive read thats for the older cars.

Six_Shooter...if you could run a check on that it would be great...if thats all that is messed up i would be happy. Im just scared its my operating system on my laptop.

 

UPDATE: It will connect if I set the definition file at 160 baud. Correct me if im wrong but at 160 baud it will not display anything right? Cause i get nothing in my value tables, or dashboard. It seems as if the .ads file wont connect at 8192 baud. Im new to this so im not about to go customize the file. Hopefully someone can shead some light on me.

 

The baud rate is just how quickly or how often new packets, or information is sent down the ALDL line. It's not really the determining factor in whether information will be displayed or not, however, the '7730 is an 8192 baud data communication, so it is unlikely that you would get usable data. 160 baud is used with older ECMs, such as the '7747.

I haven't had a chance to sit at my test bench yet, but hope to in the next couple of days.

 

ahhh...well ive learned something today then...but yes whenever you get a chance that would be great...im actually currently in my car as i speak trying it out again...with no luck lol...oh well...gotta wash her and take her up to the cruise tonight...

 

Well, I've had a few minutes to sit down and try to connect to an $88 bin through the ALDL.

I have one ALDL definition that will connect, but the values are completly wrong, asI would have expected, since it was just a "7730" ALDL def dile, but not for any specific mask.

I have a few others that are for masks used with the '7730 ECM, and they won't even connect.

So it is likely as I thought, just a problem with not having the correct ALDL def file. Will likely need to start from scratch, which the information found in the "ALDLstuff.zip" file that can be found on moates.net filemanager.

Just for reference, I'm using a '7730, AZTY bin, Home made MAX232 based serial cable, XP pro. I can connect and read values fine in other known to be good masks/ALDL def files, such as $59 and S_AUJP.

 

Thank you for doing that!

Ok well thats good news and bad....good is that i know whats wrong...bad is i have no clue how to build an aldl file from scratch...i will check out that zip file that you noted tho....and could i use those that you mentioned to at least read my values on my car?...for now if i could just read the values and look at everything to get a sense of what values are and what i can monitor that would be great...or will those not work with my car...i am also using the azty bin....well ive downloaded it but i dont have a burner yet as i cant decide on what i want to do yet...i really want to go the ostrich 2.0 route but idk yet...so could i use the $59 and S_AUJP to read my stock ecm?

 

Go Ostrich 2.0, worth the money. FWIW, I own two Ostrich 2.0's.

The $59 and S_AUJP ALDL def files are only for use with those bins, since each mask and sometimes even changes within those masks have different values or items displayed on different packets within the ALDL datastream.

The file I have that connected would be anything more than garbage, since the values were not even close, such as when I adjusted the TPS, the RPM value changed, but was not only backwards, the values were really low, so it's not even something to use to get an idea of anything and would likely only farther confuse the situation.

The .zip file I mentioned has the ALDL datastreams for most if not all OBD1 GM ALDL datastreams.
It's not too difficult to set up a datastream def file, just time consuming. If you're new to this stuff, it will be overwhelming, you just need to start with one small part, and work your way from there. Getting enough set-up to connect and display one value, such as TPS (this is an easy one to maniplulate with the car not running ), and then add more values after you get that far will be a breeze.

 

ok well i did look through that .zip earlier today...there is none for a 3.1l MPFI LHO motor with a vin code of T (im guessing MFI is what im looking for right?...there are ones that say PFI?...maybe thats what i need idk)...the only two that look like they are close are A140 and A162. Ok so say it is one of those..now what do i do?....is there a tuturial on how to do this all. I mean you can click the .ds file...i guess this means definition file or something right. Ok well what do i do with that lol. Im new to this whole computer stuff. I was HOPEING that i could just start off easy...i bought the cable and downloaded tuner pro rt and took a look at that while i was waiting for the cable...then found the .xdf file i needed...then the .ads and then found the azty .bin file...i was thinking well hmm maybe i can take this stuff and at least just read all the different values in my car. Cause when i found the cool lil dashboard thing you could click different values like RPM, TPS, Coolant temp...and so on. I was like well this is cool...now i can look at different stuff and try and get used to it all...NOW i find out im gonna have to learn the hard way...pretty much like throwing your kid in the pool and saying here swim mother ****** lol...its messed up...i wish someone had an .ads file that we know would work for me. It sucks when ppl are trying to get into this stuff and just get there feet wet then they find out they gotta jump in the deep end. Thank god im a strong willed person and really want to get into this...well i also have no choise as i REALLY REALLY want to turbo my car...no one can change my mind...i dont even want an 8 at ALL...i just want to turbo my six lol.

alright enough story...i guess i need to find a "how to" on doing all this...i didnt do a search and asked first ...and i go around telling ppl DO A SEARCH haha...alright man well thank you for all the help so far...hopefully we can figure this out

 

Yeah, I had to jump in the deep end with some of the stuff I've done too, don't worry I know how you feel.

I made a tutorial for making an ADX (used with Scanner Pro) file for the '7747 ECM, which is 160 baud and a little different in communcation with the ECM, than the '7730/8192 baud systems. I posted it on the Tuner Pro site. http://tunerpro.net/forum/viewtopic.php?t=1016 You may be able to use some of the information there.

Use known good ads/adx files as reference, and you'll start to see patterns to what needs to be done to make it work. This is how I figured out how to make an ADX file for the '7747 ECM.

Nothing wrong with turbocharging your V6, I've turbocharged a couple of my 6 cyl engines now, a 3.2L 60 degree V6, using parts from 3 generations of that engine, and more, and my 2.8L I6 in my Datsun. I'm also using a GM ECM in the Datsun, running code59, which I recommend using in the end for your turbocharging effort. For now though, get used to what is in your car now, that can help you when you try using another code.

 

ok man ive read into that...its all starting to come together...all i can say is IM SO THANKFUL for all the people that have come together to do all this stuff...i mean could you imagine being the FIRST PERSON to actually hack apart all this and find it all out...i mean seriously wow...id admit that takes bigger ***** then i have...

First thing can you do me a favor and just check that .zip to see what one you think fits my car...if i can figure that out i should be able to go from there...ive read your tutorial and im going to use tuner pro to set this all up...hopefully i can get this working on minor stuff in the next week or so

....ok now i see you did this in scanner pro...im using tuner pro rt tho....can i still do this...or will it be different....i have a complete break down on the azty code...see heres my problem tho...is this the code thats on my ecm?...i mean i have never even touched my computer or anything....i just grabbed azty off moates cause i was told i should use that one...i had plans to just upload that onto my ecm then go from there...and another question...in your tutorial it says

..."You have to offset the byte number by -1, since the first byte or word of decimal "1" will actually be hexidecimal 00 or "0x00". Byte or "word" 2 will be 01 or 0x01, etc."...

does this imply to tuner pro rt also?...i just dont want to do all this typing in there and everything and then have it not work...and last question...say i get it set up and all ive entered is the command to look at RPM....can i just stop there and try it to see if it works or would i have to have everything in there before i can try things to see if they work?

sry for all the questions...im sure u understand why i have so many questions tho as youve been in this posisiton also...once again man...thank you so much for everything

 

Yes, the offset still applies to the .ads in TP RT. Remember this is a feinition of the datastream. The datastream doesn't change, because you're using a different program. You don't need to use hex, just 0 - 7 for the flags (bits), at least that's what I'm seeing in the .ads I just opened for reference.

Creating an .ads file is a little different than creating an .adx file, but I linked the thread as an example and there will be many similarities, such as referncing the .ds file found in the aldlstuff.zip.

Yes, you can set up just one item to check for connection, and verify the reading, that's why I suggested the TPS, since you can easily just turn the key on, and then press and release the pedal, to verify correct set-up. You can move the pedal to many points between 0 and 100% throttle, or 0V (which is usually closer to .5 to .6 V at closed throttle) to 5V at WOT. You can then set up two items to look at the same part of the data stream, to display in two different ways, such as TPS in volts and percentage, or temperature in degrees F and C.

I haven't had a chance to look through the file yet. The funny thing is I have been planning on starting an .ads file for this for a bit, since there are some people on another message board I (used to) frequent, that don't seem to be able think for themselves and use the information available to them. They create more problems for themselves by switching to another mask, just because there's a pre-existing .ads file for the "newer" mask. :facepalm:

The bin is just for reference, so even if you don't have that exact bin in your ECM, it should still be $88, which will have a lot of the same items and values that are in the bin you have downloaded. So don't worry too much if you have a different bin currently in your ECM. The datastream should be the same.

I too am thankful for the tuners and hackers before us and the ones that continue to develop and support new items and ideas in the DIY tuning community.

 

Im glad to here i can kind of go as i learn if u want to call it that...and ya good point about the datastream, i never thought about it like that, it makes sense now...I thought .adx was just a miss print of .ads, seeing how the s and x are right next to eachother...what is the difference then?

 

Ok I have an update. I first started to build my own .ads file and after a lil confusion after not working, i figured why not pull up the .ads file i do have...1227730_V6_90-92.ads...well i did this and just starting picking it apart to see what is going on in the thing...well i was looking at the sensor stuff in there and it looks to be all right according to the .ds file which matches the car. THEN I NOTICED it says on the comment section of the definition title that it used the A148 .DS file....well this is exactly what i found to match up for my car....so i continued to check through it all and it seems like its very well put together and everything looks good...my guess is that it has to do something with the actual command that is sent over...so i checked that out and it appears to be perfect...it shows F0, 56, 01 as the strings...which it should be(i think lol)...and payload size of 63, this is stated in the .ds file...offset is at 4...which it should be...SO this leads me to only one thing. Maybe just maybe THE GUY and ME both have the wrong .ds file. Thats the only conclusion i can get from this. Everything seems to be set up just perfectly and still cant connect or read values.

>>SO HERE IS MY CALL OUT TO EVERY PERSON THAT READS THIS<<

Take 2 mins and check out that aldlstuff.zip and check the index file to see which .ds file you believe to fit a 91 3.1L LHO VIN "T" F body car! I still believe its the A148 but it just DOESNT WORK!...it has to be something else

...both Me and Mark Mansur have now put together a .ads file that should work and both dont...mine wasnt as complete as his, as far as sensor readings and such, but still had all the same values. I did not copy his; i just build my own and said ehhh maybe i should check his out to compare them...THEY WERE THE SAME!...waste of time but at least i learned how to build an .ads file!

>>PLEASE SOMEONE HELP!<<

 

Ok well ive been talking to Craig Moates and Mark Mansur about this problem and have tried a few things...I still have had no success tho. It seems they are leaning more towards it being my actualy laptop or something within it not working. Mark stated that others have used the .ads file before and it worked. So idk whats going on...im trying but no success...hopefully someone has the answer cause im just running out of options.

 

It's not just you, because I also can't get it working.

Unfortunatly my PC seems to taunt me and will not boot now, I'm about to "boot" it.

So now I have to set up another PC to get my test bench up and running again. :facepalm:

I'll let you know of any progress I make, when I can.

 

haha can never win with computers can we?....and ya idk mark says that people have successfully used it tho...which makes sence cause when you look through the .ads file it all looks perfect...there is no good reason that the .ads file should be wrong...it has to be my computer is not reading the com port right or something to that sort

 

It has to be something with the ads, I can get a different ads to "connect" to the same bin, just the values are not correct. I can upload a different bin and connect with a matching ads without shutting anything off, this leads me to believe it's the ads and not anything else.

I just got back from paintball practice, so I'm going to grab somethng to eat, and then set up another desktop to use, while I'm modifying a couple Nissan ECMs for a friend of mine. So I hope I'll be back to a working test bench again tonight.

 

ok sounds good...thank you for your research...i just got back from a SUPER CRUISE here in batavia....good turn out...there was a 87? twin turbo 350 TPI firebird there!...hes on this site somewhere cause he came over and talked to me...the motor looked pretty sick...two twin turbos sticking outta the hood...but ya i have a stupid question....isnt the main command what connects you to the computer?....if this is so cant you just copy that command to the .ads file im trying to run...that way it connects and will also have the right values?

EDIT: actually what .ads can you get to connect?....i want to try that one and see if i can get it to connect on mine

 

Ok another update...ive tried a few more times to tweak this thing and still have nothing...What .ads file can you get to connect?....ill just use that to base my "connection" off of and then do all my parameters around that connection

 

Possibly run the TP application in compatibility mode for an earlier operating system. Might make the control of the ports operate better.
I think that is an option in Vista, not sure on the 64 bit version does.

 

I'll have to check when I get home, the desk top I have set up right now isn't complete, it doesn't even have the correct resolution option for my monitors. :facepalm:

I haven't installed TP RT on it yet so I haven't been able to do any bench testing.

I should recognize the file name when I get home though, I might have to send you the file I have that "connects". I checked everything in the header and all seems the same, IIRC, but will check again.

 

Thanks for the info...i tried it and unfortunately got nothing still


Six_Shooter...PM me and ill give you my email to send that over...or at least refer me to a link/site that has the .ads file on it

 

Hey Six_Shooter have you got anywhere on this....i still cant figure it out...i pretty much give up...im just hoping now that you can find out the problem...if you want to consider it asking for a favor then yes im asking for a favor...i really want to get this working so i can start reading my car and do some tuning...hopefully you or somone else can help...thanx

 

I appoligize.

I've been real busy with a few pressing concerns like th ecar show that I help run that was this past weekend, and a complete wiring job on a '49 Ford pick-up that needs to be done by tomorrow night.

I haven't even had a chance to set-up another HDD in my desk top, which is the biggest hold up.

I really hope to get to it this weekend I have other needs for the test bench anyway.

I haven't forgotten about you, just haven't had enough time, sorry man.

 

its all good...i understand...its been raining here for awhile and we finally had a nice day on tues and today...was just hoping to do a lil diagnosing with the computer and maybe some nice logs...my back tires really dont like the rain so doing any more then small throttle pulls willl be scary...but ya man dont feel pushed

 

Hey i know bringing back the dead thread



...Did you get anywhere on getting this to connect?...ive still had no luck on it.

 

Ok guys finally have an update on this issue i was having. Still not fixed but deffinetly got alot farther towards the issure. Another member from this site lives close to me and we met up to try this out.


We tired my laptop and cable on his car and WAH LAH connected right away. As soon as I hit connect it said ALDL connected with the lil blue box. It read data and everything...including some of his error codes he has

Either way this means it was my car....


So we went and looked at the ALDL port and he noticed after referring to diagrams and books that my ALDL port had the organge wire(data wire) in the wrong pin. We have no clue why it was in the wrong pin(maybe factory defect?) Either way he repined it and we tried again....nothing....


Ok so then we went to the passenger side and pulled down the 16 pin black/white connector and found pin J which is data stream wire. And we check to make sure with the tester that the wire was good to the connector. It tested good.

So we called it a day as I didnt really feel like droppin my ECU as its a PITA. So the next step is to try out a spare ECU that he has to see if its my ECU.

HOPEFULLY that does the trick. I really want to get around to doing some logs so I can figure out what this motor really wants.

 

Sounds like you've made some progress. Progress is good. Sounds like it wasn't a TunerPro issue, which makes me happy.

 

UPDATE!....GUYS I GOT IT!


Went to the junk yard today looking for a shifter boot, lid, window switches(any newer car backlit style) and console lid. Didnt find any 4th gens with the parts i needed left so i couldnt get the shifter boot or lid.

Either way I did find about 5 or 6 third gens. One looked JUST LIKE the bandit car...antenna and all(but picked apart to all ****)

Anyway I figured eh why not so I snatched a ecu out of a 91 firebird. It said ATZY on it and 730. So I grabbed it and figured mind as well try. Also got some new switches for the windows and mirrors. I will make a new thread about that later.


ANYWAY jump to the point(sry im exicted) lol

Put the computer in the car and wah lah...it connected.

So idk why the reman computer put in by my mechanic wouldnt connect but the junk yard one did.

Im so happy that I can now get to connect to my car. Im looking forward to doing some logs and learn to tune. Finally!