SignalExpress 2015 Known Issues

Aperçu

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

Fields

Each Issue appears as a row in the table and includes these fields:
  • Issue ID
  • Legacy ID - The issue's legacy ID from NI's deprecated bug reporting database (if applicable)
  • Issue Title
  • Problem Description
  • Workaround
  • Reported Version - the earliest version of LabVIEW the issue was reported in
  • Resolved Version - version the issue was resolved or was no longer applicable
  • Date Added - the date the issue was added to the document (not reported date)

Document Organization

The known issues in this document are organized by the category of issue. Please refer to Developer Zone Article " LabVIEW Known Issues Categories Defined" for an explanation of the categories and what types of issues are in each category.

Contacting NI

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.

 

Known Issues by Category

The following items are known issues in SignalExpress 2015 sorted by Category.

Analysis and Math
413518 Dividing signals with Arithmetic Divide step can produce incorrect results
Compatibility
181579 Converting a SignalExpress project to LabVIEW diagram with step that uses software trigger
Controls and Indicators
466260 Changing Data View display from Gauge display to other display type crashes SignalExpress.
Functions, VIs, and Express VIs
474878 SignalExpress palette Express VIs' configuration settings will not save as default
Installation and Activation
157025 Blank licensing dialog when launching SignalExpress or dropping SignalExpress Express VI in LabVIEW
Interaction with Hardware
440973 IVI Scope Acquire step does not maintain configuration changes.
Interaction with LabVIEW
154162 LabVIEW SignalExpress cannot generate code for 64-bit LabVIEW
Logging
254455 Missing Pre-Start Condition Samples in Log When Using Force DAQmx Acquire Step
Miscellaneous
157185 Undo/Redo operations are not supported in the Project Documentation View
154289 Favorite steps with forward slashes (/) in their names get broken up in Favorites palette
Playback
173397 Data View >> Export to Excel not supported in new Data View tool
Shared Variables
201435 SignalExpress cannot read floating point Shared Variables bound to OPC servers
Steps
171860 Cannot enter data in the Limit Test Define Signal Dialog
198916 Formula Step does not maintain units
Viewers
193237 Engineering units are no longer shown in SignalExpress 2009 (or higher) Large Display data views
198745 Multiple channel digital input data exported from the Data View of Signal Express is formatted in one column
207543 Charts in SignalExpress can only show absolute time
509469 Cursor placement issue when zooming.



ID Known Issue
Analysis and Math
413518

Return
Dividing signals with Arithmetic Divide step can produce incorrect results
N/A

Workaround: N/A

Reported Version: 2012    Resolved Version: N/A    Added: 06/19/2013
Compatibility
181579

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

Workaround: N/A

Reported Version: 2009    Resolved Version: N/A    Added: 11/20/2009
Controls and Indicators
466260

Return
Changing Data View display from Gauge display to other display type crashes SignalExpress.
With data acquired from Counter-Position-Angular DAQmx Acquire step, changing Data View display from Gauge display to other display type crashes SignalExpress.

Workaround: N/A

Reported Version: 2012    Resolved Version: N/A    Added: 05/07/2014
Functions, VIs, and Express VIs
474878

Return
SignalExpress palette Express VIs' configuration settings will not save as default
The saved values return to LabVIEW's default values upon closing and reopening the VI containing the express VI.

Workaround: Covert the express VI to a standard SubVI by right-clicking on it and selecting Open Front Panel>>Convert. This will save the default values but will not allow you to reconfigure the Express VI via the configuration window.

Reported Version: 2013    Resolved Version: N/A    Added: 07/23/2014
Installation and Activation
157025

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

Reported Version: 2009    Resolved Version: N/A    Added: 07/27/2009
Interaction with Hardware
440973

Return
IVI Scope Acquire step does not maintain configuration changes.
When running a IVI Scope Acquire step in SignalExpress, the output waveform does not change when configuration settings are modified.

Workaround: Create a new IVI Scope Acquire step with the intended configuration settings.

Reported Version: 2013    Resolved Version: N/A    Added: 08/04/2014
Interaction with LabVIEW
154162

Return
LabVIEW SignalExpress cannot generate code for 64-bit LabVIEW
N/A

Workaround: If you generate LabVIEW code from LabVIEW SignalExpress, you must ensure that the most recent version of LabVIEW you launched was a 32-bit version of LabVIEW 8.2 or later.

Reported Version: 2009    Resolved Version: N/A    Added: 03/23/2009
Logging
254455

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

Reported Version: 2009    Resolved Version: N/A    Added: 08/01/2011
Miscellaneous
157185

Return
Undo/Redo operations are not supported in the Project Documentation View
Edit >> Undo (Ctrl + Z) or Edit >> Redo (Ctrl +Y) is not supported in the Project Documentation View

Workaround: Manually delete or add the necessary contents to the Project Documentation

Reported Version: 2009    Resolved Version: N/A    Added: 07/27/2009
154289

Return
Favorite steps with forward slashes (/) in their names get broken up in Favorites palette
N/A

Workaround: Do not use forward slashes in the name of a Favorite step

Reported Version: 2009    Resolved Version: N/A    Added: 07/30/2010
Playback
173397

Return
Data View >> Export to Excel not supported in new Data View tool
N/A

Workaround: Export to Excel option is available separately for each viewer.

Reported Version: 2009    Resolved Version: N/A    Added: 08/02/2013
Shared Variables
201435

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

Workaround: N/A

Reported Version: 2009    Resolved Version: N/A    Added: 07/30/2010
Steps
171860

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

Reported Version: 2009    Resolved Version: N/A    Added: 07/31/2009
198916

Return
Formula Step does not maintain units
Units may be lost when using a Formula Step.

Workaround: Use the Arithmetic step instead of the Formular Step

Reported Version: 2009    Resolved Version: N/A    Added: 12/11/2009
Viewers
193237

Return
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

Reported Version: 2009    Resolved Version: N/A    Added: 11/20/2009
198745

Return
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

Reported Version: 2009    Resolved Version: N/A    Added: 07/30/2010
207543

Return
Charts in SignalExpress can only show absolute time
N/A

Workaround: Use a time graph rather than a chart. To do this, the task must be either N samples or continuous samples.

Reported Version: 2009    Resolved Version: N/A    Added: 08/03/2010
509469

Return
Cursor placement issue when zooming.
When full log is selected in playback mode there is an issue related to zooming. Zooming in and then selecting Show the Cursor can shift the focus to the end of the signal leaving the original zoomed in area.

Workaround: N/A

Reported Version: 2013    Resolved Version: N/A    Added: 08/03/2015

Document last updated on 9/16/2015

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