       Release Notes for Version 04.08.01 of the J1699-5 software



This release includes the requirements of version 4.8 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).


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.08.01 adds the following features:
Issue #     Description
5-10095     Tests 6.4, 7.4, 8.4, 9.4 - Add Freeze Frame functionality for ICE. Test 5.11 - Remove Freeze Frame DTC check.
            PARTIAL: Requests and Receives Freeze Frame data but does not decode or evaluate
5-10114     Test 12.3 Fails because $F44A,4B is not supported. J1699-5 (V4.6) indicates that there is a discrepancy  between 1968.2 and 1968.5. The software follows the J1699-5 (V4.6).
5-10144     Test 10.13 - Add ignition cycle before SMAD request.
5-10239     Test 10.12 and 11.2 must include the FTB when writing the DTC to the log file (and on-screen) for IUMPR and SMAD.
            Also Test 11.2 - FAILURE "An OBD counter which was non-zero in test 11.7 is now zero" needs to also indicate the associated DTC and FTB
5-10243     In DID evaluations, HEV_BAT_A in DID F49A is not required for US.
5-10248     WARN for Multiple Test results; Verify Values when required.
5-10249     Test 12 - The DTC Status bit have all changed.
5-10251     Add IUMPR cycle count on-screen for Test 11.2.
5-10253     Test 9.8 Confirmed DTC Status bits have changed.
5-10254     Test 11.7 - FAILURE 'Monitor has not changed since Test 10.10' needs to also indicate the associated DTC and FTB.
5-10256     Change text "Failure Type" to "FTB" to aid in locating FAILURES in log file.  Display FTB as part of DTC with no label.
5-10263     Test 12.11 - Test logic is incorrect, it must FAIL ECUs that do not respond to a Pending DTC request and not make a Confirmed DTC request.
5-10264     Test 12.7 Add evaluation criteria for INF > $F884 (NOTE:  Functions to evaluate these INFs were coded a while ago but they were never called, therefore any changes in them are fixing problems no user would have encountere).
5-10270     Tests 6.2, 6.3, 7.2, 7.3, 8.3, 9.3 - Make the Evaluation Criteria for DTC Status Bit #5 be 'don't care'.
5-10275     Test 10.14  Move FEOCNTR check before new SMAD ignition cycle.
5-10276     Test 12.8 - change prompt text from "for only one" to "in a propulsion-related", to match document. *** PROMPT CHANGE ***
5-10277     Test 5.13 - Ext Data $19 $1A $92 requests should be physically addressed only.


Version 04.08.01 fixes the following issues:
Issue #     Description
3-1115      Test 5.17 - Valid INF $0A responses with ECU Acronyms that are less than 4 characters will not have the ECU Names logged.
5-10226     Evaluation of next unsupported DIDSupported DID is not correct for $xx00 and $xxE0.
5-10229     Test 12.7 - Failure on the DIDSupported DID evaluation generates the FAILURE message "Problems verifying PID $F4xx supported data.".
5-10231     Test 12 - Remove "MIL" checks and text.  *** PROMPT CHANGE ***
5-10238     Test 10.10 - SMAD data is being decoded as 3 bytes, when it is actually 2 bytes: MINI NUMERATOR (1 byte) and ACTIVITY RATIO (1 byte).  Remove DenomCounts also store Activity Ratio as float.
5-10240     NRC processing for UDS messages on DoIP must be consistent with ISO 15765.
5-10246     ISO 15765 message requests for SID $03, $04, and $07 produce a message with an extra byte, which is incorrect.
5-10250     Test 12 - DoIP NAK for a Diagnostic Request for $22 $F810 causes software to crash.
5-10252     Test 5.7 and 5.15 does not FAIL if EVAP supported in $F501 but $E001 not supported for SID $31.
5-10255     Re-entering the ICE Dynamic Tests, Test 11.7 fails indicating that no monitors have changed from Test 10.10.
5-10257     Test 5.6 & 5.10 - DID $F4DC is 'if Equipped', so do not FAIL if not supported.
5-10258     Test 5.7 & 5.15 reports 'SID $31 response data exceeded buffer size', S/W needs to account for RoutineInfo byte.
5-10259     Routing Activation is only being sent if bNetworkStarted == FALSE, but it should be bRoutingActivated == FALSE.
5-10260     Test 12.3 DoIP - "ECU 0 has already responded" warning, but there is no ECU 0?
5-10261     Test 12 DoIP - DoIP reconnect works sometimes: Often fails with “TCP Socket connect Error: 10048: SOCKET 10048 - Address already in use” even thou the TCP connection is closed. 
            Improve DoIP error message descriptions and add retry with closesocket.
5-10262     Test 12 DoIP - DoIP reconnect works sometimes: The script sends a Routing Activation request even thou the connection is not closed. Vehicle decides to close the TCP socket due to this.
5-10266     Test 12.3 - $F430 & $F431 DID Evaluations can fall into the Test 5.10 logic and creating an incorrect result.
            $F421,30,4D,4E support not required for ZEVs and ACC-II Credit earning PHEVs and Must be zero post code clear, if supported.
5-10267     Test 12 - DoIP NRC $78 are not extending the time for the ECU to respond.
5-10268     Fix code in RequestSID ISO 15765 NRC processing for SID $22.  "pstReqMsg->u.DID[0] >= 0xF8FF" should be "pstReqMsg->u.DID[0] <= 0xF8FF."
5-10269     Test 8.3 - "FAILURE: Verify DTC stored data unsuccessful" not followed by new line character.
            Also "j1699-5 software version in log file (%s) does not match currently running version (%s)" (and some other FAILURE/WARNING messages) missing newline.
5-10273     Test 10.10 is crashing for PHEV.
5-10274     Fix RID data display.
		    