I have multiple written conversions on different forums about using tunerPro Rt as a scan tool to read codes and clear them on an OBD1 system. How is that accomplished? Take it slow my primary tool of choice is a torch!
Printable View
I have multiple written conversions on different forums about using tunerPro Rt as a scan tool to read codes and clear them on an OBD1 system. How is that accomplished? Take it slow my primary tool of choice is a torch!
You can use TurnerPro RT as a scantool. Nearly all the scantool controls are under acquisitions. I use TurnerPro RT only as a scantool.
See this thread for a quick tutorial.
http://www.gearhead-efi.com/Fuel-Inj...-for-Beginners
Robert
OK, torches are not a tool we use! :laugh:
If you data looging well your also scantoooling! Depends on how the .adx is written but normally all codes are in there too. There is a way to clear codes on 8192 baud systems because they are bi directional. but 160 baud like 1227747 is only one direction and you have to disconnect battrey to clear codes.
So what car are you working on? what ECM or mask? Then we can get more specific...
So how do I see a code? Exactly??????????????????? All that stuff is great for the siliconhead in me, but if there is a mechanical situation that I need to address first, don't I need to fix it before I log???? I mean I know that I can use a paperclip, a short piece of wire, anything conductive, but how can I see that shit on the screen and record what I am seeing so I can print it and refer to it at a later time?
The lumina, that I have a thread on in the main (?) question forum. I was also wondering for a general question. My thought is that if I record this stuff then pull the codes, then refer to the codes, then go to the parts store and compare notes. I'll actually have something to refer to!!! I have a buddy that runs an autozone store, he hunts my land and always gives me hell about using a paperclip to pull codes. He's not a mechanic, he is a hell of a material storage specialist!!!
And while I'm at it what the hell is this for?
3.5) Optional. GM OBD1 data streams
ftp://diy-efi.org/pub/gmecm/ALDLstuff.zip
What does it do? Other then confuse the hell out of me?
I forget if it ended up being $A1 or $DF? Which adx are you using?
Just forget the ALDL stuff! It is the files we use to make the .adx
I had toe surgery today so I can't walk and will have loads of computer time and work on your adx for you and teach you.
We have links to error codes per year make model so you will know exactly what it is.
So what .adx ?
I assume this is what we are talking about in this thread.Quote:
the sticker says
Service 16149396 BDJS
86BDJS M231251017
16186551
To use TurnerPro RT as a scantool you need the correct ADX file. The ADX file corresponds to your car's ECM data stream file.
It is best to with your ECM's BCC code. Your reported BDJS.
Here is what I get out of BCC lookup.xls
BDJS 1993 33994 16186544 16149396 6578 6551 WB LH0 3.1 M13 AUTO
http://farm8.staticflickr.com/7150/6...1567999312.jpg
GM or some kind internet citizen provided a look up table to assist us in finding the correct data stream type.
What data stream your car's uses is buried in INDEX.DOC. It's is found in the zipped file you download in step 3.5. ( not optional I guess now. )
Of course, the information provided lets us develop our Sherlock Homes powers of deductions.
I suggest searching on LH0
The search yields 19 cars with the LH0 engine. Fortunately, only three were built in 1993.
The first '93 LH0 was found on line 829 of the INDEX.DOC file.
INDEX.DOC:829: 3.1L PFI (LH0) (VIN=T) 93 1J,L,2J,1,2,3W cars
INDEX.DOC:1117: 3.1L PFI (LH0) (VIN=T) 93 1W,2W,3W,4W -CAR
INDEX.DOC:1297: 3.1L SFI (LH0/GENIIS/VIN=T) 93 1W,2W,3W,4W 4T60E AND NB2 ONLY
from INDEX.DOC I notice that there are three possible data streams.
DATA STREAM A140
ENGINE USAGE:
3.1L PFI (LH0) (VIN=T) 91 W,A,J,L - CAR
3.1L PFI (LH0) (VIN=T) 91 4W (4 door) (vin serial > 799,999)
3.1L PFI (LH0) (VIN=T) 92 1,2,3,4W, 1,2J, 1,7L - cars
3.1L PFI (LH0) (VIN=T) 93 1J,L,2J,1,2,3W cars
3.1L PFI (LH0) (VIN=T) 94 1,2J
DATA STREAM A186
ENGINE USAGE:
3.4L PFI (LQ1) (VIN=X) 92 W-CAR
3.4L PFI (LQ1) (VIN=X) 93 W-CAR
3.1L PFI (LH0) (VIN=T) 93 1W,2W,3W,4W -CAR
3.1L PFI (LH0) (VIN=T) 94 1W
DATA STREAM A214
ECM USAGE:
CAR LINE:
3.1L SFI (LH0/GENIIS/VIN=T) 93 1W,2W,3W,4W 4T60E AND NB2 ONLY
That give you the data stream possibilities of A140,A186, or A214 data streams.
We can eliminate one or two by finding out what type EFI your engine uses.
That is the best that I can do. I think that there will be a prom id in the data stream, so you can tell if you have guessed correctly. The prom id is from bcc lookup.xls.
1 PROMIDA FIRST PROM I.D. WORD (MSB)
2 PROMIDA+1 SECOND PROM I.D. WORD (LSB)
Now go over to this web page and download the data stream definition file for TurnPro RT.
http://tunerpro.net/gmOBDI.htm
This page had the older ads format, but TurnerPro RT will automatically convert to adx.
Robert
PS. One step at a time will get your there.
This is more complex than even I remember it. No wonder it took me & my friend three months to get it to work. Well, it took us a month and a half to settle on TurnerPro Rt. So, only a month & a half to get TurnerPro to work on my Corsica.
Robert
Nice work!
But with that work I still don't know which adx? Looked at TunerPro and TunerCat website and still no difinitive answer, but with this:
http://wiki.3400z24.com/16149396
I think his mask is $DF, that's where I found his bin. Also in that folder I got from Robert is a $DF ads but no info as to what ALDL it started with? So I looked at the ALDL.ds files historystamp found for you to compare and found A214 just does not match what Robert had there. A186 and A140 do! But A140 is for a 1227727 which is same as 16149396 but 16149396 has additional ram and controls for e-trans as noted in link above! So I beleive A186'ds is correct ALDL file and the .ads file named $DF is correct for his car.
That one was a pain to figure out but I think we got it. Thanks to Roberts work on these type cars in the past.
Give me a break and I will get a $DF-16149396-V1.adx ready for you to try. We may need to try a few. Have you got your cable? Have you ever hooked up to the Lumina yet?
Yep I got a cable, loaded the drivers, played with it the night it showed up. The next morning I logged my drive to work. Looked at it at work (let's just say that I started at the guage cluster in tunerpro rt during every break and lunch), then logged it on the way home too. All of this was done on my 1989 V1500 suburban with 350/700R4 3.73 rear. I have not plugged into the lumina, but I did find (don't know if it is right or not) the (don't remember the names of the files) 3 files that are required for a computer to (don't know if I'm using the right language again) communicate with the lumina. The files were on this website. 3 things that need I need to advise on:
1. I can connect to this website with my pda, but I can log on and read, just can't input information. I can input information at another forum.
2. The lumina is a 4 door vehicle, and where it is there is no internet AT ALL.
3. I use another laptop to communicate with vehicles. That laptop does not have any connection to the outside world other then the disk that I load to it. I do this for a number of reasons, mostly for security, if I loose or the laptop is stolen I'm out 20 bucks, if this laptop is lost or stolen I'm out a few k's, including the information that is on it.
I said the thing about a torch because I am not a mechanic, well not professionally, I am a diesel fabricator. I only spin wrenches for myself, so a torch is my main tool of choice, and because a plasma is too damn loud!!! I mainly work on large detroit, and cat powered vehicles, but I have always been amazed at what a 25 year old truck is still capable of, and what could still be obtained out of 'passed over' technology. Granted this power plants are not as efficient as the newer motors, but I would like to begin to learn on something that is relatively cheap and plentiful to replace if I do a 'oops', compared to what I want to put in the truck. Eventually I want to dd my suburban but with a few added features, like a 6.0 rebuilt from the ground up, with twin turbos. Moderately producing 1000 horsepower, with a 4l80e and a 203/205 transfer case, I am currently building the new rear end from a $50 14 bolt that I aquired from the scrap yard. I will be attaching the truss (full width from spring perch to spring perch) hopefully by the end of the week. To top it all off I want it to sit on 40" tires. Not to much to dream for huh, I dreamed of this truck for many moons in a foreign land being home and building it, I have gotten to the point in my life (which by the way I never thought I would be alive by now) where I can think about it.
For years my buddies told stories that they were going to come home and buy the newest vette and the hottest split tails would just walk up and go for a ride, then they would ride them. Well, I told stories of a 'monster' 4x4, 30 years old looking like it just rolled off of the assembly line, but with the powertrain of a vette, with the capablity of a tank, and the agility of an airboat. That's what I'm building, and this is why I am learning.
Like a 14 bolt needs a truss! :rolleye:
The rest sounds like fun. :rockon:
Well I have a few hours into the adx for you. It may or may not hook up and record data first shot. I'm getting better at this so give it a try and let me know how it works. DashBoards are installed but not all values are set. Right click on item and put what you want where.
Item lists have engine data, Error Codes and Switches.
If it hooks up first time get a data log so I can work on it further. If not we will make small adjustments till we get one solid connection first time every time!
Your lucky that Dan T (Sil - 60degreev6.com) wrote a very complex xdf for this engine. I started working on it with data tracing. If you want simple to start get the one named $DF.xdf
If you want the more complex that will have data tracing get the set of
$DF-16149396-V1.xdf
and
$DF-16149396-V1.adx
Your bin is also in this thread with adx and xdf.
http://www.gearhead-efi.com/Fuel-Inj...Information-DF
Once you get the correct .adx working, seeing which codes are active, is not all that hard, but you would be better to set up a different dash for just that purpose. You could populate it with just malfunction flags from the bitmask section, and maybe a couple of key sensor outputs, like what you would see in a OBDII scantool. So you would connect the DA and then when you turn the key on any active codes should show up.
I never thought of a dash for error codes? Cool!
I set that up for him so he has an Item List page for error codes.
Oh yea I forgot those are all in the item list/sensor data window. :homer:
Wow, I just got rid of my headache before I read the thread. Then I reread the thread, I think I'll need more asprin. I'll go out there this coming weekend, like in 5 days and plug in to the lumina. Now where do I start?:homer:????????????????????????????????????? ?????????????????????????????????????????????????? ?????????????????????????????????????????????????? ???????????????Hope??????????????????????????????? ?????????????????????????????????????????????????? ?????????????????????????????????????????????????? ???????????????????you???????????????????????????? ?????????????????????????????????????????????????? ?????????????????????????????????????????????????? ??????????????????????? get??????????????????????????????????????????????? ?????????????????????????????????????????????????? ?????????????????????????????????????????????????? ???? the??????????????????????????????????????????????? ?????????????????????????????????????????????????? ?????????????????????????????????????????????????? ???? picture. I just got the basics understood, you guys remind me of getting in country just landing on the tarmac with 2 linguists but neither one speak the correct dialect. DOH!
Well you just did it on your truck, so what's the issue? Same thing, differant files.
Back in this thread I had them ready to try:
$DF-16149396-V1.xdf
and
$DF-16149396-V1.adx
Your bin BDJS is also in this thread with adx and xdf
http://www.gearhead-efi.com/Fuel-Inj...Information-DF
So how do I see the codes themselves? Is it in the parameter tree? Do I need to open that and then poof? They appear?
Yup! Paremeter tree should have Scalers, Bitmasks and Tables from XDF Just sift through them a few times and they start to make sense with your bin loaded.
But you are going to use the ADX to record data just like your truck. If you get a glitch in data let me know and we will fix it. I do not know if the ADX has been proven like the $42 stuff you used in yuour truck.
KO so what is the difference between the $DF-16149396-V.xdf1 stuff and the and the $DF.xdf stuff and the DF_v1.6.2.xdf I am assuming that something is different or altered but what? What constitues changing things in a file to change the name?
BTW I have ALL of it loaded on a disk sitting on top of that laptop for this weekend. Thanks!
44 Oxygen sensor voltage was under 0.25 volts for at least 60 seconds of closed
loop operation.
How the hell can the O2 report less then .25 volts for at least 60 seconds and the system stay in closed loop operation? I didn't think that was possible. Isn't the point of the O2 sensor to report back to the computer the mixture of the intake, kinda like a double check of input ops? Why wouldn't it return to open loop if there was a problem with the O2 sensor?
Sometimes ads files from TunerPro V4, are imported to TunerPro v5 to make it an ADX. The adx needs a little tweaking to work in TunerPro V5. I set up 2 files for you to try with tweaks that are known to work. So far I have found they are all differant. Tweaks that work on one, don't work on another and some need both?
So try 1 and if it connects good and no data glitch we are done. If you get a glitch? try 2.