Using the “Open in DIAdem” Feature in SystemLink Enterprise

Updated Jun 10, 2026

Reported In

Software

  • DIAdem
  • SystemLink Enterprise
  • DIAdem SystemLink Toolkit

Issue Details

I see the "Open in DIAdem" option in the latest version of SystemLink Enterprise (SLE). How do I use this feature, and are there any known caveats or limitations?

Solution

Starting with the May 2026 SystemLink Enterprise release, the "Open in DIAdem" button is available in the Files section , allowing you to directly open files in DIAdem.
 
 

To use this feature, ensure the following software are installed on the local machine:

 
When a file is selected and "Open in DIAdem" is clicked, the file is downloaded locally to %LocalAppData%\National Instruments\DIAdem\CachedFiles and automatically opened in DIAdem.
 

 Note:

  • Users should manage this folder as the files are not automatically deleted.
  • The existing files may be overwritten without confirmation.

Additional Information

Caveats

  • DIAdem Instance Behavior
    • Each file is opened in a new DIAdem instance.
  • DIAdem Version Selection
    • If multiple DIAdem versions are installed, the latest version is used.
  • Data Portal Behavior
    • For performance reasons, files are registered in DIAdem's Data Portal.
    • Regsistered channels are read-only.
    • To edit, channels must be expanded.
  • Unsupported File Types
    • The application will download and launch DIAdem for all file types.
    • Unsupported formats or missing DataPlugins will result in standard DIAdem warnings.
  • Referenced files
    • All referenced files (for example, .index files for TDMS) must be present locally.
    • You can open referenced files using the "Open in DIAdem" before opening the main file, or manually download the referenced files into the CachedFiles folder.
  • Event Logging
    • Errors and warnings are logged in the Windows Event Viewer under Windows Logs >> Application, with Source as DIAdem SystemLink Toolkit.
  • File Name Conflicts
    • If a file cannot be overwritten in the downloaded location, a new file is created with a GUID appended to the filename.
  • Path length limitations
    • Files exceeding OS path or filename limits (depending on Long Paths configuration) will not be saved.
  • Token expiration
    • Large files or slow downloads may fail with the following error when the download token expires.

The download request failed: The response ended prematurely. (ResponseEnded) for URI

    • Workarounds:
      • Download the file manually, or
      • Increase the SystemLink token timeout.
  • Connection Loss Behavior
    • If the internet connection is lost during download, the application may become unresponsive. Closing the dialog typically resolves the issue.

Other Support Options

Ask the NI Community

Collaborate with other users in our discussion forums



Request Support from an Engineer

A valid service agreement or active software subscription may be required, and support options vary by country.