new $EE tuning thing!

[spfautsch]

there must be a universal method for this stuff, I know tunercat winflash doesn't have a special ybody mode.... it "just works". maybe it detects vehicle type based on idle traffic.

From what I've been able to log, winflash sends the F4 hush request, and listens for the ECM echo. Then it seems to listen for idle traffic for a bit and sends the F1 hush request if things don't quiet down. Also worth noting, the F1 hush does not appear to be echoed by the CCM. But this could be an erroneous assumption because I'm running it in an XP virtual and I've been unable to successfully put the ECM in programming mode while also logging serial data.

Another thing of interest - I was sure I'd read something like this when I asked if there was another BCM / CCM module in the Y bodies. From the DataMaster OBD1 Manual:

4.3.4.2
Options- Advanced- Disable ALDL Handshake
This option is provided to "seize" control of the ALDL communications link, bypassing the
standard ALDL protocols. On Corvettes, this will result in the dashboard, HVAC and active
suspension modules not receiving data updates as expected; thus the ASR light may be activated
during data collection. If this occurs, the next vehicle start cycle will clear the ASR light.

Having read that I messed with DM a bit, and noticed in the data acquisition function in v4.01, options for "Disable CCM Handshake" and "Disable Dash Refresh". But I haven't had much luck capturing serial data with DM.

I just got the throttlebody back on and found the battery sucked to death, so I probably won't be able to play much tonight. But I feel optimistic this will be a simple fix once I understand the protocol and command structure better.

[steveo]

that's great news you're looking into it. keep us updated

[spfautsch]

Don't worry, I will. After getting this to compile and run on Ubuntu I'm like a kid on christmas morning with this s**t.

One more question, in regards to this from your page on $EE ALDL Communications:

MODE8 – DISABLE CHATTER

Sending this causes the device to stop sending idle traffic.
This should be sent when a new device (such as a datalogger) is to become the new bus master, and to ensure that the device doesn’t “chat” at random and screw up datalogging or programming.
This is on a timer, it will automatically resume chatter after a predefined period of time.

Any chance you know where you found this info, and what that predefined period might be?

[steveo]

Any chance you know where you found this info, and what that predefined period might be?

wrote it myself

predefined period is device dependant. for the $EE ecm, it's roughly 3 seconds.