TunerPro User Forum

Did anybody already try the Innovate LC-2 wideband controller if it works with the LC1 plugin?

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

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...

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

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

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.

I am stupid, okok, there is this Monitor Command on the Header data page... I thought, TunerPro discovers on its own, what data is shown and what commands have to be sent. But it's not this intelligent :) I still have no idea how to stopp if there is silence on the line. I now just sent both mode 8 ...

Another thing: the ALDL Mode 1 Message 1 Request is not sent by TunerPro. That causes the Tranny temp to stay at -40°. Is it a bug Mark?

Robert, I changed your ADX file: created Mode 8 command for CCM, added it to the Mode 8 macro. The two different options for the repeat count is mysterious to me. There is one on the Macro page called "Macro Repeat Count" and one "Entry Repeat Count". It seems the "Macro Rep...

I do not find in the docu how to do a loop within the ADX definition that is left when the line is quite. Maybe someone can help me out. Robert help!

One question Mangus: does TunerPro 5 calculate and verify the checksum of the ALDL frames? No, not currently. Ok, that's the reason why those wrong values get shown. Can the "Listen for silence" command be used in a loop or similar to send the mode 8 commands until PCM and CCM are quite?

One question Mangus: does TunerPro 5 calculate and verify the checksum of the ALDL frames?

Mangus, the "f4 55 b0" sequence I do not find anywhere in the log. Do you remember what you all changed to get $EE ADX work with a 94 or 95 vette?

PCMcomm shows some interpreted information if I switch it on. Sometimes it shows "bad chksum", "bad length bad chksum", "disable echo" and as a result it resends that "silent" stuff again to CCM and PCM as it seems. Maybe until the line is quite. Because later...

Another point: until PCMcomm sends "normal" messages it sends "F1 56 08 B1" during init of the PCM communication. What does it mean? A list of the serial writings without the replys: Line 3642: 3641 0.00124262 pcmcomm.exe IRP_MJ_WRITE VCP0 SUCCESS Length 4: F4 56 08 AE Line 4060:...

It seems as would TunerPro run the init process twice, the timeouts are different. Later during communication it always does: 227 0.00000782 TunerPro.exe IOCTL_SERIAL_GET_TIMEOUTS VCP0 SUCCESS 228 0.00000251 TunerPro.exe IOCTL_SERIAL_SET_TIMEOUTS VCP0 SUCCESS RI:75 RM:0 RC:400 WM:0 WC:300 229 0.0000...

I captured some serial data. The init of the COM port is the first thing that looks quite different: PCMcomm: 0 0.04120552 pcmcomm.exe IRP_MJ_CREATE VCP0 SUCCESS Options: Open 1 0.00293417 pcmcomm.exe IOCTL_SERIAL_SET_WAIT_MASK VCP0 SUCCESS Mask: RXCHAR 2 0.00000251 pcmcomm.exe IOCTL_SERIAL_SET_QUEU...

Not really Such a thing: http://technet.microsoft.com/en-us/sysi ... s/bb896644 ??

But I would like to see some interpretation of the communication going on regarding ALDL GM 8192. The plain hex numbers are too strange for me

It's especially for 94 and 95 LT1: http://carputing.tripod.com/pcmcomm.exe

Yes, default is 16, changing it to "1" did not help, all the same: - TunerPro 5.0.7575 + downloaded ADX from Robert: low connection errors, flickering - TunerPro 5.0.7575 + 'EE_Auto.adx': many connection errors, flickering - PCMcomm 4.40: works - Freescan 2.0.1: shows values only sometimes...

I'm standing right besides the car currently
The connection with the new file is not as stable as with the initial one (much more errors) and the values are still flickering. Do I have a chance to trace the serial data flow with TunerPro?

Hi Robert, thanks for your reply. I bought the cable a while ago from www.aldlcable.com It's the USB version with the 16 pin connector (95 vette). It works perfectly with TunerCat (reading/programming flash) and with PCMcomm (showing correct values). With FreeScan there are similar problems, only so...

Today I used Roberts file (EE F Y B & D Body Auto.adx) that I downloaded from his website: http://www.robertisaar.co.cc/web_images/My%20Datastreams.7z With this file the connection is much more stable (only a few errors). But the reading is strange, I took a movie with car at idle: http://www.li...

Hi, it's quite an old thread, but maybe that issue was solved. With my 95 auto LT1 Vette I'm facing the same problem as Dan had or still has. I installed Build 5.00.7575.00 on my XP machine using EE.xdf and EE_Auto.adx files. I did not yet check the xdf stuff but the datastream definition does not w...