       Release Notes for Version 17.07.00 of the J1699-3 software


Except for the issues detailed in 'J1633-3 Work Status', this release includes the
requirements of revision 17.7 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.


Version 17.07.00 adds the following features:
Issue #     Description
1017        Support J1979DA_202104.
1086        VerifyInf63_69_6F_73Data must collect the sum of [bin2] through [bin14] and compare to [bin1] for INF $73.
1087        VerifyInf64_6A_70_74Data must collect the sum of [bin2] through [bin14] and compare to [bin1] for INF $74.
1088        VerifyInf65_6B_71_75Data must collect the sum of [bin2] through [bin14] and compare to [bin1] for INF $65, $6B, $71, $75.
1089        VerifyInf66_6C_72_76Data must collect the sum of [bin2] through [bin14] and compare to [bin1] for INF $66, $6C, $72, $76.
1090        Test 9.22 INF $18 - Remove EOE-R, EOE-L, PKE-R, and PKE-L checks for '>0' or comparisons to 5.17 data.
1092        Test 5.17 Add 'If Equipped' support for PTOERT and PTOFC in INF $42, $44, $46 (max. value indicates not supported - no WARN / no FAIL).
1093        Test 5.17 Change INF $42 EFC equal 0 from WARN for all to WARN for P/HEV and FAIL for conventional.
1094        Test 5.17 Change INF $42 IERT equal 0 from FAIL for all to FAIL for conventional.
1095        Test 5.17 Add INF $42 IEFC equal 0 with WARN for P/HEV and FAIL for conventional.
1097        Test 5.17 Change INF $46 EFC equal 0 from WARN for all to WARN for conventional.
1098        Need to log ISO 15765 baud rate selection.
1102        Update PID $1C to decode up to $3B. Specifically add Brazil OBD Phase 8 (PID 1C with value of $2F) and Brazil OBD Phase 7 with IUMPR (PID 1C with value of $2A).
1105        Test 10.3 -  why is _cgets_s is being used instead of scanf_s? Test 11.2 is using _getch?
1106        Add a "\n" after prompt in Q4, Q5, Q12 User Name, LogPrint.c (ln 287, 381).
1107        Can we make Test 11.2 key instructions into a 'Prompt'?
1118        If one ECU responds incorrectly to a Pending DTC request, flag the FAILURE and continue checking the responses from all the other ECUs .
5-10107	    $F4CB says FAIL in doc but software WARNs, but allows for 'if equipped'. S/W should FAIL on values, but not if supported.

Version 17.07.00 fixes the following issues:
Issue #     Description
1083        Test 5.6 fails for Reserved I/M readiness Data C bit 4 set and Data D bit 4 set for 'India OBD without IUMPR'.
1084        Code clean-up for OBDBr_WITH_IUMPR.
1091        Test 9.11 gives WARNING if there is no Permanent DTC set for 'China OBD with IUMPR', but it should fail.
1100        Protocol Determination - Brazil OBD without IUMPR must allow 250K CAN.
1103        The prompt for Vehicle Type says "3 Medium Duty Truck Engine Dyno Certified (< 1400 lbs GVWR)", but it should be 14000.
1104        Test 10.12 The prompt should say "(BARO > 22 in Hg)", but it currently says "(BARO < 22 in Hg)".
1112        Test 5.17 INF $1D is failing if it is not supported, but it should not.
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-10116     Test 12.7 Fails because $0A list is not correct.
5-10157     Re-entering the Dynamic Test for HD OBD when Model Year and Engine Certification Year do not match, generates a FAILURE.
5-10198     Response time for ISO 15765 messages is set to 100ms, it should be 50ms.
5-10199     NRC processing on ISO 15765 for First Frame Indications does not account for $78 extended timing.
5-10233     Tests 5.6 and 5.10 - DID $F48F fails if the value is >-100, but there is not requirement for this. The PM Sensor Value should not be evaluated.
