Страница 1 мировой engineering стандарты общая спецификация

RequestOutOfRange
A PID in the request message is not supported by the Node.
The DPID# in the request message is either invalid or cannot be dynamically
defined.
M
ROOR
78
RequestCorrectlyReceived-ResponsePending.
See 7.2 Return Code Definition.
C
RCR-RP
8.10.5 Message Flow Example(s) DynamicallyDefineMessage. 
The examples below (Tables 119 thru 122)
show how a dynamic DPID is defined for a Powertrain Control Module (PCM). All of the examples assume the
following information to be true for the PCM:
•
The diagnostic CAN Identifiers for the PCM are: $241-USDT Request, $541-UUDT Response, and
$641-USDT Response.
•
$FE thru $F7 is the valid range for dynamically definable DPIDs.
•
Engine rpm is a 2-byte parameter and is identified by PID# $000C.
•
Vehicle Speed is a 1-byte parameter and is identified by PID# $000D.
•
Manifold Pressure is a 1-byte parameter and is identified by PID# $000B.
•
Engine Coolant Temperature is a 1-byte parameter and is identified by PID# $0005.
•
Engine Mass Airflow is a 2-byte parameter and is identified by PID# $0004.
•
Spark Advance is a 1-byte parameter and is identified by PID# $000E.
•
The USDT flow control parameters Block Size (BS) and Separation Time (ST) are both $00.
8.10.5.1 Example 1: Define DPID with Multiple PIDs. 
In the first example (Table 119), the tool sends a $2C
request message to define DPID $FE with Engine rpm, Vehicle Speed, Manifold Pressure, Engine Coolant
Temperature, and Mass Airflow data.
Table 119: DynamicallyDefineMessage Example 1 Message Flow
T = Frame Sent By Tester, N = Frame Sent By Node; shaded region indicates PCI
Frame Type CAN Id
#1
#2
#3
#4
#5
#6