       Release Notes for Version 04.13.00 of the J1699-5 software


This release includes the requirements of version 4.13 of the J1699-5 document,
with the exceptions identified in the Work Status spreadsheet. It is intended to test vehicles in
Model Year 2025 and beyond, that are compliant with SAE J1979-2 and J1979-3


NOTES:
 - Slow PCs/J2534 devices may cause false vehicle failures!
 - This release only supports the 0404 version of the J2534 API!
 - J2534 Interfaces that do not support all of the protocols being tested will result in the vehicle failing J1699-5.
 - To avoid false failures during the CARB Drive Cycle, do NOT operate the vehicle at exactly 25 MPH (40KM/H).

!!!!NEW NOTE!!!!
 - Command Prompt for Window must be at least 33 rows tall
   Windows 10 and earlier: Right click Command Prompt Title Bar, Left click Properties, Left click Layout Tab, Set Window Size Height to at least 33 (Screen Buffer Size Height should be significantly larger).
   Windows 11: Right click Command Prompt Title Bar, Left click Settings, Scroll Down to Launch Size, On the right-hand side, Left click Drop Down Menu Arrow, Set Rows to at least 33.



Some of the major differences from J1699-3:
	The application only attempts to connect to ISO15765 11-bit and ISO15765 29-bit protocols for ICE vehicles, for ZEVs DoIP will also be checked.
	Only US vehicles and evaluations are currently implemented.


Some of the variances from the latest J1699-5 spec:
	Some tests which were in J1699-3 but not currently in J1699-5 are still run (e.g., vehicle state checks, etc.).


User Notes:
For Tests 10 and 11, only DTCIUMPR and DTCSMAD (SID $19 subfunc $1A ExtData $91 and $93) which also have IM Readiness assigned (SID $19 subfunc $56) are requested and logged.
 
During the Manufacturers Specific Drive Cycle test, the data page (screens of IM Readiness, IPT, RG IUMPR/SMAD data) can be changed by pressing Right Arrow (next higher page) and Left Arrow (next lower page).
The currently requested ECU is at the top next to Test Status and the IUMPR or SMAD Extended Data and it's place in the full list (x of xx) and number of passes through the whole list
is printed just below that. 



Version 04.13.00 adds the following features:
Issue #     Description
5-10336     Test 11.2 - Update display for RGID/IUMPR and SMAD.
5-10398     Test 5.6, 5.10, and 10.13 Evaluation of DID $F501 per CCR 1968.2 (g)(4.1.2)(C). PID $F501 DATA_E Bit 1 (CV)., PID $F501 DATA_B Bit 1 (FUEL). Change FAILURE to WARNING if not supported.
5-10411     Change IUMPR and SMAD value logging. Also, SMAR conversion is incorrect.
5-10423     Change "USER WARNING" text in USER_ERROR to "INSTRUCTION MISMATCH" as log entry preamble and in log error totals at end of log. Additionally when there is an Engine State mismatch (on STOP/START vehicles ONLY), prompt "Is vehicle in Auto Stop? (Enter Yes or Quit)".
5-10427     Test 11.2 - Change wording of navigation prompt.


Version 04.13.00 fixes the following issues:
Issue #     Description
5-10405     With 11-bit CAN IDs, ECUs that did not respond to 22 F810 should be ignored (i.e., don't set up Flow Control filters).
5-10406     Test 12.1 - If Routing Activations response does not contain Routing Activation Code = 0x10, the DoIP is not supported. Do not retry.
5-10417     Test 10.1 DetermineOBDProtocol() works, but the Test 10.11 DetermineOBDProtocol() doesn’t. Vehicle uses 29-bit CAN IDs.
5-10419     Test 11.2 - Reports FAILURE when ESC pressed, but no indication of problem in log.
5-10420     Test 11.2 - Reported FAILURE count being logged is incorrect.
5-10421     Test 11.1 Re-Enter - DTC conversion error from log file loading: U code DTS are being interpreted as P Codes, so the subsequent SMAD request is getting an NRC $31.
5-10422     Test 11.6 and beyond - DTC lists for IUMPR/Test Results/SMAD are being attributed to the wrong ECU ID, causing NRC $31 FAILUREs.
5-10426     Test 12 indicates PASS, even though some gTestSubsection FAILED.
5-10428     Test 11.7 - The FAILURE text for SMAD evaluation must change from "…has not changed since Test 10.10" to "…has decremented since Test 10.10".
