7. Data Import and File Formats

This chapter answers frequent questions about importing measurement data into UniPlot: how to enable import filters, how to solve problems with MDF/MF4, CAN/BLF, text, CSV and Excel files, which formats are supported, and how to combine, resample and export imported data.

7.1. Enabling import filters and supported formats

7.1.1. How do I enable the import filter for a file format (MF4, CAN/BLF, TDM/TDMS, IFILE, REC, ATFX)?

Most import filters are add-ins that are switched off until you enable them. If a file type is not offered in the import dialog, or a file is reported as “unknown format”, enable the matching add-in:

  1. Choose Tools > Add-In Manager.

  2. Tick the add-in for your format, for example MDF4 Import, MDF Import (e.g. VS100/INCA), CAN Import, TDM Import/Export, IFILE Import, REC DAS700 import, ATFX Import or PAK Import. The names in the list can carry a version suffix such as “(v1.2)”.

  3. Click OK and restart UniPlot.

  4. Choose File > Import Data and select the file type (or “All files”).

Enable only the add-ins you really need: every active add-in increases the UniPlot start-up time. For HBM PNRF files the vendor’s PNRF Reader Toolkit must additionally be installed (see UniPlot asks for the HBM PNRF Reader Toolkit or shows a memory access violation (c0000005) when importing PNRF files.).

See also: Tools=>Add-In Manager, File=>Import Data, Import of MDF4 Files.

7.1.2. Which file formats can UniPlot not import?

The following formats have no import filter in UniPlot:

The usual workaround is to export the data from the originating tool to a supported format such as MDF/MF4, CSV or Excel. For other formats a custom import filter can be written in UniScript (see How can I import a file format or a CSV/text layout that UniPlot does not read directly?).

See also: Importing Data.

7.1.3. How can I import a file format or a CSV/text layout that UniPlot does not read directly?

Write an import filter as a UniScript file (.ic) and copy it into the autoload folder of your user home directory. To find the folder choose Tools > More Options > Paths and Files > User Home Directory and open the autoload sub-folder. Restart UniPlot; the new file type is then offered in File > Import Data.

A custom filter is the right tool for unusual layouts, for example a header block of several lines that must be stored as global attributes, a file with channel names in a different row than expected, or a proprietary binary format. For text-based layouts the UTX format (see How can I import a CSV or text file whose header rows are in a different order, or that has a long header block?) often avoids programming altogether. The netCDF SDK and the MDF4 importer scripts in the add-in folder are good starting points.

See also: Importing Data, netCDF-SDK.

7.1.4. Can UniPlot import HDF5 or NetCDF-4 files?

There is no generic HDF5 or NetCDF-4 import filter. The add-in TransPC: Import of TPC5/TPS5 Data Files reads TPC5/TPS5 files, which are HDF5-based, but renaming another .h5 file to .tpc5 does not make it importable. UniPlot provides HDF5 UniScript functions that can be used to write a custom import script.

UniPlot’s own NC and NC2 files are not NetCDF-4 files: NC is the classic NetCDF-based format and NC2 (UPDF, UniPlot Data Format) is UniPlot-specific. The netCDF SDK documentation describes both. To use UniPlot data in Python or other tools, export the data with File > Export > NC Export… to MF4 or CSV.

See also: HDF5, netCDF-SDK, Import of TPC5/TPS5 Files.

7.1.5. Can UniPlot import Microsoft Access (.mdb) files?

Not directly. Options:

  • Open the .mdb file in Excel (allow the data connection, select the tables and load them), save as .xlsx and import the Excel file. Importing only one table is faster.

  • For many .mdb files with the same structure, write an import script that reads the tables with the ADO functions of UniScript. The query can be derived by recording the Excel macro that performs the import.

Access macros (VBA) cannot be used by UniPlot. After an Excel import UniPlot creates an .nc2 file next to the Excel file.

See also: Overview Excel Files.

7.1.6. Can UniPlot use an ARXML file instead of a DBC file for CAN data?

Yes, from R2026.3: the CAN configuration accepts DBC files and ARXML files. In earlier versions only DBC files are accepted; convert the ARXML file to DBC with an external tool.

See also: Can-Configuration, Import of CAN Files.

7.1.7. An old UniPlot version cannot read my newer measurement files. What should I do?

New file variants (for example MF4 files from recent INCA versions, compressed MF4 4.1 files, or new CAN logger formats) are only supported by newer UniPlot releases, and many import errors reported for R2018 to R2020 releases are fixed in current versions. Update UniPlot with Help > Check for Updates (button Download) and import the file again. If the file still fails, check it with an MDF validator (see A .dat/.mf4 file opens in ETAS INCA MDA but UniPlot reports “Import filter ‘_DoImportVS100File’ failed” or crashes. Why?).

See also: An MF4/MDF file cannot be imported or UniPlot shows an error. What can I check?.

7.2. MDF, DAT and MF4 files

7.2.1. MF4/MDF file imports, but channels are empty or contain -1 (or “Missing”). What should I check?

This is the most frequent MF4 problem. Check the following points one at a time and import the original file again after each change (not an already converted .nc2 file):

  1. Delayed Channel Import. Choose Tools > More Options…, select the group Data Import and Data Browser, clear the check box Delayed Channel Import and click OK. With delayed import only the channel names are created and the data is read from the source file when a channel is used. Releases before R2020.5 could fill all channels with -1 values in this mode and could not reload them (fixed in R2020.5). Without delayed import all data is loaded at import; large files then import more slowly (see What does Delayed Channel Import do, and how can I speed up the import of very large MF4/MDF files?).

  2. File name and path. Avoid German special characters (ä, ö, ü, ß) and other special characters such as % or the degree sign in the file name and in the folder path. Keep the complete path (including file name and extension) below 255 characters and leave about 10 characters reserve, because UniPlot creates the files .mf4.nc2 and .mf4.nc2.jnl next to the source file.

  3. Unicode Data Files. On the same options page try switching Unicode Data Files on or off. The option controls whether character strings of newly created data files are stored as Unicode (UTF-8) or in the ANSI encoding of the PC.

  4. Add-in and version. Make sure the MDF4 add-in is active (How do I enable the import filter for a file format (MF4, CAN/BLF, TDM/TDMS, IFILE, REC, ATFX)?) and update UniPlot to the latest release; MDF4 import fixes are listed in the release notes.

  5. The file itself. Validate it with an MDF validator and open it in another tool such as ETAS MDA (see A .dat/.mf4 file opens in ETAS INCA MDA but UniPlot reports “Import filter ‘_DoImportVS100File’ failed” or crashes. Why?).

