− | Similar to [[#Mode 8|Mode 8]], a Mode 9 request will re-enable BCM chatter. A Mode 9 request can be sent to enable bus chatter earlier, rather than waiting for the original Mode 8 request to time out. This may be useful (and potentially good practice) if a device only requires bus silence for a short period of time, as bus silence for longer periods of time can lead to Check Engine warnings on the cluster{{Cn}}. The BCM will respond with a frame containing a single data byte <code>09</code> with an ID of <code>F1</code> (a frame identical to the request). The below table illustrates the full structure of a Mode 9 request. | + | Similar to [[#Mode 8|Mode 8]], a Mode 9 request will re-enable BCM chatter. A Mode 9 request can be sent to enable bus chatter earlier, rather than waiting for the original Mode 8 request to time out. This may be useful (and potentially good practice) if a device only requires bus silence for a short period of time, as bus silence for longer periods of time can lead to Check Engine warnings on the cluster{{Cn}}. Note that some scan tools issue a Mode 0 request instead of a Mode 9 request to re-enable BCM chatter{{Cn}}. When a Mode 9 request is sent, the BCM will respond with a frame containing a single data byte <code>09</code> with an ID of <code>F1</code> (a frame identical to the request). The below table illustrates the full structure of a Mode 9 request. |