LabVIEW LEGO MINDSTORMS NXT Module Programming Guide Manual

LabVIEW LEGO MINDSTORMS NXT Module Programming Guide Manual
Pages 97
Views 837
Downloads : 2 times
PDF Size : 572.7 KiB

Summary of Contents

LabVIEW LEGO MINDSTORMS NXT Module Programming Guide Manual

  • Chapter 1IntroductionLabVIEW LEGO MINDSTORMS NXT Module1-2ni.comAssumptionsThis document assumes that you are using the LabVIEW LEGO MINDSTORMS NXT Module with LabVIEW 2009. This document also assumes that you are familiar with the following LabVIEW programming concepts:•Data types: integers, Booleans, strings, arrays, and clusters•Basic VIs and functions used with the listed data types•Case, loop, and sequence structures•Usage of subVIs•Properties and methodsRefer to the LabVIEW Help, available in LabVIEW by selecting Help»Search the LabVIEW Help, for more information about these concepts.The module provides special palettes for working with both front panels and block diagrams. These palettes contain only supported LabVIEW features. You are not required to use these palettes, but using them will help you remember which features the module supports.This document assumes that you are using official LEGO or NI NXT firmware. Refer to the LEGO MINDSTORMS Web site at actionURI(http://mindstorms.lego.com/):mindstorms.lego.com for more information about firmware updates. NXT Firmware ConceptsThe following sections provide a brief summary of how LabVIEW concepts correspond to NXT firmware concepts. Refer to the LEGO MINDSTORMS Web site actionURI(http://mindstorms.lego.com/):at mindstorms.lego.com for the NXT SDK and HDK documents describing the NXT hardware and firmware platform.NXT Programs and LabVIEW VIsWhen you choose a VI to compile and download to an NXT brick using the module, that VI becomes the top-level VI of the corresponding program file on the NXT brick. The module compiles the top-level VI and all of its subVIs into one program file, and then downloads the program file to the NXT brick. You can think of the top-level VI and its subVIs as the complete source code for the resulting binary program file.Note the implication that subVIs have no analogous feature on the file system of the NXT brick. Inside the program file, subVIs become shared subroutines. Refer to the 17,SubVIs section of this document for more information about using subVIs.