The message Nested tree elements ignored in the log is a warning of the MDF4 import: nested channel group elements are not imported as a hierarchy. Check that all expected channels appear in the Data Browser.

See also: Data Import and Data Browser, Delayed Loading, Import of MDF4 Files.

7.2.2. What does Delayed Channel Import do, and how can I speed up the import of very large MF4/MDF files?

With Delayed Channel Import (Tools > More Options > Data Import and Data Browser) UniPlot creates only the channels at import and reads the data of each channel on demand, for example when you select it or use it in a formula. This shortens the loading time of large files dramatically (a 780 MB MF4 file that needs ten minutes without it). The option only applies to the MDF and TDM import filters.

Things to know:

  • The source file must stay unchanged in the same folder, otherwise further channels cannot be loaded later. Do not move or delete the MF4 file while the NC2 file is in use, and keep the source file when you convert a file to another format.

  • Importing only a list of selected channels is not possible. Delayed loading is the only way to speed up the import of files with tens of thousands of channels.

  • If you see empty channels, -1 values or very slow data exchange, disable the option (see MF4/MDF file imports, but channels are empty or contain -1 (or “Missing”). What should I check?).

  • To see all original samples of high-frequency data (for example 50 kHz) when zooming, disable the option so that all points are loaded at import. In addition UniPlot reduces channels that have more points than the limit data-reduce-limit (default 10 million points per channel, allowed range 2 million to 64 million). To raise it to 32 million, run these lines in the command window (View > Command Window) and load the data again (Data > Reload Data…). The first line stores the limit permanently, the second one changes it for the current session only:

    WriteProfileInt('Settings', 'data-reduce-limit', 32e6)
    _g()._data_reduce_limit = 32e6
    

See also: Delayed Loading, Data Import and Data Browser.

7.2.3. An MF4/MDF file cannot be imported or UniPlot shows an error. What can I check?

Work through this list:

  1. Look at the message (log) area of UniPlot; a failed import writes a message there. Note the exact error text.

  2. Make sure the MDF add-in is activated in Tools > Add-In Manager. If one MF4 add-in does not work, try the other MDF add-ins.

  3. Switch Delayed Channel Import and Unicode Data Files on or off as described in MF4/MDF file imports, but channels are empty or contain -1 (or “Missing”). What should I check?.

  4. Avoid special characters and very long paths in the file name.

  5. Update to the latest UniPlot version (Help > Check for Updates). Old releases cannot read newer MF4 variants, and import errors of R2018 to R2020 releases are fixed in current versions. One example: (e0000025) index out of range disappears after an update or after switching Delayed Channel Import.

  6. Check the file with an MDF validator (A .dat/.mf4 file opens in ETAS INCA MDA but UniPlot reports “Import filter ‘_DoImportVS100File’ failed” or crashes. Why?). A corrupted file leaves an empty 0 KB .nc2 file together with a .jnl file; the files stay locked until UniPlot is closed. Re-saving the recording in the measurement tool (for example with ETAS MDA as MDF 4.0) often allows the import.

  7. If a file from an older release still fails in the latest release, keep the file, the tool and version that created it and the exact message for the UniPlot support.

See also: Import of MDF4 Files, Import of MDF Files.

7.2.4. A .dat/.mf4 file opens in ETAS INCA MDA but UniPlot reports “Import filter ‘_DoImportVS100File’ failed” or crashes. Why?

UniPlot’s MDF readers follow the ASAM MDF standard strictly, whereas some other tools apply workarounds for files that do not conform. Typical causes are:

  • a corrupted file, or a file written by a recording or merge tool (for example a merged .dat file) that violates the MDF standard; an MDF validator (for example from Vector) reports errors;

  • an announced data block length that differs from the real length;

  • master (time) channels with wrong properties.

What you can do:

  • Run an MDF validator on the file. If it reports errors, re-record or repair the file with the tool that created it.

  • Convert the .dat file to MF4 (for example with ETAS MDA) and import the MF4 file.

  • Re-save the file in the source tool with the MDF standard setting.

Note that ETAS MDA may show a corrupted sample in a table but hide it in a diagram. If a signal looks different in two tools, compare the raw value in a table in both tools before assuming an import problem.

See also: Import of MDF Files, Import of MDF4 Files.

7.2.5. The import reports “Unusable master or no master signal is present for group”, or the time channel of an MF4 file is missing. What is the reason?

UniPlot needs a valid master (time) channel for every channel group. The message appears when

  • the file has a faulty master channel. According to the ASAM standard a time master channel is a channel of type master (cn_type 2) or virtual master (cn_type 3) with the synchronisation type time (cn_sync_type 1). Ask the vendor of the writing software for a corrected export;

  • the logger does not store a time channel (some loggers create it from the file creation date). Configure a time channel in the recording;

  • the file has more than 20,000 channels (see Why are channels missing after importing a large MF4/MDF file? Is there a channel limit?).

See also: Import of MDF4 Files.

7.2.6. Why are channels missing after importing a large MF4/MDF file? Is there a channel limit?

Yes. A UniPlot data file (NC2) can hold at most 20,000 channels (variables), see UniPlot Data Files and netCDF Files. Modern recordings (for example whole-bus logging) can exceed this limit; files with more channels cannot be imported completely, so channels may be missing in the Data Browser while other tools show them, or the import may fail with an error.

What you can do:

  • Reduce the number of channels at the source (export fewer than 20,000 channels).

  • Pre-filter the file with another tool and keep only the needed channels before loading it in UniPlot.

See also: UniPlot Data Files and netCDF Files.

