1. NI Error Reporter
NI is introducing an easier way to report crashes in LabVIEW 2011. In the unlikely event that LabVIEW crashes, you can report it to NI immediately with the NI Error Reporter (NIER). The NIER sends an error log detailing the root cause of the crash and, to further enhance the log, you can add comments and code to help NI find solutions faster.
The root cause of each crash has also been given a unique ID number. You can use this ID number to search the NI website and, in the event that this crash has been reported before, find advice from NI as to how to prevent a particular crash from occurring again.
Figure 1. Enhance error reports by adding comments and code and sending it all to NI to investigate.
2. .NET Assemblies in Memory
In LabVIEW 2010 and earlier, to discover which .NET assemblies were loaded in LabVIEW memory, each .NET Constructor Node had to be inspected manually. In LabVIEW 2011, a feature has been added to help visualize which assemblies have been loaded in LabVIEW memory. The .NET Assemblies in Memory dialog box provides an easy way to discover all items in memory and gives additional information that can help you resolve compatibility issues.
Figure 2. Discover all .NET assemblies loaded in memory.
3. Unable to Find Run-Time Engine
Sometimes executables are distributed to customers who do not have LabVIEW or the LabVIEW Run-Time Engine installed on their computers. When these customers attempt to run the executable, they receive a prompt saying an additional component is needed. NI has revised this prompt to give customers the option of visiting the NI website to download the appropriate software needed to run their executable.
Figure 3. A dialog prompt presents options for obtaining missing software.
4. Destination Path Is Too Long
When building a distribution, the build process may fail with Error 6: Generic File I/O error. This error may occur when the file path of the project extends beyond the 255-character limit allowed by Windows. If a VI is moved to a file path that exceeds 255 characters, a Destination Path Too Long prompt populates and forces the VI to be saved to a new and shorter location.
Figure 4. A warning indicates that the path of the VI exceeds the Window maximum 255 characters.
A path may still exceed the 255-character limit if saved from the LabVIEW environment. In this case, when the executable is built, LabVIEW works behind the scenes to compute a shorter path if all destinations are relative to the main destination. After updating the build, the process proceeds normally.
With every release of LabVIEW, a corresponding set of device drivers is also released to ensure full compatibility with the entire NI platform. Often when upgrading, customers only upgrade LabVIEW and then see compatibility issues in the form of a missing subVI. Two support features can help reduce the occurrence of a missing subVI.
5. Install Hardware Support Prompt When Installing LabVIEW
After an installation completes for LabVIEW 2011, an Install Hardware Support for LabVIEW prompt appears and explains the need for installing the latest drivers to ensure platform compatibility.
Figure 5. A prompt urges you to upgrade device drivers after installing LabVIEW.
6. LabVIEW Help File for Missing SubVIs
When a VI is opened and there are missing subVIs on the block diagram, LabVIEW Help provides information for common causes. For each scenario, suggestions are provided to help recover the missing subVIs.
Continue Providing Feedback to Improve the LabVIEW Experience
NI is very receptive to feedback pertaining to improvements for the NI platform. If there is any functionality that could be improved to help you with your development experience, let NI know by posting your ideas and opinions to the LabVIEW community.