       Release Notes for Version 17.02.00 of the J1699-3 software


Except for the issues detailed in 'J1633-3 Work Status', this release includes the
requirements of revision 17.2 of the J1699-3 document and is intended to
test Model Year 2020 and beyond.



NOTES:
 - Slow PCs/J2534 devices may cause false vehicle failures!
 - For EOBD ONLY, scanning CAN baud rates may cause ECUs to go BUS_OFF!
 - This release only supports the 0404 version of the J2534 API!
 - The file "J1699 User Notes.doc" is a simple User Guide to the J1699-3 software.
 - To avoid false failures during the CARB Drive Cycle, do NOT operate the vehicle at exactly 25 MPH (40KPH).


Version 17.02.00 adds the following features:
Issue #     Description
            Update code for move to Visual Studio 2022, safer string and dynamic memory handling,
	    standardization of variable naming and coding practices, and commonization of code with j1699-5.
1020        China6 allows ECUs to reply both positively and negatively to Clear Codes request.
1013        Implement Appendix A Vehicle Configuration requirements:
            INFs $41-$47 and $50-$5B required by US gas and diesel heavy duty vehicles,
            INFs $61-77 required by US diesel heavy and medium duty vehicles,
            US vehicles which do not match these vehicle configurations but support these INFs fail,
            INF $78 is required by all US light duty and gas and diesel heavy and medium duty vehicles.
1015        Add GPF bit support to PID $01 and $41

Version 17.02.00 fixes the following issues:
Issue #     Description
1024        Fix false failure for "Unsupported PID" in reverse order check of PID Support PIDs.