7.2.7. Where do I find the MDF import settings for channel names, for example to remove the device suffix _ETK_1?

Choose Tools > MDF Configuration (INCA)…. The command is available when the add-in MDF Import (e.g. VS100/INCA) is active (see How do I enable the import filter for a file format (MF4, CAN/BLF, TDM/TDMS, IFILE, REC, ATFX)?). The dialog box has these options:

  • Strip Group Name from Channel Name (Gxx_)

  • Strip Device Name from Channel Name: channel names of INCA measurements can contain a device name after a backslash. Mark the option to remove the characters after the first backslash; clear it to keep them.

  • Strip CAN Id from Channel Name (_CANXX)

  • Use MDF Display Identifier as Channel Name: this option is used for the DAT import, not for the MF4 import (see MF4 files from INCA are imported with numeric channel names instead of the display names. Why?).

Import the file again after you change an option.

See also: Configuration, Import of MDF Files.

7.2.8. MF4 files from INCA are imported with numeric channel names instead of the display names. Why?

UniPlot uses the channel Name stored in the MF4 file, not the Display Name. The numeric names originate from the variable definitions in the A2L file used for the recording; the same names appear in other MDF tools. Correct the A2L file or the recording configuration and record again. For .dat files the option Use MDF Display Identifier as Channel Name in Tools > MDF Configuration (INCA)… selects the display names.

See also: Import of MDF4 Files.

7.2.9. The group name of an MF4 file is missing (no _nc_group attribute, channel names get a /groupname suffix). How can I get it?

For some MF4 files (for example from INCA or Concerto) the group comment is empty and the group name is stored only in the acquisition name field cg_tx_acq_name. From R2023.1 the MF4 importer uses cg_tx_acq_name when the group comment is empty. Update to R2023.1 or later.

See also: Import of MDF4 Files.

7.2.10. Global attributes (date/time, comment, program description) are missing after importing an MF4 or DAT file. How do I get them?

UniPlot reads the global attributes from the standard comment block of the MDF file (shown as “StandardKommentar” in INCA MDA), not from the separate Date/Time fields of the MDF header. Consequences and options:

  • If the date and time are not part of the standard comment, they are not imported. In INCA, set the option that includes date and time in the standard comment. If the comment has no date/time fields, the Date/Time attributes of the NC file indicate the creation of the NC file; if the fields exist, they indicate the measurement start.

  • A recorder user comment is split into global attributes only when it uses key: value lines. Configure the recorder to write the comment in this format.

  • DAT files get a global attribute mdfComment that fills the $mdfComment$ placeholder in templates. MF4 files have no attribute of that name: add a global attribute named mdfComment in the Data Editor (Edit button of the Data Browser, then Add Attribute…) or map the MF4 comment to it with a small import script in the autoload folder. Other attributes can be referenced as $Attribute_Name$.

  • If you need the measurement start time as an attribute, a custom import script in autoload can write it; the MDF4 header provides the start time (hd_start_time_ns) and the time zone offsets. A custom copy of a delivered script overrides the delivered version, so re-check it after every UniPlot update.

See also: Global Attributes, Import of MDF4 Files.

7.2.11. Text (string) channels of MF4 files show wrong values, or become 0.000 after MF4 export and re-import. Is this a known problem?

The MF4 import reads text (string) channels since R2013.15; the text is stored as ANSI unless Unicode Data Files is switched on (Tools > More Options > Data Import and Data Browser). If text channels show wrong characters, try switching that option and import the original file again. The MF4 export does not support text channels, so after an export and re-import they show 0.000. Export text channels to a format that stores text, for example CSV, or convert the text to numeric codes before the export. If text channels are wrong in a current release, send a sample file to support.

See also: Import of MDF4 Files.

7.2.12. Can UniPlot import MF4 array channels (several values per time step)?

Only simple arrays are supported: the MF4 import converts channel array blocks (CABlock) if the array has one dimension (since R2015.6). If an array channel imports with only one value per time step, split the array into single scalar channels (one channel per element) in the source tool before the import.

See also: Import of MDF4 Files.

7.2.13. Compressed MF4 files from INCA are imported only partially: the time axis and values stop or turn to zero or negative values.

The handling of zipped (compressed) MDF4 data was changed in R2025.1 (records that are not completely contained in a data fragment) and corrected again in R2025.3 (compatibility with transposed data). Update to R2025.3 or later. Until you can update:

  • Enable Delayed Channel Import (Tools > More Options > Data Import and Data Browser). In reported cases the problem did not occur with it; the source file must then stay in place.

  • Or re-save the file with ETAS MDA.

See also: Import of MDF4 Files.

7.2.14. UniPlot reports an unknown format for MF4 files from a CANedge logger.

CANedge loggers write unfinalized and unsorted MF4 files, which UniPlot cannot read. Open the file in the asammdf GUI and save it as a finalized MF4 file, then import it again.

See also: Import of MDF4 Files.

7.2.15. An MF4/MDF file with CAN data imports without CAN signals. What is needed?

MF4 files that only contain raw CAN frames are decoded with a DBC file: activate CAN Import and MDF4 Import in Tools > Add-In Manager, open Tools > CAN Configuration (DBC file)…, add the DBC file(s), select the messages (data frames) and import the MF4 file afterwards. If the file contains bus data, delayed loading is disabled for that file and all data is loaded. If signals are missing after an update, see BLF import shows no channels (“Files does not contain any channels”), all values are zero, or signals are missing. What should I check?.

See also: Can-Configuration, Import of CAN Files.

7.2.16. How does UniPlot choose the time axis when exporting an NC2 file to MF4?

When exporting an NC2 file to MF4 UniPlot selects the time axis as follows:

  1. If the imported MF4 has channel groups and time channels, the original time axes are reused.

  2. If there is exactly one channel with the attribute Type = Time Channel and no groups, this channel is used.

  3. If none exists, UniPlot creates a 1 Hz time channel from the number of points.

Tools such as ETAS MDA may refuse to open files when the data does not fit this structure. See How do I define the time channel of an Excel or CSV file so that MF4 export works (ETAS MDA accepts the file)? for the steps to define the time channel of an Excel/CSV import.

