       Release Notes for Version 04.10.00 of the J1699-5 software


This release includes the requirements of version 4.10 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.
 - To avoid false failures during the CARB Drive Cycle, do NOT operate the vehicle at exactly 25 MPH (40KM/H).

!!!!NEW NOTE!!!!
 - Command Prompt for Window must be at least 33 rows tall
   Windows 10 and earlier: Right click Command Prompt Title Bar, Left click Properties, Left click Layout Tab, Set Window Size Height to at least 33 (Screen Buffer Size Height should be significantly larger).
   Windows 11: Right click Command Prompt Title Bar, Left click Settings, Scroll Down to Launch Size, On the right-hand side, Left click Drop Down Menu Arrow, Set Rows to at least 33.



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 Freeze Frame data and 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.10.00 adds the following features:
Issue #     Description
5-10117     Test 12.6 Fails because $F4B2 is 0, but there is no requirement to evaluate the DID content.
5-10210     PARTIAL FIX FOR J1979-3 says Functionally Addressed request are limited to Vehicle Identification, but Test 12 has some tests that are done with Functional Addressing.
5-10223     Test 12.3/12.6 - The 'Required Value' for DID $F4D0 is unclear, what is to be checked. What if the ECU indicates none of the fields are supported?
5-10224     Test 12.3/12.6 - The 'Required Value' for DID $F4D1 is unclear. J1979DA seems to indicate that they should only report a value when a charger is connected.
5-10263     Test 12.11 - Test logic is incorrect, looping must be removed and it must FAIL ECUs that do not respond to a Pending DTC request and not make a Confirmed DTC request.
5-10272     Only use ECUs that respond positively to $22 $F810 with data = 01.
5-10279     Update DID Evaluations from J1699-5 V4.10.
5-10280     Range linking $F4xx to $F5xx is not allowed. This removes the allowance implemented in Issue #5-10059.  Also $F5xx to $F6xx.
5-10281     Test 12.11 - Remove text "*** Further ZEV Tests NOT CURRENTLY IMPLEMENTED ***" from Test12_ZEV.c, as there are no tests beyond Test 12.11.
5-10295     Test 11.7 - FAILURE 'Monitor has not changed since Test 10.10' needs to include the text "IUMPR" (to distinguish from SMAD, which will be added later).


Version 04.10.00 fixes the following issues:
Issue #     Description
5-10098     Test 10.11 - Crash because ECU IDs don't match original list.
5-10101     Test 5.9/12.5 (KOER) Clear Codes did not fail Light Duty Diesel for mixed Pos and Neg responses, but did fail Light Duty Gas (as expected).
5-10182     Fix Socket communication problems when J2534 Interface disconnects.  Add connect delay and retry
5-10236     Tests that get Extended Data ($91, $92, $93) should ask each ECU for only the DTC Extended Data that the ECU supports.
5-10241     Tests that get Extended Data ($91, $92, $93) should FAIL if a request gets a NRC $31 OR if the ECU responds positively if that DTC is not supported.
5-10278     PARTIAL FIX FOR Test 9.19 - INF $F817, INF $F818, and other evaluations are returning FAIL, but not logging it.
5-10282     Test 5.5 & 5.13 - $19 $06 ($92) must allow for more than 10 Test Results.
5-10283     Delete the DTC Extended data summary statements.
5-10284     Test 12.3 & 12.6 - Should only evaluate the DIDs listed in the table. Other DID that are supported by the ECU should be decoded and logged, but not evaluated.
5-10285     Test 9.8 should not FAIL if 'Pending DTC' bit is set in the Confirmed DTC Status.
5-10290     Test 12.7 - F898 evaluation is wrong in test 12.7. According to the document the "Recent Data must reset to zero post code clear. FAIL if any counter is non zero". The software warns if any value is zero.
5-10294     Test 11.2 - IUMPR results prints from superset of IUMPR DTCs, not ECU specific list.
5-10301     Test 11.2 will not complete even though summary data in the J1699-5 log show 11.2 nothing left to do.
5-10302     Test 10.3 - Extended Data Global Counters will not be set if there is an error in getting Extended Data. This is an issue for Test 11.1.
5-10306     Test 12.1 - Sometimes gets a 'Error: 10049: SOCKET 10049 - Cannot assign requested address'. Add socket bind delay and retry.
5-10307     For SID $1A Ext Data $92, gstResponse[EcuIdx].DTCIUMPRList should be gstResponse[EcuIdx].DTCTestResultList and MAX_DTCIUMPR_COUNT should be MAX_DTCTESTRESULT_COUNT
5-10308     Add SMAD List Count limit check.
5-10311     When there is no FFDTC data, GetEcuId ( EcuIdx ) should be GetEcuId ( EcuIdx2 ).  Also improve information logged when there is no FFDTC data.
5-10314     $F8A0 should not be included in the $F885-$F8AE support requirement check
