       Release Notes for Version 04.12.02 of the J1699-5 software


This release includes the requirements of version 4.12 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.12.02 adds the following issues:
5-10211     NRC $21 (Busy Repeat request) should be allowed for $22 $F810 request during initialization of DoIP, just as it is for CAN in ISO 15765-4.
5-10227     Is Test 12.3 (Protocol Identification in document) really needed? Should Test 12.3 (PSA Active in document) be merged with Test 12.5 (Clear DTCs in document).
5-10235     J1699-5 should fail a vehicle that repetitively sends 'Vehicle Announcement' messages.
5-10410     Test 10.10  - on screen IUMPR and SMAD percent completed progress display.


Version 04.12.02 fixes the following issues:
Issue #     Description
5-10383     Test 9.19 no responses on 29-bit CAN after attempting ‘Checking for OBD on 500K ISO15765 11 Bit (Classic J1979 Services) protocol’, but CAN traffic show requests and responses are present. Appropriately handle deprecated service request/response, improve logging text for failure tracking, check $F810 inside DetermineOBDProtocol, in case response is overwritten by subsequent protocol failure, remove DetermineOBDProrocol() call from Test 9.19.
5-10394     Test 11.1 is crashing after IUMPR, SMAD, and IPD Data has been collected on a first run through the Dynamic Test. 
5-10397     Test 6.2 - Test should prompt if no Pending DTC after 30 seconds to continue with FAIL.
5-10399     Test 11.1 fails with the error "FAILURE: Could not find Test 10.10 IPD and DTCIUMPR data in log file." even though the required information appears to be in the log file.
5-10400     Test 10.7 passes, but there are no Test Results requested even though Test 10.3 shows that there are Test Result DTC (via 19 1A 92). This impacts all Extended DTC Data requests - IUMPR, Test Results, and SMAD.
5-10401     Test 10.12 logs IUMPR and SMD without making network requests. IUMPR and SMAD are not part of this test and should not be logged.
5-10403     Test 5.1 fails protocol determination, but log file also logs "Unable to continue Dynamic Tests".
5-10404     Test 9.16 - When test fails Screen says "Errors detected during Dynamic Test "… remove word "Dynamic".
5-10407     Update $F501 Data B, BIT 6 evaluation.