See also: Channel Attributes.

7.3. CAN, BLF and DBC files

7.3.1. How do I import CAN BLF or ASC log files with a DBC file?

  1. Enable the add-in CAN Import: Tools > Add-In Manager, tick it, click OK and restart UniPlot.

  2. Choose Tools > CAN Configuration (DBC file)…, click Add DBC-File…, select the DBC file, select the messages (data frames) you need and confirm with OK. The configuration is saved under a name. Since R2026.3 an ARXML file can be used instead of a DBC file.

  3. Choose File > Import Data, select the file type Vector CAN Log (*.blf; *.asc) and select one or more log files.

  4. To create a dataset versus time choose the dataset type 2D: y/t “MDF/INCA/CAN/ODS/iFile”; with this type UniPlot selects the correct time channel automatically.

The DBC configuration must be saved before the import. It is also needed for MF4 files that contain only raw CAN frames. CAN FD frames in ASCII logs are imported since R2022.4; see Does UniPlot support CAN FD, also in BLF and MF4 bus logging files?.

See also: Import of CAN Files, Can-Configuration.

7.3.2. BLF import shows no channels (“Files does not contain any channels”), all values are zero, or signals are missing. What should I check?

  • DBC matches the recording. UniPlot only adds the DBC messages that contain signals. If the DBC (for example a reduced DBC) has no signals for the frames in the BLF file, the import returns no channels. Compare with the original DBC and check the selected messages and bus numbers in the CAN configuration.

  • Add-in and configuration. The CAN add-in must be active and the DBC configuration saved before the import (How do I import CAN BLF or ASC log files with a DBC file?).

  • Version. Several CAN import problems were fixed in newer releases: the error not enough (virtual) memory when importing an MF4 file with CAN data and wrong values of unsigned 32-bit CAN signals in R2023.1, and the missing multiplexer channel of multiplexed signals in ASCII logs in R2024.3. If you use an older release, update (Help > Check for Updates).

  • File name. Special characters such as % in the file name caused errors for BLF and MF4 files. Rename the file.

  • Cut-off data. If only the first minutes of a long recording appear, check whether the DBC configuration contains several time channels: if the leading time channel has fewer points than the data channels, only that number of points is imported. Also verify the recording in another tool.

See also: Import of CAN Files, Can-Configuration.

7.3.3. Does UniPlot support CAN FD, also in BLF and MF4 bus logging files?

Only in Vector ASCII log files (.asc). The CAN add-in decodes CAN FD frames from ASCII logging files since R2022.4. Wrong time channel values, ignored classic CAN frames and frames with symbolic names were corrected in R2022.5 and R2022.6, so use a current release.

  • BLF files: only classic CAN frames are evaluated. CAN FD objects are skipped.

  • MF4 bus logging files: only classic CAN frames with up to 8 data bytes are evaluated. CAN FD, LIN, FlexRay, MOST and Ethernet frames are ignored.

If your logger or Vector tool can save the measurement as Vector ASCII (.asc), import that file with the DBC files instead. SAE J1939 (29-bit IDs) is supported in all three formats if the DBC file contains ProtocolType J1939. Note the limit of 20,000 channels per imported file (Why are channels missing after importing a large MF4/MDF file? Is there a channel limit?).

See also: Import of CAN Files, Import of MDF4 Files.

7.3.4. Loading a BLF file fails with “E0000002 Not enough (virtual) memory” or “virtual storage not enough”, or a large BLF file gives an error.

  • The error not enough (virtual) memory when importing an MF4 file that contains CAN data was fixed in R2023.1. Update to a current release.

  • Try switching Delayed Channel Import and Unicode Data Files (Tools > More Options > Data Import and Data Browser) on or off, then import again.

  • Suspect the file itself if the error occurs while reading. A very long time axis with a high start time, long CAN idle phases or corrupt (non-monotonic) time stamps can cause it.

If the problem persists, send an anonymised sample BLF and DBC file together with your UniPlot version to support.

See also: Import of CAN Files.

7.3.5. A BLF signal is displayed at a lower sample rate than it was recorded, or fast state changes are missing. How can I show the real sampling?

Use the dataset type 2D: y/t “MDF/INCA/CAN/ODS/iFile” in the Data Browser. It selects the matching time channel automatically. The spacing shown depends on the diagram type, not only on the import. Compare the signal with a table export in the source tool before you assume an import problem: missing jumps can already be missing in the recording tool.

See also: The Data Browser Window.

7.4. CSV, text and Excel files

7.4.1. In which layout must an Excel or CSV file be organised for import?

Arrange the data as a table: the channel names in the first row, optionally the units in the second row, and one column per channel with the values below. Then choose File > Import Data and select the file. In the Data Browser select the plot type (1D, 2D, 3D) and load the channels.

How the import decides:

  • UniPlot takes the first data line as the line with the most filled columns and expects captions (and units) above it. If many columns are empty in the first data lines, UniPlot may pick a later line and name the columns COL1, COL2, … Delete the first lines or fill the cells, so that the row with the most columns filled is directly below the caption and unit rows.

  • Automatic header detection needs mostly unique channel names. Make the names unique if the header row is not detected.

  • Excel has no fixed time channel; see How do I define the time channel of an Excel or CSV file so that MF4 export works (ETAS MDA accepts the file)?.

  • A column is imported as text (char) if no value in it is numeric. If at least one value is numeric, the whole channel becomes numeric (double). To keep hexadecimal values as text, add the prefix 0x to all values, or use a UTX-style import filter where the third row defines the data type. In a UniPlot table you can select hexadecimal display in the cell configuration.

  • Numbers pasted as text in Excel are not data. Use numeric cells.

See also: UTX Data File Format, Overview Excel Files, Importing Data.

7.4.2. How can I import a CSV or text file whose header rows are in a different order, or that has a long header block?

