       Release Notes for Version 17.09.00 of the J1699-3 software


Except for the issues detailed in 'J1633-3 Work Status', this release includes the
requirements of revision 17.9 of the J1699-3 document and is intended to
test Model Year 2025 and beyond, that are compliant with SAE J1979.



NOTES:
 - This release only supports the 0404 version of the J2534 API!
 - Slow PCs/J2534 devices may cause false vehicle failures!
 - J2534 Interfaces that do not support all of the protocols being tested will result in the vehicle failing J1699-3.
 - To avoid false failures during the CARB Drive Cycle, do NOT operate the vehicle at exactly 25 MPH (40KPH).
 - For EOBD ONLY, scanning CAN baud rates may cause ECUs to go BUS_OFF!
 - The file "J1699 User Notes.doc" is a simple User Guide to the J1699-3 software.
 
!!!!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.


Version 17.09.00 adds the following features:
Issue #     Description
1127        Test 5.6, 5.10, 10.2, 10.13 - Need to support PIDs up to $FE.
1130        Test 5.17 - Do not flag a WARNING or FAILURE for INF $42 EFC_A == 0 or IEFC_A == 0 on any powertrain type.
5-10117     Test 12.6 Fails because $F4B2 is 0, but there is no requirement to evaluate the DID content.
5-10158     Test 11.5 must also check DIDs $F431/$F44E.
5-10201     Test 5.6 - Change DID evaluation criteria (FAIL/WARN and/or Data Eval.).
5-10202     Test 5.10/10.6 - Change DID evaluation criteria (FAIL/WARN and/or Data Eval.).
5-10279     Update DID Evaluations from J1699-5 V4.10.
5-10347     Expand Network Message logging to support large messages… maybe up to 4K.
5-10423     Change "USER WARNING" text in USER_ERROR to "INSTRUCTION MISMATCH" as log entry preamble and in log error totals at end of log.  When there is an Engine State mismatch (on STOP/START vehicles ONLY), prompt "Is vehicle in Auto Stop? (Enter Yes or Quit)".
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 17.09.00 fixes the following issues:
Issue #     Description
1099        Test 5.2 When the EOBD protocol scan includes 500K and 250K CAN, vehicle communication that was found at 500K no longer communicates to get RPM.
1120        Test 5.17 - NRC $78 in response to a CVN request is flagged as a WARNING, but it should be a FAILURE.
1128        The FAILUREs/WARNINGs messages should not list PID/INF as "F4xx"/"F8xx" as it is confusing (this is a cut and paste error from J1699-5).
5-10242     Test 5.17 & 9.23 - Allow an NRC 0x78 for GHG tracking ITIDs (and Nox Binning + CVN for the ICEs).
5-10260     "ECU 0 has already responded" warning, but there is no ECU 0?
5-10319     Test 5.6 will not evaluate any DID responses if one ECU responds incorrectly.
