Measurement & Automation Explorer (MAX) Improvement and Bug Fix List
Primary Software: Utility Software>>Measurement & Automation Explorer
Primary Software Version: 4.5
Primary Software Fixed Version: 4.5
Secondary Software: N/A
Problem: What improvements and bug fixes have been released in the latest versions of Measurement & Automation Explorer?
Solution: Improvements and Bug Fixes
MAX 4.5
| Bug ID |
Description |
| 104932 |
If you generated a technical support report on a remote target, it included the local visaconf.ini instead of the one on the selected system. This fix requires NI-VISA 4.4. |
| 103333 |
Right- or left-clicking on a remote system item could crash MAX. |
42074,
100376,
102265 |
Discovery of remote LabVIEW Real-Time targets could fail when there are multiple network adapters on the host. This issue is fixed on Microsoft Windows Vista. |
| 97607 |
Using the DAQ Assistant on Microsoft Windows Vista would crash Measurement Studio 2008 when Data Execution Prevention (DEP) is enabled. |
| 90799 |
Made the MXS database files more robust and less susceptible to corruption. |
| 108298 |
A cRIO-9014 embedded real-time controller could run out of memory if NI-RIO 2.4 was installed and many items were added to and then removed from the MXS database. |
| 93344 |
Some remote LabVIEW Real-Time targets, such as the PXI-8106, support multiple filesystem types (FAT and Reliance). MAX now allows you to specify the filesystem type when formatting the target. This fix requires LabVIEW Real-Time 8.6. |
| 58268 |
Changed maximum length of the name of a LabVIEW Real-Time target from 15 to 32 characters. |
MAX 4.4.1
| Bug ID |
Description |
| 60412 |
MAX displayed Simplified Chinese characters on systems using Microsoft Windows for Traditional Chinese. MAX now displays English characters on these systems. |
| 45180 |
Toolbars could disappear when switching between tabs. |
MAX 4.4
| Bug ID |
Description |
| 4FQFJSKI |
Performing an export, deleting all virtual devices, and then performing an import of Switch Executive settings would hang MAX. |
| 46CDCKQ1 |
Expanding Remote Systems and quickly exiting MAX could cause a crash. |
| 3FLAM4M0 |
Time zone settings for a remote system were not complete. |
| 4EAAQRCZ |
Expanding Devices & Interfaces on a system with both NI-RIO and NI-IMAQ installed would not list all devices. Pressing F5 fixed the problem. |
| 4F5ENM5B |
MXS server could crash when there are stale entries in the registry from an old installation. |
MAX 4.3
| Bug ID |
Description |
| 46M9POLY |
Expanding IVI Drivers and then choosing File>>Generate Report would cause a crash. |
| 46NGPUNB |
Editing and Saving a DAQ Task multiple times from VI Logger could cause a hang. |
| 468FASCP |
Using a crossover cable to connect to a remote system could cause a red X to appear on a Motion device. |
| 4919NMOU |
Exporting or importing settings from Switch Executive could timeout. |
| 4AQBGMKY |
Deleting multiple remote systems could cause a crash. |
| 46L9PBO6 |
MAX would not report the correct connection speed of a remote system in Advanced Ethernet Settings. |
| 4AS9HUX6 |
MAX could intermittently lose configuration settings for FieldPoint Controllers. |
| 49GE7IG0 |
Generating a report would show 1 GB as your system memory even when you have more than 1 GB. |
| 47JCL1YW |
Calling DAQmxResetDevice would change the current directory temporarily. This could cause file I/O in other threads to fail. |
| 46KB42BQ |
MAX could not connect to MXS database on first reboot after installation. |
Related Links:
Attachments:
Report Date: 12/03/2007
Last Updated: 07/24/2008
Document ID: 4G2E58QA
