Leaderboard

Package for working with JSON. Uses high-speed text parsing, rather than building an intermediate representation as with prior LabVIEW JSON libraries (this is much faster). Allows easy working with "subitems" in JSON format, or one can convert to/from LabVIEW types. Uses the new "malleable VIs" of LabVIEW 2017 to convert to any LabVIEW type directly. JSON text makes use of a form a JSON Path notation, allowing easy and rapid access to the subitems of interest. Requires LabVIEW 2017 and install by VIPM 2017 or later. Original conversation about JSONtext. On the LabVIEW Tools Network. JDP Science Tools group on NI.com. Copyright 2017 JDP Science Limited

Hi everyone, Since GRBL standard is open source, I decided to post my Library that I used in LabVIEW to interface a standard GRBL version 1.1 controller. Not all GRBL function has been integrated, but this is a very good start. Enjoy and let me know your comments. Benoit

This VI program implements the Discrete Fourier Transform (DFT) to draw any drawn shape outline with epicycles as demonstrated in this video. For more information on the mathematical principles, please watch this video by Mathologer. How to Use: 1.Unzip the attached zip file. 2.Open Main.vi file. 3.Run the VI. 4.Draw a shape. 4.Enjoy animation!

There it is. The complete library for the MCP2221A. I2c adapter, I/O in a single IC. I love that one. Let me know if any bug is found. I try to make that library as much convenient as possible to use. Two version available 32 bit and 64 bit. little note: to open by serial number, the enumeration need to be activated on the device first. (open by index, enable the enumeration) It needs to be done only once in the life time of the device. PLEASE do not take ownership of this work since it is not yours. You have it for free, but the credit is still mine... I spent many hours of my life to make it works.

