Benutzerspezifische Werkzeuge

Information zum Seitenaufbau und Sprungmarken fuer Screenreader-Benutzer: Ganz oben links auf jeder Seite befindet sich das Logo der JLU, verlinkt mit der Startseite. Neben dem Logo kann sich rechts daneben das Bannerbild anschließen. Rechts daneben kann sich ein weiteres Bild/Schriftzug befinden. Es folgt die Suche. Unterhalb dieser oberen Leiste schliesst sich die Hauptnavigation an. Unterhalb der Hauptnavigation befindet sich der Inhaltsbereich. Die Feinnavigation findet sich - sofern vorhanden - in der linken Spalte. In der rechten Spalte finden Sie ueblicherweise Kontaktdaten. Als Abschluss der Seite findet sich die Brotkrumennavigation und im Fussbereich Links zu Barrierefreiheit, Impressum, Hilfe und das Login fuer Redakteure. Barrierefreiheit JLU - Logo, Link zur Startseite der JLU-Gießen Direkt zur Navigation vertikale linke Navigationsleiste vor Sie sind hier Direkt zum Inhalt vor rechter Kolumne mit zusaetzlichen Informationen vor Suche vor Fußbereich mit Impressum


LabVIEW-Installation unter Mac OS-X

LabVIEW-Installationsanleitung für Mac OS-X (in Englisch)

If you have a previous version of LabVIEW installed, you can install LabVIEW 2010 without uninstalling the other version. In this instance, LabVIEW 2010 does not replace the previous version of LabVIEW, which remains installed.

Refer to the LabVIEW Release Notes for more information about installing LabVIEW on Mac OS X.

Known Issues

You can access the software and documentation known issues list online. Refer to the National Instruments Web site for an up-to-date list of known issues in LabVIEW 2010.

Additions to the LabVIEW Help

The following list contains additional changes to LabVIEW that are not included in the LabVIEW Help, the LabVIEW Upgrade Notes, or both:

  • The Mass Compile dialog box includes the Include warnings for read-only VIs checkbox, which determines whether the mass compile results include warnings next to the read-only VIs.
  • The Advanced TDMS palette includes the TDMS Generate Random Data VI, which generates random data that you can use to test the performance of the Advanced TDMS VIs and functions.
  • The TDMS Configure Asynchronous Writes function does not include the data mode input.
  • On the Web Server page of the Options dialog box, the Configure Web Application Server button launches NI Web-based Monitoring and Configuration on the local system.
  • On the Web Server page of the Options dialog box, the Enable Web Server checkbox is renamed Enable Remote Panel Server.
  • In the Icon Editor dialog box, select Edit»Import Icon from Owning Library to import the icon of the owning project library. LabVIEW creates a user layer with the name NI_Library and with the icon of the owning library as the glyph. If a user layer with that name already exists, the new user layer overwrites the existing user layer.
  • The VISA Find Resource function returns error code -1073807343 if the system locates no devices.
  • LabVIEW 2010 does not support the Disconnect Polys And Typedefs method.
  • If you wire a combination of signed and unsigned integers to the upper limit, x, and lower limit inputs of the In Range and Coerce function, the data type of the coerced(x) output must be large enough to represent the full range of possible input values. If the coerced(x) output is an unsigned integer, the signed input values must be positive because an unsigned integer cannot represent a negative number.
  • When a change to a VI in a packed project library impacts the inplaceness of the connector pane, by default the caller VI adapts to inplaceness changes. As a result, you do not need to recompile the VI that calls the packed library. If you want the caller VI to recompile when the inplaceness changes, remove the checkmark from the Callers adapt at run time to Exported VI connector pane state checkbox on the Connector Pane State page of the Packed Library Properties dialog box. If you make a non-inplaceness change to a VI in a packed library, the VI must recompile.
  • Due to compiler optimizations in LabVIEW 2010, VIs can execute faster but may take up to five times longer to compile. You might not notice these changes unless you are loading a large VI. Refer to the National Instruments Web site for more information about compiler optimizations.