Archived: LabVIEW SignalExpress 2.0 Known Issues

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.

Overview



This document contains the LabVIEW SignalExpress 2.0 known issues that were discovered before and since the release of the LabVIEW SignalExpress 2.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.

Known Issues

The following items are known issues in the LabVIEW SignalExpress 2.0.

  • When you convert a project to a LabVIEW block diagram, some VIs will contain errors. Mass compile the LabVIEW\vi.lib directory to fix the VIs.
  • If you are installing both the System Identification Toolkit 3.0 and LabVIEW SignalExpress 2.0, you must install the System Identification Toolkit 3.0 before you install LabVIEW SignalExpress 2.0. Installing the System Identification Toolkit 3.0 after you install LabVIEW SignalExpress results in an error upon launch of LabVIEW SignalExpress 2.0. To resolve the error, you can uninstall the affected components and reinstall in the correct order. The easiest way to resolve the error is to install the free System Identification Toolkit 3.0.1 upgrade. Refer to ni.com for more information on obtaining the free System Identification Toolkit 3.0.1 upgrade CD.
  • LabVIEW SignalExpress only supports one version of LabVIEW at a time. When you install LabVIEW SignalExpress, it finds the most current installed version of LabVIEW and installs support for LabVIEW SignalExpress into that version. If you later install a new version of LabVIEW, you need to uninstall and reinstall LabVIEW SignalExpress. When you reinstall, LabVIEW SignalExpress will install support for the new version of LabVIEW.
  • When you convert a project that contains features not supported in LabVIEW to a LabVIEW block diagram, LabVIEW SignalExpress generates a LabVIEW block diagram with one Express VI. You cannot open the block diagram of the generated Express VI. If you include the generated Express VI in a distribution with the LabVIEW Application Builder, you must install LabVIEW SignalExpress to any target computers on which you run the LabVIEW-built application.
  • Registration information is saved on a per-user basis in Windows Vista. When you change users, the user information that appears when you launch LabVIEW SignalExpress may appear incorrectly.
  • Creating a source distribution in LabVIEW of a LabVIEW SignalExpress User Step template VI may fail and return an error. For one possible solution for this error, navigate to the Additional Exclusions page of the Source Distribution Properties dialog box and select the Remove unreferenced project library members option to remove the error.
  • LabVIEW SignalExpress only supports one version of LabVIEW at a time for project conversion into LabVIEW. LabVIEW SignalExpress only installs support for the latest version of LabVIEW installed on the system. However, when you convert a LabVIEW SignalExpress project to a LabVIEW block diagram, LabVIEW SignalExpress calls the last version of LabVIEW opened on the system. If the last version of LabVIEW open on the system is not the version of LabVIEW with LabVIEW SignalExpress support installed, you must launch the version of LabVIEW with LabVIEW SignalExpress support and re-generate the project.
  • The Getting Started with LabVIEW SignalExpress manual incorrectly states that LabVIEW SignalExpress is compatible with Windows NT. LabVIEW SignalExpress is compatible with Windows Vista/XP/2000.
  • The LabVIEW SignalExpress Help incorrectly states that LabVIEW SignalExpress LE by default does not display steps that are only available in the Full Edition. LabVIEW SignalExpress LE by default does display steps that are only available in the Full Edition.
  • The Statistics step does not accept U32 data as an input.
  • When viewing scalar data in a table, the data history of the scalar data is not saved unless you previously viewed the scalar data in a chart display.
  • The Save to ASCII/LVM step does not save any units associated with the specified data.
  • You can configure only one IVI session name for a driver. If you configure more than one IVI session name for a driver, you invalidate existing IVI session names for that driver.
  • LabVIEW prompts you with a warning dialog box during project conversion if LabVIEW loads vi.lib subVIs from the National Instruments\LabVIEW directory rather than from the directory in which you saved your LabVIEW SignalExpress project. Click the OK button to resume conversion.
  • The Load from ASCII, Load from LVM, and Load from SPICE steps convert up to 20 imported signals into the LabVIEW VI during project conversion. If you want to import more than 20 signals and then convert the project to a LabVIEW VI, use two or more Load from ASCII, Load from LVM, or Load from SPICE steps.
  • You cannot convert a LabVIEW SignalExpress project to a LabVIEW block diagram if a hardware step in the project uses software triggers.
  • Text in any step configuration view does not display correctly if you set your monitor resolution to 1400 x 1050 or higher or if you use large fonts.
  • Due to driver and operating system issues, absolute time stamps have an inaccuracy of 100 ms to 200 ms. National Instruments recommends that you use relative time stamps.
  • You cannot use a software trigger if the IVI FGEN Standard Function step or the IVI FGEN Arbitrary Waveform steps are in continuous generation mode or if the IVI FGEN steps are in a sweep operation. During a sweep operation, the NI-FGEN devices send a start trigger only at the first sweep iteration.
  • If you configure a device to start on a digital trigger and the trigger source is the start trigger of an analog output NI-DAQmx supported device, the device might receive the start trigger before the generation starts. This can occur the first time you run the project or on the first iteration of a continuous execution. To work around this issue, configure the analog output device to be a slave by configuring the device with a digital trigger and selecting a trigger signal from another device as the trigger source.

 

Additional Resources

  • LabVIEW SignalExpress 2.0 Readme

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