The standard text/CSV import expects the channel names in the first row and the units in the second row, and the data directly below. If the channel-name row is not detected, columns are named X, Y, X0, Y0 and so on. Options:

  • Edit the file before the import, for example delete the unwanted header line. With a data source row, move it to the first row so that the sequence is Data Source, Channel Name, Channel Unit.

  • Describe the layout in the UTX format: its header defines which row holds channel name, unit and source, and the data type. UTX can read complicated CSV and ASCII files.

  • Write a small UniScript that converts the file to UTX before the import, or a custom import filter (How can I import a file format or a CSV/text layout that UniPlot does not read directly?) that stores a header block as global attributes and uses the column names as channel names. Duplicate channel names get a numeric suffix.

  • When you re-import a CSV that you exported from an NC2 file, the units row cannot be detected. Export the NC2 file as CSV-UTX instead, or use a filter that takes line 1 = channels, line 2 = units, line 3 = data.

See also: UTX Data File Format, Importing Data.

7.4.3. UniPlot shows only one column or no data for a CSV file saved by Excel. What can I do?

The import finds the column separator by itself: semicolon, tab, comma or spaces, with a decimal point or a decimal comma. A CSV file saved by Excel with semicolons is therefore normally imported correctly with File > Import Data.

If all values still end up in one column:

  • Check that the data lines use the same separator. UniPlot detects the separator from the last lines of the file, so a different separator or extra text at the end of the file can confuse the detection.

  • Open the file in Excel, save it as .xlsx and import that file.

See also: UTX Data File Format.

7.4.4. A CSV timestamp column such as 2020-12-16T15:30:23 is imported as text instead of a date/time channel. How can I plot it on a time axis?

UniPlot recognises date/time strings in UTC ISO 8601 format, so a time stamp without a trailing Z is imported as character data. Options:

  • Best: write the time stamps with a trailing Z, for example 2020-12-16T15:30:23Z. Other date formats are also supported; see DT_ParseDateTime.

  • If you cannot change the data, use a formula that appends Z to the text channel and converts it with DT_ParseDateTime into a number (a UniPlot date/time number counts days since 30 December 1899). Copy the formula file into your user formula folder, choose Tools > Update Formula List, import the file, press F9 in the Data Browser to update the formulas and drag the new channel to the x-axis. For local time instead of UTC, adapt the offset in the formula.

There is no import option to define a custom date format. If a time channel has the format dd:hh:mm:ss:000 (colon before the milliseconds), it is read as a string; write the milliseconds after a decimal separator (HH:MM:SS.mmm). Text files without a time channel get a default time step of 1 s.

See also: DT_ParseDateTime, UTX Data File Format.

7.4.5. CSV import cuts channel names that end with array brackets such as [4], and takes the wrong unit.

The importer reads name and unit from the same cell if the unit is in square brackets, and takes the first bracket pair as the unit. A name such as Channel_Array[4] [-] therefore yields the unit 4. Provide names and units in separate rows, or remove the brackets of the array size, so that only one bracket pair (the unit) remains. To split names and units in a channel list ChannelName[unit], enable Tools > More Options > Data Import and Data Browser > Split Channelname in Name and Unit before importing.

See also: UTX Data File Format.

7.4.6. Can I import all sheets of an Excel workbook in one step?

No. Import each sheet separately with File > Import Data. A script using the Excel functions (excel_get_sheetnames) can automate the import of all sheets.

See also: Overview Excel Files, File=>Import Data.

7.4.7. An Excel (.xlsx) file cannot be imported although Excel opens it (error such as rs_biff, “Not supported format”, or 0 rows / 0 columns).

Some .xlsx files have a slightly different internal structure than files written by Excel, for example files generated by script libraries (such as openpyxl) or exported by measurement software. UniPlot cannot read them or reads them as empty. Open the file in Microsoft Excel, choose Save As and save it as a new .xlsx file, then import the new file. If your files are generated by a script, check the library and version so that the workbook has a standard structure. If the import still fails, send a sample file to support.

