Need Step by Step Help for 91 Corvette

aklim · Post by **aklim** » Thu Dec 11, 2014 5:25 pm

I have set it to port 3 but I can't seem to make it work. Is there a step by step manual? I just want to datalog. I don't care about tuning nor will I ever tune. TIA

This is for a 91 Corvette.

aklim · Post by **aklim** » Fri Dec 12, 2014 8:08 am

I copied the 2 files from the download page but that doesn't give me anything as far as parameters. Set to port 3 but no joy.

Do I really need Moates or TunerPro RT for simple datastream reading? If I will NEVER program my 91 Corvette, do I have to wade through all the confusion or is there a simpler way where I can return the hardware and find an easier solution?

I worked with DIACOM in my Fbody and it was so easy, a caveman could do it. I can't find a STEP BY STEP manual for ONLY datalogging and get referenced to load 3 files but can't find them anywhere other than a link to a download page. Can someone tell me the exact files to load with the steps to make this work, assuming there is no other way?

I bought the Actron unit and it can't datalog what I need it to do. I want to see all parameters and not just a few.

Thanks

Post by **Mangus** » Fri Dec 12, 2014 3:27 pm

1. Download the $8D ADS file.
2. Open TunerPro RT and plug your USB cable into your computer
3. Drag and drop the $8D ADS file into the main TunerPro window to import it into the newer ADX format.
4. When it prompts you to save the new 8D.ADX file, save it to the location of your choice
5. Open up TunerPro preferences (Tools->Preferences)
6. On the Data Acq / Emulation tab, on the Data acquisition side, set the Interface Type to "Use Plugin", set the plugin to "TunerPro Data Acquisition I/O Interface"
7. Click "Configure Plug-in COmponent" and set it to "Standard Serial" and select the COM port that the cable is installed to. Only active COM ports will be available in the list.
8. With the cable unplugged from the vehicle but plugged into the PC, hit the "Test for Valid Interface" button. It should report success if you've selected the correct COM port.
9. Click OK buttons until you're back to the main TunerPro program
10. Hook the cable up to your vehicle. Turn the key on, but leave the engine off until you confirm you're getting valid data.
11. Click the connection button (two blue, opposing arrows) in the toolbar. Look for "Connected" in the status bar at the bottom of the window.
12. If you see "Not connected" after the connection attempt, try again. It might take a few tries to hook up, especially if your Vette has a digital dash.
13. Once you see Connected, open the Dashboard (Ctrl + Shift + 1) and Item lists (Ctrl + Shift + 2)
14. Move the throttle and verify that the throttle position value changes as expected.

If you get through that and see valid data, you should be good to go.

-M

aklim · Post by **aklim** » Fri Dec 12, 2014 3:49 pm

Mangus wrote:10. Hook the cable up to your vehicle. Turn the key on, but leave the engine off until you confirm you're getting valid data.
11. Click the connection button (two blue, opposing arrows) in the toolbar. Look for "Connected" in the status bar at the bottom of the window.
12. If you see "Not connected" after the connection attempt, try again. It might take a few tries to hook up, especially if your Vette has a digital dash.
13. Once you see Connected, open the Dashboard (Ctrl + Shift + 1) and Item lists (Ctrl + Shift + 2)
14. Move the throttle and verify that the throttle position value changes as expected.

If you get through that and see valid data, you should be good to go.

-M

So far, it flashes between "DA Connected" and "DA Data Error". With the Key off, it just keeps trying to connect. Tried this several times. It tests out good so far.

I even tried running the engine and it reads data but the numbers are wild and fluctuating. Somewhere I got 48 volts of battery and 20 volts for TPS so I know that is wrong.

Tried with the 10K switch on and off but no change

Post by **Mangus** » Fri Dec 12, 2014 4:00 pm

You don't need the 10k.

Does your Vette have a digital dashboard?

There's a gentlemen that has a working definition here: http://www.corvetteforum.com/forums/c4- ... vette.html

I've requested that he send it to me, and I"ll put it up on the website when I have it in hand. You might want to request it, too.

aklim · Post by **aklim** » Fri Dec 12, 2014 4:03 pm

Mangus wrote:You don't need the 10k.

Does your Vette have a digital dashboard?

Yes

Post by **Mangus** » Fri Dec 12, 2014 4:07 pm

OK. See my edit above.

aklim · Post by **aklim** » Fri Dec 12, 2014 4:25 pm

Mangus wrote:You don't need the 10k.

Does your Vette have a digital dashboard?

There's a gentlemen that has a working definition here: http://www.corvetteforum.com/forums/c4- ... vette.html

I've requested that he send it to me, and I"ll put it up on the website when I have it in hand. You might want to request it, too.

He hasn't been on for a couple of weeks. Any way you know what he did or where it is if it is public?

aklim · Post by **aklim** » Sat Dec 13, 2014 6:06 am

Mangus wrote:You don't need the 10k.

Does your Vette have a digital dashboard?

There's a gentlemen that has a working definition here: http://www.corvetteforum.com/forums/c4- ... vette.html

I've requested that he send it to me, and I"ll put it up on the website when I have it in hand. You might want to request it, too.

http://www.thirdgen.org/forums/diy-prom ... vette.html

This the file you are talking about in Post 7?

aklim · Post by **aklim** » Sat Dec 13, 2014 7:17 am

