Academic Company Events NI Developer Zone Support Solutions Products & Services Contact NI MyNI
30 ratings:
 3.70 out of 5     Rate this Document

LabVIEW 8.2.x Upgrade Issues

Primary Software: LabVIEW Development Systems>>LabVIEW Professional Development System
Primary Software Version: 8.2
Primary Software Fixed Version: N/A
Secondary Software: N/A

Problem: This page documents issues arising while upgrading from LabVIEW 8.0.x to LabVIEW 8.2.x or from LabVIEW 8.2 to 8.2.1. This page is not meant to document all bugs in LabVIEW 8.2.x, only those that prevent a user from seamlessly and successfully upgrading their code from the previous version.  Examples of such issues are ones that cause different, undocumented execution behavior, broken VIs upon load, issues with Application Builder that prevent creating a build with the same behavior as in the previous version, etc. The most recently found issues will be added to the bottom of this list.  If you encounter behavior that is preventing you from successfully upgrading or caused trouble during your upgrade process, please report it at ni.com/support and ask that it be added to this page. This page should be used in conjunction with the LabVIEW 8.2/8.2.1 Upgrade Notes and LabVIEW 8.2/8.2.1 Release Notes as part of your upgrading process.

Solution:

Upgrading from LabVIEW 8.0.x to LabVIEW 8.2.x
Upgrading from LabVIEW 8.2 to LabVIEW 8.2.1

