       Release Notes for Version 4.11.02 of the J1699-5 software


This release includes the requirements of version 4.11 of the J1699-5 document,
with the exceptions identified in the Work Status spreadsheet. It is intended to test vehicles in
Model Year 2024 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:
During the Manufacturers Specific Drive Cycle test, the data page (screens of DTC IUMPR data) can be changed by pressing Right Arrow (next higher page) and Left Arrow (next lower page).
The currently requested DTC with IUMPR Extended Data and it's place in the full list (x of xx) is printed next to the data page number. 


Version 04.11.02 adds the following features:
Issue #     Description
5-10158     Test 11.5 must also check DIDs $F431/$F44E.
5-10287     $F898 (Recent) should be non-zero, $F899 (Lifetime) can be any value.
5-10332     Test 5.16 - Update Evaluation Criteria for $F817, $F81C.


Version 04.11.02 fixes the following issues:
Issue #     Description
5-10349     Test 11.7 is not correctly evaluation signed Test Results data.
5-10350     Test  5.16, 12.7 - NRC $31 being flagged as a FAILURE for Physically Addressed SID $22 $F8xx DIDSupported DID requests - but not consistently.
5-10351     Test  5.16, 12.7 - Reported "DID $F8A0  NAK $31 (Unsupported DID request) for functionally addressed request!", but this request was Physically Addressed.
5-10352     $F810 requests for ECU detection must be functionally addressed.
5-10364     Test 6.4 DID decoding is not accounting for the DID count byte in the response, which can cause an infinite loop.
5-10355     Test 5.16 - Fails INF $F878 for Gas engines, but requirements say that it only applies to "D – MDV/MDDE OBD II, HD OBD FAIL if value is zero".
5-10356     Test 5.6 & 5.10 - DID $F471 decodes VGT_A_STA and VGT_B_STA incorrectly.
5-10357     Test 5.6 & 5.10 - In DID $F47A & $F48B, the references to "Diesel" or "D" (like in DPF) must be removed from the DID decode.
5-10358     Test 5.13 contains "Failure: Test ResultList error", which is a summary statement that must be removed, but was missed.
5-10359     Test 5.6, 5.10 - DID $F4BD decode says "Hybrid/EV Battery Temperature Data support", but it should say "HVESS Total Energy Throughput Data support".
