       Release Notes for Version 04.08.00 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.00 adds the following features:
Issue #     Description
5-10088 - In Test 5.16 (can be 200 sec after clear codes) a Warning/Failure for EOE-A ($F818, $F841, $F845) may need to allow for 0.  Remove INF $F841 EOE-A and $F845 EOE-L 0 check
5-10123 - Remove physically addressed Clear Codes.
5-10138 - Tests 10.6 - Add $F501 Data_D Bit 4 may be 0 or 1 for EOBD Gasoline Engines.
5-10139 - Tests 10.6 - Add $F501 Data_F Bit 6 must be 1 for Compression Ignition Engines.
5-10153 - Tests 10.10 - Change the evaluation criteria for DID $F501.
5-10167 - Test 5.10 Fails if DID $F501 Data_E Bit_5 is ready (CV_RDY), but this may become ready before the the data in Test 5.10 is evaluated.
5-10184 - Test 5.5.3 & 5.13 FAILs if an ECU report more than one result for $19 $06 DTC $92.  Change DTC Test Result structure to allow for multiple test results.
5-10193 - Test 8.3 & 9.3 Fails if PendingDTC, Test Failed This Operation Cycle, and Test Failed status are not indicated.  Add DTC State machine definitions and Update DTC Status bit checks.
5-10196 - Test 12.8 - DTC Status bit 5 and 7 are optional for ZEVs and J1699-5 should not check for these.
5-10201 - Test 5.6 - Change DID evaluation criteria (FAIL/WARN and/or Data Eval.).
5-10202 - Add $F4DC minimum support check, Update $F40D support requirements, Add $F482, $F489, $F48A, $F4DC support requirements.
5-10207 - Test 11.8 - Change evaluation criteria for DID $F501 DATA_B Bits 0-2 and DATA_E Bits 2-3. 
5-10225 - Test 12.3/12.6 - Tests are failing because DID $F501 is not supported by any ECU, but it is not required for ZEV.



Version 04.08.00 fixes the following issues:
Issue #     Description
5-10103 - Test 11.5 why are all supported I/M Readiness bits not being checked for 'complete'? Only a few are being flagged for failure.  Update evaluation of $F501 Data Bits.
5-10160 - Test 10.10 - Error message for bad IUMPR or SMAD data not logging the DTC from the Request.  Save the DTC even if the rest of the data is not there.
5-10163 - Ignore all but the first Vehicle Identification message.
5-10194 - Tests 5.7 & 5.15 Request message is incorrect and no response not flagged as error.  Fix handling of RID messages.
5-10203 - Test 5.19 - Burst test must use DIDs $F800 and $F810.
5-10204 - Test 6.1 - Replace "Let idle." with "Let idle for one minute or whatever time it takes to set a pending DTC."
5-10214 - Retry message write on socket closed by peer error.
5-10216 - Test 5.4.1 - When there is only 1 ECU and it responds correctly to the $22 $F501 Physically Addressed request, the error "FAILURE: Number of PID $F501 responses in error (2 responses, 1 to 1 expected" is generated..  Clear gNumOfECUsResp before looping RequestSID_PhysicallyAddressed_Single to correctly calculate number of responders.
5-10222 - Correct DHCP discovery process.  Allow DHCP server to be disabled and ignoring of duplicate DHCP Discover messages with the same Transaction ID or from the Tester Device. 
5-10228 - Test 12 - Change "Engine Running", "PSA On", and "PSA = TRUE (ON)" to "PSA Active". Change "Engine OFF" to "PSA Inactive".
5-10233 - Tests 5.6 and 5.10 - DID $F48F fails if the value is >-100, but there is not requirement for this.  Remove $F48F PM11 < -100 check.
5-10237 - Test 5.5 & 5.13 - The Test Results is being converted incorrectly.  Handle big-endian/little endian mismatch.
5-10244 - Test 9.16 can display zeros for IGN_CNTR and OBDCOND ($F882) because DID-Support DID $F880 may be cleared making it appear unsupported. Refresh $F8xx DID-Support DIDs.
5-10245 - Test 9.17 can falsely fail if there was a failure in Test 9.16.  Clear bSubTestFailed before test.

