       Release Notes for Version 04.00.00 of the J1699-5 software


This release includes the requirements of version 4.0 of the J1699-5 document,
with the exceptions mentioned below. It is intended to test vehicles in
Model Year 2023 and beyond, that are compliant with SAE J1979-2


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!


Some of the major differences from J1699-3:
	the application only attempts to connect to ISO15765 11-bit and ISO15765 29-bit protocols,
	only US vehicles and evaluations are currently implemented.


Some of the variances from version 2.6 of the J1699-5 spec:
	only J2534 04.04 is currently supported,
	physical addressing of requests is currently implemented only in Test 5,
	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),
	Control of System, Test or Component ($31) tests are not currently implemented (noted in the log file as "NOT CURRENTLY IMPLEMENTED"), 


User Notes:
DoIP communication is currently only implemented via J2534 (V04.04) ETHERNET_NDIS.
ZEV Tests (Test 12) currently only do vehicle communication initialization and Protocol ID check (INF $F810).

DTC-based SMAD and IM Readiness are requested and logged but no evaluation is done currently.
During the CARB 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.00.00 adds the following features:
Issue #     Description
3-1086      Collect the sum of $F863,69,6F,73 [bin2] through [bin14] for comparison to [bin1] and add check that the values of $F873 (EAL) are greater than $F863 (Active) Test 5.16 values.
3-1087      Collect the sum of $F864,6A,70,74 [bin2] through [bin14] for comparison to [bin1] and add check that the values of $F874 (EAL) are greater than $F864 (Active) Test 5.16 values.
3-1088      Collect the sum of $F865,6B,71,75 [bin2] through [bin14] for comparison to [bin1] and add check that the values of $F871 (Lifetime) and $F875 (EAL) are greater than $F865 (Active) Test 5.16 values.
3-1089      Collect the sum of $F866,6C,72,76 [bin2] through [bin14] for comparison to [bin1] and add check that the values of $F872 (Lifetime) and $F876 (EAL) are greater than $F865 (Active) Test 5.16 values.
3-1090      Remove INF $F818 EOE-R, EOE-L, PKE-R, and PKE-L checks for greater than 0 and comparisons to 5.17 data in Test 9.22.
5-10001     Add support for DoIP J2534 ETHERNET_NDIS).
5-10051     Remove PID Support check for $F4AD,AF,B0,D3,D7
5-10053     Do not fail for NRC $31 when an ECU does not support a physically addressed SID $14 request.
5-10058     Update evaluation of INF $F81D-1F, $F821-2A, $F841,44,45,46, $F851-5B, $F861-66, $F867-76.
5-10059     Fail if $F4E0 indicates support for $F500, after 2026.
5-10060     Do not fail for Type A DTC in Test 6.4.
5-10061     Test 5.10 should not fail if $F502,03 misfire count is greater than 0.
5-10069     Update test category selection prompts to match requirements document.


Version 04.00.00 fixes the following issues:
Issue #     Description
5-10056     Fix text of Fail/Warn messages which should say "INF $F841 EOE-A must return a value of greater than 1 sec" instead of "INF $F841 ERT-A must return a value of greater than 1 sec".
5-10057     Fix text of Fail/Warn messages for INF $F854 AT2_TIME_S which incorrectly reports "AT1_TIME-S", AT2_DT-S which incorrectly reports "AT1DT-S", and AT2_DT-L which incorrectly reports "AT1DT-L".
5-10062     Add support for up to 255 DTC IUMPRs.
5-10064     Remove Fail/Warnings for $F808/F80B
5-10066     Correct pointer assignment so that DisplayPid01 displays the data in $F401 instead of $F501.
5-10070     Correct $F41C range check for greater than or equal to instead of just greater than MAX_OBD_TYPES.
5-10071     Fix an incorrect pointer assignment which could prevent evaluation of Protocol ID response.
            