       Release Notes for Version 04.06.03 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.03 adds the following features:
Issue #     Description
5-10100     All DID check tests, there is no requirement that either $F492 or $F4B1 be supported.
5-10107     $F4CB says FAIL in doc but software WARNs, but allows for 'if equipped'. S/W should FAIL on values, but not if supported.
5-10197     Test 9.18, Engine Running Vehicle Information validation was removed from document, remove functionality from software.


Version 04.06.03 fixes the following issues:
Issue #     Description
5-10157     Re-entering the Dynamic Test for HD OBD when Model Year and Engine Certification Year do not match, generates a FAILURE.
5-10161     Test 5.6 & 5.10 - DID $F49A evaluation is testing HEV_BATT_A, but it should be testing HEV_BATT_V.
5-10162     Test 5.6 - DID $F4A5 FAILURE message lists a bad DID number.
5-10163     Test 12.1 - DoIP Vehicle Identification response is constantly sent by vehicle causing software to be in an infinate loop (waiting for vehicle to stop responding).
5-10166     J1699-5 not acting as a DHCP Server.
5-10169     Test 12 - Don't call PassThruIoctl(CLEAR_MSG_FILTERS) if a protocol was not found.
5-10178     Do not decode or evaluate DIDs $F401, $F402, or $F441.
5-10179     Move request for input in Prompts to next line.
5-10180     Prompt for VIN file Name in Dynamic Tests is not reading correctly.
5-10187     DID decode for $F441 displays DID number as 4F41 for some bits.
5-10188     Support UDS NRC evaluation for DoIP messages.
5-10189     Test 12.8 crashes for no apparent reason with DoIP.
5-10190     Test 12 - The $F4B9 transformation to engineering values and units are incorrect.
5-10191     Test 12 - The $F4D4 transformation to engineering values is incorrect.
5-10192     Test 12 - The $F4B2 Name and units are incorrect.
5-10198     Response time for ISO 15765 messages is set to 100ms, it should be 50ms.
5-10199     NRC processing on ISO 15765 for First Frame Indications does not account for $78 extended timing.
5-10213     Test 12.6 should not evaluate the contents of DID $F44E.
5-10218     Remove redundant check in evaluation of $F845
