The following items are known issues in MAX 5.5.x and System Configuration 5.5.x Known Issues sorted by Date.
ID | Known Issue | |||||
---|---|---|---|---|---|---|
113710 Return | Import/Export wizards may fail to report errors (Only Applicable to MAX) 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 46EA9908 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. (Only Applicable to MAX) 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
| |||||
286591 Return | Accessing Remote Systems and certain Network Devices on Windows Server may cause an Internet Explorer error When trying to access Remote Systems or certain Network Devices on Windows Server OS, an Internet Explorer error will display a window explaining that the content is blocked by Internet Explorer Enhanced Security Configuration. The user will then be unable to view the System Settings and Network Settings tabs. Internet Explorer Enhanced Security Configuration is enabled by default starting with Windows Server 2003. See the following Microsoft article for more details: http://support.microsoft.com/kb/815141 Workaround: Disable Internet Explorer Enhanced Security Configuration.
| |||||
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
| |||||
359857 Return | Error Dialog when Exporting in MAX An error dialog is prompted when exporting the DAQmx nodes in MAX File >> Export Workaround: N/A
| |||||
360642 Return | "S_relFsLib_FILE_NOT_FOUND" is printed on screen during cRIO target installation via MAX After formatting the cRIO target, during the installation, MAX prints several internal error messages(S_relFsLib_FILE_NOT_FOUND) on screen. Workaround: N/A
| |||||
373614 Return |
Set System Image.vi hangs when applying image that was taken from a target that had never had the IP address set after formatting it IP_Address = USE_DHCP
| |||||
381024 Return | Property FreePhysMem doesn't work properly when executed on RT Target The FreePhysMem, or Free Physical Memory, property of the Real Time System Property Node doesn't work properly if called from the RT Target. When run, even if the property node is in a loop, it only returns the initial available memory 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.
| |||||
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
| |||||
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
| |||||
414190 Return | Error -2147467259 appears periodically when calling Find Hardware on a CompactRIO device with a large software stack Workaround: Adding a ~60 second sleep after installing software and before calling Find Hardware allows all of the other binaries to load.
| |||||
415171 Return | libnisyscfg.so.5.5.0 requires LabVIEW symbols to load on 32-bit desktop Linux There are LabVIEW symbols that are required by libnisyscfg.so.5.5.0. If those symbols are not in the process that is loading libnisyscfg.so.5.5.0, libnisyscfg.so.5.5.0 will fail to load. Workaround: N/A
| |||||
431439 Return | Installing/uninstalling software after imaging an NI Linux Real-Time target fails with error -2147220352 Imaging the NI Linux Real-Time target currently removes a file necessary for installing/uninstalling software. Workaround: Format the target and install the necessary software.
|
Document last updated on 11/04/2013