OK. While I run the dash and get readings, without something like a Tech1 or my old AutoXray, I can't remember if the values are right for the conditions. The thing that is causing issues is that TPRT keeps going in and out so I don't have confidence. It will be "connecting DA" for a bit then flicker about 1Hz rate between "DA Connected" and "DA Data Error" so I can't be sure it is doing anything right.

aklim · Post by **aklim** » Sat Dec 13, 2014 7:57 am

Using A100 lists 6 squares for the "Dash" but not filled. Prom ID is correct but very slow in data acquisition since the values don't change. Refresh rate is probably very slow.

CaptainKawasaki's file: $8D-1227727-1990Corvette.adx shows all 8 gauges seems ok, doesn't show PromID but values are close to the others. Refresh rate is reasonable. Still cycles between DA Data Error and DA Connected

$8D-1227730-90-Y-Car-V1.adx seems ok too. Shows all 8 gauges, No PromID. Also cycles the same way as above.

So how to trust the values if it is in and out?

Post by **Mangus** » Sat Dec 13, 2014 9:26 am

That Thirdgen thread is a good one. I'm glad to see you chipping away at this on your own.

If the data is no longer erratic, then you're probably fine. You should be getting ~8hz when connected.

You can right-click on dashboard gauges to select whatever you want to display in each gauge.

I'll take a closer look at the Y car definitions and see if I can clean them up a bit for you to try.

aklim · Post by **aklim** » Sat Dec 13, 2014 4:07 pm

Mangus wrote:That Thirdgen thread is a good one. I'm glad to see you chipping away at this on your own.

If the data is no longer erratic, then you're probably fine. You should be getting ~8hz when connected.

You can right-click on dashboard gauges to select whatever you want to display in each gauge.

I'll take a closer look at the Y car definitions and see if I can clean them up a bit for you to try.

Thanks. Looking forward to seeing it

Post by **Mangus** » Sun Dec 14, 2014 11:44 am

I've uploaded a definition for you to try. http://www.tunerpro.net/downloadbindefs.htm

It's on the 8D line under GM.

aklim · Post by **aklim** » Sun Dec 14, 2014 12:32 pm

Mangus wrote:I've uploaded a definition for you to try. http://www.tunerpro.net/downloadbindefs.htm

It's on the 8D line under GM.

Seems to be pretty stable. Only one oddity I noticed when compared with a Tech 1. Engine oil temp was 175 and coolant was 180. TP said Coolant was 180 and engine oil temp was 256. It had steadily rose so I don't think it was an issue with the data itself.

I also verified by shooting the oil pan with an infra red gun and it was about 170 give or take and the Tech One was accurate. Any idea why the temp was that high?

Other than that, besides going in and out of DA Data Error and DA Connected, it seems to be working.

THANKS A BUNCH FOR YOUR EFFORTS

Post by **Mangus** » Sun Dec 14, 2014 12:40 pm

Thanks for the verification. I've found and fixed the oil temp issue. I've replaced the file on the site now. If you have time, please download and verify once more.

aklim · Post by **aklim** » Sun Dec 14, 2014 1:07 pm

Mangus wrote:Thanks for the verification. I've found and fixed the oil temp issue. I've replaced the file on the site now. If you have time, please download and verify once more.

Verified. It works.

So the "DA Data Error" and "DA Connected" switching, is it an issue or what exactly does it mean?

Post by **Mangus** » Sun Dec 14, 2014 3:52 pm

Each time you see the error, that means that TunerPro failed to retrieve a packet. When this occurs, the UI isn't updated at all; it just manifests as a gap in the data.

That you're seeing it seems to indicate that there's still some chatter on the ALDL line from the CCM, ABS, or perhaps HVAC modules.

I really need to find one of these cars locally. That'd make it quite a bit easier for me to find out what's going on and build a better ADX.

I appreciate your help and patience thus far.

aklim · Post by **aklim** » Sun Dec 14, 2014 4:47 pm

Mangus wrote:Each time you see the error, that means that TunerPro failed to retrieve a packet. When this occurs, the UI isn't updated at all; it just manifests as a gap in the data.

That you're seeing it seems to indicate that there's still some chatter on the ALDL line from the CCM, ABS, or perhaps HVAC modules.

I really need to find one of these cars locally. That'd make it quite a bit easier for me to find out what's going on and build a better ADX.

I appreciate your help and patience thus far.

Kinda figured. These cars are pretty scarce since you can only use a 90-91.

I appreciate what you have done so far to make it easier. Not sure how to help you unless you happen to be in the WI area, I could get my car to you with the cables and laptop.

aklim · Post by **aklim** » Mon Dec 15, 2014 8:47 pm

Mangus wrote:Each time you see the error, that means that TunerPro failed to retrieve a packet. When this occurs, the UI isn't updated at all; it just manifests as a gap in the data.

That you're seeing it seems to indicate that there's still some chatter on the ALDL line from the CCM, ABS, or perhaps HVAC modules.

I really need to find one of these cars locally. That'd make it quite a bit easier for me to find out what's going on and build a better ADX.

I appreciate your help and patience thus far.

Do you need the whole car or just the ECM?

Post by **Mangus** » Mon Dec 15, 2014 8:59 pm

It would need to be the whole car, with the CCM/Dash and HVAC controls (all of which communicate on the ALDL line).

Eventually I'll come across one. Thanks!