This document contains the MAX 15.0 and NI System Configuration 15.0 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 15.x and System Configuration 15.x known issues that were discovered before and since the release NI System Configuration 15.0 and 15.3. Not every issue known to NI will appear on this list; it is intended to only show the severe and common issues.
The following items are known issues in MAX 15.x and NI System Configuration 15.x KIL sorted by Date.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 113710 Return | Import/Export wizards may fail to report errors Under certain situations, Import/Export wizards may display only an error code, rather than a descriptive message. In other cases, these wizards could fail to report an error even if failure did occur. Workaround: N/A
| |||||
| 91473 Return | MAX behaves incorrectly with a disconnect ENET device in the system ENET Serial or GPIB devices added in MAX are treated as static resources. When the devices are off, MAX still attempts to connect to them. This can cause a timeout if you have a high port count. Workaround: Delete the ENET devices from MAX.
| |||||
| 217233 Return | Exporting LabVIEW RT target configuration without expanding Remote Systems Devices and Interfaces returns incorrect information If you try to export the configuration of a LabVIEW Real-Time target without expanding Remote Systems Devices and Interfaces on that target, certain items will show up incorrectly in the Export Wizard. Workaround: Expand Devices and Interfaces on the LabVIEW RT target before trying to export its configuration.
| |||||
| 225580 Return | DHCP address not assigned if target is not immediately restarted after Network Settings are saved If you change the DHCP settings of a Real-Time target running VxWorks, such as a cRIO target, and then save but do not immediately restart the target, the DHCP settings will not persist. Workaround: Restart immediately after saving.
| |||||
| 227480 Return | MAX provides no warning when the same static IP address is used on multiple targets MAX allows you to use the same static IP address on multiple LabVIEW Real-Time targets without providing any warning or error. Workaround: N/A
| |||||
| 281382 Return | Find (Systems) VI may hang if executed repeatedly on a Real-Time target Find (Systems) VI may hang if it is executed repeatedly inside a loop on a Real-Time target. Workaround: N/A
| |||||
| 294730 Return | Cannot prevent a Real-Time target from being rebooted by users that do not have reboot permissions Users that do not have reboot permissions under the Web-Based Security Configuration of a Real-Time target are still able to reboot that target. Workaround: N/A
| |||||
| 299006 Return | Duplicate entries of LabVIEW software versions may appear in MAX Certain upgrade scenarios can cause multiple entries of the same LabVIEW software version to show up under the Software tree in MAX each time the Software tree is refreshed. Workaround: N/A
| |||||
| 375447 Return | VxWorks targets crash if Gateway IP is not specified in ni-rt.ini Workaround: Add the Gateway entry manually or do a reformat without saving network settings.
| |||||
| 381557 Return | Deleted cDAQ appears in NI MAX even if it is physically removed from the network Workaround: N/A
| |||||
| 383091 Return | Installation has a long timeout when the target goes offline during deletion of files When trying to process an uninstallation request, multiple file deletions are requested if components get uninstalled. If the target goes offline during that time, it can result in a long wait. Workaround: N/A
| |||||
| 399803 Return | The Initialize Session VI fails if the username is set to Admin unless System Configuration Remote Support is installed on the target. Workaround: Leave the username blank.
| |||||
| 400589 Return | On NI Linux Real-Time targets, you cannot read the IP settings immediately after setting them using NI System Configuration API On NI Linux Real-Time targets, IP settings modified using the NI System Configuration API cannot immediately be read. Workaround: Wait a few seconds after modifying the IP settings to read the values.
| |||||
| 408978 Return | IPAddrMode values for myRIO are different for System Session and System Hardware property nodes When reading the IPAddrMode property with the System Configuration API, the System Session property node returns a different value than the System Hardware property node. Workaround: N/A
| |||||
| 429277 Return | After changing network adapter properties using the Hardware Property node, the System Configuration session is no longer valid. Workaround: Update the network adapter properties using NI Measurement & Automation Explorer.
| |||||
| 429278 Return | Closing a System Configuration session does not completely clear session information from memory. Workaround: N/A
| |||||
| 474723 Return | Setting or reading DST Enabled using the NI System Configuration API on a Linux RT target results in error -2147220364 Workaround: Use NI Measurement & Automation Explorer to set the property.
| |||||
| 531487 Return | GPIB ENET devices in MAX fail to open a configuration interface in the Microsoft Edge web browser When you attempt to configure a GPIB ENET device through the web configuration, you cannot open the browser page by the devices .local hostname. Workaround: Open the web interface configuration by the devices IP address or use another web browser to open the web interface configuration by .local hostname.
| |||||
| 534133 Return | Remote System Discovery Troubleshooting Wizard does not detect foreign LabVIEW and LabVIEW module versions The Remote System Discovery Troubleshooting Wizard released in MAX 15.0 will not successfully detect foreign LabVIEW installations on a system. The wizard incorrectly reports that no LabVIEW software is installed on the system. Workaround: There is no workaround for the issue, however the wizard can be advanced to the next page to continue troubleshooting.
| |||||
| 573183 Return | NI System Configuration returns error -2147220361 (Password supplied for the operation is invalid) about 0.2% of the time When using the Install All VI to install software on a NI Real Time target, the Install All VI will return error -2147220361 (Password supplied for the operation is invalid) about 0.2% of the time. Workaround: Restart the application using the Install All VI
| |||||
| 554232 Return | Cannot format or install NI Linux-RT targets that has been in safe mode for a few days When left in safe-mode for several days, the /var/log/messages directory on an NI Linux-RT target can grow. Workaround: Contact NI support for Safemode recovery media.
| |||||
| 552242 Return | Set System Image VI does not apply NI-Auth settings when self-imaging When imaging the cRIO-9068 target by running Set Image VI on cRIO, the user settings in the image cannot be applied to the cRIO target. Workaround: Use a remote system to apply an image or do not use non-default NI-Auth settings.
| |||||
| 554012 Return | [Mac] NI I/O Trace is not included in Mac NI System Configuration Installer NI I/O Trace is not installed by the NI System Configuration installer as on a Windows OS. Workaround: Install NI-VISA for Mac.
| |||||
| 515183 Return | Reading from a System Configuration “System Status” Property node does not return new data from the target Reading from a “System Status” property node does not pull new data from the target, but rather reads data from the session. The status property is updated when an action in the session (for example, Restart.vi) is responsible for the change in status, but not otherwise. Workaround: Reopen the session and the System Status property will be updated.
| |||||
| 571470 Return | Web Interface page is not refreshed properly after changing the time setting in MAX After changing the time zone in MAX, refreshing the WIF page cause the page load improperly. Workaround: N/A
| |||||
| 565772 Return | Cannot launch "Reset Configuration Data" utility from MAX with .NET 4.5.2 on Windows 7 x64 Pre-SP1 When .NET 4.5.2 is present on a on Windows 7 x64 Pre-SP1 system, launching Tools >> Reset Configuration Data in MAX fails to reset the configuration data. The application can be manually launched from outside of MAX. Workaround: Upgrade to System Configuration 16.0 or update to Windows 7 x64 SP1
|