doublepost
doublepost
Found the idle chatter logger thing and took some logs. Filenames are what state the car was in when the log was taken. Please let me know if there's any other test I can perform, I'll be more than happy to do whatever test is necessary to pin down this issue. :)
Nothing unusual in the logs. It seems that only the ccm is talking and other modules are passive listeners, only the pcm response to the requests of the CCM. I am not sure if the CCM should talk with ignition off.
You can try disconnect the CCM fuses and repeat the logs. Than try to read the PCM, with CCM off and make a verbose log.
I can tell you from experience the CCM starts talking when you open a door. I've been using a FTDI board hanging on the passenger's side of the console with rx/tx leds on it for several years, and when mine's not connected to my usb hub the leds start flashing away when I open the passenger side door.
The PKE coming into range most likely causes chatter on the aldl - mine doesn't work correctly so I have no idea.
there must be command sets for the ccm has anyone seen any documentation for them? a .ds file or something?
Here's the DS file for the 1994 Corvette CCM: http://gearhead-efi.com/gearhead-efi/def/aldl/A239.DS
I'm currently mid-project on a drivetrain swap for a GTR which is on jackstands in my driveway, so my Corvette is in the driveway under a car cover. I won't be able to play around with it until this Sunday at the earliest. Might take until the weekend after, we'll see.
well i don't see much good there to help with our comms but why dont we add that to the definition for the next version.... i did write multiple device support into EEHack, and it's barely been tested. there is some cool stuff in there. i wonder if it responds to any of the other commands we usually use for reflash, read ram, etc?
Posting Permissions
Reply With Quote
Bookmarks