       Release Notes for Version 04.11.01 of the J1699-5 software




This release includes the requirements of version 4.11 of the J1699-5 document,
with the exceptions identified in the Work Status spreadsheet. 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:
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.11.01 adds the following features:
Issue #     Description
3-1117 		Test 10.2.2 - Make an exception for PID $01 to not test Values.
5-10021		Test 11.1, 11.2 & 11.7 - Support SMAD (INF $93) in Mfg. Specific Drive Cycle.
5-10205		Test 10.10, 10.15, 11.12 - Evaluate SMAD data.
5-10265		DTC tests should FAIL if DTC format identifier != 4.
5-10287		Test 12.7 - Update F886, F887, F888, F889, F88A, F88B, F88C, F88D, F88F, F898 to not FAIL/WARN if recent 0.
5-10288		Test 12.7 - Update F890 to not FAIL/WARN if 0.
5-10289		Test 12.7 - Update F896 to not FAIL/WARN if 0.
5-10291		Test 12.7 - Update F8AD to not FAIL/WARN if 0.
5-10292		Test 12.7 - F4D6 values can be either zero or non-zero in test 12.6.
5-10331		Test 5.6, 5.10, 10.6 Update DIDs $F502, $F503, $F504, $F505
5-10333		Test 5.16 - Update Evaluation Criteria for $F877.
5-10340		Test 10.15 - Need to Test Results line to log file (it is a User action, which will always PASS).
5-10347		Expand Network Message logging to support large messsage… maybe up to 4K.
5-10363		Print currently requested DTC IUMPR and SMAD to indicate progress in Test 11.2.


Version 04.11.01 fixes the following issues:
Issue #     Description
5-10320		Test 12.8 DoIP - DoIP reconnect not working, DHCP UDP Socket bind  gives Error: 10049: SOCKET 10049 - Cannot assign requested address.  Increase default bind delay.
5-10329		Test 10.7 & 11.6 report the offending DTC as 'P000 00' when ECU response does not contain Test Results data in the WARNING and INFORMATION log entries.
5-10334		Test 10.10 - "WARNING: ECU 7E8 received unexpected response to SID $19 $06 DTC P0000 00 ExtData $93 (SMAD) request (Response not stored)" reported without an ECU 7E8 response.
5-10335		Test 5.7 - FAIL VerifyRIDSupportAndData() if there is no response to 31 01 E0 00 request if one or more ECUs supports EVAP Monitor (DID $F501 Data_D bit 0 == 1).
5-10337		Test 12.2 & 12.6 - Functionally clear codes for DoCAN only.
5-10339		IdentifyOBDProtocol() error message for SID $01 PID $00 incorrectly says "PID $01".
5-10348		Test 6.4 is stuck in an infinite loop.  Fix handling of variable size PIDs, fix $F4D8 erroneous zero entry, add $F5xx PIDs.
5-10352		Tests 12.8-12.11 Reconnecting to DoIP must include the $F810 DID request.
5-10354		Test 10.10 is making a Functional Addressed request for the Readiness Groups, but it must be a Physically Addressed request.  Fix naming of DTC IM Readiness variables to DTC Readiness Group.
