MAX 18.5 and NI System Configuration 18.5 Known Issues
Updated Apr 2, 2020
This document contains the MAX 18.5 and NI System Configuration 18.5 known issues that were discovered before and since the previous release. 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.
This document contains the MAX 18.5 and System Configuration 18.5 known issues that were discovered before and since the release NI System Configuration 18.5. Not every issue known to NI will appear on this list; it is intended to only show the severe and common issues.
NI-VISA Trigger Bus Query Property is not supported by NI System Configuration API.
NI-VISA allowed users to query for the PXI Trigger Bus number using the instrument session handle but there is no similar functionality in the NI System Configuration API.
NI System Configuration installer does not include header files on Linux.
When installing NI System Configuration a Linux machine the System Configuration header files (i.e. nisyscfg.h) are not installed on the machine.
Workaround: Contact technical support at ni.com/support for a copy of the header file.
Initialize Session VI Returns Error -2147220598 When Run From Pharlap or VxWorks Target With Non-Default Admin Password.
When running the Initialize Session VI from the System Configuration palette on a Pharlap or VxWorks device, you will receive error -2147220598: "The username or password is incorrect" if the admin account does not have a blank password.
Workaround: Do not set a non-blank admin password, disable LabVIEW Project Access on the device and run the Initialize Session VI from a host PC, or use an NI Linux RT device if you require a non-blank admin password.
NI MAX System Settings page doesn't 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 machine.
On Linux RT devices, target discovery can cause the calling process to crash when a large number of NI discoverable devices are present on the network
When performing network device discovery on a Linux RT target, the lvrt process can occasionally crash. Examples of discovery include a call to the Initialize Session VI, or the discovery of a network cDAQ. This will only happen in situations where a large number of devices that are discoverable by NI are present on the network.
Workaround: Reduce the number of NI discoverable devices on the same network.
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.
NI IO Trace on Linux displays only the hex code for properties instead of the property name
When using NI IO 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. Note that this file may need to be requested due to CAR 609380.
When interacting with a PharLap Real-Time device using the System Configuration API, the API will hang if the system has a network adapter set to DHCP Only that does not obtain an IP address
When using a PharLap Real-Time device with System Configuration API, API calls will hang in scenarios where one of the system's Network Interfaces is set to DHCP Only mode and has not obtained an IP address. For example, this error will occur if the port is set to DHCP Only with no connected Ethernet cable.
Workaround: Set the Network Interface to use DHCP or Link Local instead of DHCP Only.