Scan and data log cable & software recommendations
Thread Starter
Melting Slicks
Joined: Nov 2007
Posts: 2,830
Likes: 147
From: Gainesville FL
Scan and data log cable & software recommendations
Need for 1986 Convertible .. CF used to have a scan and tune section with all this stuff covered but now it only points to c4 tech & performance.
I got a vintage 2012 laptop running windows 8.1 ... will I be OK for ALDL cable and OBDI data?
Any good threads with most of this covered?
I am not that interested in tuning but rather scanning and diagnosing issues that come up.
I got a vintage 2012 laptop running windows 8.1 ... will I be OK for ALDL cable and OBDI data?
Any good threads with most of this covered?
I am not that interested in tuning but rather scanning and diagnosing issues that come up.
Last edited by 3D-Aircrew; Apr 3, 2018 at 04:26 PM.
Thread Starter
Melting Slicks
Joined: Nov 2007
Posts: 2,830
Likes: 147
From: Gainesville FL
Need ADX file for 1986 not ads
Need for 1986 Convertible .. CF used to have a scan and tune section with all this stuff covered but now it only points to c4 tech & performance.
I got a vintage 2012 laptop running windows 8.1 ... will I be OK for ALDL cable and OBDI data?
Any good threads with most of this covered?
I am not that interested in tuning but rather scanning and diagnosing issues that come up.
I got a vintage 2012 laptop running windows 8.1 ... will I be OK for ALDL cable and OBDI data?
Any good threads with most of this covered?
I am not that interested in tuning but rather scanning and diagnosing issues that come up.
Sure wish the C4 scan and tune section was still alive;(
Does anyone have an ADX file that is known to work with TunerPro and the 1320Electronics Bluetooth adapter? 1986 Aluminum Heads, auto tranny.
Last edited by 3D-Aircrew; Apr 8, 2018 at 02:25 PM.
Melting Slicks
Joined: Aug 2003
Posts: 3,394
Likes: 393
From: Lakeville MI
Start with a 160 baud adx file. Use the 10k setting and 160 baud setting on your adaptor. I’ve uploaded a 160 baud adx in another thread if you want to search for it.
Disregard the Hardware Not Found indicator. This just means that you don’t have an ostrich plugged in.
Under the Tools/Preferences.../Data Acq./Emulation check the com settings via the Configure Plug-in Component button (left side).
Note: 86s are notorious for connecting at 8192 baud. There are some possible work arounds, but we’ll cross that bridge when we come to it.
Note: these are general suggestions for logging with an 86. I have no direct experience with your Bluetooth adaptor and interface. Hopefully they will play well together with TunerPro.
Disregard the Hardware Not Found indicator. This just means that you don’t have an ostrich plugged in.
Under the Tools/Preferences.../Data Acq./Emulation check the com settings via the Configure Plug-in Component button (left side).
Note: 86s are notorious for connecting at 8192 baud. There are some possible work arounds, but we’ll cross that bridge when we come to it.
Note: these are general suggestions for logging with an 86. I have no direct experience with your Bluetooth adaptor and interface. Hopefully they will play well together with TunerPro.
Thread Starter
Melting Slicks
Joined: Nov 2007
Posts: 2,830
Likes: 147
From: Gainesville FL
Start with a 160 baud adx file. Use the 10k setting and 160 baud setting on your adaptor. I’ve uploaded a 160 baud adx in another thread if you want to search for it.
Disregard the Hardware Not Found indicator. This just means that you don’t have an ostrich plugged in.
Under the Tools/Preferences.../Data Acq./Emulation check the com settings via the Configure Plug-in Component button (left side).
Note: 86s are notorious for connecting at 8192 baud. There are some possible work arounds, but we’ll cross that bridge when we come to it.
Note: these are general suggestions for logging with an 86. I have no direct experience with your Bluetooth adaptor and interface. Hopefully they will play well together with TunerPro.
Disregard the Hardware Not Found indicator. This just means that you don’t have an ostrich plugged in.
Under the Tools/Preferences.../Data Acq./Emulation check the com settings via the Configure Plug-in Component button (left side).
Note: 86s are notorious for connecting at 8192 baud. There are some possible work arounds, but we’ll cross that bridge when we come to it.
Note: these are general suggestions for logging with an 86. I have no direct experience with your Bluetooth adaptor and interface. Hopefully they will play well together with TunerPro.
That's funny ... I just before this post found your ADX file and downloaded it ... thanks ... that did the trick I can now log!!!
Thread Starter
Melting Slicks
Joined: Nov 2007
Posts: 2,830
Likes: 147
From: Gainesville FL
Intermittent code 33
So now I need some help interpreting the information from the scanner. Unfortunately the code 33 has not presented itself yet since I got the scanner hooked up.
So a code 33 is MAF voltage too high and I'm hypothesizing here but I know a hot wire anemometer works by changing resistance depending upon the air flow. So more flow would be a lower voltage and less flow would be a higher voltage. So the MAF is seeing lower flow than expected.
My O2 sensor reading was all over the place up and down the RPM range. Does the ECM make and educated guess at what the MAF should be reading depending on the O2 sensor output?
here is a test run in TP where I was just idling and revving in the driveway ... any gurus can help? I'm using Tunerpro RT
PS: 3 days now no code 33.
TunerPro Test Run
So a code 33 is MAF voltage too high and I'm hypothesizing here but I know a hot wire anemometer works by changing resistance depending upon the air flow. So more flow would be a lower voltage and less flow would be a higher voltage. So the MAF is seeing lower flow than expected.
My O2 sensor reading was all over the place up and down the RPM range. Does the ECM make and educated guess at what the MAF should be reading depending on the O2 sensor output?
here is a test run in TP where I was just idling and revving in the driveway ... any gurus can help? I'm using Tunerpro RT
PS: 3 days now no code 33.
TunerPro Test Run
Last edited by 3D-Aircrew; Apr 9, 2018 at 05:33 PM. Reason: added file link
Thread Starter
Melting Slicks
Joined: Nov 2007
Posts: 2,830
Likes: 147
From: Gainesville FL
TunerPro RT Scan
Using TunerPro RT I got a chance to datalog again this time with it driving and the code 33 active. I noticed that the airflow was behaving weird going high sometimes when the RPM was low and going low sometimes when the RPM was higher (thus the error code). I'll post the log tonight and maybe somebody can help me tell what it means. I still got to clean up my wiring as soon as I find a pigtail for the fan relay.
Race Director
Joined: Mar 1999
Posts: 12,595
Likes: 237
From: Bartlett Illinois
I will suggest if you have an android tablet.. ALDLDroid.. it uses the same configuration files from TunerPro and you can log from a phone or tablet
Last edited by -=Jeff=-; Apr 12, 2018 at 12:12 PM.
Corvette Stories
The Best of Corvette for Corvette Enthusiasts
Top 10 Most Explosive Corvettes Ever Made: Power-to-Weight Ratio Ranked!
Joe Kucinski
150 hp to 1,250 hp: Every Corvette Generation Compared by the Specs That Matter
Joe Kucinski
8 Coolest Corvette Pace Cars (and Replicas) of All Time
Verdad Gallardo
Top 10 Corvette Engines RANKED by Peak Torque (70+ Years of Muscle!)
Joe Kucinski
Corvette ZR1X Will Be Pacing the Indy 500, And Could Probably Race, Too!
Verdad Gallardo
Top 10 Corvettes Coming to Mecum Indy 2026!
Brett Foote
Top 10 C9 Corvette MUST-HAVES to Fix These C8 Generation Flaws!
Michael S. Palmer
10 Revolutionary 'Corvette Firsts' Most People Don't Know
Joe Kucinski
5 Reasons to Upgrade to an LS6-Powered Corvette; 5 Reasons to Stay LT2
Michael S. Palmer
Thread Starter
Melting Slicks
Joined: Nov 2007
Posts: 2,830
Likes: 147
From: Gainesville FL
Thread Starter
Melting Slicks
Joined: Nov 2007
Posts: 2,830
Likes: 147
From: Gainesville FL
I have some new runs that I did yesterday ... my laptop took a dump last night but I did notice the "airflow" gauge on my dashboard was reading too high at times and too low at other times and seem to be intermittent. If I can fix my 'puter tonight I'll post those logs to. Both of them I had the code 33 set which is different from the above run.
Melting Slicks
Joined: Aug 2003
Posts: 3,394
Likes: 393
From: Lakeville MI
Need to correct airflow signal conversion in adx. Divide by 255 (x/255) and set for floating point with 2 decimal places.
Note: When a MAF error code is active, the airflow signal is driven from the default airflow calculation instead of the sensor signal. (Default airflow calc is rpm, IAC, and tps dependent).
Note: When a MAF error code is active, the airflow signal is driven from the default airflow calculation instead of the sensor signal. (Default airflow calc is rpm, IAC, and tps dependent).
Last edited by tequilaboy; Apr 12, 2018 at 03:55 PM.
Thread Starter
Melting Slicks
Joined: Nov 2007
Posts: 2,830
Likes: 147
From: Gainesville FL
Need to correct airflow signal conversion in adx. Divide by 255 (x/255) and set for floating point with 2 decimal places.
Note: When a MAF error code is active, the airflow signal is driven from the default airflow calculation instead of the sensor signal. (Default airflow calc is rpm, IAC, and tps dependent).
Note: When a MAF error code is active, the airflow signal is driven from the default airflow calculation instead of the sensor signal. (Default airflow calc is rpm, IAC, and tps dependent).
Test2-code33
Test2-drive-code33
Thanks for all your help.
Thread Starter
Melting Slicks
Joined: Nov 2007
Posts: 2,830
Likes: 147
From: Gainesville FL
I'll have to mmake those changes tommorow in the meantime these 2 runs threw the code 33.
Test2-code33
Test2-drive-code33
Thanks for all your help.
Test2-code33
Test2-drive-code33
Thanks for all your help.
Melting Slicks
Joined: Aug 2003
Posts: 3,394
Likes: 393
From: Lakeville MI
Gonna be pretty tough to diagnose anything at 160 baud. Have you attempted connecting at 8192 baud yet?
Since you are running a hypertech, it may be based on a newer mask. Give it a shot, or a try a newer $32b or $6E bin.
Note: From your log file, the Prom ID is 2241, so it would appear that your hypertech bin was based on AANL (86, 3.07 gear, Auto trans).
Since you are running a hypertech, it may be based on a newer mask. Give it a shot, or a try a newer $32b or $6E bin.
Note: From your log file, the Prom ID is 2241, so it would appear that your hypertech bin was based on AANL (86, 3.07 gear, Auto trans).
Last edited by tequilaboy; Apr 15, 2018 at 06:42 PM.
Thread Starter
Melting Slicks
Joined: Nov 2007
Posts: 2,830
Likes: 147
From: Gainesville FL
Gonna be pretty tough to diagnose anything at 160 baud. Have you attempted connecting at 8192 baud yet?
Since you are running a hypertech, it may be based on a newer mask. Give it a shot, or a try a newer $32b or $6E bin.
Note: From your log file, the Prom ID is 2241, so it would appear that your hypertech bin was based on AANL (86, 3.07 gear, Auto trans).
Since you are running a hypertech, it may be based on a newer mask. Give it a shot, or a try a newer $32b or $6E bin.
Note: From your log file, the Prom ID is 2241, so it would appear that your hypertech bin was based on AANL (86, 3.07 gear, Auto trans).
I know the car calls for an AANK (86 2.73 auto AL heads)... maybe that's part of my problem. Is there a way to compare the differences?
Melting Slicks
Joined: Aug 2003
Posts: 3,394
Likes: 393
From: Lakeville MI
https://goo.gl/images/xYTTmZ
I saw your updated post.
It is likely you have an open circuit on the maf signal wire. The ecm pulls the signal up to 5 volts which causes the high flow reading when started.
I saw your updated post.
It is likely you have an open circuit on the maf signal wire. The ecm pulls the signal up to 5 volts which causes the high flow reading when started.
