       Release Notes for Version 03.05.00 of the J1699-5 software


This release includes the requirements of version 3.5 of the J1699-5 document,
with the exceptions mentioned below. It is intended to test vehicles in
Model Year 2023 and beyond, that are compliant with SAE J1979-2


This is a beta test version, primarily to confirm proper communication between the application
and the vehicle and data formatting and values, but is not intended as an "official" vehicle validation.



NOTES:
 - Slow PCs/J2534 devices may cause false vehicle failures!
 - This release only supports the 0404 version of the J2534 API!


Some of the major differences from J1699-3:
	the application only attempts to connect to ISO15765 11-bit and ISO15765 29-bit protocols,
	only US vehicles and evaluations are currently implemented.


Some of the variances from version 2.6 of the J1699-5 spec:
	only J2534 04.04 is currently supported,
	physical addressing of requests is currently implemented only in Test 5,
	some tests which were in J1699-3 but not currently in J1699-5 are still run (e.g.,
            recurring protocol determination after changing key state, vehicle state checks),
	Control of System, Test or Component ($31) tests are not currently implemented (noted in the log file as "NOT CURRENTLY IMPLEMENTED")


Version 03.05.00 adds the following features:
Issue #     Description
3-1067      Remove greater than zero check of IEFC-A in evaluation of INF $42.
3-1069      Change INF $F878 verification to only fail RPM_RATING for zero (no other range checks).
3-1070      INFs $F848-50 support required for PHEV only.
3-1071      INF $F851 support required for S/S only.
3-1072      INFs $F852-5B only warn for non-support.
3-1075      INF $F847 support required for PHEV only.
3-1077      Add support for up to Model Year 2039.
3-1079      INFs $F816-29 parameters which report max value or "not available" are not evaluated in any test step.
3-1080      Remove max INF ID check.
5-10005     Add support for Dynamic testing. This includes adding support for handling 
                SID $19 LEV $04, $06 and $1A, DTCEDRN $91 and $93, and LEV $56 responses ( DTC-
                based IUMPR, SMAD, and IM Readiness) and for In-Use                 Performance Data from INF $F882 and changes to display screen.
5-10017     Changes to treat the $F4xx and $F5xx ranges as independant (and make functions more generic).
5-10019     Don't fail for non-support of PIDs $F503 or $F505.

5-10030     Added function to evaluate INF $F82A.
5-10031     Added required support evaluate for INF $F883 and $F884.
5-10032     Added evaluation for PIDs $F4CF,D3,and D7.
5-10033     Change INF $F817 evaluation to warn if Recent and Lifetime DT values are zero OR equal,
                warn if Recent and Lifetime FC values are zero for HEV or PHEV, fail if Recent and Lifetime FC
                values are equal for CONV and S/S, and fail if Fuel Consumed Bytes not supported for EOBD.
5-10034     Change INF $F818 evaluation to fail if Recent and Lifetime values are equal or zero for CONV and S/S or warn for HEV and PHEV.
5-10035     Change INF $F819 evaluation to fail if Recent and Lifetime values are equal or zero for
                Total and Idle PSA and warn if Recent and Lifetime values are zero or Equal for City PSA.
5-10036     Change INF $F81A-1C evaluation to warn if Recent and Lifetime values are equal or zero for PHEV.
5-10037     Change INF $F81D-1F,21-2A evaluation to warn if Recent and Lifetime values are equal or zero and
                warn if it is supported but all timers are "not available".
5-10038     Change INF $F841 verification to fail if ERT and EOE Active counters are zero for CONV and S/S or
                warn if P/HEV, and warn if DT and FC Active counter are zero.
5-10039     Change INF $F842 verification to fail if Idle Active counters (except Idle FC, see 3-1067) are
                zero and warn if Engine FC, Idle FC, Urban Speed Run, and PKE counters are zero.
5-10040     Change INF $F845 verification to fail if ERT and EOE lifetime counters are zero for CONV and
                S/S or warn if P/HEV, and warn if DT and FC lifetime counter are zero.
5-10041     Change INF $F846 verification to fail if Idle run time lifetime counter are zero and
                warn if Engine FC and Idle FC, PKE, and Urban Speed Run counters are zero.
5-10042     Change INF $F847 verification to fail if Total and Idle PSA time Lifetime counters are
                zero for P/HEV and warn if Urban PSA Active and Lifetime counters are zero for P/HEV.
5-10043     Change INF $F848-50 verification to fail if Stored and Lifetime counters are zero for PHEV and warn if Active and Lifetime counters are both zero for PHEV.
5-10044     Change INF $F851-5B verification to fail if Stored and Lifetime counters are zero.
5-10045     Change INF $F861-66 verification to fail if Active data is not zero after clear codes command.
5-10046     Change INF $F867-6C verification to fail if Stored data is zero.
5-10047     Change INF $F86D-76 verification to fail if Lifetime data is zero.


Version 03.05.00 fixes the following issues:
Issue #     Description
3-1066      Fix incorrect expected number of ECU displayed in failure message for INF $6 CVN support.
3-1076      Remove reserved bit checks from SID $1 PIDs $A3-5, $A9, $AB-E, $B0 evaluations.
3-1078      Fix compliance test selection (Q10) to accept more than one digit.
5-10023     Add size checks for PID $F4A7,A8,AA,AC-B1,C3,C7,C9,CB,CF,D3,D7.
5-10024     Clean up defunct, commented-out code and change Physically/Functionally addressed coding for new standard.
5-10025     Comment out MID tests (and VerifyVehicleState tests when the rest of the test section is not performed).
5-10026     Fix the misspelling in RequestGrouPIDSupportData to RequestGroupPIDSupportData (found while working on 5-10017).
5-10027     Fix MDDC check for PID $F4A2 (was incorrectly compared to gstUserInput.eComplianceType, now compared to gstUserInput.eVehicleType).
5-10028     Fix PID display for $F505 (it used to mistakely show $F504).
5-10029     Fix formatting of printing of values in PID $F4C9 and $F4CB.
