       Release Notes for Version 16.04.03 of the J1699-3 software


Except for the issues detailed in SourceForge, this release includes the
requirements of revision 16.4 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.04.03 fixes the following issues:
Issue #     Description
396         Allocate memory for FEOCNTR array before entering test 9.19 to prevent the application crashing.


NOTES ON CHANGES:

Issue 266 - This is the initial implementation of 239 ECU support.  Future changes to better support
            unexpected ECUs (more ECUs than entered by the user).

            NOTE: The number of maximum number of ECUs possible depends on the capabiliteis of the
                  J2534 Interface. J2534-1 limits this to 10, but some Interfaces exceed this. J2534-2
                  will allow additional ECUs, but the Task Force must decide how the user will access this.

            For 8 or less EUCs, there are no changes from previous versions of the software.

            If there are more than 8 ECUs, the PgUp and PgDn keys can be used in to view
            the previous and next set of 8 ECUs on the following screens:
              Test 9.19  (The Permanent Code Drive Cycle),
              Test 10.12 (The CARB Drive Cycle), and
              Test 11.2  (The Manufacturer Specific Drive Cycle)
