[cowboy_dan]

I have been trying to clear some codes using the AE, but have been 100% unsucessful.

My procedure:
1. Connect laptop, truck, and adapter.
2. Turn ign on if not already
3. Press 'Connect to vehicle'
4. When the prompt comes up, get codes from ALL modules (yeah, I know there's only one on the OBS trucks, but I tell it ALL anyway)
5. When codes are retrieved (KAM, CPS and overboost), I press the button to clear the codes (button on the RH side of the screen).
6. in no particular order shut off the ign, disconnect the laptop, truck, and dongle.
7. I then repeat the process, expecting the codes to be gone, but they're still there.

What am I doing wrong?

[Blowby]

Make sure you don't have a chip plugged in. Mine won't clear unless it's just reading the PCM only.

[cowboy_dan]

OK, I'll have to try that. Hopefully I can get to it this week sometime.

[Power Hungry]

One of the things we're starting to see more frequently on OBS trucks is difficulty in communicating with the PCM. All I can assume is that it is because the components in the PCM are aging are are starting to experience signal and timing drift which is affecting the timing critical diagnostic communications. In most communications, a drift of up to +/- 1.5% is usually acceptable although at higher data rates this often presents more of a problem. At 10.4K (J1850 VPW), 1.5% accounts for +/- 156 bits per second drift. At 41.6K, this increases to +/- 624 bits per second. Sizable difference.

Often, replacing the PCM resolves the timing issues since the problem is usually isolated to a specific PCM.

Hope this helps.

[cowboy_dan]

Originally Posted by Power Hungry

One of the things we're starting to see more frequently on OBS trucks is difficulty in communicating with the PCM. All I can assume is that it is because the components in the PCM are aging are are starting to experience signal and timing drift which is affecting the timing critical diagnostic communications. In most communications, a drift of up to +/- 1.5% is usually acceptable although at higher data rates this often presents more of a problem. At 10.4K (J1850 VPW), 1.5% accounts for +/- 156 bits per second drift. At 41.6K, this increases to +/- 624 bits per second. Sizable difference.

Often, replacing the PCM resolves the timing issues since the problem is usually isolated to a specific PCM.

Hope this helps.

If this is the cause of the problem I am having, wouldn't you expect the data logging or testing procedures to be affected?
I can log data all I want, and I have run the cyclinder cutout and buzz tests, and they all work fine without having to retry.

[Power Hungry]

You are correct. I'd expect that all of the functions would either not work or work poorly. I'm not sure what the scoop is on that and would probably say that would be a question for AE directly.

Has anyone else had that problem with AE?