       Release Notes for Version 04.13.01 of the J1699-5 software


This release includes the requirements of version 4.13 of the J1699-5 document,
with the exceptions identified in the Work Status spreadsheet. It is intended to test vehicles in
Model Year 2025 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:
For Tests 10 and 11, only DTCIUMPR and DTCSMAD (SID $19 subfunc $1A ExtData $91 and $93) which also have IM Readiness assigned (SID $19 subfunc $56) are requested and logged.
 
During the Manufacturers Specific Drive Cycle test, the data page (screens of IM Readiness, IPT, RG IUMPR/SMAD data) can be changed by pressing Right Arrow (next higher page) and Left Arrow (next lower page).
The currently requested ECU is at the top next to Test Status and the IUMPR or SMAD Extended Data and it's place in the full list (x of xx) and number of passes through the whole list
is printed just below that. 



Version 04.13.01 adds the following features:
Issue #     Description
5-10381     Test 12.7, DID F89C-F8A1 - Is the rule that “DIDs for Motor A-E output energy should be start at A and there should be no gap” is still valid?
5-10409     Test 12.7, DIDs F89C-F8A1 - There is no directions to move the vehicle after the clear codes so there must be NO WARNING if the Recent or Lifetime values are 0.
5-10453     Requirements for NRC $78 for Clear Codes: must allow up to 5sec for positive response and only one NRC $78 per ECU. Anything else is a FAILURE.


Version 04.13.01 fixes the following issues:
Issue #     Description
5-10417     Test 10.1 DetermineOBDProtocol() works, but the Test 10.11 DetermineOBDProtocol() doesn’t. Vehicle uses 29-bit CAN IDs.
5-10430     Test 9.16 indicates "FAILURE: Unable to capture Initial OBDCOND and IGNCNT", but there was no FAILURE there… However, RequestIDSupportData() did fail, which triggered the log entry.
5-10431     Test 9.16 reports "OBDCOND incremented too late (RUNTM = 30665)", but OBDCOND incremented in time and RUNTM = 30665 is incorrect based on DID $F41F.
5-10432     Test 5.16 reports "INF $F81B CIFC-L must not be equal to CIFC-R" when they are not.
5-10433     Test 5.16 DID evaluations F885-8D, F896-97 are incorrect.
5-10434     Test 5.16 - Remove WARN (for any powertrain type) for DIDs $F81A, $F81B, and F81C if recent/lifetime values are 0 or are the same.
5-10435     There is no FAILURE if Permanent DTCs are not supported by all ECUs and ECUs that do not respond when DTCs are expected get flagged with a 'Format ID' FAILURE (rather than Permanent DTCs not supported).
5-10436     Test 5.6, 5.10, and 5.17 did not flag a DIDSupported DID that supported nothing.
5-10437     Log of Fuel Type prints "DIESELCOMPRESSED NATURAL GAS/HYDROGENOTHER" when 'Diesel' is selected.
5-10438     Test 5.16 - There is a problem with vehicle applicability: $F877-$F878 is for MDDC with US_OBD_II, HD with HD_OBD.
5-10439     Test 10.10 - The logging of $F879 indicates the value is always "$02X", which is wrong but the decimal value is correct.
5-10440     In VerifyINF98_99Data() the log call contains "$F8$02X", but it should be "$F8%02X".
5-10441     ReadDTCIUMPRData() and ReadDTCSMADData() must load and process RGID=$00.
5-10442     Test 11.2 - The correct SMAD DTC count and list is not being used.
5-10443     Test 11.2 - The 'Get next IUMPR' and 'Get next SMAD' should not request Extended Data for DTCs with RGIDs that are in the 'Ignore list'.
5-10444     Tests 11.1, 11.2, 11.5, 11.7, and 11.12 - All evaluations on IUMPR ad SMAD Extended Data also includes DTCs with RGIDs that are in the 'Ignore list'.
5-10445     Tests 11.2 - Change Results Logging on Exit.
5-10446     Tests 10.11 FAILs with "FAILURE: ECU 18DAF111  INF $F810  Data Size = 254 (Must be 1 byte!)", but log show proper response to $F810.
5-10449     Test 5.2 - Receives normal mode traffic when searching for OBD Responses in 11-bit CAN.
5-10450     Test 10.1 - In IdentifyOBDProtocol() a positive response from a Classic OBD protocol will cause SaveOBDConnectInfo() to be called.
5-10451     ProcessISO15765Msg() error message "ECU %X  reponded but not found during Determine Protocol\n" has a typo, should be "responded".
5-10456     Test 11.5 & 11.8 - No FAILURE flagged for COOL_SUP=1(YES) and COOL_RDY=1(NO).
5-10457     Test 11.6 - Test Results value comparisons to Minimum Test Value or Maximum Test Value are not working for signed ranges.
5-10458     There is no need to check for Test 6.5 in LogDTCTestResultData().
5-10460     Test 11.2 - When loging results on exit, "I/M STATUS (continued)", but "OTH" is missing in the I/M STATUS log entry 
5-10461     In RunDynamicTest11(), the calls to CheckIUMPRData() and CheckSMADData() being called with update = FALSE, so that the Test11_CurrentDisplayData elements are not being updated and that is what PrintECUData() is looking printing to the log - so they end up printing the original default values. 
5-10462     the log shows that Tests 10.10, 10.15, 11.1 - RGID is always $00 in log entry 
