The following items are known issues in MAX 5.3.x and System Configuration 5.3.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
| |||||
| 258540 Return | Deploying an image of a standard RSS to a cRIO may cause the FPGA target on that cRIO to disappear from MAX If an image of a cRIO controller containing the standard RSS is re-deployed to the same controller, the FPGA target on the controller may disappear from MAX. 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
| |||||
| 358877 Return | Cannot save RT PXI settings changes from Windows 8 host You cannot change hostname and address type (static/DHCP) on a PXI target when configuring on a Windows 8 system. When you click the "Save" button the following message displays: "There was a problems saving the settings to the target. make sure your hardware is powered on and that it is connected to the network." Workaround: N/A
| |||||
| 363150 Return | SysCfg API "Restart.vi" errors when passed an IP address connected via secondary NIC When calling the NiSysCfg API Restart VI with your target's IP address, the VI returns error -2147024809 (Invalid parameter). If you pass in the target's hostname instead, it reboots successfully. 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
| |||||
| 366310 Return | Set System Image Returns Error -2147220327 when deploying image created by RT VIs Workaround: Open the .zip file that was created by the RT VIs, edit the file named RTimageInfo.ini and add this line to the section named [RT Controller Image Info] and save the file and re-zip the image. Image_Pull_Impl="MXRMCFG"
| |||||
| 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
|
Document last updated on 8/30/2012