55 Figure 1: Softing Automotive Electronics‘ OBD support throughout the entire life cycle Figure 2: The user interface in Softing DTS.monaco for SAE J1979-2/3 drive battery, i.e., the ratio of the current capacity to the nominal capacity when newly installed (in percent): Request (functional or physical addressing): 0x22 F4 B2 (0x22 =service identifier; 0xF4 B2 = data identifier) Response (positive): 0x62 F4 B2 FE Interpretation: 0xFE = 99.6 % SoH These values are crucial for warranty decisions, residual value models, and battery life assessment. Challenges for implementation OEMs and suppliers are responsible for implementing and validating the new communication rules, including standardized diagnostic addresses, request/response formats, and timing rules. Development testers and after-sales scan tools must combine “old” and “new” and support DoCAN and DoIP. Due to possible changes and country-specific differences in the legal framework, a high degree of flexibility is required in the data of such tools. SAE emphasizes that some regional regulations have not yet been finalized. In this respect, vehicles must also meet regulatory requirements in the field, and additional time must be allowed for updating the data in the test software! Compliance without re-engineering Softing Automotive Electronics offers complete OBD support, including flexible configurations and expandability in its tools, thereby supporting customers throughout the entire life cycle from the development tester Softing DTS.monaco to the After-sales tester Softing TDX . One example is the user interface in Softing DTS.monaco. With just a few clicks, the ZEV drive-related parameters (PIDs) can be retrieved. Error codes (DTCs) and InfoTypes can also be determined and displayed in a central report. The future of diagnostics in the SDV - SOVD The shift to software-defined vehicles (SDVs) means that diagnostic intelligence is moving from the tester to the vehicle. The new diagnostic standard of tomorrow is called Service-Oriented Vehicle Diagnostics (SOVD). ASAM SOVD defines three types of access: in-vehicle, proximity, and remote. This means that OBD data can also be used without local access. ZEVonUDS and SOVD complement each other: ZEVonUDS defines the data, while SOVD defines access. Together, they enable a modern diagnostic path for highly efficient monitoring of OBD-relevant data and regulatory compliance of the vehicle via the cloud. www.softing.com
RkJQdWJsaXNoZXIy MjUzMzQ=