LAVA 1.0 Content

Approved 3-10-10

Name: BlinkingLED Submitter: LAVA 1.0 Content Submitted: 04 Jul 2009 Category: X-Controls LabVIEW Version: 8.6 Version: 1.0.0 License Type: BSD (Most common) Make this available on the VI Package Network?: Undecided Copyright © 2009, Martin Weiss. All rights reserved. Author: Martin Weiss --see readme file for contact information Description: Implements a blinking LED with adjustable blinking interval. The value of this XControl is the blinking interval in milliseconds. Minimal value allowed is 100ms. This XControl acts as an indicator only. Inspired by Aristos Queue's "Scrolling LED XControl" example. Many thanks for that! Dependancies: None Change Log: 1.0.0: Initial release. Click here to download this file

Name: simple gauge LabVIEW XControl Submitter: LAVA 1.0 Content Submitted: 04 Jul 2009 Category: X-Controls LabVIEW Version: 8.6 Version: 0.0.1 License Type: GNU Public Make this available on the VI Package Network?: Undecided GISXControl Technology Preview Version 0.0.1 ============================================ Copyright © 2009, Technogerma Systems France S.A.R.L. All rights reserved. ---------------------------------------- Description: ---------------------------------------- This project is a technology preview of a simple gauge LabVIEW XControl limited in features and visual aspect. The XControl is based on a C wrapper on our Graphical Instruments Solution (GIS). GIS is a set of instruments currently in development (Buttons, LEDs, Gauges, Knobs, Sliders, LCDs, Switches, Tanks, Thermometers, ...) with the following main features: - C++ library based on Qt framework - Multiplatform (Mac, Linux, Windows) - Skin system based on SVG and XML to customize the appearance of each instrument - Property system to customize the behaviour of each instrument - Double license: Open source and commercial --------------------------------------- Aim: ---------------------------------------- The purpose of this technology preview is to see if such a library of XControls could be usefull and to get feedbacks from LabVIEW users community. --------------------------------------- Usage: ---------------------------------------- Windows 1. Copy mingwm10.dll, QtCore4.dll, QtGui4.dll and QtSvg4.dll into your LabVIEW installation directory (e.g. C:\Program Files\National Instruments\LabVIEW 8.6) 2. Open the project 3. Run the demo.vi Linux and Mac Not yet available. If you are interested in a Linux or Mac version please contact us. --------------------------------------- Known issues: ---------------------------------------- - Performance issue when the value change rate is too fast. This will introduce a desynchronization between the current value and the displayed value. This is due to the XControl architecture that stacks data changed events. See http://forums.lavag.org/XControl-DataChanged-events-stacking-t13459.html for more details. --------------------------------------- Contact: ---------------------------------------- If you have questions or if you want to give some feedback you can send mail to gisxcontrol@technogerma.fr or post directly on GISXControl LAVA support forum thread. ---------------------------------------- License: ---------------------------------------- - XControl is released under the GNU General Public License version 3 (see license.txt for details) - QLVXControl library is the property of Technogerma Systems France S.A.R.L. but is freely redistribuable ---------------------------------------- Third party: ---------------------------------------- - Pointer System V1.1.2 by Bjornar Svingen (Creative Commons Attribution 2.5 License) Click here to download this file

Name: Strings Levenshtein Distance Submitter: LAVA 1.0 Content Submitted: 03 Jul 2009 File Updated: 03 Jul 2009 Category: General LabVIEW Version: 8.5 Version: 1.0.0 License Type: GNU Public Potentially make this available on the VI Package Network?: Yes Copyright © 2008, Leif S. Kirschenbaum All rights reserved. Author: Leif S. Kirschenbaum --see readme file for contact informaation. Description: This VI computes the Leventshein distance between two strings. It is based on the pseudocode found in Wikipedia online: http://en.wikipedia....shtein_distance "The Levenshtein distance between two strings is given by the minimum number of operations needed to transform one string into the other, where an operation is an insertion, deletion, or substitution of a single character." It functions by creating a step matrix which is N+1 x M+1, where N and M are the lengths of the two strings to be compared, and filling in each cell of this matrix indicating how many steps (insertions, deletions, character substitutions) are required. The total number of steps to convert one string into the other is given by the last cell in the matrix. Change Log: 1.0.0: Initial release of the code. Click here to download this file

Name: Data Repository with INI files (not a Source-Code-Control) Submitter: LAVA 1.0 Content Submitted: 03 Jul 2009 Category: Database & File IO LabVIEW Version: 7.0 Version: 1.0.1 License Type: Creative Commons Attribution 3.0 Potentially make this available on the VI Package Network?: Undecided Copyright © 2006, Sam Behashtei All rights reserved. Author: Sam Behashtei --see readme file for contact information Description: Data.vi V1.0.0 LabVIEW Versions 7.0,7.1 The purpose of the VI is to demonstrate how to save all your application’s parameter in one central INI file. Using this method will reduce errors and eases debugging. This Data VI has the following functionality 1: Can be used as a Central Data Repository for your Application. 2: It allows access to the Data via SET/GET method. 3: It uses semaphores to stop any race conditions and (concurrent SET access to data) It will allow parallel "READ-ONLY" access to the Data. 4: A Function to Save all of the DATA to an INI file. 5: A Function to Load a previously saved Data from the INI file. Library Dependency: OpenG: oglib_variantconfig-2.6- OpenG: oglib_lvdata-2.5-1 http://web.archive.org/web/20071205114227/http://www.openg.org/ Version History: 1.0.1: Added LabVIEW 7.0 code. 1.0.0: Initial release of the code. Click here to download this file

