       Release Notes for Version 04.06.00 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.00 adds the following features:
Issue #		Description
5-10073		Add ZEV Fault Insertion tests.
5-10105		Test 10.6 is not decoding the ECU response to $F501, it appears to be decoding an older response from Test 10.2.
5-10129		Remove NRC requirement for a Functionally Addressed request for and unsupported SID $22 DID $F401, $F402, or $F441.
5-10131		Test 5.3 - Add check for SID $04 (Classic OBD II).				
5-10132		Tests 5.5.2 & 5.13.1 - Add request for $19 $1A $92.				
5-10133		Tests 5.5.3 & 5.13.2 - Add request for $19 $06 for all DTCs returned from $19 $1A $92.				
5-10134		Tests 5.7 & 5.15 - Add VerifyService $31.				
5-10135		Tests 6.2, 7.2, 8.2, 9.2, 10.8, 11.10 - Add check that Pending DTC Status reports correct values.				
5-10136		Tests 6.3, 7.3, 8.3, 9.3, 9.8, 10.9, 11.9 - Add check that Confirmed DTC Status reports correct values.				
5-10137		Tests 10.3 - Add collecting of DTC Extended Data $91 (IUMPR), $92 (Test Results), and $93 (SMAD).				
5-10140		Tests 10.7 - Add Physically Addressed $19 $06 $013001 $92 (Test Results).				
5-10141		Tests 10.10.1 - Add $19 $56 to list DTCs for each Readiness Groups.				
5-10142		Tests 10.10.3 - Add for each DTC obtained in 10.3, send physically addressed request for IUMPR data.				
5-10143		Tests 10.10.4 - Add for each DTC obtained in 10.3, send physically addressed request for SMAD data.				
5-10145		Tests 11.1.2 - Add $19 $06 DTC $91, IUMPR by DTC.				
5-10146		Tests 11.1.3 - Add $19 $06 DTC $93, SMAD by DTC.				
5-10147		Tests 11.6 - Add $19 $06 DTC $92, Test Results by DTC.				
5-10148		Tests 11.7.1 - Add $19 $06 DTC $91, IUMPR by DTC.				
5-10149		Tests 11.7.2 - Add $19 $06 DTC $93, SMAD by DTC.				
5-10151		Tests 11.12.1 - Add $19 $06 DTC $91, IUMPR by DTC.				
5-10152		Tests 11.12.2 - Add $19 $06 DTC $93, SMAD by DTC.				


Version 04.06.00 fixes the following issues:
Issue #		Description
3-1105		Test 10.3 - why is _cgets_s being used instead of scanf_s?
3-1106		Add a "\n" after prompt in Q4, Q5, Q12 User Name, LogPrint.c (ln 287, 381)
3-1107		Can we make Test 11.2 key instructions into a 'Prompt'?
5-10099		Test 7.4 Fails if all F501 responses don't indicate that MIL is active.
5-10102		VerifyVehicleState is reporting that a non-Hybrid vehicle is a Hybrid.
5-10109		Test 12.3 Fails because no $F5xx DIDs are supported, but there is no requirement to support this range for ZEVs.
5-10111		Test 12.3 Fails because $F4D1 is 00 00 00 00, but there is no requirement to evaluate the content.
5-10112		Test 12.3 Fails because $F4D6 is 00 00, but it should be 0.
5-10113		Test 12.3 Fails because $F4DA is 00 00 00 00, but there is no requirement to evaluate the content.
5-10115		Test 12.3 Fails because $F4D5 is supported on a ZEV, but this DID is only required to be supported on FCEV (FUEL CELL).
5-10116		Test 12.7 Fails because $F80A list is not correct.
5-10119		Test 10.10 will decode 0's for all ECUs IUPMR and SMAD data if one of the ECUs issues an NCR. This is a 'continue on FAILURE' issue.
5-10120		Test 10.14 - Add ECU ID to SMAD data decode.
5-10121		Test 11.1 is FAILs ECU for IUMPR counters that have not changed since Test 10.10, but there is no requirement to do so.
5-10125		Software not correctly parsing data from DoIP socket that contains more than one DoIP message. 
5-10126		DoIP Req MSG not being written to log. 
5-10128		DoIP "ACK message correctly received, processed, and put into transmit buffer." being counted as ECU response message in RequestSID().				
