Shut up CCM and Dash updates on 1990 Y Body

[captainkawasaki]

Anybody know what hex to send to get the CCM and the Dash to quit sending crap on the ALDL line? I'm trying to datalog with Tunerpro v5 and I'm getting lots of garbage in the datastream. I know it's not a hardware issue (ALDU1/CABL1) since I can datalog in TTS Datamaster and Tunerpro v4. I'm currently sending 0x56 0x56 0x09 0xB0 in the connection macro with a 5x repeat and a 1200ms timeout between sends. For the dump request I send 0xF4 0x56 0x01 0xB5 and then listen for a 67 byte response (payload 63, offset 3). The the end of the monitor macro just for the fun of it I put in a 10ms pause. I restart the CCM with the same set of hex that I shut it off with. Can anybody steer me in the right direction for getting Tunerpro v5 datalogging to work with the 90/91 Corvette? Any help is greatly appreciated--Thanks in advance--GD

[EagleMark]

If you had it working with TP V4 ADS file try importing that into TP V5 and saving it as ADX file. Must have the newest TP update as I think this command import issue was fixed.

[RobertISaar]

could also see if another module is causing the issue, easiest way i can do that is via the OSE tool that the australian guys built, i "abuse" it's ALDL monitoring capability to see which modules are communicating on a line that is supposed to be open. last time i did this, i found somewhere around 30 packets per second that would have been directed to the trip computer, if the car would have been equipped as such. send enough mode 8 commands to the PCM and it shut it up.

[EagleMark]

I just tried the new TP V5 update and looks like all the commands are there including silence, I added the silence command to the data macro first... it may need a pause after... I'm not sure if TP still needs the extra 1 added to body size so may have to increase 66 to 67?

If you need more help let us know and also if you get it working correctly please post it back and I will add it to $8E info thread so we have another one done and ready to use.

[captainkawasaki]

Thanks for the replies, I'm going to copy the commands from your $8E.ADX to my $8D mask and I'll post up my results.

[captainkawasaki]

No love with the commands from your $8E copied into my $8D mask. I also tried changing the size of the reply window from 66 bytes to 67 bytes but I still get wildly fluctuating values on the PC. I did a little googling for the OSE tool and mode 8 commands but came up empty. I can handle anything you throw at me from the PC side but am still learning on the ECM side. I also tried importing the Tunerpro V4 1227730.ADS file into Tunerpro V5 but it also gives the wildly fluctuating values. I can slap up some screenshots of my ADX commands if it will help, appreciate what you've all done so far--thanks GD

[captainkawasaki]

FWIW I spied on the serial port and with no datalogging requests in the system I found this junk (in hex) flying around the ALDL

1059086A00002540556B416100F5006A620100000076005FC7 1059086A00002540556B416100F5006A620100000076005FC7 1059086A00

In ASCII it looks like this, it repeats over and over again: Yk $@UkAa ô ka
v `ÇðVñÉYk $@UkAa ô ka
v `ÇYk

Mean anything to anyone?

[EagleMark]

Ahhhh... we must have a glitch in the TunerPro Lookup because all I show is $8E for LT5 for 90 and 91 Corvette, both of which are differant files and neither are $8D...
http://www.gearhead-efi.com/Fuel-Inj...our-files-here!

Found it in the old ALDL doc for the non LT5 Corvette. It's ALDL A115.ds and it has the CCM commands which is A111.ds, both of which Robert has converted to ADS files. I imported them and now have adx files. Look at this A115.adx file, I changed a few things and it will take some testing on your end but I believe it works something like this... Connection Command is Mode 8 to silence the CCM and I added a pause, then the Monitor for engine data which I changed 66 to 67. Then disconnect is the Mode 9 Enable communications. The way the file is set all you have to do is connect or disconnect. Look at the ADX header commands, Aqcusition, Edit Definition.

The A111.adx is to read data and codes from CCM stuff...

EDIT: I typed wrong engine, changed from LT4 to LT5...

[captainkawasaki]

Looking forward to trying out those adx's, I don't get home from work until 4:30 EST and will post up results then. Don't know if it matters but 90/91 base model vettes run L98 engines, the LT-1 came in 92 and the LT-4 was sometime later (I don't know exactly what year).

[RobertISaar]

BTW, that's LT5 Mark... LT4 didn't come around until 1996 IIRC. LT5 is a beast of an engine for its day.

either way, both the L98 and LT5 corvettes got the same CCM, so what works with one should work with the other.



i did a quick check on that packet, it has the correct checksum at the end of the string, so i have to believe it's valid. so i opened up A111 and guess what i see?

        MODE 0 (RETURN TO NORMAL MODE)
                ALDL REQUEST:
                - MESSAGE ID     = $F1
                - MESSAGE LENGTH = $56
                - MODE           = $00
                - CHECKSUM
             CCM RESPONSE:
                CCM BROADCAST MESSAGE
                - MESSAGE ID     = $10
                - MESSAGE LENGTH = $59
                - STATUS WORD
                   BIT  DESCRIPTION
                    0   ENGLISH/METRIC STATUS      0 = ENGLISH  1 = METRIC
                    1   ENGINE                     0 = L98      1 = LT5
                    2   A/C CLUTCH STATUS          0 = OFF      1 = ON
                    3   SPARE
                    4   SPARE
                    5   SPARE
                    6   SPARE
                    7   SPARE
                - COOLANT TEMPERATURE
                      DEG C = N*.75 - 40
                - ENGINE RPM
                      RPM = N*25
                - VEHICLE SPEED
                      MPH = N
                - CHECKSUM

matching that up, 10 59 08 6A 00 00 25 comes out perfectly, checksum included.

the next portion is 40 55 6B(checksum included)... kind of odd, but i can't find any modules using a code of 40. considering the length, i get the feeling that it's an ALDL device poll.

then we end with 41 61 00 f5 00 6a 62 01 00 00 00 76 00 5f c7(C7 being checksum)

now i'm fairly certain that the 40 was a poll from either the ECM or CCM to one or the other and the 41 is its counterpart.



so, there's your communications decoded.

[EagleMark]

It does matter a lot between LT4 and LT5, I knew the difference but mistyped... Thanks!

Robert, did you look at the A115.adx I changed? I think that is correct to send silence, pause then data, that is simalar to how I made LT1 work, not sure about the return to normal but that should just happen at dissconnect.

Also another tip to getting this connected, do it with engine running. It's not like an old ECM that can connect with engine off.

[RobertISaar]

that A115 might work.... might not. some applications need a bunch of mode 8s slammed through in a short amount of time to shut everything up. the P66 V6 stuff generally takes between 5 and 10 mode 8 commands based on my VIN sometimes showing up the the datalog(i have it set to grab after the first 5 mode 8s), but it always connects and stays connected on the first attempt. i don't have any delay time between mode 8 commands either, they slam in there as fast as possible, then 50mS delay before transmitting and mode 1 requests.

return to normal looks fine.

also, i never have issues engine running or not, but i also only play with P4/P6/P66.

[EagleMark]

So does repeating the Mode 8 help? I had it set to 10...

[RobertISaar]

usually, assuming you're sending mode 8 to the right module. with this..... may need sent to the CCM instead of the ECM, depending on which one is initiating communications. or even both needing mode 8 commands is possible.

[EagleMark]

Ahhh... I didn't check to see if the Mode 8 silence in A111 for CCM was the same as Mode 8 Silence in A115! So that would need to be checked, the poll may be from ECM and the CCM also needs silenced.

AS much as I like making these work it's almost impossible without having hands on the car. But I think we have a good remote hands on car here!