       Release Notes for Version 01.00.00 of the J1699-5 software


This release includes the requirements of the Phase 1 revision 1.4 of the J1699-5 document
(with the exceptions mentioned below) and is intended to test Model Year 2023 and beyond.


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!


J1699-5 Version 01.00.00 is based on J1699-3 version 17.01.00


Some of the major differences from J1699-3:
	the User is prompted to accept the vehicle information (ECUNAMEs, CALIDs, CVNs, etc), collected from the vehicle, before continuing the test,
	the application only attempts to connect to ISO15765 11-bit and ISO15765 29-bit protocols,
	ignored DTCs from the .ini file is not currently implemented,
	country specific support and evaluation is not currently implemented.


Some of the variances from the Phase 1 revision 1.4 of the J1699-5 spec:
	only J2534 04.04 is currently supported,
	no physical addressing of requests is currently supported
	some tests which were in J1699-3 but not currently in J1699-5 are still run (ie recurring protocol determination after changing key state, vehicle state checks),
	some tests are not currently implemented (noted in the log file as "NOT CURRENTLY IMPLEMENTED"): 
		Freeze Frame ($19 $04),
		Control of System, Test or Component ($31),
		Performance Counters (Test 11),
	drive cycle tests (Tests 9.8-22 and Test 10), called out but not detailed in the spec, are implemented as in j1699-3
	(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),
	completeness tests of $F501 are not implemented.

