Does anybody know whether or not tunerpro and ostrich are compatible with the ecm of a 1985 2.8 l MPFI vehicle? Thanks

 

I would go to the manufacturers site and ask them.

 

Thanks. He can ask here as well and get the answer in a forum for all to benefit.

Toehead, unfortunately I'm not aware of any bin definitions for your year and engine. Do you happen to know what ECM your vehicle uses?

 

Actually, I don't. I tried to find it last night for a few hours, but every web site I could find listed every other ECM and then simply said "1985 MPFI" for mine, without the number. I do know it is a slow ECM that transmits at 160 baud. I will try to do some more research today and figure out what ECM I have.


EDIT : I found a site online that seems to suggest that the 1985 and 1986 MPFI ecm's are the same. I just happen to have the '86 ECM lying around from my parts car, and it is a 1227302 ECM, and there does seem to be a *.bin for that on the on the DIY ftp site.

 

Pulled from http://www.cruzers.com/~ludis/c3xref.html#1226870

Does that help?

 

Sure does. Everything you need is available to tune your application, and the Ostrich will ineed work with your vehicle.

1F.XDF (TunerPro definition) is available here and will allow you use TunerPro to tune your vehicle:
http://www.moates.net/files/3)%20Binary%20Editor%20Definitions/1)%20TunerPro%20XDF%20Files/1)%20General%20Motors/1F.xdf

Mark

 

Thanks for all your help magnus. This is why I love thirdgen. Does anybody know if there is a bin file available for me to download?

 

You mentioned the diy-efi.org FTP site in an earlier post. That's the place to start your search for a bin.

 

Sorry to revive the old post, but my car is coming along well and it's time to do some tuning. Does anybody know of a workable ALDL stream definition file for my ECM? The only one for my ECM seems to be from an 85 305, whereas I have the v6. When I use this file, it gives rediculous readings. Any help?
Thanks
Brendan

 

Looks like the A20 Datastream file has the definition for it.

DATA STREAM A20
2.8l MFI (LB6) (VIN=W) 85, 86
2.8l MFI (LB8) (VIN=S) 86, 87, 88, 89
5.0l MFI (LB9) (VIN=F) 85

If you can't find one and this is the correct definition, I can make it for you.

Besides the MALF words, it looks like there is much data output from the ECM.

ENGINEERING
WORD DESCRIPTION CONVERSION UNIT
1 MODE WORD 2 NONE
2 FIRST PROM ID WORD NONE
3 SECOND PROM ID WORD NONE
4 IAC NONE
5 COOLANT TEMPERATURE SEE TABLES DEGREES C
6 VEHICLE SPEED NONE
7 EGR DUTY CYCLE EU = N/2.56 % DUTY CYCLE
8 RPM EU = N*25 RPM
9 THROTTLE POSITION EU = N*.0196 VOLTS
10 BASE PULSE CLOSED LOOP CORRECTION NONE
11 OXYGEN SENSOR EU = N*4.44 MILLIVOLTS
12 MALF FLAG WORD 1 NONE
13 MALF FLAG WORD 2 NONE
14 MALF FLAG WORD 3 NONE
15 FUEL-AIR MODE WORD NONE
16 MANIFOLD AIR TEMPERATURE TABLE LOOKUP
17 MCU INPUT STATUS WORD NONE
18 LOAD VARIABLE
19 BLOCK LEARN MULTIPLIER NONE
20 ALDL RICH LEAN CHANGE COUNTER SEE **
21 UNLIMITED SPARK ADVANCE Not used !
22 MASS AIR FLOW RATE BYTE #1
23 MASS AIR FLOW RATE BYTE #2
24 BASE PULSE WIDTH BYTE #1
25 BASE PULSE WIDTH BYTE #2 EU =(BYTE1*256+BYTE2)*.0153 *** MS

 

That is the correct information, as far as I can tell . I've been looking and I can't find the file for the life of me, on any of the sites. If it's not too much trouble, i'd really appreciate you making the file for me! thanks for the help, it is very much appreciated

 

No problem. I will try to get it done in the next day or 2. Problem is, I can't find the connection string so not sure what to use so I can connect to it.

**Never mind found a 160 buad ads for a idfferent vehicle and see that it just streams the data out and needs no conneciton stream.

 

It's almost certainly 160 baud, so there is no connection string. Use 1227165_160baud.ads as a model.

 

Found one for it on Moates Site. The 5.0L F boday uses the same stream as your 2.8. Here is the link to the file.

http://www.moates.net/files/4)%20Dat...ud_85_Fcar.ads

 

Thats the one that gives nonsense numbers, such as I'm going 3000 miles an hour haha.
I'll take a look at the file, maybe there is a mistake in it?

 

I'll go through it and post a new file if need be. But that looks like the correct ADS file.

 

Ok, thanks, You're a real help. I'll also go through it and see how it ticks.... Who knows, maybe I can figure out how everything works, despite my lack of experience with the software.
-edit. I did a limited running of the file.... I had winaldl open, verified the cable transmitting data correctly. I then shut winaldl down, and started tuner pro. The data was still all gibberish and all over the place, changing with every refresh. I forgot to mention that I am using the cable diagram from the winaldl site.. Tomorrow I'll dissect that file anc compare it with the A020.ds file.. maybe I can figure out how everything works. Thanks again for your help.

 

Fixed it It was a faulty solder connection introducion noise. All better now, no more gibberish! thanks for all your help!

 

nevermind. On the running car, it still is gibberish with occasional good data. WinALDL works perfectly.... Any ideas?