General Specification Electrical Function gmw3110 General Motors Local Area Network Enhanced Diagnostic Test Mode Specification

Y
seconds (
Y
= specified in the ECU
’s memory). The 
Y
second 
timer shall begin with the 
X
failed attempt or upon a power/ignition cycle or reset of the ECU to ensure a 
security lockout after all power interruptions. 
7.2.8 RequestCorrectlyReceived-ResponsePending ($78, RC_RCR-RP). 
This response code indicates that 
the request message was received correctly, and that any parameters in the request message were valid, but 
the action to be performed may not be completed yet. This response code can be used to indicate that the 
request message was properly received and does not need to be retransmitted, but the server (ECU) is not yet 
ready to receive another request. The negative response message with this response code may be repeated 
by the ECU(s) within P2
C
= P2
C
* until the final response message (which may be positive or negative, where 
RC_ is not equal to $78). 
Example:
A typical example where this response code may be used is when periodic messages are 
scheduled (see $AA service) and a new request is sent to modify the contents of the scheduler. It is possible 
that the first response may not be sent within P2
C
due to the status of the other messages in the scheduler. 
7.2.9 SchedulerFull ($81, RC_SCHDFULL). 
This response code indicates that the tester attempted to 
schedule a diagnostic message via the $AA service and the ECUs scheduler table was full. 
Example:
ECU 
A
is capable of scheduling 4 messages and currently has two messages in its scheduler. A 
request is received by ECU 
A
which would attempt to schedule three additional messages. This request would 
be rejected as it would make the total number of messages that ECU 
A
would have scheduled (5), greater 
than the number which it is capable of scheduling.