Upgrading from LabVIEW 8.0.x to LabVIEW 8.2.x:
  • Problem [Fixed in 8.2.1]: In some situations, a While Loop with an array indexing input tunnel wired directly to a non-indexing output tunnel incorrectly overwrites values in the array if the data was subsequently modified after the While Loop.  See screenshot.
    Workaround(s): Branching the wire from the non-indexing output tunnel and wiring it to the edge of a structure (a dummy sequence structure, for example) will force LabVIEW to not overwrite the memory of the terminal.
    ID: 40DAF67U


  • Problem [Fixed in 8.2.1]: It is not possible, manually or programmatically, to configure a floating-point numeric control to show zero digits of precision after the decimal point.
    Workaround(s):  Use format %d instead of %f. This workaround works either manually, using the dialog (advanced editing, %d), or programmatically, using a property node (FormatString "%d").
    ID: 40FC9LTX


  • Problem [Fixed in 8.2.1]:  Clicking in a table indicator while it was being updated programmatically crashes LabVIEW (transact.cpp line 1323).
    Workaround(s): Place a transparent decoration on or overlapping a section of the table.  It is not necessary that the decoration covers the selectable parts of the table.  For example, place a thin line decoration on the table and color the line transparent.
    ID: 40A8TF70


  • Problem [Fixed in 8.2.1]:   VI Settings saved in a build specification are ignored while building the application.
    Workaround(s):  Simply change and save the settings in the VI properties of the actual VIs before building the application. This works for all settings except for Run When Opened. A workaround for this setting is tot go to the Advanced page of the build specification and check "Enable debugging" and "Wait for debugger on launch". One side effect is this will include the block diagrams of the VIs and extra code for debug tool support.
    ID: 41D846X2, 40HEDDJG


  • Problem: When a VI's front panel is set to use the Dialog Window Appearance with the additional option of "Window has title bar" unchecked,  a several-pixel wide 3D border is displayed around front panel when programmatically maximized.   See screenshot.
    Workaround(s): This is different behavior than previous versions of LabVIEW by design.  To obtain the original behavior, check the "Allow user to resize window" option in the Window Appearance configuration dialog.
    ID: 41H7SJ7U


  • Problem [Fixed in 8.2.1]:  The File Delete function does not prompt to confirm the delete operation when configured to do so.  This behavior is also present in the New Zip File.vi which uses the File Delete function.
    Workaround(s):  Create custom logic to prompt the user before file deletion.  For the New Zip File.vi, programmatically detect if there is an existing file that will be overwritten and if there so, display a prompt to the user.
    ID: 41HDO7D5


  • Problem:  In some situations, a digital waveform graph originally created in 8.0 displays data differently in 8.2.  At least one of the plots is shifted by 1/2 of a unit of Time. See screenshot.
    Workaround(s):  Replace your digital waveform graph with a new digital waveform graph in LabVIEW 8.20.  
    ID: 41EBHLAI


  • Problem [Fixed in 8.2.1]:  (Windows) The Sound Output Set Volume (Single) VI does not work with sound tasks created using the Play Sound File VI.
    Workaround(s):  Use the Sound Output Set Volume (Array) VI.
    ID: 41T9SLKJ


  • Problem [Fixed in 8.2.1]:  Compiling a VI that contains a bundle function, which bundles a cluster and one of that cluster's elements in the same bundle function crashes LabVIEW or results in error "There was not enough memory to compile this VI" or ufpstart errors (ufpstart err, avail=0x16164; ufpstart err, avail=0x1716C). See screenshot.
    Workaround(s):  Build the cluster with two separate bundle functions, separating the two inputs mentioned above.  
    ID: 423GHDQ4


  • Problem:  Writing to the Palette:Active Tool (ActPaletteTool) property of a graph using one of the graph palette tools (zoom, pan, etc) generates error 1107, LabVIEW: Invalid property value.
    Workaround(s):  Architect your VI to where these two actions cannot be done at the same time.  For example, use a control registered with an event structure to write to the Palette:Active Tool property.
    ID: 41PFS83Q


  • Problem [Fixed in 8.2.1]:  Stopping a Timed Loop repeatedly with the Stop Timed Structure VI causes LabVIEW to hang.  This can happen when your Timed Loop and Stop Timed Structure are in parallel loops that are out of sync.
    Workaround(s):  Place the Stop Timed Structure VI in a Timed Loop with the same timing parameters as the Timed Loop it is meant to stop.
    ID: 42CHH33W


  • Problem:  Building source distributions while preserving hierarchy sometimes puts distributed files in incorrect locations.  This is also visible in the generated preview.  This has only been seen while distributing VIs located in vi.lib, user.lib, or instr.lib.
    Workaround(s):  Do not include VIs from vi.lib, user.lib, or instr.lib in the source distribution, or manually move the mislocated files to the correct location after building the source distribution.
    ID: 43788G7U


  • Problem [Fixed in 8.2.1]:  In rare cases, clicking the broken arrow of a VI to show the error list window crashes LabVIEW.
    Workaround(s):  Fix the errors without bringing up the error list window, then force recompile and save the VI.
    ID: 437E4N1Y


  • Problem [Fixed in 8.2.1]: Deferring panel updates has no effect when writing to certain graph plot properties programmatically.  As a result, VIs utilizing deferred panel updates to increase speed of writing to a graph's plot properties no longer see the performance gain.
    Workaround(s):  None currently available.
    ID: 42JA9UW4


  • Problem [Fixed in 8.2.1]:  In some situations, a case structure within a loop, having an input tunnel passing straight to an output tunnel in one but not all cases will cause extra copies of the data to be created and will result in slower performance. See screenshot.
    Workaround(s):  Converting tunnels to shift registers and/or moving wire branches outside the case structure may eliminate this behavior.
    ID: 43J7L3MD


  • Problem [Fixed in 8.2.1]: Classic Slide controls with inverted scales increment and decrement in value, not direction when the increment/decrement arrows are clicked.  This is not the case with the modern slide controls, which are the most commonly used.
    Workaround(s):  Use a customized slide control to create a control with the previous behavior of classic slide controls.
    ID: 43K8PJJ0


  • Problem [Fixed in 8.2.1]:  VIs with nested For Loops and their N terminals wired together saved in a development environment with Show Constant Folding turned on causes incorrect array output of the nested For Loops on the first run of the VI. See screenshot.
    Workaround(s):  Turn off the Show constant folding options (Tools->Options), force recompile the VI, and save the VI.
    ID: 41422LTO


  • Problem:  LabVIEW does not properly load a VI Template that is an exported function of a LabVIEW Shared Library (DLL for Windows).
    Workaround(s):  Manually point LabVIEW to the VI Template while it is searching for it by pressing Browse, or change the VI Search Path to include the directory which contains the VI Template.
    ID: 444CDDJ0


  • Problem [Fixed in 8.2.1]:  A Format Into String function with constant inputs is constant folded and uses the locale settings to determine whether to use the period or comma as the decimal separator.  If the VI is saved and then opened on another machine with different locale settings without forcing a recompile of the VI, the resulting string is may use the incorrect decimal separator.
    Workaround(s):  Wire at least one control to the Format Into String function to prevent it from being constant-folded.
    ID: 4468LEU9


  • Problem [Fixed in 8.2.1]:  The Mouse Leave and Mouse Enter events do not work for the pane class unless the front panel window behavior is set to modal.
    Workaround(s):  Set the Front Panel Window Behavior to Modal.
    ID: 44BDUOO5


  • Problem:  Executing the XScaleInfo and YScaleInfo graph properties (deprecated since LabVIEW 6.0) cause LabVIEW to crash (support.cpp 6165).
    Workaround(s):  Use the X Scale and Y Scale properties to read and write to these graph properties.  Refer to Knowledgebase 4467K954 for more information.
    ID: 4467K954


  • Problem [Fixed in 8.2.1]: When a Sweep Chart's Y scale is autoscaled, the Y scale does not take into account the data that is still displayed from the previous sweep. This makes the data from the previous sweep displayed incorrectly due to the change in scale. 
    Workaround(s):  Do not use the built-in Y autoscale for Sweep Charts. Instead implement custom logic to programmatically rescale the Y scale when necessary.
    ID: 44JEGQ7U


  • Problem:  Applications built with the Enable Enhanced DSC Support option selected (need DSC installed to enable this) display "Debug Deployment" as the target in the lower, left corner of the frame.
    Workaround(s):  None currently available.
    ID: 44KB3ORW


  • Problem [Fixed in 8.2.1]:  Wiring a constant to the case selector terminal of a case structure that contains a case with a negatively, open-ended range in the case selector label will result in incorrect case selection/execution if the constant's value is equal to the bound of the negatively, open-ended range. See screenshot.
    Workaround(s):  Change the constant to a hidden control, or make the negatively, open-ended range case default.
    ID: 4474NJ00
Upgrading from LabVIEW 8.2 to LabVIEW 8.2.1:
  • Problem: Installing LabVIEW 8.2.1 on top of LabVIEW 8.2 causes broken VIs and libraries. SubVIs and typedefs for ODE Solver.vi in the NI_Gmath.lvlib library are not properly installed in this scenario. This causes ODE Solver.vi and the NI_Gmath.lvlib library to break, which can break your VI hiearchry and cause errors when using Application Builder, deploying VIs with TestStand, using LabVIEW Control Design and Simulation products, etc.
    Workaround(s):   You will need to repair the simulation.msi component. To do so, shut down LabVIEW, locate and run simulation.msi from the installation distribution (\Products\LabVIEW_Simulation_Core_Shared\simulation.msi), choose to repair, and proceed through repairing this component. Refer to Knowledgebase 47CDMI00 for more information.
    ID: N/A

Please refer to the Related Links below for more upgrade information.

Related Links:
LabVIEW 8.2.1 for Windows - Compatibility, Bug Fix and Upgrade Information
LabVIEW 8.2/8.2.1 Upgrade Notes
LabVIEW 8.2/8.2.1 Release Notes
NI Discussion Forums
ni.com/support

Attachments: