Archived: MAX 4.8.x and System Configuration 1.2.x Known Issues

NI does not actively maintain this document.

This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.

Panoramica

This document has been archived and is no longer updated by National Instruments.

This document contains the Measurement & Automation Explorer (MAX) 4.8.x and System Configuration 1.2.x known issues that were discovered before and since the release of MAX 4.8.x and System Configuration 1.2.x. Not every issue known to NI will appear on this list; it is intended to only show the severe and more common issues that can be encountered.

Each Issue appears as a row in the table and includes these fields:
  • Issue ID
  • Legacy ID - The issue's legacy ID from NI's deprecated bug reporting database (if applicable)
  • Issue Title
  • Problem Description
  • Workaround
  • Reported Version - the earliest version of MAX the issue was reported in
  • Resolved Version - version the issue was resolved or was no longer applicable
  • Date Added - the date the issue was added to the document(not reported date)

Known Issues by Date

The following items are known issues in MAX 4.8.x and System Configuration 1.2.x sorted by Date.

113710 Import/Export wizards may fail to report errors
174178 MAX crashes when deleting multiple remote targets
91473 46EA9908 MAX behaves incorrectly with a disconnect ENET device in the system
217233 Exporting LabVIEW RT target configuration without expanding Remote Systems Devices and Interfaces returns incorrect information
225580 DHCP address not assigned if target is not immediately restarted after Network Settings are saved
225915 Chinese, Japanese, and Korean comment strings show up improperly
227480 MAX provides no warning when the same static IP address is used on multiple targets
236028 Clicking the error button to view any errors after importing a MAX Configuration File does nothing
237136 Internal and External Calibration properties incorrectly returns an error for some devices
255826 Get System Image.vi does not obtain files in hidden folders and files related to authentication from RT targets
258540 Deploying an image of a standard RSS to a cRIO may cause the FPGA target on that cRIO to disappear from MAX
275768 Quickly deleting ethernet cDAQ devices may crash MAX
281382 Find (Systems) VI may hang if executed repeatedly on a Real-Time target
282710 Adding network cDAQ device with old firmware to MAX might crash MAX
284269 Certain MAC Address formats will cause the Initialize VI to initialize the wrong target
284282 Resetting a USB-cDAQ chassis with one or more modules may hang MAX
285330 Cannot update BIOS on PXI-8145RT with MAX 4.7 and LabVIEW 2010 installed
286591 Accessing Remote Systems and certain Network Devices on Windows Server may cause an Internet Explorer error
292788 Get System Image VI cannot obtain zero byte files



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

Reported Version: 4.5    Resolved Version: N/A    Added: 08/03/2009
174178

Return
MAX crashes when deleting multiple remote targets
During the discovery stage, MAX may crash if you attempt to delete multiple existing targets together.

Workaround: Launch MAX and try again or delete targets one by one.

Reported Version: 4.6    Resolved Version: N/A    Added: 08/03/2009
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.

Reported Version: 4.2    Resolved Version: N/A    Added: 08/03/2009
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.

Reported Version: 4.6    Resolved Version: N/A    Added: 08/02/2010
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.

Reported Version: 4.7    Resolved Version: N/A    Added: 08/02/2010
225915

Return
Chinese, Japanese, and Korean comment strings show up improperly
After saving and refreshing a comment string containing Chinese, Japanese, or Korean characters, the comment string does not display the same characters previously entered.

Workaround: N/A

Reported Version: 4.7    Resolved Version: N/A    Added: 08/02/2010
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

Reported Version: 4.7    Resolved Version: N/A    Added: 08/02/2010
236028

Return
Clicking the error button to view any errors after importing a MAX Configuration File does nothing
If any errors occur while importing a MAX Configuration File, clicking the error button does not display anything.

Workaround: N/A

Reported Version: 4.6.2    Resolved Version: N/A    Added: 08/02/2010
237136

Return
Internal and External Calibration properties incorrectly returns an error for some devices
If the IntCal or ExtCal property is queried for NI-DAQmx devices that do not have a valid Last Temperature value, the property node incorrectly returns an error, even if there is a valid Last Date value.

Workaround: N/A

Reported Version: 1.1    Resolved Version: N/A    Added: 08/02/2010
255826

Return
Get System Image.vi does not obtain files in hidden folders and files related to authentication from RT targets
A system image created with the Get System Image VI does not obtain all files from the RT target. Files related to user authentication and files in hidden folders are not replicated in the image.

Workaround: N/A

Reported Version: 1.1    Resolved Version: N/A    Added: 10/29/2010
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

Reported Version: 1.1    Resolved Version: N/A    Added: 04/27/2011
275768

Return
Quickly deleting ethernet cDAQ devices may crash MAX
Deleting ethernet cDAQ devices from an ethernet cDAQ chassis may crash MAX if the devices are deleted quickly.

Workaround: N/A

Reported Version: 4.8    Resolved Version: N/A    Added: 04/27/2011
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

Reported Version: 1.2    Resolved Version: N/A    Added: 04/27/2011
282710

Return
Adding network cDAQ device with old firmware to MAX might crash MAX
Adding a network cDAQ device with out-of-date firmware to MAX might cause MAX to crash. This has been seen with network cDAQ devices running firmware revision 1.1.0.

Workaround: N/A

Reported Version: 1.2    Resolved Version: N/A    Added: 04/27/2011
284269

Return
Certain MAC Address formats will cause the Initialize VI to initialize the wrong target
If a MAC address of the form "#### #### ####" is passed into the Initialize VI, the VI will succeed but will initialize the local system, and not the target with that MAC address.

Workaround: Use a MAC address of the form "##:##:##:##:##:##"

Reported Version: 1.2    Resolved Version: N/A    Added: 04/27/2011
284282

Return
Resetting a USB-cDAQ chassis with one or more modules may hang MAX
If a USB-cDAQ chassis containing one or more modules is reset through MAX, MAX may hang for approximately 20 seconds.

Workaround: N/A

Reported Version: 4.8    Resolved Version: N/A    Added: 04/27/2011
285330

Return
Cannot update BIOS on PXI-8145RT with MAX 4.7 and LabVIEW 2010 installed
The BIOS of a PXI-8145RT system cannot be updated from a system with MAX 4.7 and LabVIEW 2010 installed. The update will start, then fail.

Workaround: Update BIOS from a machine using LabVIEW 2009 and MAX 4.6

Reported Version: 4.7    Resolved Version: N/A    Added: 04/27/2011
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.

Reported Version: 4.8    Resolved Version: N/A    Added: 04/27/2011
292788

Return
Get System Image VI cannot obtain zero byte files
Get System Image VI cannot obtain zero byte files from a Real-Time target.

Workaround: N/A

Reported Version: 1.2    Resolved Version: N/A    Added: 04/27/2011

Document last updated on 4/27/2011

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).