LabVIEW Task Manager v1.10.0 (for LV2013+) This code is Open-Source, and free of charge Authors: Ravi Beniwal, Tim Vargo LAVA Names: Ravi Beniwal, TimVargo Contact Info: Contact via PM at the LAVA site (http://lavag.org) LabVIEW Versions Supported: LV2013 and up LabVIEW Versions Tested on: LV2017 LV2016 LV2013 Dependencies: GPower Error & Warning = 1.2.0.14 lava_lib_tree_control_api >= 1.0.1-1 NI SmartBalloon = 2.0.0.2 OpenG Application Control Library >= 4.1.0.7 OpenG Comparison Library >= 4.0.0.3 OpenG Array Library >= 4.1.1.14 OpenG Error Library >= 4.2.0.23 OpenG File Library >= 4.0.1.22 OpenG LabVIEW Data Library >= 4.2.0.21 OpenG String Library >= 4.1.0.12 LAVA Palette >= 1.0.0.1 Description: LabVIEW Task Manager is a debugging tool for use during LabVIEW code development. An expandable/collapsible tree diagram displays detailed information (both static and dynamic) on all VIs in memory, belonging to a selected project/target. It allows for interacting with single or multiple selected VIs at a time, and includes the following major features: Selection of project/target Lists all VIs in memory, grouped by class/library or disk folder, or a flat list Searches for and enumerates clones in memory DropIn VI for including dynamically referenced clones (Clone Beacon) 'Refresh Now' (F5) re-reads all VIs in memory and adds new ones to the tree Displays VI name, owning class/library, state, path, data size & code size Displays VI FP Behavior, Reentrant?, Reentrancy Type, Paused? & Highlight? Group by Class/Library or Folder, or display a Flat List Sort by any column, ascending or descending Filter out item types vi, ctl, and vit/ctt Filter out vi.lib and global VIs Filter out items from being displayed, per folder paths. Tracking of, and ability to toggle, execution highlighting on multiple selected VIs Tracking of paused VIs with ability to Pause/Resume/TogglePause multiple selected VIs DropIn VI for pausing only while debugging If a clone initiates a pause, a different pause symbol is used for all clones of that same reentrant original VI Select multiple VIs and open or close their FPs or BDs Double Click a VI from the tree to bring the BD (first choice) or FP to front, if already open Select multiple top-level VIs and Abort them Remotely close any VI's Front Panel Installation and instructions: Install this tool by using the VI Package Manager to install its associated package file (.vip). Installation requires VIPM 2014 or higher, which is available for free from jki.net (http://jki.net/vipm). Known Issues: Cannot abort SubVIs launched from remote VI Server or local Asynch Call By Ref

There it is... finaly... Because the code given in the FTDI web page is not convenient, not working and haven't been developed by real LABview programmer, I decided to create a library for the I2C. a version for SPI will come soon. This library is free to use. If FTDI want's it in ther site, I do not allow you to publish it since you didn't help any of your customer with LABview. but of course feel free to publish this link.

Mark Balla Icon editor V2.7 December 2020 Author: Mark Balla Description: This is a text based vi icon editor The purpose is to help quickly create text base icons. The editor can be used in place of the standard NI icon editor or as a stand alone vi. see instructions. Version 2.7 Updated font table to recognize the standard "Small Font" letters used by the NI icon editor. This will improve the OCR function when importing icons generated by the NI Icon editor. Version 2.6 Added quick drop code to allow the user to switch between NI and custom editor. QD_Swap Icon Editor.vi and support folders will be placed in the LabVIEW quick drop folder ..\National Instruments\LabVIEW 20XX\resource\dialog\QuickDrop To switch LabVIEW to a custom icon editor that uses the lv_icon.vi set a shortcut key to call the QD_Swap Icon Editor.vi. Ctrl-Space Ctrl-<<assigned letter key>> To switch LabVIEW to the NI icon editor that uses the lv_icon.lvlibp use the same shortcut key with the Shift key Ctrl-Space Ctrl-Shift-<<assigned letter key>> Version 2.5 Fixed install bug where lv_icon.lvlibp was not being renamed after LV 2016 2.5 was set to 2017 or later. Instructions: LV 2017 to LV2020 + Ver 2.7 + Here is the intended process. Download package from LAVA Install Package Package will install MB icon editor files Package will install QD_Swap Icon Editor.vi in the QD plugins folder Package will copy the lv_icon.lvlibp And rename it to COPY_ lv_icon.lvlibp Package will delete the lv_icon.lvlibp Popup will show stating you are using the custom editor. Open LV Open QD, click configure and select the Ctrl-Key Shortcut Tab at the top Assign a control key to the QD_Swap Icon Editor and click OKWhen you select Ctrl-Space Ctr-<<Assigned Key>> the QD vi will setup the IDE to use my custom editor. The vi will verify there is a copy of the lv_icon.lvlibp And if not create it. The vi will delete the lv_icon.lvlibp From the ..\National Instruments\LabVIEW 20XX\resource\plugins folder When you select Ctrl-Space Ctr-Shift-<<Assigned Key>> the QD vi will setup the IDE to use the NI editor. The vi will copy the COPY_lv_icon.lvlibp and rename the copy to lv_icon.lvlibp LabVIEW will use the lv_icon.lvlibp If it sees it in the plugins folder. If it does not see the lv_icon.lvlibp It will call the lv_icon.vi which is the name of my icon editor. LV 2010 to LV 2016 Ver 2.4 Install using JKI VI Package Manager LV 2009 Ver 2.3 1:Rename the curret LabVIEW 2009 Icon editor LabVIEW 2009\resource\plugins\lv_Icon.vi to a different name so it will not be overwritten. 2: Place the three files (lv_icon.vi, color templates.bin and the folder lv_icon_Subvis) in the LabVIEW 2009\resource\plugins directory. The next time the icon editor is called LabVIEW will use the lv_icon.vi instead of the standard one. There is a button on the editor that will allow you to use NI's editor (Old editor not the new one) when a text icon is not desired. For LabVIEW 8.2 Use the "MB Icon Editor_V2.3_LV82.zip" file For LabVIEW 8.5 Use the "MB Icon Editor_V2.3_LV85.zip" file For LabVIEW 8.6 Use The "MB Icon Editor_V2.3_LV8.6.zip" file

(latest version 5.5 - November 3, 2015 - LabVIEW 2010) Chess Game with artificial intelligence 100% LabVIEW AI : algorithm MinMax + Alpha-Beta pruning two game levels : "novice" and "Jedi" editing interface (edit on/off) a) moving mode : left-clic on the starting square, left-clic on the destination square b) positioning mode : right-clic on a square opens a context menu to choice the piece. This engine 5.5 is stronger than the previous engine 5.0 (Jedi level) unzip - run "Chess_ouadji.vi" Have fun! ouadji, if you like this Chess Game, a kudo is most welcome! (here - first post)

