       Release Notes for Version 05.01.01 of the J1699-5 software


This release includes the requirements of version 5.1 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 05.01.01 adds the following features:
Issue #     Description
5-10118     Add output path from .ini file to dynamic test logfile.
5-10415     Test 5.8 - Add protocol determination (baud rate test order is different than Test 5.2).
5-10481     PARTIAL IMPLEMENTATION of logging decode, received data size checks, function calls, and decimal places for DIDs $F4DD-E1, $F506-45, and $F8B5-E5.
5-10490     Test 5.10 - Evaluation criteria for DID $F44E must be 'FAIL if greater than 5 minutes' (for Test 5.10 only).


Version 05.01.01 fixes the following issues:
Issue #     Description
5-10484     Test 11.1 and 11.7 may falsely pass SMAD counts if all IUMPR counts have incremented or if no IUMPR is supported.
5-10485     Test 11.2 - ECU Status and RGID IUMPR/SMAD Status are not being correctly displayed for ECUs with CCM only and no IUMPR or SMAD.
5-10488     INF $F877 must allow bytes 12-35 to be $FFFFFFFF to indicate "Not Supported or Valid distance not available".
5-10492     Test 10.10 IUMPR logging is incorrect, causing a re-entry of Test 11.2 to have initial values of 0.
5-10494     Tests 6.4, 7.4, 8.4, and 9.5 - Must account for DID $F4AD being variable size in the Freeze Frame Data.
5-10497     Fix DID-Support DID requesting the next range when $FxE0 has support bits set for Group Requests.
5-10498     Fix response time display in FAILURE messages.
5-10499     ReadDTCSMADData - replace IUMPR with SMAD in the text of failure messages and comments.
5-10500     Standardize printf format code for unsigned long and proper number of decimal places for float.
5-10501     Add newline to logging of INF $F8A6 CEC_WC and $F8A7 SOC_T_50PCT_SWG to match standard.
5-10502     Remove superfluous TempData_long from some Log calls.
5-10503     DID $F40C should be treated as float instead of long.
5-10504     DID $F4C6,C8 add '$' to display of status to indicate hexadecimal.
5-10505     DID $F4C8 pPid->Data[1] should be pPid->Data[0] for status display.
5-10506     DID $F4D0 INIT_ESS_RSRV_CAP display should use TempData_float instead of TempData_long.
5-10507     DID $F4E1 OBM_MON_PM logging should use szOBM_MON_STATUS[pPid->Data[3] instead of szOBM_MON_STATUS[pPid->Data[2].
5-10508     DID $F503,04,05 should include "PID " in front of $F5xx in failure text, for consistency.

