       Release Notes for Version 04.06.02 of the J1699-5 software


This release includes the requirements of version 4.6 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.


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:
DTC-based SMAD are requested and logged but no evaluation is done currently.
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.06.02 adds the following features:
Issue #     Description


Version 04.06.02 fixes the following issues:
Issue #     Description
	issue 5-10185 - Do not save ECU ID $E000 (functional address) to a received ECU structure and check all received ECU structures (when extra ECUs respond), not just the number of ECUs entered by the user.
