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.
This document contains the LabVIEW SignalExpress 2011 known issues that were discovered before and since the release of SignalExpress 2011. 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.
The LabVIEW 2011 Platform Known Issues contains a full listing of known issues, including LabVIEW toolkits and modules.
Each Issue appears as a row in the table and includes these fields:
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.
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.
The following items are known issues in SignalExpress 2011 sorted by Category.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 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
| |||||
| File I/O | ||||||
| 173678 Return | Import from ASCII step: User specified dt and Input X values combo results in failed data import Changing User specified dt value when Input X values is set to a column of data will prevent the data from being imported. User must set Input X values to None to use a User specified dt. Changing Input X values back to the desired column will import the data correctly. Workaround: User must set Input X values to None to use a User specified dt. Changing Input X values back to the desired column will import the data correctly.
| |||||
| 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 Hardware | ||||||
| 145055 Return | On Windows Vista x64 Edition, the 64-bit version, USB plug-and-play functionality does not work because LabVIEW SignalExpress is a 32-bit application Workaround: Open SignalExpress and select the necessary devices/channels through Channel View or by adding the necessary data acquisition step
| |||||
| 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.
| |||||
| 144442 Return | Code Generation Fails when VI Server is not Enabled If VI server is not enabled for remote access, code generation will throw an error indicating that the VI server settings are preventing a VI from being created. Workaround: Turn on remote access to VI Server and add * to the exported VI list
| |||||
| Logging | ||||||
| 133032 Return | Unable to use cursors in SignalExpress 3.0/2009 and higher on a log file created with SignalExpress 2.5 If you create a log file in SignalExpress 2.5 and import the log file into SignalExpress 3.0 or 2009, you cannot use cursors on the imported signal in the Data View. The cursors appear, but you cannot move them. Workaround:
| |||||
| 130108 Return | Unable to use cursors in SignalExpress 3.0 (and higher) on a log file created with SignalExpress 2.5 If you create a log file in SignalExpress 2.5 and import the log file into SignalExpress 3.0 (and later versions), you cannot use cursors on the imported signal in the Data View. The cursors appear, but you cannot move them. Workaround: N/A
| |||||
| 142179 Return | The Save to ASCII/LVM step does not save any units associated with the specified data. Workaround: For LabVIEW Measurement Files (.lvm): Include 'Notes', 'Waveform notes' etc. in the Save to ASCII/LVM step to indicate what units are being used For Generic ASCII Files (.txt): Update the signal names so the units are also mentioned and have the option 'Include Signal Names' selected in the Save to ASCII/LVM step under the File Settings tab.
| |||||
| 167020 Return | Export to Excel throws error unless Excel open When you right-click on a log file and select "Export to Microsoft Excel" it throws a Exporting Data Error that says "Data could not be sent to Microsoft Excel. It is possible that you attempting to send too much data for your current version of Microsoft Excel" Workaround: Open Microsoft Excel first before attempting to export data from the log file OR Use the Export to... >> Microsoft Excel in the Data View tab
| |||||
| 178160 Return | Not Enough Memory Error with large NI-SCOPE records in LabVIEW SignalExpress If you perform an NI-SCOPE acquisition in LabVIEW SignalExpress greater than ~10 MS (or ~5 MS/channel; system dependent), LabVIEW SignalExpress might return a "not enough memory to complete this operation" error. The NI-SCOPE step gets the entire record of data at once, and LabVIEW SignalExpress cannot handle this much data at once, even with all the displays turned off. Workaround: N/A
| |||||
| 180702 Return | SignalExpress log data shows "reconfiguration" when dragged into data view display SignalExpress shows "reconfiguration" when trying to load the log data from a dc value of a signal into a display on the data view. The data is valid when taken from the original step (not the log) and when the log is exported it shows fine as well (so the data is actually there). Workaround: N/A
| |||||
| 208273 Return | Error reading LVM file "Incorrect file type" If you save data to a LVM file using the "Overwrite once, then append to file" mode, you can potentially get an error when reading this file back. The error will show up as "incorrect file type". The problem is that the step reads back the file in 65K chuncks and if this chunk happens to end in the middle of a header section, the step will give this error. Workaround: A potential workaround is to add a few extra lines in the beginning of the file and thus shifting where the next 65k chunk starts. Also, in general, the LVM file type is not the best file format for overwriting the file with multiple sections, thus it's better not to use this mode
| |||||
| 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
| |||||
| 175412 Return | A runtime error occurrs occasionaly when the DAQ Assistant is closed quickly in SignalExpress localized to Korean The error says NI Asssitant Host is stopped. In all other languages (except Korean), you will get a clear warning ""Execution has not completed. Please wait for execution to complete..." when trying to close the DAQ Assistant. Workaround: Wait till execution completes before trying to close DAQ Assistant. Once a frequency is selected as a counter input for a card, the device is running in the DAQ Assistant.
| |||||
| 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
| |||||
| 173744 Return | Double-clicking in Channel View cell causes brief auto-selection but then gets unselected. Workaround: N/A
| |||||
| 199436 Return | Unit controls don't give an option to enter custom units when the "Custom" property is selected Workaround: N/A
| |||||
| 201439 Return | Selecting "Run" in DAQ Asst doesn't always update the graph when doing reference triggering Selecting "Run" in DAQ Asst doesn't always update the graph when doing reference triggering. Sometimes the "Run" button deselects itself when a trigger is detected, but the graph does not update. Then, the next time you click "Run", the graph immediately updates with the result of the previous acquisition, and "Run" doesn't deselect itself until another trigger is detected Workaround: N/A
| |||||
| 203920 Return | Code generation of DAQmx task example fails if login user name contains Japanese stress character If the user's machine login user name contains a Japanese stress character, attempts to code generate an example of a DAQmx task (from a DAQmx Task name control) will fail and no code will be generated. Workaround: Change the login user name to be one that does not contain a Japanese stress character
| |||||
| 208252 Return | Load from LVM step will not reload different files once a file has been selected Workaround: Delete the step and add another Load from LVM Step.
| |||||
| 258461 Return | Output of some steps contain incorrect units when group has elements with different units Some steps don't manage individual channel units correctly, hence when the output is created, the output has incorrect units when the said channels are in a single group Workaround: Do not group signals with different units into a single group
| |||||
| Operating System Specific | ||||||
| 172817 Return | On Japanese versions of Windows Vista, switching the system locale to another language causes error 1 to occur when you launch LabVIEW SignalExpress Workaround: N/A
| |||||
| Playback | ||||||
| 207734 Return | Steps reset when unpausing or stepping through playback When playing back a log, steps that can be restarted/reset get reset by stepping through playback (such as by pausing playback and then either unpausing or stepping through one block at a time) You do not get the same results. In general stepping through playback is not a viable method to study the evolution of a measurement Workaround: N/A
| |||||
| 303074 Return | Playback With Multiple Scalar Logs doesn't Reinitialize When switching between logs which contain scalar data, the display for the data does not properly reinitialize in the playback viewers. Instead, the entire log is shown. Workaround: Right click the scalar chart and select Show Full Log. Repeat to unselect it and the appearance should be restored.
| |||||
| Shared Variables | ||||||
| 176917 Return | Group of scalars published to a shared variable will be read as an array A group of scalar data published to shared variable, will be read back as an array of size matching the number of items in the group. Even if only 1 scalar member of a group is published, it will be read back as an array. Workaround: N/A
| |||||
| 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 | ||||||
| 173577 Return | Cannot print a selection or a specific page from the Project Documentation tab in LabVIEW SignalExpress Workaround: Use a 3rd-party PDF printer as an intermediate step, and then print specific pages from the PDF.
| |||||
| 174978 Return | Dragging and dropping steps into viewers oesn't Show Option Dialog in Korean Workaround: N/A
| |||||
| 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
| |||||
| 30892 43LE967X Return | Extremely large number of alarms makes Data View slow and unusable Workaround: N/A
| |||||
| 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 7/25/2011