��<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <script type="text/javascript"> var L_WWW_Trademark = "http://www.ni.com/cgi-bin/redirect.cgi?dest=infcoprod&src=help&openagent&code=rdtrad"; function WWW(url) { var urlWindow; urlWindow = window.open(url, "New", "directories=yes,location=yes,menubar=yes,resizable=yes,scrollbars=yes,status=yes,toolbar=yes"); } </script> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=UTF-16"> <title>LabVIEW SignalExpress Readme</title> <style type="text/css"> /***************************************************/ /* MINIMAL STYLES */ /* The following section defines styles that every HTML Help project should need. */ /* Specifies White Background color */ body {background-color:#ffffff} /* The default style of P is red to alert you that you need to apply a style class, such as Body. */ P { margin-top:6.00pt; margin-bottom:6.00pt; font-family:Verdana; font-size:8pt; color: #000000; } BR { font-size:4.00pt; } H1,H2,H3,H4,H5,H6 { color:#000000 } /* Use H1 for all topic headings. */ H1 { margin-top:3.00pt; margin-bottom:3.00pt; font-family:Verdana; font-size:12pt; font-weight:bold; } /* Use H2 for second-level headings. */ H2 { margin-top:9.00pt; margin-bottom:3.00pt; font-family:Verdana; font-size:10pt; font-weight:bold; } /* Use H3 for third-level headings. */ H3 { margin-top:6.00pt; margin-bottom:3.00pt; font-family:Verdana; font-size:8pt; font-weight:bold; } /* Use H4 for fourth-level headings. */ H4 { margin-top:3.00pt; margin-bottom:3.00pt; font-family:Verdana; font-size:8pt; font-weight:bold; } /* H5 and H6 have the same definition as H4 because you should not need this level of heading in one topic. If you need to use H5 or H6, consider breaking up your topic into more than one topic. */ H5 { margin-top:3.00pt; margin-bottom:3.00pt; font-family:Verdana; font-size:8pt; font-weight:bold; } H6 { margin-top:3.00pt; margin-bottom:3.00pt; font-family:Verdana; font-size:8pt; font-weight:bold; } /* Use the Body style class for normal paragraphs. */ P.Body { margin-top:6.00pt; margin-bottom:6.00pt; font-family:Verdana; font-size:8pt; color:#000000; } /* Use the Anchor style class for graphic references on a line by themselves. */ P.Anchor { margin-top:6.00pt; margin-bottom:6.00pt; font-family:Verdana; font-size:10pt; color:#000000; } /* Use the Indent style classes to indent a paragraph. If you need to indent text below a list item, use <br><br> to start the new paragraph within the same set of <li></li> tags. If you need to indent a list within another list, nest the indented list within the first list's set of <ol></ol> or <ul></ul> tags. */ P.Indent1 { margin-left:12.00pt; margin-top:6.00pt; margin-bottom:3.00pt; font-family:Verdana; font-size:8pt; color:#000000; } P.Indent2 { margin-left:24.00pt; margin-top:6.00pt; margin-bottom:3.00pt; font-family:Verdana; font-size:8pt; color:#000000; } P.Indent3 { margin-left:36.00pt; margin-top:6.00pt; margin-bottom:3.00pt; font-family:Verdana; font-size:8pt; color:#000000; } /* Use the LI style for all list items. */ LI { margin-top:3.00pt; margin-bottom:3.00pt; font-family:Verdana; font-size:8pt; color:#000000; } /* Use the OL style for numbered lists. You do not have to type the number for each list item in a numbered list. */ OL { margin-left:18.00pt; margin-top:3.00pt; margin-bottom:3.00pt; text-indent:0pt; font-family:Verdana; font-size:8pt; color:#000000; list-style-type: decimal; } /* Use the OL style for numbered lists. Nested lists will use the bullet types according to the nesting scheme below */ ol ol {list-style-type:lower-alpha} ol ol ol {list-style-type:decimal} ol ol ol ol {list-style-type:lower-alpha} ol ol ol ol ol {list-style-type:decimal} ol ol ol ol ol ol {list-style-type:lower-alpha} ol ol ol ol ol ol ol {list-style-type:decimal} ol ol ol ol ol ol ol ol {list-style-type:lower-alpha} /* Use the EquationNum style class for numbered lists of equations. You do not have to type the number for each list item in a numbered list. */ OL.EquationNum { margin-left:36.00pt; margin-top:3.00pt; margin-bottom:3.00pt; text-indent:0pt; font-family:Verdana; font-size:8pt; color:#000000; list-style-type: decimal; } /* Use the List-abc style class for lettered lists. You do not have to type the letter for each list item in a lettered list. */ OL.List-abc { margin-left:18.00pt; margin-top:3.00pt; margin-bottom:3.00pt; text-indent:0pt; font-family:Verdana; font-size:8pt; color:#000000; list-style-type:lower-alpha; } /* Use the UL style for bulleted lists. You do not have to type the bullet for each list item in a bulleted list. */ UL { margin-left:12.00pt; text-indent:0pt; margin-top:3.00pt; margin-bottom:3.00pt; font-family:Verdana; font-size:8pt; color:#000000; list-style-type: disc; } /* Use the UL style for bulleted lists. Nested lists will use the bullet types according to the nesting scheme below. NOTE: hyphen.gif required in same directory as minimal.css */ ul ul {list-style-image:url(hyphen.gif)} ul ul ul {list-style-image:none;list-style-type:disc} ul ul ul ul {list-style-image:url(hyphen.gif)} ul ul ul ul ul {list-style-image:none;list-style-type:disc} ul ul ul ul ul ul {list-style-image:url(hyphen.gif)} ul ul ul ul ul ul ul {list-style-image:none;list-style-type:disc} ul ul ul ul ul ul ul ul ul{list-style-image:url(hyphen.gif)} /* Use the List-Box style class for bulleted lists with boxes instead of bullets. You do not have to type the box for each list item in a box list. */ UL.List-Box { margin-left:12.00pt; margin-top:3.00pt; margin-bottom:3.00pt; text-indent:0pt; font-family:Verdana; font-size:8pt; color:#000000; list-style-type: square; } /* Use the List-Diamond style class for bulleted lists with diamonds instead of bullets. You do not have to type the diamond for each list item in a diamond list. */ UL.List-Diamond { margin-left:12.00pt; margin-top:3.00pt; margin-bottom:3.00pt; text-indent:0pt; font-family:Verdana; font-size:8pt; color:#000000; list-style-image:url(diamond.gif); } /* Use the List-Hyphen style class for bulleted lists with hyphens instead of bullets. You do not have to type the hyphen for each list item in a hyphen list. */ UL.List-Hyphen { margin-left:12.00pt; margin-top:3.00pt; margin-bottom:3.00pt; text-indent:0pt; font-family:Verdana; font-size:8pt; color:#000000; list-style-image:url(hyphen.gif); } /* Use the Borderless style class for tables that do not need borders, such as for 2-column or 3-column lists with no headings. */ Table.Borderless { border:none; } /* Use the Bordered style class for tables that need borders. */ Table.Bordered { border-width: 1pt; border-style: solid; border-color: #000000; border-collapse: collapse; } /* Use the Borderless-Wide style class for tables that do not need borders and that you want to stretch to fill the entire topic width. */ Table.Borderless-Wide { border:none; width:100%; } /* Use the Bordered-Wide style class for tables that need borders and that you want to stretch to fill the entire topic width. */ Table.Bordered-Wide { border-width: 1pt; border-style: solid; border-color: #000000; width:100%; border-collapse: collapse; } /* Use the TD style for table cells in Borderless or Borderless-Wide tables. */ TD { font-family:Verdana; font-size:8pt; color:#000000; vertical-align:top; padding:3px; } /* Use the Bordered style class for table cells in Bordered or Bordered-Wide tables. */ TD.Bordered { font-family:Verdana; font-size:8pt; color:#000000; vertical-align:top; border-width: 1pt; border-style: solid; border-color: #000000; } /* Use the Icon style class for table cells that contain note, caution, warning, or tip icons, or LabVIEW datatype terminals. */ TD.Icon { width:40px; vertical-align:top; } /* Use the Table-cell-8pt style class for table cells in tables that contain a lot of information and need smaller text to fit it all on one screen to prevent a horizontal scroll bar from appearing. */ TD.Table-cell-8pt { font-family:Verdana; font-size:7pt; color:#000000; } /* Use the TH style for table heading cells in Borderless or Borderless-Wide tables. */ TH { font-family:Verdana; font-size:8pt; color:#000000; font-weight:bold; padding:3px; } /* Use the Bordered style class for table heading cells in Bordered or Bordered-Wide tables. */ TH.Bordered { font-family:Verdana; font-size:8pt; color:#000000; font-weight:bold; border-width: 1pt; border-style: solid; border-color: #000000; } /* Use the Table-cell-8pt style class for table heading cells in tables that contain a lot of information and need smaller text to fit it all on one screen to prevent a horizontal scroll bar from appearing. */ TH.Table-Head-8pt { font-family:Verdana; font-size:7pt; color:#000000; font-weight:bold; } /* Use the Left-Align style class for table heading cells that you want to left align instead of center align. */ TH.Left-Align { font-family:Verdana; font-size:8pt; color:#000000; font-weight:bold; padding:3px; text-align:left; } /***************************************************/ /* CHARACTER FORMATS */ /* The following section defines character formats that every HTML Help project should need. */ /* Use the Dark-Red format for warnings or cautions. */ #Dark-Red { color: #800000 } /* Use the Monospace format for code or syntax examples. */ #Monospace { font-family: Courier New; font-size: 8pt; } /* Use the Monospace-Bold format for messages and responses that the computer automatically prints to the screen. */ #Monospace-Bold { font-family: Courier New; font-size: 8pt; font-weight: bold; } /* Use the Monospace-Italic format to denote text that is a placeholder for a word or value that the user must supply. */ #Monospace-Italic { font-family: Courier New; font-size: 8pt; font-style: italic; } /* Use the Platform format to denote a specific platform. */ #Platform { color: #0000FF; font-weight: bold; } /* Use the Symbol format for characters not in the Verdana character set. Use this format sparingly. When possible, you should use the correct ASCII code for the symbol or use a graphic to recreate the symbol. */ #Symbol { font-family: Symbol; font-size: 8pt; } /* The following styles define the color of links. */ a:link { color: #007700 } a:hover { color: #FF0000 } a:active { color: #FF0000 } a:visited { color: #7F007F } /***************************************************/ /* ACTIVITY STYLES */ /* The following section defines styles that only tutorial-style HTML Help projects should need. */ /* Use the Activity-Objective style class for the objective at the beginning of an activity topic. */ H3.Activity-Objective { color: #800000; } /***************************************************/ /* CODE STYLES */ /* The following section defines styles that you need to format entire sections of code or syntax examples. If you have just a few words you need to format as a code or syntax example, use the Monospace character format. */ P.Code { margin-top:3.00pt; margin-bottom:0.00pt; font-family:Courier New; font-size:8pt; color:#000000; } P.Code1 { margin-left:12.00pt; margin-top:3.00pt; margin-bottom:0.00pt; font-family:Courier New; font-size:8pt; color:#000000; } P.Code2 { margin-left:24.00pt; margin-top:3.00pt; margin-bottom:0.00pt; font-family:Courier New; font-size:8pt; color:#000000; } P.Code3 { margin-left:36.00pt; margin-top:3.00pt; margin-bottom:0.00pt; font-family:Courier New; font-size:8pt; color:#000000; } /***************************************************/ /* FUNCTION STYLES */ /* The following section defines styles that you might need to format function reference help. */ P.F-VI-Code4 { margin-left:48.00pt; margin-top:3.00pt; margin-bottom:0.00pt; font-family:Courier New; font-size:8pt; color:#000000; } P.F-VI-Code5 { margin-left:60.00pt; margin-top:3.00pt; margin-bottom:0.00pt; font-family:Courier New; font-size:8pt; color:#000000; } P.F-VI-Equation { margin-top:9.00pt; margin-bottom:9.00pt; font-family:Verdana; font-size:8pt; color:#000000; } OL.F-VI-EquationNum { margin-top:3.00pt; margin-bottom:3.00pt; text-indent:0pt; font-family:Verdana; font-size:8pt; color:#000000; list-style-type: decimal; } </style> </HEAD> <body> <h1>LabVIEW SignalExpress 2.0 Readme</h1> <p class="Body">January 2007</p> <p class="Body">Afficher ce fichier en <a href="readmeFRA.html" target="_blank">fran�ais</a>.</p> <p class="Body">S0n0�0�0�0�0�0<a href="readmeJPN.html" target="_blank">�e,g��</a>g0h�:y0</p> <p class="Body">This file contains important information about LabVIEW SignalExpress 2.0, including known issues, installation instructions, and compatibility issues. Refer to <em>Getting Started with LabVIEW SignalExpress</em> for information about getting started with LabVIEW SignalExpress. You can access this PDF by selecting <strong>Help&#0187;Getting Started with&#0187;LabVIEW SignalExpress</strong> in the LabVIEW SignalExpress environment.</p> <h2>Installation Instructions</h2> <p class="Body">Place the LabVIEW SignalExpress CD in your CD-ROM drive and follow the prompts through the rest of the installation.</p> <p class="Body"><strong>Note</strong>&nbsp;&nbsp;If you are using Windows 2000, you must install Service Pack 4 and all additional critical updates before you install LabVIEW SignalExpress</body> <p class="Body">Complete the following steps to use LabVIEW SignalExpress with hardware.</p> <ol><li>Install the appropriate driver. For Multifunction DAQ, use NI-DAQmx. For high-speed digitizers, use NI-SCOPE. For signal generators, use NI-FGEN. For digital multimeters, use NI-DMM. All drivers are available on the Driver CD.</li> <li>Shut down the computer.</li> <li>Install the hardware.</li> <li>Restart the computer to complete the software installation.</li></ol> <h2>Compatibility Issues</h2> <p class="Body">To convert a LabVIEW SignalExpress project to a LabVIEW VI, you must have the LabVIEW 7.1 Full Development System or later installed.</p> <p class="Body">LabVIEW SignalExpress is compatible with the following products: <ul> <li>NI-DAQmx 7.3 or later</li> <li>NI-SCOPE 2.7 or later</li> <li>NI-FGEN 2.2 or later</li> <li>NI-HSDIO 1.3.1 or later</li> <li>NI-HWS 1.3.1 or later</li> <li>NI-DMM 2.4.1 or later</li> <li>IVI Driver Toolset 2.0 or later</li> </ul></p> <p class="Body">LabVIEW SignalExpress will install or update the following applications: <ul> <li>MAX 4.2.1</li> <li>LabVIEW Run-Time Engine 7.1</li> <li>LabVIEW Run-Time Engine 8.0</li> <li>LabVIEW Run-Time Engine 8.2</li> <li>IVI Compliance Package 2.0 or later</li> <li>NI-VISA 4.1.0</li> <li>Microsoft .NET Framework 2.0</li> </ul> </p> <p class="Body">LabVIEW SignalExpress also installs the NI Measurement Studio Network Variable and WindowsForms support in the Global Assembly Cache for runtime purposes.</p> <h2>Known Issues</h2> <ul> <li>When you convert a project to a LabVIEW block diagram, some VIs will contain errors. Mass compile the <span class="Monospace">LabVIEW\vi.lib</span> directory to fix the VIs.</li> <li>If you are installing both the System Identification Toolkit 3.0 and LabVIEW SignalExpress 2.0, you must install the System Identification Toolkit 3.0 before you install LabVIEW SignalExpress 2.0. Installing the System Identification Toolkit 3.0 after you install LabVIEW SignalExpress results in an error upon launch of LabVIEW SignalExpress 2.0. To resolve the error, you can uninstall the affected components and reinstall in the correct order. The easiest way to resolve the error is to install the free System Identification Toolkit 3.0.1 upgrade. Refer to <a href="http://www.ni.com" target="_blank">ni.com</a> for more information on obtaining the free System Identification Toolkit 3.0.1 upgrade CD.</li> <li>LabVIEW SignalExpress only supports one version of LabVIEW at a time. When you install LabVIEW SignalExpress, it finds the most current installed version of LabVIEW and installs support for LabVIEW SignalExpress into that version. If you later install a new version of LabVIEW, you need to uninstall and reinstall LabVIEW SignalExpress. When you reinstall, LabVIEW SignalExpress will install support for the new version of LabVIEW.</li> <li>When you convert a project that contains features not supported in LabVIEW to a LabVIEW block diagram, LabVIEW SignalExpress generates a LabVIEW block diagram with one Express VI. You cannot open the block diagram of the generated Express VI. If you include the generated Express VI in a distribution with the LabVIEW Application Builder, you must install LabVIEW SignalExpress to any target computers on which you run the LabVIEW-built application.</li> <li>Registration information is saved on a per-user basis in Windows Vista. When you change users, the user information that appears when you launch LabVIEW SignalExpress may appear incorrectly.</li> <li>Creating a source distribution in LabVIEW of a LabVIEW SignalExpress User Step template VI may fail and return an error. For one possible solution for this error, navigate to the Additional Exclusions page of the Source Distribution Properties dialog box and select the <strong>Remove unreferenced project library members</strong> option to remove the error.</li> <li>LabVIEW SignalExpress only supports one version of LabVIEW at a time for project conversion into LabVIEW. LabVIEW SignalExpress only installs support for the latest version of LabVIEW installed on the system. However, when you convert a LabVIEW SignalExpress project to a LabVIEW block diagram, LabVIEW SignalExpress calls the last version of LabVIEW opened on the system. If the last version of LabVIEW open on the system is not the version of LabVIEW with LabVIEW SignalExpress support installed, you must launch the version of LabVIEW with LabVIEW SignalExpress support and re-generate the project.</li> <li>The <em>Getting Started with LabVIEW SignalExpress</em> manual incorrectly states that LabVIEW SignalExpress is compatible with Windows NT. LabVIEW SignalExpress is compatible with Windows Vista/XP/2000.</li> <li>The <em>LabVIEW SignalExpress Help</em> incorrectly states that LabVIEW SignalExpress LE by default does not display steps that are only available in the Full Edition. LabVIEW SignalExpress LE by default does display steps that are only available in the Full Edition.</li> <li>The Statistics step does not accept U32 data as an input.</li> <li>When viewing scalar data in a table, the data history of the scalar data is not saved unless you previously viewed the scalar data in a chart display. </li> <li>The Save to ASCII/LVM step does not save any units associated with the specified data. </li> <li>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.</li> <li>LabVIEW prompts you with a warning dialog box during project conversion if LabVIEW loads <span id="Monospace">vi.lib</span> subVIs from the <span id="Monospace">National Instruments\LabVIEW</span> directory rather than from the directory in which you saved your LabVIEW SignalExpress project. Click the <strong>OK</strong> button to resume conversion.</li> <li>The Load from ASCII, Load from LVM, and Load from SPICE steps convert up to 20 imported signals into the LabVIEW VI during project conversion. If you want to import more than 20 signals and then convert the project to a LabVIEW VI, use two or more Load from ASCII, Load from LVM, or Load from SPICE steps.</li> <li>You cannot convert a LabVIEW SignalExpress project to a LabVIEW block diagram if a hardware step in the project uses software triggers.</li> <li>Text in any step configuration view does not display correctly if you set your monitor resolution to 1400 x 1050 or higher or if you use large fonts.</li> <li>Due to driver and operating system issues, absolute time stamps have an inaccuracy of 100 ms to 200 ms. National Instruments recommends that you use relative time stamps.</li> <li>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.</li> <li>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. To work around this issue, 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.</li> </ul> <hr> <p class="Body"><strong>Copyright</strong></p> <p class="Body">&#0169; 2004&#8211;2007 National Instruments Corporation. All rights reserved.</p> <p class="Body">Under the copyright laws, this publication may not be reproduced or transmitted in any form, electronic or mechanical, including photocopying, recording, storing in an information retrieval system, or translating, in whole or in part, without the prior written consent of National Instruments Corporation.</p> <p class="Body"><strong>Trademarks</strong></p> <p class="Body">National Instruments, NI, <span class="Monospace">ni.com</span>, and LabVIEW are trademarks of National Instruments Corporation. Refer to the <em>Terms of Use</em> section on <span class="Monospace">ni.com/legal</span> for more information about <a href="javascript:WWW(L_WWW_Trademark)">National Instruments trademarks</a>.</p> <p class="Body"><strong>Patents</strong></p> <p class="Body">For patents covering the National Instruments products, refer to the appropriate location: <strong>Help&#0187;Patents</strong> in your software, the <span class="Monospace">patents.txt</span> file on your CD, or <a href="http://www.ni.com/patents" target="_blank">ni.com/patents</a>.</p> </body> </html>