Import File Log Data from Speedgoat Target Computer

There are different approaches for importing Simulink^® Real-Time™ file log data from a Speedgoat target computer to a development computer as data in the Simulation Data Inspector or as Parquet format files. The workflows differ in how you choose to transfer the data, how you choose to access the data, whether you choose to use the Simulation Data Inspector to visualize the data, and the required licenses. For more information, see Simulink Real-Time License Requirements for Development and Test Roles.

The import file log workflows include the options and capabilities in the table.

Import File Log Options and Capabilities

Simulink Real-Time (SLRT) File Log Import Options:	Description	Parquet format files available for analysis	Requires SLRT to transfer Parquet format files	Requires SLRT to access the data
Direct File Log import into the Simulation Data Inspector using Simulink Real-Time	Import file log data directly into the Simulation Data Inspector for visualization, analysis, and export.	No	N/A	Yes
Import File Log data as Parquet format files using Simulink Real-Time	Download Parquet file log data by using built-in SLRT functions, for later analysis in MATLAB or third-party tools.	Yes	Yes	No
Import File Log data as Parquet format files using MATLAB or Third-Party Tools	Download Parquet log data using SFTP (SSH File Transfer Protocol) or third-party file transfer tools for later analysis in MATLAB or other third-party tools.	Yes	No	No
Import File Log data manually into the Simulation Data Inspector using Simulink Real-Time	Download file log data separately by using SFTP or third-party file transfer tools, for later import into the Simulation Data Inspector.	Yes	No	Yes

Direct File Log Import into the Simulation Data Inspector Using Simulink Real-Time

This approach is the most convenient option for test engineers with access to MATLAB^® and Simulink Real-Time. File log data is transferred and imported into the Simulation Data Inspector either automatically or on demand.

If a development computer is connected to the target computer, Simulink Real-Time automatically imports file log data into the Simulation Data Inspector at the end of a recording run. The AutoImportFileLog option for the start function or user interface control that starts the application (for example, Run on Target button) controls this behavior, which is enabled by default.

You can also import file logs interactively by using the Import File Log dialog box. This interface is accessible by clicking the Import File Log button, which is available in Simulink Real-Time Explorer, on the Real-Time tab in the Simulink Editor, as the ImportFileLogButton component in an App Designer app, or through the openImportDialog function.

When you use the Import to SDI button from the Import File Log dialog box, the file logs that you select directly import into the Simulation Data Inspector without retaining a copy of the corresponding Parquet format files on the development computer. The same operation is available programmatically by using the import function.

Use this workflow when:

• You want to primarily view and analyze the data in the Simulation Data Inspector.

• You are a test engineer with access to MATLAB and Simulink Real-Time on the development computer.

• You don’t need access to the underlying Parquet format files.

Import File Log Data as Parquet Format Files Using Simulink Real-Time

In R2026a and later releases, the Import File Log dialog box provides an Import to Folder button. The Import to Folder button copies the Parquet format files and related JSON files for a file log from the target computer to a selected local folder on the development computer. This operation does not load the file log data into the Simulation Data Inspector. The same operation is available programmatically by using the importToFolder function.

After File Log transfer, you can read the Parquet format file data in MATLAB by using the parquetread function or by using third-party tools that support Parquet format.

Use this workflow when:

• You are a test engineer with access to MATLAB and Simulink Real-Time on the development computer.

• You need direct access to the Parquet format files for analysis.

• You want to perform data analysis in MATLAB or other third-party tools that support Parquet format.

Import File Log Data as Parquet Format Files Using MATLAB or Third-Party Tools

If Simulink Real-Time is not available, you can transfer the Parquet format files over SFTP (SSH File Transfer Protocol) manually by using the MATLAB sftp and mget functions or by using third-party tools (for example, PuTTY or FileZilla). Then, you can process the data by using MATLAB or any analysis tool that supports Parquet file format.

Use this workflow when:

• File logs are transferred by a computer without Simulink Real-Time.

• You need direct access to the Parquet format files for analysis.

• You want to perform data analysis in MATLAB or other third-party tools that support Parquet format.

Import File Log Data Manually into the Simulation Data Inspector Using Simulink Real-Time

This approach separates the file transfer from the data import into the Simulation Data Inspector. You can transfer the file log data in over SFTP manually by using the MATLAB sftp and mget functions or by using third-party tools (for example, PuTTY or FileZilla). Then, you can use the slrealtime.fileLogImport function to import the data into the Simulation Data Inspector. This workflow does not require MATLAB for file transfer, but it does require MATLAB and Simulink Real-Time for data access.

Use this workflow when:

• File transfer and data analysis occur on different computers.

• File logs are transferred by a computer without Simulink Real-Time.

• The test engineer wants to view and analyze the data in the Simulation Data Inspector on a development computer with MATLAB and Simulink Real-Time.