Name: Class Iconizer Submitter: LAVA 1.0 Content Submitted: 03 Jul 2009 Category: LabVIEW OOP LabVIEW Version: 8.2 Version: 1.2.0 License Type: Creative Commons Attribution 3.0 Potentially make this available on the VI Package Network?: Undecided Copyright © 2006, jimi All rights reserved. Author: jimi --see readme file for contacct information Description: This tool allows user to apply new icon templates to LabVIEW classes. New template is applied to each item inside the class. User can define which parts of the template is transparent so that the template can be overlaid on top of the existing icons. Version History: 1.0.0: Initial release of the code. Click here to download this file

Name: In-Window Popup Submitter: LAVA 1.0 Content Submitted: 03 Jul 2009 Category: User Interface LabVIEW Version: 8.2 Version: 1,0,2 License Type: Creative Commons Attribution 3.0 Potentially make this available on the VI Package Network?: Undecided The inspiration for this VI came from a popular web javascript image viewer that darkens the background and popups a box in the current browswer window. This is also a great concept for a user interface that forces the user's attention onto what you want them to see. Summary & Features: Uses a tab control and a cluster with a constant, semi-transparent PNG image to display inline poup box Uses any type and number of controls you place in the tab control Dynamically sizes and recenters to fill up the front panel window Stops execution and removes popup from view when specified controls reaches a desired value Returns the values of all controls on the page being displayed Planned Future Revisions Selectable color for overlay Popup effects This is my first submission! Enjoy! Instructions: 1. Put these two controls anywhere on the FP of the VI you will use them in. Both the tab control and the overlay are automatically sized to fit and centered within the FP window bounds. 2. Rename the controls to whatever you would like. The default names are "Popup" for the tab control and "Overlay" for the overlay cluster. Don't forget to hide the labels on these controls and to hide the tabs on tab control. 3. Add pages to the tab control and add your own controls inside each page. You can place as many as you need. 4. To use popup, call this VI. Wire in the references to the tab control and overlay cluster. Selectively show which tab you want the user to see with the "Tab to Show" string control. Use the controls on the tab control as normal. 5. You can handle control value changes either with a event structure or let this VI stop executing when a control reaches a certain value. For the latter, wire "Control to Wait For" cluster witht he reference of the control you are waiting for and the desired value. This VI uses an event structure with a 50ms timeout to wait for the control value change and then returns an array of all controls on the page specified in "Page to Show." 6. If you do not wire "Control to Wait For" cluster, you must use the "In-Window Popup Destroy.vi" to remove the popup. Click here to download this file

Name: String AutoComplete Submitter: sam Submitted: 02 Jul 2009 File Updated: 03 Jan 2011 Category: User Interface LabVIEW Version: 7.1 License Type: Creative Commons Attribution 3.0 Copyright © 2006, Sam Behashtei All rights reserved. Author: Sam Behashtei --see readme file for contact information Description:: In most modern application, in web based application, the user input Textbox, or (String-Control) have the ability to Auto-Complete the words being typed. This utility helps the programmer give the Auto-Complete behavior to a LabVIEW String. Version History: 1.0.1: The mechanism to store suggestion list has been changed. 1.0.0: Initial release of the code. Click here to download this file

Name: log event error Submitter: LAVA 1.0 Content Submitted: 02 Jul 2009 File Updated: 02 May 2010 Category: General Version: 1.0.0 LabVIEW Version: 7.1 License Type: Creative Commons Attribution 3.0 This VI logs an Application event associated with "error" to the Windows Event Viewer (eventvwr.exe). An event description includes the "error" source and code along with the leading "reason". This information can be viewed by opening an Event Properties window in the Event Viewer. Click here to download this file

Hoovah, you should get the whole library directory, these VIs are located in the Utilities\Padding folder. Ton

I wrote an continious digest version of the MD5 OpenG routine. You can download the source from sourceforge. Look for Continous MD5 inside the public folder. I am interested in how this one goes in your benchmark. Ton Hmm, somehow I cannot upload...

QUOTE (jlokanis @ Jun 9 2009, 08:52 PM) So you know which VIs are troublesome (from trial and error), what you could do is build an additional library with just these VIs placed inside a container VI (similar to an 'old' tree VI), and load this container VI into memory of your RTE, I am not sure if this will work since it might require a recompile of the library VIs. Another option is to exclude the vi.lib but have a call-back VI loaded with OpenG builder that includes the troublesome VIs into your distro. My advice is to open up the builder sourcecode and see which specific call-back VI you need. Ton

QUOTE (MJE @ Jun 5 2009, 02:31 PM) You mean like a project integration tool? Or could we build a better project explorer? Ton

Based on LabVIEW scripting I have started a 'Polymorphic VI Editor', the changes from the NI one will be: A tree interface to the selector menu to easier build a good menu structure Drag and drop support inside the selector menu tree Drag and drop of an external VI onto an 'Add' button Creation of new polymorphic VIs Opening up of existing polymorphic VIs Is anyone interested in helping out? PM me. The source code will be hosted on the LAVAG Code repository at Google Code and the product will be released onto the LAVA CR. Ton

QUOTE (Darren @ Jun 4 2009, 11:54 AM) Thanks alot

is there a way to clear the display using a reset button? Many Thanks

hope they could create a vi tat allows user to zoom in or zoom out if the labview gui is too big or too small.

QUOTE (Aristos Queue @ May 29 2009, 06:50 PM) Thanks a lot- But why you didn't included your help files? :question:

as the title have stated. i would like to know how do i control/interface a maxon dc motor by using labview. thanks.