       Release Notes for Version 02.03.00 of the J1699-5 software


This release includes the requirements of version 2.3 of the J1699-5 document
(with the exceptions mentioned below) and is intended to test Model Year 2023 and beyond.


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.3 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 (ie 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"): 
	drive cycle test (Tests 9.8-22), called out but not detailed in the spec, are implemented as in j1699-3 (only INF $F808 and $F80B are implemented for OBDCOND and INGCNTR)
	(These can be skipped by answering "No" to the prompt "Do you wish to run the CARB drive cycle portion for Permanent DTCs (Tests 9.8-9.22)?" at Test 9.7),


Files renamed since V01.04.00 j1699-5 to better fit naming conventions:
CheckMILLight.c                           changed to  CheckMIL.c
DIDSupport.c                              changed to  CheckIDSupport.c
SidRequest.c                              changed to  RequestSID.c
SidResetResponseData.c                    changed to  ResetSIDResponseData.c
SidSaveResponseData.c                     changed to  SaveSIDResponseData.c
TestToVerifyInUseCounters.c               changed to  Test10_InUseCounters.c
TestToVerifyPerformanceCounters.c         changed to  Test11_PerformanceCounters.c
TestToVerifyPermanentCodes.c              changed to  Test9_8to21_PermanentCodes.c
TestWithConfirmedDtc.c                    changed to  Test7_ConfirmedDTC.c
TestWithFaultRepaired.c                   changed to  Test8_FaultRepaired.c
TestWithNoDtc.c                           changed to  Test5_NoDTC.c
TestWithNoFaultAfter3DriveCycles.c        changed to  Test9_NoFaultsAfter3DriveCycles.c
TestWithPendingDtc.c                      changed to  Test6_PendingDTC.c
VerifyControlSupportAndData.c             changed to  VerifyTIDSupportAndData.c
VerifyDiagnosticBurstSupport.c            changed to  VerifyPIDBurstSupport.c
VerifyDiagnosticSupportAndData.c          changed to  VerifyPIDSupportAndData.c
VerifyDTCPendingData.c                    changed to  VerifyPendingDTCData.c
VerifyDTCStoredData.c                     changed to  VerifyConfirmedDTCData.c
VerifyFreezeFrameSupportAndData.c         changed to  VerifyFFSupportAndData.c
VerifyLinkActive.c                        changed to  VerifyECUCommunication.c
VerifyMonitorTestSupportAndResults.c      changed to  VerifyMIDSupportAndResults.c
VerifyPermanentCodeSupport.c              changed to  VerifyPermanentDTCData.c
VerifyVehicleInformationSupportAndData.c  changed to  VerifyINFSupportAndData.c


Files removed from j1699-5 project to consolidation related functionality to fewer files:
IsDTCPending.c functionality moved to  VerifyPendingDTCData.c
IsDTCStored.c  functionality moved to  VerifyConfirmedDTCData.c


Version 02.03.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-3.
3-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.
3-1020      China6 allows ECUs to reply both positively and negatively to Clear Codes request.
3-1027      INF $78 is required by only US medium duty and heavy duty diesel vehicles.


Version 02.03.00 fixes the following issues:
Issue #     Description
3-1024      Fix false failure for "Unsupported PID" in reverse order check of PID Support PIDs.
3-1025      Fix sections of information missing from logfile.
3-1028      Remove extra space between "****" and other text.
3-1029      Fix display of IUMPR data.
3-1030      Fix problems with use of pFEOCNTR causing application to crash.
3-1031      Fix waiting for unsupported bank completion.
3-1032      China6 allows ECUs to reply both positively and negatively to Clear Codes request when engine running.
3-1033      Change wording for Prompt Q03 to clarify VIN model year.
3-1034      Improve wording of 2022-2024 phase-in warning and failure
3-1039      Fix on-screen display of PID $A1 Byte A bits and comparison of NOXC11 and NOXC12 using TempData_float instead of TempData_long.
3-1040      Fix resolution loss in calculation of PID $85 and $96 from using TempData_long instead of TempData_float (display only, no evaluation of these PIDS).
3-1041      Change TEST 11.2 on-screen text from RESERVED to GPF for gasoline vehicles.
5-10000     INF $F810 response indicates ECU's link is active

