To create a report, you must provide one or more measurement files. EATB reads measurement data with the following file extensions:

• DAT
• MDF 3.x, MDF 4.0, MDF 4.1, and AFF (BLF and DBC)

• TSV, CSV, TXT, and ASCII

  EATB has an auto-detection mechanism that checks the structure of these files and tries to identify the correct parameters and structure. But you can also manually define the structure in the asciiFormat.json file. An example file can be found under C:\Users\UserID\.EATB\config.

  If you want to use this option, remove the ".example" extension of the asciiFormat.json.example file. Then, make your changes and save the file. Keep the file in this directory. Otherwise, EATB is not able to detect it. If the asciiFormat.json file is used, the defined parameters (delimiter, decimal etc.) have the highest priority. EATB uses these parameters to read the values out of your files. If you do not define the structure of the used measurement file in asciiFormat.json, then EATB uses the default state so that the first column in your data is considered to be the time vector. If this is not the case, an error message appears. To avoid these error messages, it is recommended to use asciiFormat.json.

• *.zip containing files with an extension from above

  If the measurement files are zipped, then EATB unzips the folder in a temporary location. The unzipped files are processed and then deleted. The original *.zip file remains intact. In this case, the MDA path under "Report Info" is pointing to the temporary location. You can then unzip your files and edit the MDA path by entering the new path in order to be able to use the XDA export functionality later. Otherwise, MDA cannot find your measurement files.