       Release Notes for Version 16.02.02 of the J1699-3 software


Except for the issues detailed in SourceForge, this release includes the
requirements of revision 16.2 of the J1699-3 document and is intended to
test Model Year 2018 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 (40KM/H).


Version 16.02.02 adds the following features:
Issue #     Description
269         All ECUs which support IM Readiness must respond the same to Clear Codes request.
268         Do not fail EOBD vehicles which do not support AFRI and warn other vehicles until 2021.


Version 16.02.02 corrects the following bugs:
Issue #     Description
379         Ensure that Initial Response Time is based on first (or single) frame response time.
381         Updated evaluation of SID $9 INFs $13, $16-$1C.
380         increase CVN and CALID buffer size to allow for more than one value
382         Only warn OBDII and HOBD vehicle which do not have PID $65 bit 3 set.
383         Initialize InfSupportCount array to prevent failures caused by incorrect ECU count.




NOTES ON CHANGES:

Issue 259 - INFs $21-$29 data is displayed but not evaluated, pending confirmation
            of the evaluation criteria in the j1699-3 document.
