95 LT1 Vette and V5 TunerProRT setup

Post by **robertisaar** » Tue May 24, 2011 4:40 am

some people don't need the extra commands, and would do nothing but slow down their log rate.

and as long as sending the commands a ridiculous amount of times works consistently, i think the extra second or so it takes to connect is worth it.

Faceman · Post by **Faceman** » Tue May 24, 2011 5:17 am

My acquisition rate is about 10 per second with only the m1m0 command. Is this normal? I do not really need the m1m1 stuff currently.

When I had 10 repeats of the mode 8 commands it was sometimes not showing correct values, with 30 now it seems to work.

Post by **robertisaar** » Tue May 24, 2011 5:31 am

10 per second is a very reasonable number considering the size of the m1m0 stream for EE.

i'm up to a consistent 10.67 with A1 and it's 63 byte stream(came up with this value after exporting a very long log to CSV and checked number of samples against log duration).

Faceman · Post by **Faceman** » Tue May 24, 2011 7:13 am

8192 bits/sec = 1024 bytes/sec
m1m0 --> 5 bytes send + 64 bytes receive = 69 bytes
-->1024 / 69 = 14.8

so theoretically 14.8 samples per second, a little overhead whatever, I see 10 is ok, thanks Robert. And we see, it's important to make the CCM quiet, it steals bandwidth otherwise

Post by **robertisaar** » Tue May 24, 2011 7:31 am

i don't know if you want to send your modified and working ADX to Mark or what, but i'm sure there are a few people that would love to have it.

when it's up, i'll have to replicate the changes for the manual trans version and then EE should officially no longer be a problem.

Faceman · Post by **Faceman** » Tue May 24, 2011 9:15 am

After I used the ADX file several times today with my 95 Vette I've sent it to Mark. I cannot guarantee that it works for all people in all cases. We will await the feedback.
So long, Face

lynch · Post by **lynch** » Thu Jun 23, 2011 3:38 am

Hi... I'm about to download tunerpro and start looking through a 94 F body PCM. Is the EE ADX file for F bodys the same as the vette ADX file that Face was working on?

Is that the one that I can download from this site?

I'm new to this so I just wanna try and make it as painless as possible. Didn't know if I'd be running into the same problems face encountered or if that was something vette specific.

Thanks in advance for sharing all this awesome work.

Post by **robertisaar** » Thu Jun 23, 2011 6:49 am

your transmission will determine what ADX you need, all of the auto cars use the same ADX, all of the manual cats use the same ADX. not sure if Mark has the newest version posted or not yet.

lynch · Post by **lynch** » Tue Jun 28, 2011 5:07 am

So is it possible that the EE available here could give me the same problems as face was, uhh, facing??

Or was that problem something vette PCM specific? Are they different than F body PCMs?

Post by **robertisaar** » Tue Jun 28, 2011 5:52 am

the problem was multiple reasons, mostly the CCM(vette specific0 liked to chat with other modules on the ALDL line, and the PCM liked to chat with other modules as well, both of which caused interference that would ruin an otherwise good datalog.

assuming Mark has updated the TP downloads page with Faceman's version, it should be working more or less flawlessly now.

ckp · Post by **ckp** » Tue Aug 16, 2011 6:53 pm

Has anyone else got a '95 Vette Auto to log data?

EagleMark · Post by **EagleMark** » Sat Sep 10, 2011 5:47 am

I've been through lots of things before reading this thread, have the EE stuff from TunerPro, still can not get meaningful data into TunerPro?

Car is a little differant the Corvette, 1994 Buick Roadmaster Wagon W/Factory Lt1 and 4l60e same PCM...

Earlier in thread there was an issue with an AutoProm but I think it was the same with cable. I am usuing AutoProm as a pass through device.

Also all my equiptment has worked on 7747 and 427 ECMs since and back to LT1 and all I get is mostly nonsense and sometimes realistic numbers?

ckp · Post by **ckp** » Sat Sep 10, 2011 7:04 am

I gave up on it. I've been using Datamaster.

EagleMark · Post by **EagleMark** » Sat Sep 10, 2011 10:07 am

I've got a scantool that will record data as well.

But to many guys are making this work with no issues?

Some have issues exact to mine. Only difference is mine is early Rev B version and I don't know if the data to TP is differant, but the 95 is not Rev B and has same issue?

I have used the EEB.XDF on the REV B and it is fine. I have used the EE.XDF fine.

I reflashed the ECM with a 1995 Impala SS tune using WinFlash and no issues so I think the PCM is identical and the Rev B is just in early 1994 vehicles. No codes in 10 days or so driving. All systems work as normal.

Same issue with data to TP on both tunes...

Since I am using the EEB_Auto.ADX from here, it has got to be the AutoProm or something in my COM port settings? AutoProm has worked on several non LT1 ECMs

EagleMark · Post by **EagleMark** » Wed Sep 14, 2011 3:40 pm

Tested this all again today. Got to read PCM through AutoProm with WinFlash. Re flashed PCM with WinFlash. Got hooked up to data and saw some normal numbers, others not and then jumpy.i have a log file if looking at it would help find my issue with recording data with TPV5...

Post by **Mangus** » Sat Sep 17, 2011 9:41 am

Faceman wrote:8192 bits/sec = 1024 bytes/sec
m1m0 --> 5 bytes send + 64 bytes receive = 69 bytes
-->1024 / 69 = 14.8

so theoretically 14.8 samples per second, a little overhead whatever, I see 10 is ok, thanks Robert. And we see, it's important to make the CCM quiet, it steals bandwidth otherwise

Don't forget that serial data bytes are 9 bits. Also, 5 bytes to send, 72 bytes to receive (echo and response header bytes included). That's 11.8 hz theoretical max. Factor in processing time and the fact that theory and reality rarely align perfectly, and anything over 10 hz looks pretty good.

pjg1173 · Post by **pjg1173** » Fri Nov 18, 2011 7:21 am

I believe I am having the same issue with TPr5. while datalogging the monitors will ramdomly go nuts and put garbage in my log. I looked in the ADX file and do not see the mode 8 that was mentioned above, but most of what was mentioned above is greek to me. when the monitor starts going screwy i noticed down at the bottom of the window where (I assume its the comm speed) it normally is around 6Hz jumps up to around 14Hz. I know I don't have a LT1 so I'm not sure this applies or will work, and I'm not sure on how to go about trying it. I don't have this issue with DM. What can I try to get decent logs.

I am using the
moates autoprom
$E6 mask
16168625 ecu
E6_tpv5_v250.xdf
A201_E6_v250.adx
93 s10 4.3L w/4l60e.

photomoto · Post by **photomoto** » Fri Mar 09, 2012 7:24 pm

the EE data logging works perefect with what is uploaded on the main site.

I was having issues with bad data coming in on the logs, but it works great for me now on my 94 lt1 using a 2 transistor DIY cable.

be sure to start connection **AFTER** you have started the car. Starting the car seems to interrupt the PCM and the connection command needs to be resent.

Hope this helps someone. Tunerpro is way more flexibly and powerful than both freescan, and datamaster. plus it doesnt have the crazy broken POS DRM of datamaster.

Faceman · Post by **Faceman** » Thu May 17, 2012 3:10 am

Connecting after the engine was started did not work with my auto tranny Vette, but the ADX with my modifications works until today. On Saturday I get a manual vette in my hands, also did the mods based on Roberts EE file, let's see if it works...