Each Class II module is programmed with a list of serial data messages that are important and should be received by the module. One of those important messages is the State of Health (SOH) message. The SOH message is sent out periodically, even if no other information is being transmitted. The SOH message is used to let all other modules on the serial data circuit know the sending module is working correctly.
Each controller relies on information from another controller and incorporates a diagnostic associated with that controller. The diagnostic uses the SOH message for performing the diagnostic. Each time the ignition is turned On, Class II modules first learn the other modules connected to the Class II serial data circuit. If a controller did not initially receive needed information when the ignition was first turned On, the controller will not know which controller the needed information comes from. In this case, DTC U1000 will be set. Once a controller has learned which controller has sent the information, a DTC indicating which controller stopped communications will be indicated if that message is lost. Each controller learns which other controller is sending the message it has to receive every ignition cycle.
Refer to specific "U" code definitions for more details of code setting conditions.
The Class II serial data link is used by the body control module (BCM), electronic brake and traction control module (EBTCM), instrument panel cluster (IPC), sensing and diagnostic module (SDM (airbag)) and the powertrain control module (PCM). The Class II link is used for normal vehicle communication between control modules and for scan tool diagnostic communication.
Class II is a 10.4 k/baud ( equivalent k/bits per second) digital data communication protocol that operates only on logic 1's and logic 0's. Logic 0 is defined as 0 volts and logic 1 is defined as 7 volts. The Class II serial data structure incorporates a variable pulse width, so a logic 1 for instance would not be at 7 volts for the same amount of time for all messages. This is used to allow faster messaging to specific controllers.
The Class II link allows the reduction of separate wires that would otherwise be used to turn On or turn Off a device. For example, if the PCM needed the SERVICE ENGINE SOON (SES) telltale On because it detected an emission related fault, it would send a message to the I/P cluster to turn On the telltale instead of discretely sending a signal over a specified wire. Also, each controller could pass any type of information to other controllers at all times improving on-board convenience features. All messages that each controller uses are sent continuously whether the controller needs them or not. If the SES light is not being commanded On, the PCM to I/P cluster message will indicate to keep the light Off. Most likely, logic 0 would be sent to keep the SES telltale Off. When the PCM needed the SES telltale to be turned On, it would change the bit to logic 1. This method of continuous messaging allows each controller to know when another controller is not communicating on the Class II link.
Each Class II module does not know which controller sent a message until it receives the message. Each message string contains a source identifier, which tells the controller where the message came from. For example, if the PCM lost battery voltage, then the ignition was turned On, the BCM and EBTCM would set a U1000 DTC. This DTC indicates that an expected message was not received and the source ID was not learned. If, for example, the PCM lost battery voltage after the ignition was turned On, the BCM and EBTCM would set a U1016, lost communications with the PCM, since the PCM ID was already learned. This method of "learning" by each control module allows different product lines to use different manufacturer controllers.