Read software version, SW number and HW number for the request

Software version work is less about the act of reading and more about matching the correct technical base. A provider may need to know whether a dealership update changed the calibration, whether the current file was read before or after a failed flash, and whether the workshop still has the earlier version available. HW and SW numbers should be written exactly as shown by the tool, including prefixes, suffixes and calibration labels where available. Screenshots can help, but typed values in the request make comparison faster. This page is therefore about compatibility discipline: the same ECU name can hide different calibrations, market variants, emissions configurations or update levels. A structured software block gives the provider a better starting point for filecheck, correction or offer preparation.

For software-version discipline, treat identifiers like part numbers in a parts department. One suffix or calibration label can separate a safe reference from a mismatch. When several files exist for one customer vehicle, name them by date and state: before update, after update, customer supplied, current read, checked file. This prevents confusion during correction, comparison and provider communication.

For provider communication, version data should be copied exactly rather than normalized. Do not translate labels from the tool, do not remove leading zeros, and do not shorten long calibration strings. Those small details can be the difference between a useful comparison and another round of questions.