       Release Notes for Version 04.11.00 of the J1699-5 software


This release includes the requirements of version 4.10 of the J1699-5 document,
with the exceptions mentioned below. 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.).
	DTC-based SMAD data is requested and logged but no evaluation is currently bring doned.


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.00 adds the following features:
Issue #     Description
5-10095     Tests 6.4, 7.4, 8.4, 9.4 - Add Freeze Frame functionality for ICE.  Add PID lookup table, add flag to disable failure logging, and make PID evaluations into functions for logging Freeze Frame DID data.
5-10183     Test 5.5.2.2, 5.13, 10.3, 10.7, 11.1, 11.6, 11.12 - Do not FAIL if an ECU does not have DTCs that supports $91 Ext. Data, $92 Ext. Data, $93 Ext. Data. NEW PASS/FAIL/WARN criteria See 5.5.2.2.
5-10206     Test 11.2 & 11.7 - Change evaluation criteria for IUMPR data using RGID.
5-10210     J1979-3 says Functionally Addressed request are limited to Vehicle Identification, but Test 12 has some tests that are done with Functional Addressing.
5-10296     Test 10.13 - This was the DID validation after the CARB Drive Cycle, but this is no longer part of the requirements. The DID evaluation must be removed.
5-10297     Test 5.3, 5.9, 9.23.4 Clear Codes - Check that ALL OBD II ECUs respond.
5-10298     Test 10.1 is not failing if there is a response to SID $01 PID $01.
5-10299     Physically Addressed requests must FAIL if the requested item is supported, but no response is received.
5-10312     Test 9.1 Need to allow for User Fail, that is continue with MIL ON (e.g., Yes, No, Fail).
5-10321     Test 12.3 & 12.6 - DID $F4D0 bits 1 & 2 are required to both be 1 in V4.10 of document. 'Reserve Battery Capacity' should 
5-10326     WARN for both ICE and ZEV if $F810 != 1.

Version 04.11.00 fixes the following issues:
Issue #     Description
5-10338     Correct the handling of 'Not Supported' for $F842, $F844, and $F846 for PTOERT and PTOFC.
5-10278     Test 9.19 - INF $F817, INF $F818, and other evaluations are returning FAIL, but not logging it.
5-10286     Test 12.7 - Number of decimal places in Engineering Values is incorrect.
5-10303     Test 5.17 - Reverse Order checks for Group Requests are allowing positive responses without DIDs.
5-10310     Tests 5.5, 5.13, 10.7, 11.6 - Test Results (Test Value, Min Test Limit, or Max Test Limit) do not have the appropriate Unit/Scaling applied.
5-10315     Don't stop Tester Present on DoIP.
5-10316     $F898 and $F899 logging FAIL if counters != 0 but not counting as FAILURE.
5-10317     Test 9.19 must FAIL if the FC_R value in $F817 is not equal 0.
5-10318     Log entry for $F819 incorrectly list $F918 in text.
be an 'if equipped' option.
5-10323     Test 12.8 DoIP fails to connect because bNetworkStarted and bRoutingActvation are both TRUE.
5-10327     Test 12.8 - There is no requirement that there only be one CALID. The software must not WARN if there is more than one CALID.
5-10328     Test 12.8 - There is no requirement to support or check CVN so the check/WARNING/FAILURE must be removed.
5-10330     increase size of DTC buffers.
