       Release Notes for Version 02.06.00 of the J1699-5 software


This release includes the requirements of version 2.6 of the J1699-5 document,
with the exceptions mentioned below. It is intended to test vehicles in
Model Year 2023 and beyond, that are compliant with SAE J1979-2


This is a beta test version, primarily to confirm proper communication between the application
and the vehicle and data formatting and values, but is not intended as an "official" vehicle validation.



NOTES:
 - Slow PCs/J2534 devices may cause false vehicle failures!
 - This release only supports the 0404 version of the J2534 API!


Some of the major differences from J1699-3:
	The application only attempts to connect to ISO15765 11-bit and ISO15765 29-bit protocols,
	Only US vehicles and evaluations are currently implemented.


Some of the variances from version 2.6 of the J1699-5 spec:
	Only J2534 04.04 is currently supported.
	Physical addressing of requests is currently implemented only in Test 5.
	Some tests which were in J1699-3 but not currently in J1699-5 are still run
		(e.g., recurring protocol determination after changing key state, vehicle state checks).
	Control of System, Test, or Component ($31) tests are not currently implemented (noted in the log file as "NOT CURRENTLY IMPLEMENTED"), 
	Drive cycle test (Tests 9.8-22), are implemented as in j1699-3 (only INF $F808 and $F80B are implemented for OBDCOND and INGCNTR)
		(These can be skipped by answering "No" to the prompt "Do you wish to run the CARB drive cycle portion for Permanent DTCs (Tests 9.8-9.22)?"
		at Test 9.7).
	Prompt for type of engergy (internal combustion or zero-emission) as well as the subtypes (battery electric, fuel cell or cng, other) are not implemented.
	Dynamic tests 10 and 11 are not currently implemented.


Version 02.06.00 adds the following features:
Issue #     Description
3-1035      Add Medium Duty Truck to Vehicle Type Options (MD for trucks chassis certified and MDDC for trucks dyno certified).
3-1047      Change wording to prompts to match changes in j1699-3 doc V17.04 (ECU number, Test 6.1, Test 7.1, Test 9.8.
3-1048      INF $77 should not have a phase-in period warning.
3-1054      EOBD allows ECUs to reply both positively and negatively to Clear Codes request
5-10002/5-10003  Add support for NAK values in UDS
5-10004     Allow use of ignored DTCs read from ini file.
5-10006     Remove prompt to "Disable Tester Present Messages?" (Tester Present Messages are always disabled now)
5-10007     Allow subtest to continue after failure in DID-Support DID check.


Version 02.06.00 fixes the following issues:
Issue #     Description
3-1049      Fix additional failures when closing channels for unsupported protocols of partially-compliant j2534 interfaces.
3-1051      Log UNSUPPORTED for unsupported IUMPR rather than zero to match on screen display.
3-1052      To prevent incorrect IUMPR values in Test 11.2, only free ECUs IPT memory if in Test 9.19, move ReadIPT to TestToVerifyPerformanceCounters.c.
3-1053      Add delay after banner display to prevent screen issues on Windows 11 machines.
3-1057      Fix improper failure on ESC (Abort) from test 11.2, also note any true failures before allowing test to abort.
3-1060      Fix poorly formatted failure message which would cause application to crash if current and previous test vehicle types did not match.
3-1061      Add evaluation for $F4A2
