       Release Notes for Version 04.06.01 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.01 adds the following features:
Issue #		Description


Version 04.06.01 fixes the following issues:
Issue #		Description
5-10164		J2534 Interface not accepting Connect Flags when both Option1 and Option2 bits are set (even though this is VALID).  Change Auto-Detect value to 0x00000000, instead of 0x00030000.
5-10165		Test 12 - Initialize bNetworkStarted in DoIP.c.
5-10168		Test 12 - Log RX and TX of Routing Activation message.
5-10169		Test 12 - Don't call PassThruIoctl(CLEAR_MSG_FILTERS) for DoIP, it is not allowed.
5-10171		Test 12 - Process Vehicle ID response and decode; if a response is received, do not repeat request 3 times.  Allow variable data size responses.
5-10172		Test 12 - Some DoIP ECU responses are not being process or logged.  Fix received data storage buffer handling to prevent data loss and set TxMsg ExtraDataIndex to Max to ensure that the transmitted DoIP message is logged.
5-10173		Test 12 - Don't repeat transmission of the Routing Activation, if a response was received.  Check for the same number of responses as Entity Status, not number of ECUs.
5-10174		Test 12 - Support up to 239 ECU for DoIP.
5-10175		Test 12 - For DoIP, logs a "Current protocol is not allowed for UDS" FAIURE, which is incorrect. Remove outdated protocol limitation.
5-10181		Improve network socket maintenance.
5-10182		Temporary work-around to prevent socket communication problems when j2634 device disconnects.
