       Release Notes for Version 05.01.00 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.00 adds the following features:
Issue #     Description
5-10118	    Add output path name to .ini file.
5-10455     Test 12.3 - DIDs $F4B9, $F4D4, $F4D6, and $F4DA should not be required for PHEVs.
5-10459     Test 12 - DIDs $F41C generates a FAILURE if the value is not $33 or $39, but $01 (OBD II) should be allowed.
5-10463     HD OBD - DID $F4D3 is an 'if Equipped' and should not WARN.
5-10466     Test 5.4 - Remove Physically Addressed request for DID $F501.
5-10472     DID $F80A is missing the followig ECU names: AuxElecPTO, BrakeActCtrl, ContactorCtrl, EnergMgmtCtrl, EVAPSysCtrl, MtrInvertCtrl, ParkBrakeCtrl, ParkPawlCtrl, PrpSysActCtrl, PowerSteerCtl, RefuelingCtrl, and SteerWireCtrl.
5-10480     Test 10.14 Prompt - Change "Turn ignition OFF for 60 seconds" to "Turn ignition OFF for 60 seconds or until all ECUs complete after-run diagnostics". 
5-10481     PARTIAL IMPLEMENTATION - new INFs $F8B5-E5 and new PIDs $F4DD-E1 and $F506-45 evaluation functions written, functions not called, no testing.


Version 05.01.00 fixes the following issues:
Issue #     Description
1132        Test 5.6 is not correctly checking PID $F501 supported bits.
1133        Test 5.6 - PIDs are defined as signed values but are being treated as unsinged values.
5-10464     DIDs $F482, $F489, and $F48A are "if equipped" and should not cause a FAILURE if they are not supported.
5-10471     Test 12.11 - This test should fail if there are pending DTCs, but it does not.
5-10473     Test 5.6 & 5.16 - Remove Physically Addressed request for DIDSupported DIDs, but retain Physical Requests for individual DIDs.
5-10474     Test 5.10 - Add Physically Addressed request for individual DIDs, but not for DIDSupported DIDs.
5-10475     Test 9.16 - A FAILURE in validating DIDSupported DIDs causes a misleading error message of "Unable to capture Initial OBDCOND and IGNCNT.".
5-10476     Reading the “D” value of IUMPR from the log of Test 10.10 is always getting the “N” value.
5-10483     Test 11.2 - Fix display of “Processing DTC:” percentage to always use the same amount of space.
