95 LT1 Corvette Erratic Data Logging

chadk1650 · Post by **chadk1650** » Sun Nov 30, 2014 1:44 pm

Hello all, I am trying to use the data logging feature of TP but get the DA: connected to DA Error problem. When it has connected for any length of time the data was all over the place.

I have spent hours researching and trialing fixes to correct the error and erratic data logging with Tunerpro V5.
I have loaded different ADX files.
I have tried adding the "pause" and the "listen for silence" fixes and still nothing works.
I have tried adjusting Com port settings.
I have tried several different "timeout" values.
I have tried using different XDF files.

I have uploaded the BIN file from the car using winflash and used the default $EE.bin file at different times for troubleshooting.

Can someone please help? I would like to read the real-time values from the car as the Service Engine Light is on and I need to diagnose this problem
Thanks
Chad

chadk1650 · Post by **chadk1650** » Thu Dec 04, 2014 4:42 pm

I take it from the lack of response from the creator of the software that there is no fix. I have researched many threads about this and it seems many have the same problems with TP with respects to the 94-95 corvette. I just with TP would have disclosed this before I spent so much time trying to get it to work.

Chad

Post by **Mangus** » Mon Dec 08, 2014 9:02 am

I've personally seen it work fine with 94-95 F and Y bodies. It's all in the definition. I have not created a single 94-95 definition myself. In fact, I haven't created a single definition for any vehicle outside of the $6E definitions for the single test vehicle that I actually own and have access to.

This forum exists pretty much explicitly so that I, the "the creator of the software," don't have to respond to every question.

Thank you for your understanding.

chadk1650 · Post by **chadk1650** » Mon Dec 08, 2014 4:39 pm

Sorry did not mean to come off so negative. I was a little frustrated at the time. I downloaded the definition from your link? The ECM is stock to my knowledge. The only thing I can think of now is to look at the cable and the PC. I have been successful using C.A.T.S. flash software with the same hardware, to upload the bin file from the car. I have also used datamaster-ee to log data and was successful. I was really hoping to get your software to work as it is less costly (and yes i wanted to donate). I read your home page and think its great you want to help guys like me out.
anyway should I still look closer at cable?

Thanks,
chad

here is my cable:

FT232RL

http://www.gearhead-efi.com/Fuel-Inject ... ALDL-Cable

chadk1650 · Post by **chadk1650** » Mon Dec 08, 2014 4:50 pm

One note about the cable, I think the design is correct. I suspect noise as a possible cause. I would like to hear if anyone else has suspected noise to be problem. My cable is somewhat long but well within specs. of serial communication.

Post by **Mangus** » Mon Dec 08, 2014 5:46 pm

The cable is probably fine if you're getting any data at all, even erratic or nonsensical data.

The 94/95 LT1 masks are chatty on the ALDL line with the dashboard, BCM, TCM, etc, so usually there's some listening and silencing done in the communication command set. I've not seen a definition that fully implements the necessary protocol. I did build one several years ago, but it's been lost.

During connection, you generally need to listen for a module to broadcast (e.g. $F0 $55 $(checksum)) and then send that module a mode 8 silence command ($F0 $56 $08 $(checksum)), then issue the mode 1 message 0 dump request.

Unfortunately I don't know anyone around me with a 94/95 vehicle to use to build another, otherwise I"d do it once and for all.

Faceman · Post by **Faceman** » Tue Jan 06, 2015 10:47 am

Is your car auto or manual transmission ? I was able to log two 95 auto vettes, but also failed with a manual vette.