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

shall not
respond 
to any diagnostic request until diagnostic responses are enabled.
Note: 
Reference the Diagnostic CANId section of this specification for more information on the AllNode
request CANId and the AllNode extended address.
An SPS_TYPE_C ECU shall enable diagnostic responses after receiving a request for this diagnostic service
while the DisableNormalCommunication ($28) service is active. The SPS_TYPE_C ECU shall respond to the
request for this service using the SPS_PrimeRsp CANId. The SPS_PrimeRsp CANId is a special case
diagnostic response CANId in the format of 3xx, where the xx is the diagnostic address of the ECU.
Note: 
Refer to Appendix D of this specification for more information on Diagnostic Addresses.
Once diagnostic responses are enabled, the SPS_TYPE_C ECU shall continue to accept diagnostic requests
using the AllNode CANId with the AllNode extended address, or the SPS_PrimeReq CANId. The
SPS_PrimeReq CANId is a special case diagnostic request CANId with the format 0xx, where xx is the
diagnostic address of the ECU. All subsequent diagnostic responses to requests using the SPS_PrimeReq
CANId or the AllNode request CANId with AllNode extended address shall be transmitted using the
SPS_PrimeRsp CANId. The SPS_PrimeReq and SPS_PrimeRsp CAN Identifiers shall be available for use
until a ReturnToNormalMode ($20) request is received or a P3
C 
(TesterPresent) timeout occurs. If a $20
request is received or a P3
C 
timeout occurs before the ECU is completely programmed, an SPS_TYPE_C
ECU shall once again disable diagnostic responses and disable the SPS_PrimeReq and SPS_PrimeRsp CAN
Identifiers.
Note: 
An SPS_TYPE_C ECU shall not send a mode $20 response if it receives a mode $20 request message
or a when a TesterPresent timeout occurs during the phase when the SPS_PrimeReq and SPS_PrimeRsp
CAN identifiers are enabled. Reference the pseudo code of service $20 for more details.
SPS_TYPE_A and SPS_TYPE_B ECUs shall use their permanent diagnostic CAN Identifiers for receiving and
responding to requests for this diagnostic service.
If a programmable node receives a $A2 request, it will report to the tester its current state of programming as
follows:
•
That a memory error has been detected. The memory error could indicate a problem with RAM or
permanent memory (e.g., EEPROM or Flash, potentially including the boot memory).
•
That it is has only boot software present (without operational software and without calibration data).
•
That it has boot software and operational software but without calibration data.
•
That it has boot software, operational software, and calibration data present but the calibration data is a
defaulted and programming needs to be performed.
•
That it is fully programmed with both operational software and calibration data.
Note: 
A defaulted calibration set may be used if vehicle assembly plant operations require some module
functionality at a point in the build process prior to the point where the ECU would be programmed. Default
calibrations may also be present in the ECU when delivered to service. For example an engine controller may
have a no start calibration when delivered to service.
--``,,``````,``,,``,,,`,`,`,,-`-`,,`,,`,`,,`---