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 LabVIEW SignalExpress 2009 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
| |||||
| Controls and Indicators | ||||||
| 176888 Return | SignalExpress Gauge and Meter controls can crash with given a NaN value The Gauge and Meter controls are currently unable to support NaN values and can lead to unexpected behavior including errors in data for that control and possibly crashing SignalExpress when running. If loading a project that has a NaN value in a Gauge or Meter, SignalExpress may crash on load. Also, if loading a project that has a NaN value in a Gauge or Meter, SignalExpress may crash on load. Workaround: Show the NaN value in a table or chart.
| |||||
| Documentation | ||||||
| 181411 Return | 30-day evaluation period starts with first load of LabVIEW 8.x or later after installing SignalExpress Full Edition If you install LabVIEW SignalExpress on a machine that has LabVIEW 8.0 or later installed, the 30-day evaluation period of the LabVIEW SignalExpress Full Edition begins the first time you launch either LabVIEW or LabVIEW SignalExpress. Workaround: N/A
| |||||
| 181446 Return | 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
| |||||
| 170754 Return | The documentation incorrectly states that you can export a Data View to File (text) The Data VIew help topic incorrectly states that you can export a viewer to a text file in SignalExpress 2009. 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.
| |||||
| 181583 Return | Load from ASCII step does not let you deselect a signal In the Load from ASCII step, if you deselect an output signal, it still appears to be selected. Workaround: The Load from ASCII step enables a signal in the Import Signals tab by default. If you do not want to import this signal, first select a different signal and then deselect the signal you do not desire
| |||||
| 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
| |||||
| 181447 Return | SignalExpress DAQ step receives AO start trigger before AO generation starts 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. Workaround: 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.
| |||||
| 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.
| |||||
| 114421 Return | Relative file paths in SignalExpress steps do not work when converted to a LabVIEW VI If a LabVIEW SignalExpress project includes relative paths and you convert the project to a LabVIEW block diagram, the resulting LabVIEW code might not work correctly. For example, if you specify a path to an ASCII text file in the Load from ASCII step, you must enter the full path if you want to generate LabVIEW code for the project that contains the step. This issue occurs when LabVIEW SignalExpress generates a LabVIEW block diagram that contains a single VI, but the LabVIEW SignalExpress project contains more than one step. Workaround: Change the paths to absolute.
| |||||
| 170506 Return | Code generation errors when logging waveforms When you use the configuration dialog box to modify a LabVIEW Express VI that was generated from a LabVIEW SignalExpress project with waveform logs, you get the following errors when you click the OK button: 7, 1026, 1026, 1055, 1055, 1055. Workaround: Make the changes you require in the original LabVIEW SignalExpress project and regenerate the LabVIEW code.
| |||||
| 180332 Return | SignalExpress Execution Control timing type in Run LabVIEW VI steps defaults to periodic Changing the timing type from 'periodic' to 'untimed' or 'continuous' after running the project once or more results in the VI executing at the specified rate as mentioned in Sample Periods (s), even though the periodic timing type is not selected and the Sample Periods (s) option is not visible Workaround: Replace the User Step - Run LabVIEW x.x VI with a new one that has the correct settings
| |||||
| 181581 Return | Source distribution in LabVIEW of a SignalExpress User Step template VI might fail and return an error Workaround: 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.
| |||||
| 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 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: 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
| |||||
| 174363 Return | Nested Conditional Repeats do not trigger recording based on current iteration If you have a nested conditional repeat step whose current iteration is used as a start condition for recording, nothing happens. The recording never starts. Workaround: Use time, duration, software trigger etc. instead to trigger a recording
| |||||
| 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.
| |||||
| 182846 Return | SignalExpress does not import TDMS files correctly if there is a "-" in the file name When you import a SignalExpress TDMS file back into Signal Express, it does not parse the file correctly if there is a "-" in the file name which makes the logged data unreadable. Workaround: Don't use a "-" in the file name and it works fine.
| |||||
| 181987 Return | Signal Express becomes unresponsive when trying to setup imaginary ASCII/LVM step Workaround: Do not use imaginary data with ASCII/LVM Step
| |||||
| 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
| |||||
| 181412 Return | Due to Windows operating system being non-deterministic, absolute timestamps are only accurate to within 100 ms to 200 ms. Workaround: N/A
| |||||
| 181445 Return | Software trigger with IVI FGEN steps in either continuous generation or sweep You cannot use a software trigger if the IVI FGEN Standard Function step or the IVI FGEN Arbitrary Waveform step 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. Workaround: N/A
| |||||
| 181449 Return | 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. Workaround: N/A
| |||||
| 189596 Return | Clicking the ReadMe link from the autorun installation dialog will fail to open the html file in Internet Explorer 8. Clicking an HTML link (e.g. readme) from the autorun dialog fails to open the HTML page when installing LabVIEW 2009 Platform products from CD/DVD. This problem exists for the LabVIEW 2009 Platform DVD and most National Instruments software released prior to October 2009. The problem does not occur when using other default browsers. Workaround: Open Internet Explorer 8, then click ReadMe while in autorun and the file will open.
| |||||
| 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.
| |||||
| 186976 Return | A sequence structure before a conditional repeat step results in Error 50103 Workaround: Remove conditional loop.
| |||||
| 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
| |||||
| 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.
| |||||
| Viewers | ||||||
| 170309 Return | The Export to Clipboard (Text) operation in a Data View can cause SignalExpress to crash If you attempt to export a large data set using Export To Clipboard (Text) option in a Data View, it can cause SignalExpress to crash. This usually occurs when a large number of channels are used. SignalExpress has a check for a long data set. It is possible that SignalExpress will hang instead of crash. In this case, you may need to use Task Manager to stop it. Workaround: SignalExpress has two other options to export large data sets. The recommended method is to log the data, then convert the data to a text file. One may also export the data to Excel, if the number of points is less than the maximum number of lines your version of Excel supports.
| |||||
| 172969 Return | The Event Viewer might show the incorrect times for the items it displays. Workaround: If you double-click an item, LabVIEW SignalExpress finds the item at the correct time in the associated display.
| |||||
| 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.
| |||||
| 181448 Return | Data View does not display output signal from a Limit Test step that was created in SignalExpress 1.1 When you load a project created in LabVIEW SignalExpress 1.1 or earlier that contains a Limit Test step with an output displayed on the Data View tab, the Data View tab does not display the signal. Workaround: Create a new display on the Data View tab and drag the Limit Test output signal to the display to view the signal.
| |||||
| 181584 Return | SignalExpress looks like it's skipping data in the Data View If you log a non-continuous finite signal, such as the output of a DAQmx Acquire step with an Acquisition Mode of N Samples, for a long period of time, and if the time interval between each block of data is large (an order of magnitude longer than the block itself), the logged data might not appear correctly when you display the data on the Data View tab. For example, LabVIEW SignalExpress might skip a data point when it displays the log. Workaround: This issue is due to decimation used to optimize performance of viewing larger data sets and only affects the view of the data (not the actual data)
| |||||
| 181585 Return | LabVIEW code generation from SignalExpress not working correctly LabVIEW code generation from LabVIEW SignalExpress and the LabVIEW SignalExpress Express VIs work correctly when you install LabVIEW SignalExpress 3.0 or 2009 and the device drivers included on the August 2008 or later Driver DVD. However, if you later install older versions of NI device drivers, such as the NI-DAQ 8.7.1 or 8.7.2 drivers, or if you install NI Sound and Vibration Measurement Suite 6.0 or earlier, LabVIEW code generation and the LabVIEW SignalExpress Express VIs do not work correctly. Workaround: Do not use pre-Aug 2008 Device Drivers with SignalExpress 3.0 and higher
| |||||
| 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 lLarge 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
| |||||
Document last updated on 11/30/2009