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

8.3.4 Supported Negative Response Codes (RC_). 
The following negative response codes shall be 
implemented for this service. The circumstances under which each response code would occur are 
documented in Table 63 below:
 
Table 63: Supported Negative Response Codes 
Hex 
Description 
Cvt 
Mnemonic 
12 
SubFunctionNotSupported-InvalidFormat 
1. A readFailureRecordIdentifiers request message does not contain one data 
byte following the service identifier. 
2. A readFailureRecordParameters request message does not contain five data 
bytes following the service identifier. 
3. The request message contains a sub-parameter which is not supported. 
M 
SFNS-IF 
22 
ConditionsNotCorrectOrRequestSequenceError 
This response code shall be used if internal conditions within the node (ECU) 
prevent the reading of failure record information stored in the node (ECU). 
C 
CNCORSE 
31 
RequestOutOfRange 
A request for the parameters in a failure record contains a failure record 
identifier (failure record number + DTC identifier) that does not correspond to a 
single unique failure record or is not a valid failure record identifier for the node. 
M 
ROOR 
78 
RequestCorrectlyReceived-ResponsePending 
See 7.2 Return Code Definition. 
C 
RCR-RP 
CameraLoops.com

---

GM WORLDWIDE ENGINEERING STANDARDS 
GMW3110 
© Copyright 2010 General Motors All Rights Reserved 
February 2010 
Page 90 of 336 
8.3.5 Message Flow Examples. 
The example below (Table 64) shows a request for the failure record 
identifiers of the PCM followed by a request for the data parameters from one of the failure records which 
contains a DTC. The example assumes the following information to be true:
 

The point to point request CAN Id for the PCM is $241. 

The USDT response CAN Id for the PCM is $641. 

The PCM contains failure record numbers $00, $01, $02, and $03. 

A failure record is stored for DTC P1671 ($16 $71) with a DTC Fault Type byte = $00 in both failure record 
$00 (freeze frame) and $01 (first failure record). 

No DTCs are stored in failure records $02 and $03. 

The PCM supports providing failure record data with PIDs. 

Engine rpm is a 2-byte parameter stored in the failure record and is identified by PID# $000C. 

Vehicle Speed is a 1-byte parameter stored in the failure record and is identified by PID# $000D. 

Manifold Pressure is a 1-byte parameter stored in the failure record and is identified by PID# $000B. 

Engine Coolant Temperature is a 1-byte parameter stored in the failure record and is identified by 
PID# $0005. 

The USDT flow control parameters Block Size (BS) and Separation Time (ST) are both $00.