Archived: LabVIEW Communications System Design Suite 3.0 Known Issues
Updated Mar 17, 2020
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.
This document contains the LabVIEW Communications System Design Suite 3.0 known issues that were discovered before and since the release of LabVIEW Communications System Design Suite 3.0. 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.
Note: As of the release of LabVIEW Communications System Design Suite 3.0, most FPGA functionality is now contained in the LabVIEW NXG 3.0 FPGA Module which is included in the LabVIEW Communications System Design Suite. For FPGA Known Issues, refer to LabVIEW NXG 3.0 FPGA Module Known Issues.
Using a Shared Library Interface (SLI) with a number in the name on a Real-Time Target will not work
If a Shared Library Interface (SLI) used on a Real-Time Target in LabVIEW Communications has a number in it's name, that SLI will not resolve correctly to the proper library name. For example, foo2.sli on a Windows system will properly resolve to foo2.dll. On a Real-Time Target, this will not properly resolve to foo2.so.
Workaround: Do not use shared libraries with a number in the name on LabVIEW Communications Real-Time Targets.
Migrating a FPGA project from LabVIEW Communications 2.1 to LabVIEW Communications 3.0 may cause resource I/O Constant references in clusters to become unlinked
After migrating a LabVIEW Communications 2.1 project to LabVIEW Communications 3.0, I/O Constants of FPGA resources such as FIFOs or Memory items within a cluster will no longer be linked properly to the resource. This will result in previously working code having a broken run arrow.
Workaround: Switch the I/O Constant to a different resource, then back to the intended resource.
Exiting the LabVIEW NXG environment immediately after running a real-time VI may cause LabVIEW NXG to crash
If a user runs a VI on a real-time target in LabVIEW Communications and then immediately exits the editor, the LabVIEW NXG environment may crash.
Workaround: Wait until the real-time code has been running for some time before exiting, or ensure that all real-time VIs are stopped before exiting.
Error 0x80004005 can occur when trying to configure the Ethernet settings on a LabVIEW Communications Real-Time Target when no Ethernet connection is present
When trying to change the Ethernet port settings on a LabVIEW Communications Real-Time Target, error 0x80004005 will occur if no connection is active on the port.
Workaround: Connect the Ethernet port you are trying to configure to an active network connection. For example, connect the port to a switch.
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 or 3.0 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.