MAX 20.0 Known Issues

Overview

This document contains the MAX 20.0 known issues that were discovered before and since the release of MAX 20.0. Known issues are performance issues or technical bugs that NI has acknowledged exist within this version of the product.

 

Not every issue known to NI appears on this list; it is intended to show the most severe and common issues that you may encounter and provide workarounds when possible. Other technical issues that you may encounter could occur through normal product use or system compatibility issues. You may find more information on these issues in NI’s Product Documentation, Knowledgebase, or Community.

Bug Number

Legacy ID

Description

Details

222393 700712

NI I/O Trace on Linux Displays Only the Hex Code for Properties Instead of the Property Name

When using NI I/O Trace on a Linux operating system, only the hex code will display for certain properties and not corresponding the property name.

Workaround:

Refer to nisyscfg.h for the numeric values that correspond to each property.

Reported Version:

NI I/O Trace 18.0

Resolved Version:

NI I/O Trace Unknown

Added:

Jan 24, 2019

221851 633751

NI MAX System Settings Page Does Not Populate When All Host Network Adapters Are Disabled

On any system that either has no network adapters, or has all network adapters disabled, the Systems Settings page in NI MAX for My System does not populate.

Workaround:

Enable a network adapter on the system.

Reported Version:

MAX 17.0

Resolved Version:

MAX 17.5

Added:

May 19, 2017

221854 683930

The Install Startup VI Will Reinstall All Dependencies of the Real-Time Startup Executable Even If Those Dependencies Are Present on the Target

When using the System Configuration API Install VI to install a startup executable to a Real-Time system, all dependencies of the executable will be reinstalled to the target. This installation will happen even if those dependencies were previously installed on the target.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

System Configuration 17.0

Resolved Version:

System Configuration 18.0

Added:

May 1, 2018

222425

NI MAX Can Report an Inconsistent IP Settings Status for Network Targets If NIC Teaming Is Enabled on Windows Server

If a Windows Server system is configured to use NIC Teaming, NI MAX may report Inconsistent IP Settings for network devices even if the network adapter configuration is valid.

Workaround:

Disable NIC Teaming.

Reported Version:

System Configuration 19.0

Resolved Version:

System Configuration 19.0

Added:

Jan 10, 2020

957758

Older versions of MAX and System Configuration Runtime will not allow you to format a RIO target that was formatted in MAX 20.0.

When attempting to format a RIO target with a 20.0 system image in an older version of MAX or System Configuration Runtime, an error will display that the target is incompatible with the current version.

Workaround:

Upgrade NI System Configuration to the latest version.

Reported Version:

System Configuration 20.0

Resolved Version:

N/A

Added:

May 7, 2020

Final Time Issue Listed

Issues found in this section will not be listed in future known issues documents for this product.

 

There are currently no issues to list.

Additional Resources

Explore Support Content and Product Documentation 

 

 

Ask the NI Community

 

 

Request Support from an Engineer

 

A valid service agreement may be required, and support options vary by country

 

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).