This VI allow an easy way to create HTML color table in the LabVIEW report generation toolkit. This VI should be connected to the "Append User Formatted HTML to Report.vi". For this version, all the column are the same size. But alignment and color of each cell can be defined. Please rate this file if you download it. It's free... you can at least give some second of your time to rate it... I spend some hours to make it... Enjoy

An extensive library for passing messages between parallel processes. Generalizes the communication method, allowing the message sender to use the method provided by the receiver. Supported communication methods include wrappings of simple queues, user events, and notifiers, as well a more complex channels such as a TCP server and client. In addition, one can configure simple forwarding addresses (“Observers"), which can send messages to multiple destinations, optionally with modifications such as adding a prefix to the message label, relabelling, or substituting a different message. Communication patterns supported include request-reply (asynchronous or synchronous), where the reply is sent to a "reply address" attached to the request, and register-notify, where one process sends a registration message to another in order to subscribe to a series of updates. Also supports scatter-gather, the gathering of replies from multiple senders into an array of messages. An option framework for dynamically-launched VI "actors" is also provided, including example templates, which can be accessed via the Tools menu (from an open Project, select Tools>>Messenger Library>>Create Actor from Template..). An "Actor Manager" debug tool is also installed under the Tools menu. Please note that this package has nothing directly to do with the NI Actor Framework (other than both packages are influenced by the Actor Model). ***Introductory Videos are on a YouTube channel.*** ***A great summary of many Messenger Library sources, provided by Bob W Edwards*** JDP Science Tools group on NI.com. Original conversation on this work is here. Now hosted on the LabVIEW Tools Network (but note that the latest version will often be on LAVA) ***NOTE: latest versions require VIPM 2017 or later to install.***

This toolkit combines a variety of TDMS functions and tools into a single package. The initial release has a variety of features: - Classes for Circular, Periodic, Size, and Time of Day TDMS generation with examples of using each - Reading and Writing Clusters into TDMS Channels - XLSX Conversion example - File operations for combining files, renaming, moving, and saving in memory to zip - Basic function for splitting TDMS file into segments (useful for corrupt files) - Reorder TDMS Channel with Demo There is plenty of room for improvements but I wanted to get this out there and gauge interests. The variety of classes for doing things, along with VIMs, and class adaptation makes for using them easier. If I get time I plan on making some blog posts explaining some of the benefits of TDMS, along with best practices.

Here is the Hooovahh Array VIMs. This initial release contains VIMs for manipulating array data, which are intended to replace OpenG functionality, but with the added benefit of data type propagation, and increased performance using newer array manipulation techniques. In later versions other Array manipulation functions were added moving all the OpenG stuff to their own palette. Version 2.0 changed the suffix naming standard. Updating may mean replacing calls to the new versions since the name on disk has changed. This was for consistency and I'm sorry for breaking compatibility. The added type defs in 2.0 may break compatibility too but these help avoid code breaking bugs since VIMs allowed any data type previously. Most of the OpenG functions are unchanged, but a few use the newer conditional and concatenating tunnels. And a few functions have added performance based on other inputs. For instance the Delete Array Elements can operate in a more efficient way if the input indexes are already sorted. The Filter 1D array can also be more efficient if the input is known to not contain any duplicates. Because these packages contain VIMs, they require LabVIEW 2017 or newer. Having these functions be VIMs mean all functions work with various array data types. Included functions are: Conditional Auto-Indexing Tunnel Delete Elements from (1D or 2D) Array Filter 1D Array Index (1D or 2D) Array, Scalar, Row, Column Remove Duplicates from 1D Array Reorder (1D or 2D) Array Reverse 1D Array Slice 1D Array Sort (1D or 2D) Array Convert 1D to 2D Convert 2D to 1D Find Subarray Force Array Min/Max Size Foreign Key Sort

Introductory video now available on YouTube: Intro to SQLite in LabVIEW SQLite3 is a very light-weight, server-less, database-in-a-file library. See www.SQLite.org. This package is a wrapper of the SQLite3 C library and follows it closely. There are basically two use modes: (1) calling "Execute SQL" on a Connection to run SQL scripts (and optionally return 2D arrays of strings from an SQL statement that returns results); and (2) "Preparing" a single SQL statement and executing it step-by-step explicitly. The advantage of the later is the ability to "Bind" parameters to the statement, and get the column data back in the desired datatype. The "Bind" and "Get Column" VIs are set as properties of the "SQL Statement" object, for convenience in working with large numbers of them. See the original conversation on this here. Hosted on the NI LabVIEW Tools Network. JDP Science Tools group on NI.com. ***Requires VIPM 2017 or later for install.***

I think I've finalized my example for the XNode UpdateState ability. This is a very important ability. Failure to properly manage the update process can have dire consequences.

This tool-set gives access to all the 1-wire TMEX functionality. I was able to access 1-wire memory with this library. It has all the basic VI to allow communication with any 1-wire device on the market. It needs to be used in a project so the selection of the .dll 64 bit or 32 bit is done automatically. It works with the usb and the serial 1-wire adapter.

UI Tools v1.4.0 Copyright © 2009-2016, François Normandin All rights reserved. Author:François Normandin Contact Info: Contact via PM on www.lavag.org LabVIEW Versions: Created and tested with LabVIEW 2012 Dependencies: OpenG Application Control Library >= 4.1.0.7 OpenG Array Library >= 4.1.1.14 OpenG File Library >= 4.0.1.22 OpenG LabVIEW Data Library >= 4.2.0.21 OpenG String Library >= 4.1.0.12 LAVA Palette >= 1.0.0.1 Description: This package contains tools for designing user interfaces. A first palette helps create special effects using transparency of front panel. Using them allows to quickly create fade-ins or outs using linear or exponential variation of the intensity. A second palette contains VIs to calculate the position of GObjects for many purposes like alignment, snap, mouse follow, etc. A third palette contains VIs to create dialog boxes based on class instances. "Simple Error Dialog" and "Simple Selection List" are featured with or without backrground blackening effect. A fourth palette includes some VIs to move objects programmatically on the front panel, using a basic deceleration algorithm to provide an impression of a smooth movement. The packaged VIs are all namespaced using a suffix “__lava_lib_ui_tools” which should not conflict with any of your own code. Includes: Front Panel Transparency (Fade In & Fade Out) Utilities (Alignment, Snap) Dialog (OOP based, extensible) Engine (Beta) for object movement Instructions: This package is distributed on the LabVIEW Tools Network (version 1.3) and updates are on LAVA (1.4). It can be installed directly in the addon folder of any LabVIEW version from 2012 to now. The addon installs automatically under the LAVA palette of the addon submenu. License: Distributed under the BSD license. Support: If you have any problems with this code or want to suggest features, please go to www.lavag.org and navigate to the discussion page.

For a personal project, I needed to communicate between my computer and a SPI device slave device. So, I use a FTDI chip FT232h. I have adapted the library MPSSE I2C already available on this website to make it works for SPI. Warning ! VI are not 100% tested (especially Read functions), I provided it as it is.

lava_lib_LabVIEW_API_scripting_tools v0.22.1.21 by University of Leeds Author: Gavin Burnell Copyright: Copyright © 2007-2010, University of Leeds License: BSD Compatible LabVIEW Versions: >= 8.6. Compatible OS Versions: ALL. Description: This is a LabVIEW 8.6.1 Library of VIs to help with scripting. The public VIs include routines to get hold of the block diagram references, control terminal references, get the connector pane reference and select the connector pane pattern and wire controls up to it. There are a number of routines to help wire the block diagram up, including creating a selection of the primitives (I got bored of coding them all up !). I've stuck in some routines that work with tags - hidden away is the capability to tag LabVIEW vi-server objects with arbitary data. One possibility is to use this to identify bits of the block diagram of a vi for moving and rewiring via scripting. The scripting Tools includes a separate XNode support library that provides routines to help scripting and terminal adaptation in XNodes. There are some routines to help with undo transactions new to this release. This Package Conflicts with these other packages: LAVAG_scripting_tools >= 0.0 Scripting Tools >= 0.0

This Vi Calculate th Cp and Cpk values of a dbl array values. It's quite usefull to do some statistical analysis of a process capability.

This XControl has the nice feature that a Calendar control should give you. Multilanguage support by property node. The input and output are Labview Time Stamp. When selecting a date, the date in the calendar become light blue. Please you receive this XControl for free. The minimum you can do is to rate it.

Since the standard Tick Count VI has very limited resolution, I made a simple timer using the QueryPerfomanceCounter methods in the windows kernel32.dll. The output is the time in seconds as a double precision value.

Variant Probe V2.4.1 Copyright © 2012, Ton Plomp All rights reserved. Author: Ton Plomp tcplomp@gmail.com Distribution: This code was downloaded from: http://lavag.org/index.php?app=downloads&showfile=19 Description: A custom probe to put on a variant. It will create a tree based on the variant data, and populate the tree with the data, the attributes of the variant will be shown as well. The datatype description will determine the color of the tree items. Historical data is available as well. Version 2.0 introduces a Variant Tree XControl which can be used in any project. Located under the user.lib palette, it gives great flexibility to the programmer. The programmer has the possibility to give the end user permissions for the following actions: -Reset This will reset the whole tree contents -Traverse Variant Attributes This will enable/disable the traversion of variant attributes -Colorize This will enable/disable coloring of the actual datatype All of these customizations are available as properties/methods for the actual XControl as well, or you access them (while the owning VI is in edit mode) via the short cut menu. Installation method 1: Install the OGP file using VIPM (www.jkisoft.com/vipm) and you have a custom VariantProbe and xcontrol To use it add a probe to a variant datatype or to an array of variants. It can pause if the data changes, and will notify you if a change happens. Dependencies: The following OpenG packages should be installed: oglib_string>=2.6 oglib_lvdata>=2.8 oglib_comparison>=2.3 oglib_error>=2.0 Known issues: Is slow on large variants. Support: If you have any problems with this code or want to suggest features: http://lavag.org/index.php?showtopic=10269 Version History: 2.4.1: Fixed issue #132: An array inside another array crashes the probe/XControl 2.4: Immediate updating after changing of attributes Rebuild in LabVIEW 2011 2.3: Fixed a bug that caused attributes not to be traversed on certain data-types 2.2: Fixed a relinking bug 2.1: Fixes a bug where unnamed cluster elements where used (http://lavag.org/topic/10269-discuss-variantprobe/page__view__findpost__p__67677) 2.0: Added an XControl Show XControl in palette (under user.lib controls) Add coloring Add 'user permissions' on XControl Add Reset on XControl Add optionally traversing attributes on XControl Add optionally colorizing on XControl Add optionally restting on XControl 1.2.0: Upgraded to LabVIEW 8.5 to use inheritance Support for Waveforms, timestamps and dynamic datatypes (thanks to Osvaldo) Added probe for an array of Variants Distributed as one .llb and added OGP installer If a Variant hasn't changed it's not decomposed (optimization) 1.1.0: Support for attributes of variants 1.0.1: Controls placed on a seperate pane Resize tree to upper pane Hide unused columns Limited maximum history length (default 10) Window resizable 1.0.0: Initial release of the code. License: This code is distributed under the BSD License Copyright © 2012, Ton Plomp All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: * Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. * Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. * Neither the name of the Ton Plomp nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

This package consist of a series of tools in native LabVIEW 2010 code. For encryption/decription the AES (Rijndael) routine is used with key sizes of 128, 192 and 256 bytes. The encryption supports the following block modes: EBC CBC CFB128 OFB For signing of string/packages it performs the SHA-1 and SHA-2 hashing, for MD5 hashing the OpenG functionality is used. The hash functions return a binary string and a hex-formatted string with the hash. The following hashes are supported: MD5 (via OpenG library) SHA1 SHA-2 224 bit SHA-2 256 bit SHA-2 384 bit SHA-2 512 bit For Hashed key authentication the HMAC functionality is provided based on the supported hash functions. The used functions are tested against NIST public test vectors. The use of these functions is not: secure the code does not try to protect it's memory nor the used keys. © Ton Plomp 2011 - No warranty implied.

Installation: Copy the contents to LabVIEW xxxx/resource/plugins Abstract: Speed up creating new vi's from templates! It's using the 'new vi'-hook to create the new vi from a custom template. A plugin architecture allows to map different templates to the keyboard. For a quick-start, try Ctrl+N followed by 'H' (without releasing the Ctrl key). Detailed Description: When using New -> Blank VI from the Startup Window File -> New VI from the menu of any vi or the Ctrl+N shortcut the lv_new_vi.vi hook is called. Releasing of the Ctrl key (when using the shortcut) uses the Default.vit. The next key-press k creates a new vi from the template [...]/plugins/lv_new_vis/templates/k.vit. This is case insensitve and only works with a..z and SPACE. If no template is found or if an error occures, the default action of LabVIEW (empty vi) is performed (Failsafe). In addition to normal vi templates it supports global vi templates and control templates. Even more customization is possible using special tags on the vi or vit. Use [...]/plugins/lv_new_vis/tools/lv_new_vi__TagEditor to read and set them: isBD_ToFront? bring the block diagram in front instead of the front panel isRunMe? will instead run the vi in the template folder. Use this for wizards, more sophisticated scripting and other dialogs. Examples (V0.9.3: seperate ogp package): Try the following keys to see the different possibilities: f: normal vi, FP at front b: BD at front g: global vi c: control w: wizard h: help You do not need to delete the demo templates, a w.vit will load even with w_example.vit present. Compatibility: Developed in good old 7.1 and tested with 2010. I don't know if it works nicely with the project explorer and did never try to use it with projects, libraries and classes. Planned Features: * Error logging * Redirections via Config file (I will link the standard templates) (Edit: It's faster to just place them in the templates folder.) V 0.9.1 Fixed issues with the Application Instances of LV8.0 and higher. Wizards are still launched in the diaolog App.Instance, they need to get the default App on their own. V 0.9.2 Changes: Closing all references Beta: Uses VI Activation Event to abort when the user switched to a different app. (See discussion for details). V 0.9.3 Uses VI Activation Event to check Ctrl-Key when user switches from a diffrent application. Now available as packages (ogp). Uses a seperate package for the examples. V 0.9.4 Fixed issues with 0.9.3: After start of LV, Ctrl+N didn't work the first time Enjoy, Felix

