Help with WINALDL Software & 1985 Corvette?
#1
Instructor
Thread Starter
Member Since: Oct 2002
Location: Seguin Texas
Posts: 116
Likes: 0
Received 0 Likes
on
0 Posts
Help with WINALDL Software & 1985 Corvette?
I have the USB WINALDL cable and the newest version of WINALDL software. When I connect to the car I only receive data on the RAW data panel. I have numbers for MW2, PROMIDA, PROMIDB, and an occasional number for IAC and CT. Nothing else shows up. No other screen shows any data.
I have the 1226870 ECM selected.
Am I doing something wrong? Is my ECM bad?
I have the 1226870 ECM selected.
Am I doing something wrong? Is my ECM bad?
#4
Drifting
Member Since: Apr 2004
Location: crystalriver Florida
Posts: 1,453
Likes: 0
Received 0 Likes
on
0 Posts
since were on the subject....SAME boat here too-almost. With my winaldl program running (While connected to my 85's ecm) I get the raw data,sensor data and errorcodes showing, but as for BLM, 02 and INT--these 3 are exactly the same, shows a bargraph and a bar floating between 800-1200 scale----I'm assuming thats the RPM of the car as its running. I thought the bar graphs would show the data right there before me, But I have discovered by hitting the
"save" button at the bottem, it will save the file onto the aldl program. And when you click on that, you'll get several bar graphs show up and the bottem ones have "1" in every section...Any idea of how to get the proper readings, pcm4less needs the BLM/02/INT readings inorder to properly check the readings and make sure the chip is correct that he did for me.
Here is 1 same off of an o2 file: Not sure what 24/48/72/96 etc are ?? baud rate, I know the left column is the RPM range,
Wide # Samples
RPM \ MAF 24 48 72 96 120 144 168 192
400 9 0 0 0 0 0 0 0 0
800 26 0 0 0 0 0 0 0 0
1200 25 0 0 0 0 0 0 0 0
1600 1 0 0 0 0 0 0 0 0
2000 0 0 0 0 0 0 0 0 0
2400 0 0 0 0 0 0 0 0 0
2800 0 0 0 0 0 0 0 0 0
Wide Avg 10
RPM \ MAF 24 48 72 96 120 144 168 192
400 0.451 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000
800 0.484 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000
1200 0.477 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000
1600 0.349 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000
2000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000
2400 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000
HERES a sample of the INT file: Do these readings look right ?
Wide Std. Dev. 10
RPM \ MAF 24 48 72 96 120 144 168 192
400 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
800 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
1200 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
1600 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
2000 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
2400 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
2800 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
Narrow Correction 10
RPM \ MAF 24 48 72 96 120 144 168 192
400 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000
800 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000
1200 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000
1600 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000
2000 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000
2400 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000
2800 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000
3200 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000
"save" button at the bottem, it will save the file onto the aldl program. And when you click on that, you'll get several bar graphs show up and the bottem ones have "1" in every section...Any idea of how to get the proper readings, pcm4less needs the BLM/02/INT readings inorder to properly check the readings and make sure the chip is correct that he did for me.
Here is 1 same off of an o2 file: Not sure what 24/48/72/96 etc are ?? baud rate, I know the left column is the RPM range,
Wide # Samples
RPM \ MAF 24 48 72 96 120 144 168 192
400 9 0 0 0 0 0 0 0 0
800 26 0 0 0 0 0 0 0 0
1200 25 0 0 0 0 0 0 0 0
1600 1 0 0 0 0 0 0 0 0
2000 0 0 0 0 0 0 0 0 0
2400 0 0 0 0 0 0 0 0 0
2800 0 0 0 0 0 0 0 0 0
Wide Avg 10
RPM \ MAF 24 48 72 96 120 144 168 192
400 0.451 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000
800 0.484 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000
1200 0.477 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000
1600 0.349 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000
2000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000
2400 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000
HERES a sample of the INT file: Do these readings look right ?
Wide Std. Dev. 10
RPM \ MAF 24 48 72 96 120 144 168 192
400 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
800 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
1200 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
1600 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
2000 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
2400 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
2800 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0
Narrow Correction 10
RPM \ MAF 24 48 72 96 120 144 168 192
400 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000
800 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000
1200 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000
1600 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000
2000 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000
2400 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000
2800 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000
3200 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000 1.000
Last edited by chillcat; 03-27-2007 at 11:35 PM.
#8
Instructor
Thread Starter
Member Since: Oct 2002
Location: Seguin Texas
Posts: 116
Likes: 0
Received 0 Likes
on
0 Posts
I have data under the BLM tab but it is slow and takes a while to show up. So far I see nothing under INT or O2. A box will light up just like the BLM but no data shows up.
#10
Burning Brakes
Member Since: Dec 2002
Location: Lakeland fl
Posts: 1,088
Likes: 0
Received 0 Likes
on
0 Posts
Why not just try TunerPro? Its much newer and better than WinALDL. There never used to be a publicly available XDF for a 6870 but I think there is one posted on Moates.net/fileman now. A 6870 is $1F right?
http://www.moates.net/fileman/index....neral%20Motors
I think you'll also need the datastream definition here;
http://www.moates.net/fileman/index....%20Definitions
If you need a username and password its;
moatesuser
moatespassword
-Jim
http://www.moates.net/fileman/index....neral%20Motors
I think you'll also need the datastream definition here;
http://www.moates.net/fileman/index....%20Definitions
If you need a username and password its;
moatesuser
moatespassword
-Jim
Last edited by SBNova; 04-01-2007 at 09:36 AM.
#12
Safety Car
Member Since: Mar 2005
Location: Fredonia WI
Posts: 3,567
Received 491 Likes
on
392 Posts
2023 C4 of the Year Finalist- Modified
Finalist 2020 C4 of the Year - Modified
C4 of Year Finalist (performance mods) 2019
2018 C4 of Year Finalist
Why not just try TunerPro? I think you'll also need the datastream definition here; http://www.moates.net/fileman/index....%20Definitions
Thanks,
Gary
#13
Burning Brakes
Member Since: Dec 2002
Location: Lakeland fl
Posts: 1,088
Likes: 0
Received 0 Likes
on
0 Posts
I never tried it because my 6870 ecm is long gone. The 6870 was used in a few different cars in '85, and although the bin file changed the ecm is still the same so it should work fine. Newer 165 bins are easily interchanged between F and Y cars.
#14
Drifting
Member Since: Apr 2004
Location: crystalriver Florida
Posts: 1,453
Likes: 0
Received 0 Likes
on
0 Posts
I downloaded that tunerpro file, so when I connect the aldl chord to laptop, I open the tunerpro log and fire up engine and will data start showing up in the bargraph? I'm not familar with tunerpro. Car is at chevy getting a problem fixed so I can't check it yet.
#15
Burning Brakes
Member Since: Dec 2002
Location: Lakeland fl
Posts: 1,088
Likes: 0
Received 0 Likes
on
0 Posts
You'll actually need TunerPro RT. It costs $35 to register it, but its free to use eternally if you dont mind the 10 second nag screen. You *should* load the correct XDF file for the 6870, which really only shows what you can change in the bin file, if you have the means to read or burn a chip (or emulate). Then click the small icon near the top that looks like a hand holding a piece of paper. Under datastream definition there is a box that says "browse". Click that box, and select the 6870 .ADS file from wherever you stored it. While your on that page, click the "select log file for REC/PLAY" button, and create a file to store your datalog. Logging/recording is not required to view data, but this is where you create and name the file to do so. Choose a name and click "open". It will say the file doesnt exist and ask you if you want to create it- click "yes". You are now ready to record data. I usually name my files with the date. Create a new file each time you log.
Once the cable is hooked up to the ALDL port and your laptop, turn the key on (some just start the car, but I like to log the startup myself). Click the two opposing arrows- thats the connect button. It will say "connecting" or "connected" at the bottom. Once connected, you can click the letters near the top of the screen "D" "V" "F" or "M", those are different ways to view data. When in "D" or "M", you can right click any field and change it to view whatever you want, like TPS,RPM,engine temp, etc...
To record, just hit the red dot, and to stop hit the stop button. Then disconnect communication and hit play to replay the data.
Once the cable is hooked up to the ALDL port and your laptop, turn the key on (some just start the car, but I like to log the startup myself). Click the two opposing arrows- thats the connect button. It will say "connecting" or "connected" at the bottom. Once connected, you can click the letters near the top of the screen "D" "V" "F" or "M", those are different ways to view data. When in "D" or "M", you can right click any field and change it to view whatever you want, like TPS,RPM,engine temp, etc...
To record, just hit the red dot, and to stop hit the stop button. Then disconnect communication and hit play to replay the data.
#16
Advanced
Member Since: Apr 2007
Location: N. Augusta SC
Posts: 51
Likes: 0
Received 0 Likes
on
0 Posts
winaldl help for my '90
When I connect the USB/ALDL cable, I get the following on the MW2 line on the raw data page, I get 255 over and over. When I turn the key on, everything stops, starting the engine also stops the 255 from showing up. Nothing else shows up anywhere in the program. Please offer some suggetions !!
#17
Instructor
Member Since: Jan 2007
Location: Silver Spring MD
Posts: 131
Likes: 0
Received 0 Likes
on
0 Posts
When I connect the USB/ALDL cable, I get the following on the MW2 line on the raw data page, I get 255 over and over. When I turn the key on, everything stops, starting the engine also stops the 255 from showing up. Nothing else shows up anywhere in the program. Please offer some suggetions !!
#18
Burning Brakes
Will TunerPro work with the .ads file here? The only 870 ECM file I see is: 1226870_160baud_85_Fcar.ads which appears to be for the LB9 (305ci TPI). Will this work, or ??
I use the Moates cable setup with the 10K resistor switched on, works fine.
I have the same problem as you with WinALDL - only data on the RAW tab. This is With that same Moates cable setup and With the resistor on. Yes, I had to select 4800 baud to even get That much. The good news it that at least all of the sensor data appears to be correct and accurate. I wish it would show the BLM's in a table, though I guess I'm not certain that the -6870 ECM even Has that sort of organization.