Related causes:

  • The import of an Excel file that is replaced or added in the data exchange can fail after an update; copying the data into a fresh Excel file helps, and a sample file lets support analyse the problem.

  • A cell containing a very long text (for example one that begins and ends with ###) can cause Exception in Converter: not enough virtual memory. Try switching Unicode Data Files off (Tools > More Options > Data Import and Data Browser) and import the original file again. If the error persists, send a sample file to support.

  • COL1, COL2 as channel names: see In which layout must an Excel or CSV file be organised for import?.

See also: Overview Excel Files.

7.4.8. After a data change UniPlot plots the wrong columns of an Excel file on the X/Y axes. What is wrong?

A channel (column) name containing a TAB character, for example a trailing tab after the name, breaks the column mapping, because the tab is used as the separator and cannot be part of a channel name. Remove the tab from the header cell and import again; check where the tab is added when the file is generated.

See also: UTX Data File Format.

7.4.9. Importing a text/CSV file fails with “Import Filter_DoImportTextFile_Failed”, “Insufficient virtual memory” or “Exception in Converter”. What can I do?

If the problem persists, send the file and your UniPlot version to support.

See also: UTX Data File Format.

7.4.10. How do I import a whitespace-separated text file when header names contain spaces?

Spaces inside names make the importer split a name into several columns. Prepare the file before the import with a script: read the header, replace the spaces inside the channel names with underscores and then import the data. Lines before the header (for example a descriptive block) must be removed or skipped; otherwise the file cannot be imported.

See also: UTX Data File Format.

7.4.11. Imported values differ slightly (for example 8.3 becomes 8.3000001, or a number is off by 1). Why?

The default data type for 1D and 2D datasets is float (4 bytes), which cannot represent some numbers exactly. Choose double (8 bytes) under Tools > Options (setting “Data Type for 1D-, 2D-Datasets”), then import the file again. Double precision makes loading somewhat slower. Channel data is limited to 64-bit double precision, so integers with more than about 15 significant digits cannot be represented exactly.

See also: Tools=>Options.

7.5. Other import formats

7.5.1. How do I import ATFX files, and what do I do if the import fails?

Only ATFX (the XML variant of ATF) is supported. Enable the ATFX import add-in in Tools > Add-In Manager and restart UniPlot. Since R2023.2 the import loads all measurements of a file at once and groups the channels by measurement name (channel attribute _nc_group). R2025.0 made the import more tolerant to variations of the format. The settings are in Tools > ATFX Configuration.

If the import raises an error or reports that the plug-in cannot be loaded, update UniPlot to the latest release and send the file to support.

See also: Import of ATFX Files.

7.5.2. How do I import PAK measurements (Müller-BBM VibroAkustik Systeme)?

New in R2026.6

A PAK measurement is a folder with the header file theader.xml and the binary throughput files (sub folder PAK_Throughput0). Since R2026.6 the add-in PAK Import reads these folders:

  1. Enable the add-in in Tools > Add-In Manager and restart UniPlot.

  2. Choose File > Import Data, file type PAK Measurement (theader.xml).

  3. Open the measurement folder and select theader.xml.

The NC file gets the name of the folder. The time data of all channels (scaled to physical values) and the rotational speed computed from the tacho pulse times are imported; the channels are grouped by data group. Values recorded before the measurement start (pretrigger) get negative times and can be switched off in Tools > PAK Configuration, where the speed can also be averaged over several pulses. Not imported are PAK’s own analysis results, that is the spectra, levels and order analyses PAK computed during the measurement (file PAK_Data), and the reduced overview data PAK uses for its display (groups level, compressed, integrity). Compute spectra from the imported time data in UniPlot, or export the results from PAK. Keep the complete folder together: the header references the binary files by relative path.

See also: Import of PAK Measurements.

7.5.3. How do I import TDM/TDMS files (for example from DIAdem or LabVIEW)?

  1. Enable TDM import/export in Tools > Add-In Manager and restart UniPlot.

  2. In File > Import Data select the file type TDM File (*.tdm; *.tdms) in the file type filter before choosing the file. If the Calibration Data import add-in is also active, releases before R2026.1 could mistake a TDM/TDMS file for a DCM file (corrected in R2026.1); selecting the TDM filter forces the correct importer. Alternatively deactivate the Calibration Data import add-in.

  3. For files with a separate header and data file (.tdm plus .tdx) both files must be in the same folder with their original names.

TOPexpert cannot read TDM/TDMS files; use UniPlot to import them and export with File > Export > NC Export… to MF4 or DAT. Some TDMS files could not be loaded before R2023.0 (updated National Instruments TDM library); use a current release.

See also: Import/Export of TDM Files.

7.5.4. A MATLAB .mat file cannot be imported or its channels are wrong. What can I do?

UniPlot imports MATLAB MAT files, including the HDF5-based MATLAB 7.3 format (since R2015.9). Some MATLAB data types cannot be read:

  • MATLAB table variables cannot be read and are reported with a misleading “corrupted file” error. Extract the table columns into separate vectors and save these:

    vars = Newdata.Properties.VariableNames;
    for i = 1:numel(vars)
      assignin('base', vars{i}, Newdata.(vars{i}));
    end
    

    (This is MATLAB code.) Timetable data is not supported either.

  • Elements with a single value are imported as a global attribute and additionally as a channel with one data point (since R2020.1), so formulas that use them as a vector fail. Save them as vectors of the full length.

  • Text with umlauts: see After an update imported units show “?” instead of the degree sign, or umlauts in text channels are wrong. Why?.

  • The record filter check box could be disabled for MATLAB files in HDF5 format; this was fixed in R2021.1.

See also: Import of MATLAB Data Files.

7.5.5. How do I import ERG result files (CATS), and why does the import fail?

ERG files consist of system data, header values and measure data. A dedicated ERG import add-in (ERG file import) exists since R2023.1. The import expects a fixed structure: a blank line between the “System data” and “Head values” sections and a blank line between “Head values” and “Measure files”. A file that misses one of these blank lines fails. Text values in numeric columns cannot be converted.

If you have your own ERG import filter, deactivate the ERG file import add-in in the Add-In Manager so that your filter is used. For global headers to be imported from text files the file must follow the UTX data file format.

See also: Import of ERG files, UTX Data File Format.

7.5.6. How do I import indicating (IFILE / INDI) files, and what if the import fails?

  1. Enable IFILE Import in Tools > Add-In Manager and restart UniPlot. If “unknown format” appears, the add-in is not active.

  2. Import the file again.

Further hints:

  • Some indicating systems store the measurement as a compressed archive with a numeric extension (for example .001). Extract the archive first (for example with 7-Zip), then import the extracted files. Extracted files of about 1 KB contain no data.

  • Time-based IFILE data files are supported since R2022.6. An import error for files with data of type eType = 20 was fixed in R2023.4, and R2025.0 improved the X axis and the storage of the cycle information. Update to a current release.

  • A converted NC2 file of 0 KB means the conversion failed: check that the source file is not locked or still being written and that the target folder is writable.

  • NC2 files are not compressed and are larger than the source file; compress them with an external tool if needed.

See also: Import of IFILE Data Files.

7.5.7. KiBox files (.open or I-file) import with “missing” channels or zero values. What should I check?

Check the file first: a .open archive whose IndicationResultData is empty is a broken file. Make sure the KiBox import add-in is active in the Add-In Manager. In the Data Browser use Edit and the shortcut menu command More Functions > Load delayed Channels to test. For files measured on another PC check the decimal separator settings (point or comma) of that PC. A crash when creating a PV diagram with a specified range was fixed in R2023.4.

See also: Import of KiBox Files.

7.5.8. Can UniPlot import Dewesoft .d7d/.dxd files? Why is a channel missing after the import?

Yes, with the add-in DEWESoft D7D Import (beta). Enable the add-in, restart UniPlot and select the file type DEWESoft D7D File (*.d7d;*.dxd) in File > Import Data. UniPlot reads the files with the official Dewesoft data reader library (see the add-in page for the license information).

  • Regular and reduced data are supported (reduced data since R2022.6). CAN and binary data exported by Dewesoft are not.

  • For each reduced channel four channels are created (average, minimum, maximum and rms). Channels that exist only as reduced data in the file therefore contain only these values.

  • One time channel is created per time group (time1, time2, …). To plot channels with different sampling rates, use the dataset type 2D: y/t “MDF…”.

  • A channel is missing (for example the crank angle): channels that are marked as “not stored” in the Dewesoft setup contain no data in the file. The reader library cannot return them, so they do not appear in UniPlot. Check in Dewesoft that the channel is stored.

  • The cycle counter has one value more than the per-cycle results (IMEP, MFB, …): a counter such as CycleCnt starts at 0 in the file. UniPlot keeps the values as stored by Dewesoft.

  • A corrupt .d7d file cannot be read.

See also: Import of D7D files.

7.5.9. UniPlot asks for the HBM PNRF Reader Toolkit or shows a memory access violation (c0000005) when importing PNRF files.

The PNRF Reader Toolkit (HBM/HBK) is required only for .pnrf files. Install it from the vendor (HBM/HBK) and restart UniPlot. A newer build of version 7.50 was reported to remove the memory access violation. For other formats keep the PNRF Import add-in disabled. If a PNRF file still fails with the toolkit installed, update UniPlot and, if possible, export the data from the original software to MF4.

See also: Import of PNRF Data Files.

7.5.10. How do I import .rec (DAS700), MORPHEE, Stiegele MDF, CAS or X-One files?

  • .rec files (DAS700): available from UniPlot R2022.6. Enable REC DAS700 import in Tools > Add-In Manager (see Import of REC DAS 700 files).

  • MORPHEE: the unit characters of MORPHEE files can look different on PCs with other regional settings.

  • Stiegele MDF (description file .mdf plus separate .dta data file): both files are needed; see Import of MDF-Stiegele Files.

  • CAS/FEVIS channels: helper channels such as cylinder volume or crank angle get an index depending on the recording configuration. Since R2023.4 the CAS add-in has a syntax option (Tools > CAS Configuration) that improves the data exchange in templates, see Import of CAS files.

See also: Import of MORPHEE files.

7.6. Encoding, channel names and units

7.6.1. After an update imported units show “?” instead of the degree sign, or umlauts in text channels are wrong. Why?

Since R2024.3 the UniScript functions fopen and text_file_write default to UTF-8 (older versions used ANSI), which affects import scripts. Text data files saved in ANSI encoding can therefore show special characters such as the degree sign or superscripts incorrectly. Options:

  • Save the data file as UTF-8.

  • If your own import script reads the file, specify the encoding explicitly (for example ANSI) when opening it with fopen or another UniScript text file function.

  • Check Tools > More Options > Data Import and Data Browser > Unicode Data Files. For umlauts in text channels enable Unicode Data Files and Allow Special chars in channel names and import the original file again. For text channels of MAT files and some MF4 files it can help to disable Unicode Data Files instead. If the option makes no difference, a special cell value (see An Excel (.xlsx) file cannot be imported although Excel opens it (error such as rs_biff, “Not supported format”, or 0 rows / 0 columns).) may be the cause.

The options apply to newly created data files, so import the original file again after every change.

See also: Unicode Strings, Data Import and Data Browser.

7.6.2. Which options in More Options control how channel names and text are imported?

Choose Tools > More Options and select the group Data Import and Data Browser. These options affect the import:

The options apply to newly imported files, so import the original file again after a change. If umlauts in text channels of MAT files are displayed wrongly, try switching Unicode Data Files off.

See also: Data Import and Data Browser, After an update imported units show “?” instead of the degree sign, or umlauts in text channels are wrong. Why?.

7.6.3. Can UniPlot use Chinese or other Unicode characters in channel names, or in file names?

Channel (standard) names must follow the NC file conventions: they begin with a letter or underscore, followed by letters, digits or underscores; blanks are not allowed, special characters are replaced by underscores and case is significant. Unicode text such as Chinese is supported in many other places, for example the axis label from the long_name attribute. Import the text as an additional attribute (for example Comment) and show it in diagrams with field functions:

@f{ncattfromdata(Data1, title, use_y_channel)}
@f{ncattfromdata(Data1, Comment, use_y_channel)}
@f{ncattfromdata(Data1, units, use_y_channel)}

Excel files whose file name contains Chinese characters may not be recognised by IsFileExcel; enable the Windows setting Region > Administrative > Change system locale > Beta: Use Unicode UTF-8 for worldwide language support and restart Windows. Maximum length of a channel, attribute or dimension name: 128 characters.

See also: Properties of UniPlot data files (nc2), UniPlot Data Files and netCDF Files.

7.6.4. How can I remove the unit from channel names (for example _rpm_) or keep the name and unit separate?

Enable Tools > More Options > Data Import and Data Browser > Split Channelname in Name and Unit (format ChannelName[unit]) before importing the file, then export to MF4.

See also: Data Import and Data Browser.

7.6.5. How do I set up the Norm-Name table so that one template works with data files from different sources?

  • The scheme names used in the Norm-Name table must be real names, not plain numbers. Rename schemes such as 1 and 2 to n1 and n2 and create the Norm-Name tables again.

  • For every project or scheme define the channel names in the Norm-Name table (one table sheet per scheme).

  • The data files must contain the header with the scheme entry so that the import knows which scheme applies.

  • The Norm-Name add-in renames channel and header names; since R2026.4 it can also convert channels to the specified unit. In your own import scripts units can be converted with nc_convert_units (it uses a separate Excel unit table).

Templates then work with data from both projects.

See also: Norm-Names, nc_convert_units.

7.7. Combining, resampling, synchronising and exporting data

7.7.1. How can I merge several data files into one?

Import the first file, open it in the Data Browser with Edit, right-click a channel and choose Add Data Records from File…, select the next file and confirm. The data is concatenated and the time continues. Files with different time channels or sampling rates can be merged too. Scripts can use NC_AddFiles.

Problems occur when a channel has a different data type in the second file (for example integer in the first and characters in the second file). In this case use matching data types. When merging with NC_AddFiles delete leftover time channels (for example time_22) before exporting, and beware of files with the same time channel name but different sampling rates. To show merged continuous data in hours, change the unit of the time channel.

If you add data with the option “sort by”, select a real time channel or counter that increases monotonically; with a date channel (for example Datum) channels such as Datum0 and Datum00 are created. Merging corrupted DAT/MDF files can crash UniPlot: validate the files first (A .dat/.mf4 file opens in ETAS INCA MDA but UniPlot reports “Import filter ‘_DoImportVS100File’ failed” or crashes. Why?).

See also: NC_AddFiles, The Data Browser Window.

7.7.2. How can I resample signals with different time bases to a common sample rate and export them to Excel or CSV?

Open the NC file in the Data Browser, right-click and choose More Functions > Channel Interpolation…, and select the sampling frequency. The data is interpolated linearly without filtering. For scripts use NC_Interpolation and NC_TimeInterpolation. Other fill strategies, for example holding the last value, must be scripted. Afterwards export the new file with File > Export > NC Export… to CSV or Excel.

Since R2022.4 the interpolation keeps the _nc_enum value-to-text mapping of the channels and supports string channels. If the interpolation takes very long, update to the latest release.

See also: Browser=>Interpolation, NC_Interpolation.

7.7.3. The Synchronize Data Files tool gives wrong results. What can I check?

  • The synchronisation channel must exist in both files with the same name (a renamed channel gives a wrong preview and a wrong offset), and both files must be complete.

  • The algorithm cannot determine the correct delay for every file; if it returns 0 s, enter the delay manually and zoom into the curves with X-min/X-max in the synchronisation window.

  • To see the synchronised result enable Plot synchronized curves.

  • Synchronising an Excel file with too many columns creates an empty file; reduce the number of columns.

See also: File=>More File Functions=>Synchronize Data Files, NC_SynchronizeTime.

7.7.4. How do I define the time channel of an Excel or CSV file so that MF4 export works (ETAS MDA accepts the file)?

Excel files have no fixed time channel, so after the import UniPlot does not know which column is the time. Set it before exporting:

  1. Import the file with File > Import Data and open the Data Browser.

  2. Switch to Edit, right-click the time channel and choose Add attribute…. Add the attribute Type with the value Time Channel.

  3. For several time bases, MDF needs channel groups. Add the attribute _nc_group (data type char) with a group name (for example MF4) to the time channel and to the channels that belong to it. Make sure that the global attribute _nc_hasgroups equals 1.

  4. Export the NC2 file (not an already exported MF4 file) with File > Export > NC Export… and choose MF4 as file type.

See also: How does UniPlot choose the time axis when exporting an NC2 file to MF4?, Channel Attributes.

7.7.5. How do I export imported data to another format (MF4, CSV, DAT, MATLAB) and what are the limits?

Choose File > Export > NC Export…, select the NC2 file, choose the target format as File type (the command writes the selected type, not only NC files), pick the channels and confirm. To convert an old NC file to the current format choose “netCDF format compressed”, which saves it as NC2.

MF4 (.mf4): you only need the add-in MDF4 Import (beta, see Import of MDF4 Files). It reads and writes MDF4 files, so no separate export add-in is needed. Enable it in Tools > Add-In Manager (see Tools=>Add-In Manager), restart UniPlot and choose MF4 as File type. MF4 export is available since R2016.6.

Known behaviour:

  • Only the selected channels are exported; the matching time channels are exported automatically in current versions.

  • MF4 export is basic: channels are stored as float/double without compression, so exported files can be much larger than the original. Global attributes are only partly written to MF4.

  • Export to BLF is not possible.

  • MAT files exported by older versions could not be read by newer MATLAB versions. Exporting several files at once without selecting channels takes the variable selection from the first file only; variables with special characters in their names (for example a dot) may be omitted. Rename the variables or use a script for batch export.

  • CSV export writes values with %.15g. Excel may reformat numbers when it opens the CSV; use the Excel function Data > Text to Columns and format the column as text.

  • Exports to netCDF (.nc) could write a corrupt result in releases before R2021.5 (fixed in R2021.5).

  • For crashes or empty channels in MF4 export, switch off Delayed Channel Import before importing.

  • Export templates are stored in the folder ini_list\dataexport of the user directory.

See also: File=>Export Data, NC_ExportData.

7.7.6. How can I export only the filtered data of a measurement file?

There is no direct switch. Delete the filtered-out points from the NC2 file that UniPlot created and export that file:

  1. Import the file (File > Import Data) and open it in the Data Browser.

  2. Enable the filter checkbox and enter the filter; only matching points are shown.

  3. Right-click and choose More functions > Mark filtered values as deleted (red).

  4. Right-click and choose Delete marked rows/columns permanently and confirm. Only the NC2 file is changed; the original file stays untouched.

  5. Remove the filter and export with File > Export > NC Export….

Alternatively store the filtered data in a new channel and export only that channel. To split a very large CSV or measurement file into smaller NC2 files, filter on the test time, classify and use the split/export function; when you reload split NC2 files UniPlot may add the original file name and filter info to the file name.

See also: The Data Browser Window.

7.7.7. What are NC and NC2 files, where are they stored, and can they be opened by several users?

UniPlot converts imported data files (MDF, Excel, CSV, …) into NC2 files for fast access. NC2 is UniPlot’s own netCDF-based format (UPDF); since 2012 NC2 is the official format, the older NC format is no longer used. No other end-user program is known that opens NC2; the netCDF SDK documentation describes how to read and write it. To hand data over to other tools, export it to MDF, CSV or ASCII.

  • Location: the NC2 file is created next to the source file unless Tools > More Options > Data Import and Data Browser > Data File Directory names a folder (for example a local temp folder). The folder must exist. You can delete NC2 files when they are no longer needed.

  • Network drives: if UniPlot cannot write to the source folder, the import fails. Set a writeable data file directory, or run UniPlot with sufficient rights.

  • Several users: NC and NC2 files can be opened by several users or UniPlot instances at the same time. IPZ and IPW documents cannot, because one user could overwrite the changes of the other.

  • Size: NC2 files are uncompressed and are larger than the source.

See also: Properties of UniPlot data files (nc2), netCDF-SDK, Data Import and Data Browser.

id-1183527