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.
The following items are known issues in SignalExpress 2013 sorted by Category.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| Analysis and Math | ||||||
| 413518 Return | Dividing signals with Arithmetic Divide step can produce incorrect results N/A Workaround: N/A
| |||||
| 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
| |||||
| 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.
| |||||
| Interaction with LabVIEW | ||||||
| 154162 Return | LabVIEW SignalExpress cannot generate code for 64-bit LabVIEW 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.
| |||||
| 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".
| |||||
| 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
| |||||
| 154289 Return | Favorite steps with forward slashes (/) in their names get broken up in Favorites palette Workaround: Do not use forward slashes in the name of a Favorite step
| |||||
| 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
| |||||
| 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.
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 207543 Return | Charts in SignalExpress can only show absolute time Workaround: Use a time graph rather than a chart. To do this, the task must be either N samples or continuous samples.
| |||||
Document last updated on 8/2/2013