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 SignalExpress 2013 known issues that were discovered before and since the release of SignalExpress 2013. 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.
Each Issue appears as a row in the table and includes these fields:
Legacy ID - The issue's legacy ID from NI's deprecated bug reporting database (if applicable)
Reported Version - the earliest version of LabVIEW the
issue was reported in
Resolved Version - version the issue was resolved or was no
Date Added - the date the issue was added to the document
(not reported date)
The known issues in this document are organized by the category of issue. Please refer to Developer Zone Article
Known Issues Categories Defined" for an explanation of the categories and what types of issues are in each category.
You can contact us by phone, email, or the discussion forums. Visit the NI Website to contact us. If you are contacting NI in regards to a specific issue, be sure to reference the ID number given in this document. If you have feedback on this specific document, please contact NI on this NI Developer Zone post.
Converting a SignalExpress project to LabVIEW diagram with step that uses software trigger
You cannot convert a LabVIEW SignalExpress project to a LabVIEW block diagram if a hardware step in the project uses software triggers.
Blank licensing dialog when launching SignalExpress or dropping SignalExpress Express VI in LabVIEW
When launching a non-activated SignalExpress or dropping a SignalExpress Express VI prior to activating SignalExpress, the license dialog may have a blank window.
Workaround: The buttons at the bottom of the dialog are still functional and the user may continue to use SignalExpress or the Express VI as appropriate for the current license state.
Missing Pre-Start Condition Samples in Log When Using Force DAQmx Acquire Step
When configuring pre-start condition in the start condition of the recording options for a Force Task (Bridge or IEPE), the samples in the log before the start condition are missing.
Workaround: Change the Acquisition Mode of the Force configured step to "Continuous Samples".
SignalExpress cannot read floating point Shared Variables bound to OPC servers
SignalExpress cannot read shared variables of floating (short or floating type) bound to an OPC server. It can read booleans, strings, and integer(word) datatypes, but when you configure the 'Read Shared Variable' step in signalexpress and select one of these floating, bound shared variables, you get a warning "The data type of specified shared variable \\localhost\Untitled Library 1\Random1 is not supported." and it is not properly added to the step.
Cannot enter data in the Limit Test Define Signal Dialog
If you fill out a cell in the Limit Test Define Signal dialog and use the mouse or arrow keys to navigate to another cell in the table, the current value will be lost. The Enter key must be used to enter data into this table.
Workaround: Enter data using the Enter key after every cell is filled. This will ensure that the value is actually entered.
Engineering units are no longer shown in SignalExpress 2009 (or higher) Large Display data views
This is a behavior change from SignalExpress 3.0 to SignalExpress 2009. Earlier it was possible to show engineering units of a particular data in a large display
Workaround: Manuallly enter the units as part of the channel name by renaming it
Multiple channel digital input data exported from the Data View of Signal Express is formatted in one column
If you drag a digital acquisition step that acquires from multiple digital input channels into the Data View you will see the data properly. However, when you export it from the data view into notepad (or excel) the data appears all in one column and all the channels are named Signal 0
Workaround: Record/log the digital signals and use the TDMS Excel plugin to view the recorded TDMS digital data in Excel