LabVIEW Communications System Design Suite 3.1 Known Issues

Panoramica

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

Note: As of the release of LabVIEW Communications System Design Suite 3.0, most FPGA functionality is now contained in the LabVIEW NXG FPGA Module which is included in the LabVIEW Communications System Design Suite. For FPGA Known Issues in LabVIEW Communications System Design Suite 3.1, refer to LabVIEW NXG 3.1 FPGA Module Known Issues.

Known Issues by Date

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

728092 Dropping a large number of unplaced FPGA devices in SystemDesigner can cause a hang
714413 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
712446 Error 0x80004005 can occur when trying to configure the Ethernet settings on a LabVIEW Communications Real-Time Target when no Ethernet connection is present
733974 SSH Connection to Linux RT target with non-blank root password fails



ID Known Issue
728092

Return
Dropping a large number of unplaced FPGA devices in SystemDesigner can cause a hang
Attempting to drop a large number of FPGA (USRP RIO or FlexRIO) devices in SystemDesigner, such as using the Unplaced Live Hardware>>All menu, can fail or cause a hang.

Workaround: Drop the FPGA hardware items one by one.

Reported Version: 3.0    Resolved Version: N/A    Added: 5/17/2019
714413

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

Reported Version: 3.0    Resolved Version: N/A    Added: 11/09/2018
712446

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

Reported Version: 3.0    Resolved Version: N/A    Added: 11/09/2018
733974

Return
SSH Connection to Linux RT target with non-blank root password fails
Attempting to connect to a Linux RT target via SSH when the root password is non-blank fails.

Workaround: Modify /etc/ssh/sshd_config by changing “PermitEmptyPasswords yes” to “PermitEmptyPasswords no” and reboot the controller.

Reported Version: 3.1    Resolved Version: N/A    Added: 05/17/2019

 

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