Copyright © 2007, GTech Automation All rights reserved. Author: Dave A. Graybeal --see readme text for contact information Instructions: This code has been tested to run under LabVIEW 8.2.1. Unzip the code into any folder of your choice and open the example called, GetRefExample.vi. This shows how to use the 'Get Reference To All Controls.vi' as well as the 'Get Control Reference by Name.vi' to obtain a reference to all controls and how to search thru those reference to obtain the reference you want. Features: Get Reference to All Controls.vi -Gets the references and labels to All the controls on the front panel of the calling VI. -Is Able to search thru all Tab Controls recursively to compile a complete list of Controls from the front panel. Get Control Reference by Name.vi -Polymorphic VI that allows for searching list for single reference or an array of references. -Gets a Specific Reference from the List of All Controls by Control Name(Label). Get Control References By Match Pattern.vi -Gets an Array of References for all Controls containing the regular expression in the label. Change Log: 1.0.0: Initial release of the code. 1.1.0: Changed the Class ID of a Tab Control from a constant to a Property Node (To support Future LabVIEW Releases) 1.2.0: Added Get Control References By Match Pattern.vi (Authored By: Justin Goeres) Thanks! Modified GetRefExample to Include the Get Control References By Match Pattern.vi Improved some performace by removing unnecessary Items from Loops (Thanks JFM!) Removed all Dialog boxes from VI's and replaced them with proper error output messages. Added shift registers where necessary to ensure proper error is passed out of each VI. Recompiled under LabVIEW 8.2.1.

