LabVIEW Communications System Design Suite 2.1 Known Issues

Panoramica

This document contains the LabVIEW Communications System Design Suite 2.1 known issues that were discovered before and since the release of LabVIEW Communications System Design Suite 2.1. 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.

Known Issues by Date

The following items are known issues in LabVIEW Communications System Design Suite 2.1 sorted by Date.

704824 The Xilinx IP Generator fails to launch after clicking the "Configure Xilinx IP" button on some builds of Windows 10 (version 1709)
703930 It is not possible to use variable sized array controls in Optimized FPGA VIs
703080 FPGA compilations fail when dependencies in a Library are not exported
688821 Installing LabVIEW Communications 2.1 on a machine with an existing installation of LabVIEW Communications 2.0 prevents the older version of the software from communicating with Real-time targets.
706310 Shared Library Interface documents that use Type Definitions as the type for function parameters are broken following conversion.
706319 Some PXIe controllers mistakenly appear as Real-Time Compatible in SystemDesigner.
707042 Any project containing a MathScript Node that had the 'Show Label' checkbox selected will fail to migrate properly.



ID Known Issue
704824

Return
The Xilinx IP Generator fails to launch after clicking the "Configure Xilinx IP" button on some builds of Windows 10 (version 1709)
Clicking the "Configure Xilinx IP" button on the Item tab of a Xilinx CORE Generator IP Node fails to launch the Xilinx IP Generator on some builds of Windows 10 (version 1709).

Workaround: Update to a newer build of Windows 10 (version 1709).

Reported Version: 2.1    Resolved Version: 3.0    Added: 08/17/2018
703930

Return
It is not possible to use variable sized array controls in Optimized FPGA VIs
As a result of the Known Issue tracked by ID 703080 all FPGA subVIs in a Library that are separate from the library that contains the top-level VI must be marked as exported. When a VI in an Optimized FPGA Library is marked as exported it is treated as a top-level VI and top-level Optimized FPGA VIs don't support variable sized array controls.

Workaround: N/A

Reported Version: 2.1    Resolved Version: 3.0    Added: 08/17/2018
703080

Return
FPGA compilations fail when dependencies in a Library are not exported
When a Bitfile Application contains a VI that references an exported VI from a Library Document and that VI references a third VI that is not marked for export then an error is incorrectly thrown during compilation. VIs in a Library are marked for export by default.

Workaround: Select the export checkbox for all affected VIs in the Library Document.

Reported Version: 2.1    Resolved Version: 3.0    Added: 08/17/2018
688821

Return
Installing LabVIEW Communications 2.1 on a machine with an existing installation of LabVIEW Communications 2.0 prevents the older version of the software from communicating with Real-time targets.
Installing LabVIEW Communications 2.1 on a machine with an existing installation of LabVIEW Communications 2.0 prevents the older version of the software from communicating with Real-time targets. This is a result of LabVIEW Communications 2.1 upgrading software components used for system discovery and communication, rendering these components incompatible with LabVIEW Communications 2.0.

Workaround: Maintain a separate PC for use only with LabVIEW Communications 2.0. Alternatively, fully uninstall both versions of LabVIEW Communications and related shared components from your system and then reinstall LabVIEW Communications 2.0.

Reported Version: 2.1    Resolved Version: N/A    Added: 08/17/2018
706310

Return
Shared Library Interface documents that use Type Definitions as the type for function parameters are broken following conversion.
Opening a LabVIEW Communications 2.0 project in LabVIEW Communications 2.1 that contains a Shared Library Interface document using Type Definitions as the type for function parameters are broken following conversion.

Workaround: After conversion click on each affected function parameter and on the Item tab click the GType dropdown and select the correct GType from the list.

Reported Version: 2.1    Resolved Version: N/A    Added: 08/17/2018
706319

Return
Some PXIe controllers mistakenly appear as Real-Time Compatible in SystemDesigner.
The PXIe-8840, PXIe-8840 Quad-Core and PXIe-8821 mistakenly appear in SystemDesigner as supported Real-Time controllers. These controllers are not supported as Real-Time controllers at this time.

Workaround: Use a PXIe-8880 or PXIe-8135 if a Real-Time controller is needed.

Reported Version: 2.1    Resolved Version: 3.0    Added: 08/17/2018
707042

Return
Any project containing a MathScript Node that had the 'Show Label' checkbox selected will fail to migrate properly.
Migration fails when opening a LabVIEW Communications 2.0 project in LabVIEW Communications 2.1 that contains a MathScript Node that had the 'Show Label' checkbox selected. The failure will occur even if the 'Show Label' checkbox was later deselected. The Conversion dialog may report "Converting source files to components failed with unknown error" and when you attempt to open the VI that contained the MathScript Node an error is thrown stating that "The source file format is invalid."

Workaround: In a backup copy of the LabVIEW Communications 2.0 project open the VI containing the MathScript Node, drop a new MathScript Node, copy the text from the old node into the new node, and delete the old node. Then rewire as necessary, save the VI and attempt the conversion process in LabVIEW Communications 2.1 again.

Reported Version: 2.1    Resolved Version: 3.0    Added: 08/17/2018

 

 

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