1 / 10

Useful LabVIEW 8.20 Features

Useful LabVIEW 8.20 Features. CS Workshop 2007 February 2nd, 2007 Holger Brand, GSI. Project Explorer Libraries Shared Variables Custom DSC IO Server Periodic OnChange Classes Simple class hierarchy Online Tutorial: How to create and inherit from LVOOP classes

gittel
Télécharger la présentation

Useful LabVIEW 8.20 Features

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Useful LabVIEW 8.20 Features CS Workshop 2007 February 2nd, 2007 Holger Brand, GSI

  2. Project Explorer Libraries Shared Variables Custom DSC IO Server Periodic OnChange Classes Simple class hierarchy Online Tutorial: How to create and inherit from LVOOP classes LVOOP Examples, Graphics.lvproj, Board Testing.lvproj LVOOP DesignPatternshttp://wiki.gsi.de/cgi-bin/view/NIUser/LabVIEWObjectOrientedProgramming Referenced Object, Singleton, Agent Factory, Hierarchy Composition, Delegation, Aggregation, Specification, Channeling, Visitor XControls -> Talk of D. Beck Contents H.Brand@gsi.de

  3. Project Explorer • A Project contains all project resources • Documents • *.vi, *.doc, *.html, *.c etc. • organized in Folder and libraries • Hardware configuration • Local hardware • Remote systems • Documents • *.vi, *.doc, *.html, *.c etc. • Hardware configuration • Dependencies • Build Specifications • A Project is an Application instance • closed shell or sandbox! • e.g. Queues with the same name are different in different application instances and do not know each other! - You can supply a project description an define condtional disable symbols H.Brand@gsi.de

  4. LabVIEW Libraries • A Library defines a namespace • Like package in Java • So, different libraries can contain different VIs with the same name. • A Library-VI name is always automatically prefixed with the library name • A Library-VI is part of the owning Library and can not be opened without. • It has a version numer, default icon, etc • Library items can have public or private scope • Private items can be accessed from within the library only • A library has its own DSC settings H.Brand@gsi.de

  5. Successor of DataSocket variables Variable Types Single Process Time stamped, Real-Time-FIFO Network published Buffered, Bind to Source, e.g. OPC item, Single Writer, Real-Time-FIFO Time-Triggered IEEE 1588-Standard, Deterministic Ethernet Data Types All standard data types and array of them, Variant, Bit-Field Custom Typedef Can be linked to DataSocket, OPC, ChannelAccess, Custom-IO Server Can have DSC properties: Scaling, Alarming, Trending, Security etc. Shared Variable are alway part of a LabVIEW Library Shared Variables I H.Brand@gsi.de

  6. Tools Shared VariableVariable Manager, Multiple Variable Editor, Front Panel Binding Mass Configuration DSC-Module Monitor Variables, View Historical Data Migrate: Configuration (.scf), Front Panel Security VI Based Server Wizard On Input Change Periodic Examples Help->Find Examples...->Browse by Task->Fundamentals->Shared Variable->Shared Variable Client – Server.lvproj Help->Find Examples...->Browse by Task->Toolkits and Modules->DataLogging and Supervisory Control->Fundamentals->DSC Event Structure Demo.lvproj Shared Variables II H.Brand@gsi.de

  7. An I/O server is an application that communicates with and manages input/output devices such as programmable logic controllers (PLCs), remote input/output devices, remote Shared Variable Engines, and data acquisition (DAQ) plug-in devices. These servers read selected input items and write to the selected input items on demand. The I/O server starts running when you deploy the project library that defines the server and stops when you stop or undeploy the project library. Applications can be used as OPC Server if the Installer includes the Shared Variable Engine Custom DSC IO Server I H.Brand@gsi.de

  8. You might want to create a custom I/O server in the following example situations: You do not have an OPC server to handle communication between hardware and LabVIEW. Custom VI-based I/O servers can interface directly with the hardware and expose data items through the Shared Variable Engine. You want to create a simulation server to emulate hardware connections. You can create two types of custom I/O servers: Periodic I/O Server does not need controls or indicators on the connector pane is running continuosly On Input Change I/O Server needs controls and indicators on the connector pane is called on change of input control value MyIOServer.lvproj MyPeriodicIOServer, MyOnChangeIOServer, MyOnChangeDIMServer Custom DSC IO Server II H.Brand@gsi.de

  9. Custom DSC IO Server III • Periodic IO Server On Change IO Server H.Brand@gsi.de

  10. Create a new LV-Project: MyFirstClass Create a new class: Automobile Add Description Edit Icons Add Attributes: Number of Gears, Number of Doors, Make, Model Add Methods: setAutoAttribute, getAutoAttribute, Start, Stop Create Subclasses Truck Add Attributes: Short Bed?, Four Wheel Drive Add Methods: setTruckAttribute, getTruckAttribute Car Add Attribute: Number of Seats Add Methods: setCarAttribute, getCarAttribute Create a Main.vi and use that classes Simple Class Hierarchy H.Brand@gsi.de

More Related