The file extensions Measurement Data Format version 4 (MDF4), or in short, MF4 are used interchangeably in the context of data files. Principally MDF4 is an ASAM standard file format specifically designed for the automotive industry to handle a diverse range of data efficiently. As a compact binary format, MDF offers efficient and high-performance storage of huge amounts of measurement data.

The MDF file format allows storage of raw measurement values and corresponding conversion formulas; therefore, raw data can still be interpreted correctly and evaluated by post-processing tools, while the compressed file sizes facilitate easy sharing and collaboration.

MF4 is simply a file that follows the MDF4 standard, containing measurement data stored in accordance with the structure and conventions defined by the MDF4 format. This makes it fully compatible with software and tools that support this standard.

In the realm of data analysis and visualization, the ability to seamlessly convert various file formats into a standardized, easily accessible format is paramount. ATI’s VISION Data Analyzer (VDA) software, - part of the firm’s renowned VISION ecosystem - comprehensively supports MF4 files, plus offers a streamlined process for converting non-MDF files into the universally compatible MF4 format.

VDA easily facilitates the conversion or import of file types into the MF4 file format, enabling users to harness the power of their data without being constrained by incompatible files. This is accomplished by the ASCII Import Wizard which automatically starts when opening a TXT, CSV, or TSV file via the VDA "Open" command. The wizard initially displays data differently based on the file type. File types use different delimiters to separate fields, text, columns, etc.... The ASCII Import Wizard walks the user through setting the rows and columns to distinguish what data is the trace name, measurement units, timestamp, and recorded data points. Each step in the wizard asks for a specific row or column to be selected except for the first step of the import process.

For example, opening a 'TXT' file displays all information in the first column (below image). 

Defining a separator in the "Field Separator" drop-down separates data based on the defined separator character. The "<space>" separator is used in this example to yield an idea of how the wizard works (below image).

Files (MF4, REC, TXT, CSV, and TSV) may be extremely large and can be loaded into the VDA via multiple methods. MF4 files import directly, REC files import and convert to MF4, with TXT, CSV, and TSV files starting the ASCII Wizard in any of the following methods.

· Go to "File -> Open" and within the "Open" browser, locate and select a file.

· Double-click on a file in a browser window.

· Drag and drop a file from a browser window onto a VDA tab.

The process remains intuitive and accessible.

For VISION recorder (REC) files, VDA Software employs a sophisticated approach. Upon opening a REC file, VDA initiates a background process utilizing VISION to export the REC file into an MDF4 format. The resulting file is named according to the original REC file, ensuring seamless continuity in data management. For instance, opening a file named "Test.rec" would result in an MDF4 file named "Test-rec.mf4".

In scenarios where a related MDF file already exists for a REC file, VDA Software offers a seamless reimport process. Users are prompted for confirmation, enabling them to effortlessly overwrite existing MDF files or proceed with opening the existing MDF file, depending on their preferences.

ATI is thrilled to announce the launch of VISION 7.0, the latest iteration of its software suite. Engineered to meet the evolving needs of automotive professionals, VISION 7.0 introduces features and enhancements that improve the calibration and diagnostic experience to unprecedented levels of sophistication and efficiency.

Key Highlights of VISION 7.0:

• 64-Bit Application
• Increased addressable memory of a 64-bit architecture theoretically addresses 18.4 million terabytes (TB) of RAM, compared to the previous 32-bit system which is limited to just 4 GB. This is crucial for applications that require extensive memory, such as video editing, 3D rendering, and large databases. 

• Custom Screen Controls (CSC)
• VISION with user created CSC are linked via scripts written in languages such as C#, Python, VBScript (Excel), or MATLAB M-scripts. VISION 7.0 includes several CSC demos to inspire creativity and customization.

• GPS Location Recording and Visualizer
• Virtual location data items that can be mapped to various location sources, including Windows Location Services, GPS units, CAN GPS units, and vehicle network GPS information. Users can effortlessly map GPS coordinates post-recording and leverage the Map Visualizer with trigger and cursor markers for precise analysis.

• Improved Flash Support/Scripting
• With an updated 64-bit Flash interface, VISION 7.0 delivers seamless compatibility and enhanced performance. The software supports both 32-bit and 64-bit Seed&Key DLLs and introduces API support for controlling automated flashing, streamlining workflows, and boosting productivity.

VISION 7.0 represents a significant milestone in ATI's ongoing commitment to delivering innovative solutions that empower engineers to achieve exceptional results. With its comprehensive suite of features and unparalleled performance, VISION 7.0 sets a new standard for measurement, calibration, and diagnostics software.

Website:

https://www.accuratetechnologies.com/Products/VISIONSoftware

Datasheet:

https://www.accuratetechnologies.com/PDFs/VISION%20Software%20EN.pdf

Through ATI’s VISION ECU Calibration, Data Acquisition and Diagnostics software, an ASAP 3 host can be set up to remotely control devices for automated tests using the ASAP 3 communication protocol. This remote-control capability is advantageous for engineers who need to access specific items during acquisition.

Created by ASAM (the Association for Standardization of Automation and Measuring Systems) ASAP 3 defines an RS232 communication protocol between a test automation system and a measurement and calibration system connected to an ECU.

Several reasons drive the extensive use of ASAP 3. Primarily ASAP 3 provides a standardized protocol for communication between calibration tools and ECUs, ensuring seamless interoperability between tools and ECUs from various manufacturers.

Efficiency is crucial during the development and calibration phases of automotive electronic systems. The protocol is designed for high-speed communication, enabling faster data exchange between calibration tools and ECUs.

Flexibility makes ASAP 3 suitable for a wide range of applications in the automotive industry, supporting various automated measurement and calibration tasks such as adjusting parameters, measuring data, and flashing ECUs.

Compatibility, as a widely adopted standard, ensures high levels of interoperability between various calibration tools and ECUs from different vendors. This is particularly important in the automotive industry, where multiple suppliers frequently contribute difference components to a single development vehicle or powertrain.

ASAP 3 enhances the reliability of the calibration process. Engineers can trust that the communication between tools and ECUs follow a well-defined and tested standard, reducing the risk of errors or inconsistencies.

The benchmark of the ASAP 3 standard contributes to cost saving in the development process by minimizing the need for custom interfaces and special adaptations for each tool-ECU pair.

Now developed as ASAP 3 V3.0, the latest iteration maintains backward compatibility with previous versions (V2.0, V2.1, and V2.1.1). Notably, previous V2.1 versions lacked documentation or implementation of Diagnostics functionality. In the context of ATI’s VISION software, the ASAM ASAP 3 interface actively listens for commands transmitted by the Automation System (AuSy) through a serial link (RS232) or Ethernet port. Although Ethernet connection is not officially part of the standard, it can be utilized for test implementations.