       Release Notes for Version 04.12.00 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.00 adds the following features:
Issue #     Description
5-10342     Test 10.3 - Treats a re-entry when ECU VIN is invalid and User enters VIN manually as a re-start of the Dynamic Tests instead of a continuation.
5-10369     Test 5.10 - F501, DATA_F, bit 5 (CSERS) Document says 'must be 1', but comment seems to allow 1 or 0. Document says WARN, but software logs FAILURE.
5-10371     DID $F501, F43D, F43E, F43F, F4CF Evaluation updates.
5-10376     Test 5.16 – INF F877 Bytes 12-35 may be allowed to be $FFFFFFFF when the distance is unavailable.


Version 04.12.00 fixes the following issues:
Issue #     Description
5-10241     Tests that get Extended Data ($91, $92, $93) should FAIL if a request gets a NRC $31 OR if the ECU responds positively if that DTC is not supported.  Add gbAllECUResetCompleted to indicate response data has already been reset (for all ECUs) when doing physically addressed requests.
5-10309     Need to remove superset DTC list from Tests that request Extended Data. No need to round-robin the ECU DTC requests… do all DTCs for one ECU at a time.
5-10319     Test 5.6 will not evaluate any DID responses if one ECU responds incorrectly.
5-10360     Tests 5-11 Reconnecting to CAN must include up to 5 attempts of the $F810 DID request.
5-10361     Test 12.2 - The software is not waiting for a response time-out, for ECUs that respond with a valid NRC $78 to a physically sent request, before continuing with the next ECU in the ECU list.
5-10362     Entering Mfg. name with space is accepted, but when log file is created the name ends where the space in Mfg. name is.   Allow spaces in Make and Model names in static test.
5-10365     Test 10.3 is locking up at the '18 DA 10 F1 19 1A 93' request while "Receiving segmented responses, please wait…". Increase MAX_LOG_STRING_SIZE to 12416 to accommodate 4k of data as 3 characters each in log string.
5-10366     Test 10.3 crashes when receiving 19 1A 93 response of 2280 bytes. Increase MAX_LOG_STRING_SIZE to 12416 to accommodate 4k of data as 3 characters each in log string.
5-10370     Test 10.15 - SMAD numerator should be allowed to increment by more than 1 since Test 10.10.
5-10378     Test 12.7 - Change the evaluation of INF $F89A Byte 4. It must be non-0 if INFs F891-F893 are supported.