Copyright © 2006, Adam Rofer All rights reserved. Author: Adam Rofer --see readme file for contact information Description: A couple of Picture datatype hacks to illustrate the structure of the (LV 6.1 - LV 7+ is untested) picture control. -- Main VIs -- Example - Show How Picture Is Made.vi: Main example, shows (incrementally) how a specific picture is generated by displaying the picture with each packet incrementally added. Good way to see how your own pictures display information. Opcodes.csv: Comma-delimited file explicitly describing the packet types and their requirements / uses. Tool - Picture concat.vi: Given two pictures, concatenates the data to create a single overlapped picture. Tool - Packets to Picture.vi: Given an array of picture packets (cluster), generates a picture. Tool - Picture to Packets.vi: Given a picture, generates an array of picture packets. -- Utility subVIs -- sub - 8-Bit string to 32-Bit number.vi: utility VI to cast a string to a 32-bit number. Typecast might work instead but this is more explicit. sub - Find Opcode: Given a picture data string that has the size header removed, this will extract an opcode from the front. sub - Strip top of and check picture.vi: Utility VI to strip the header (size) from a picture data string so that it can be scanned for packets. Change Log: 1.0.1: (11/13/06) Cleaned up code for LAVA requirements: - Renamed VIs for clarification of purpose - Fixed coercion dots - Added 0ms delays in all loops - Added error encapsulation in some subvis - Replaced local variable for cluster to constant in order to limit thread swapping between the user interface and code threads 1.0.0: (11/07/06) Cleaned up code from 6i 2001 version for submission.

Windows Environment Variable Reader Writer Vc Copyright © 2006, Brian Hoover All rights reserved. Author: Brian Hoover **see email address in readme txt** Description:: Purpose: This Vi was made so that you can easily view and create environment variables from within Windows XP. Features: You are able to read all environment variables which you have available to you at the command prompt by typing "set". It also can write environment variables by writing them to the registry in the following location: HKEY_CURRENT_USER\Environment Also for added safty it will check the name you are trying to use, and won't allow its creation if a variable with that name already exists. Usage: To use this VI you need to be using Labview version 8.20. With Labview 8.20 installed open the VariableReadWrite.vi file, then click run. While it's running open the View Variables tab and click "Refresh Variables" to view all your command prompt variables. Two String arrays are created, the Name of the variables, and their values. A text window is also displaying what the user would see if they typed "set" at a command prompt. To create a variable open the Create Variables tab and fill in the information for Variable Name and Variable Value; then click Create Variable. Please note that you may need to log off then back on for the new variable to take effect. If needed there is a "Run Regedit" button which will open the registry. From here you can see the newly created variables in the location mentioned in the Features section. When you are done click stop to end the program. Version History: 1.0.0: Initial release of the code.