https://labviewwiki.org/w/api.php?action=feedcontributions&feedformat=atom&user=Hooovahh 2026-04-22T10:18:47Z User contributions MediaWiki 1.43.0 https://labviewwiki.org/w/index.php?title=Symbolic_path&diff=31611 2022-04-18T17:40:56Z

<p>Hooovahh: </p> <hr /> <div>When files are located beneath certain special folders, callers that link to these files will link to them using a ''symbolic path'', rather than an absolute or relative path. The ''symbolic path'' will be relative to the special folder. The following table lists these special folders and their ''symbolic path'':<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! symbolic path<br /> ! description<br /> ! actual path<br /> |-<br /> | &lt;userlib&gt;<br /> | User Libraries<br /> | &lt;LabVIEW&gt;\user.lib<br /> |-<br /> | &lt;vilib&gt;<br /> | NI Libraries and Addons<br /> | &lt;LabVIEW&gt;\vi.lib<br /> |-<br /> | &lt;instrlib&gt;<br /> | Instrument Drivers<br /> | &lt;LabVIEW&gt;\instr.lib<br /> |-<br /> | &lt;helpdir&gt;<br /> | Help Files<br /> | &lt;LabVIEW&gt;\help<br /> |-<br /> | &lt;osdatadir&gt;<br /> | Default file directory of the operating system<br /> | (OS Dependent)<br /> |-<br /> | &lt;menu&gt;<br /> | Palette Menus<br /> | &lt;LabVIEW&gt;\menus<br /> |-<br /> | &lt;resource&gt;<br /> | Various VIs and resources used by LabVIEW and plugins, and generally not intended to be called by end-user applications.<br /> ''Note this first appeared in LabVIEW 2012 (based on [https://forums.ni.com/t5/Developer-Center-Discussions/Make-the-LabVIEW-quot-resource-quot-folder-a-symbolic-path/td-p/3438293?profile.language=en this idea exchange post]) and prior to that it was not a symbolic path.''<br /> | &lt;LabVIEW&gt;\resource<br /> |}<br /> <br /> Note that some of these can have the actual path changed by changing the settings in '''Tools&gt;&gt;Options'''. The whole point of the symbolic path is to indicate &quot;load from whatever location this path is currently defined to be.&quot;<br /> <br /> For example, if you have a VI located in the following location:<br /> <br /> &lt;LabVIEW&gt;\user.lib\_OpenG.lib\array\array.llb\Conditional Auto-Indexing Tunnel__ogtk.vi<br /> <br /> Callers will link to this VI using the following ''symbolic path'':<br /> <br /> &lt;userlib&gt;\_OpenG.lib\array\array.llb\Conditional Auto-Indexing Tunnel__ogtk.vi<br /> <br /> ''symbolic path'' are not generally encountered. They are used mostly under the hood of LabVIEW, for example, when using the Application '''Linker:Read Info From File''' and '''Linker:Write Info To File''' methods.<br /> <br /> == Resolving Symbolic Paths Programmatically==<br /> <br /> You can call the private '''Resolve Symbolic Path''' method to convert a Symbolic Path to an absolute path, as shown in the screenshot, below.<br /> <br /> [[Image:ResolveSymbolicPath.png]]<br /> <br /> == Auto update of symbolic paths ==<br /> If you have a VI linked to another VI inside a symbolic path LabVIEW will automatically store the path symbolically. Here's the following use case:<br /> <br /> Suppose you want to build a LabVIEW tool that resides under the Tools menu but is also accessible via the user.lib palette. What you can do is create a set-up upon built like this:<br /> <br /> *[Built]<br /> **[Tools]<br /> ***Menu VI<br /> **[user.lib]<br /> ***Actual VI<br /> <br /> When you copy the contents of ''Built'' to the LabVIEW folder the ''Menu VI'' will have a relative path like ''..\user.lib\Actual VI'' when you do a resave of the ''Menu VI'' the path will be changed to an absolute path ''&lt;userlib&gt;\Actual VI''. Now you can move the ''Menu VI'' around without breaking it.<br /> <br /> == When Using Modules (FPGA, RT, etc) ==<br /> A symbolic path may resolve to different actual files on disk depending upon which target the VI is loaded into. So a VI that is written to use &lt;vilib&gt;\a.vi may use &lt;labview&gt;\vi.lib\a.vi when loaded for the desktop target, but may use &lt;labview&gt;\vi.lib\fpga\a.vi when loaded for the FPGA target.<br /> <br /> == External Links ==<br /> * [http://zone.ni.com/reference/en-XX/help/371361B-01/lvhowto/using_symbolic_paths/ LabVIEW Help: Using Symbolic Paths]<br /> <br /> [[Category:File IO]]<br /> [[Category:Development Environment]]</div>

Hooovahh https://labviewwiki.org/w/index.php?title=Package_Manager_Comparison&diff=8175 2019-06-28T17:15:21Z

<p>Hooovahh: </p> <hr /> <div>This is the comparison of package management solutions in the LabVIEW community.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Characteristic !! [https://vipm.jki.net/ VI Package Manager (Free)] !! [https://vipm.jki.net/ VI Package Manager (Pro $599/user/year)] !! [https://www.ni.com/en-us/support/downloads/ni-package-manager.html NI Package Manager] !! [https://gpackage.io/ G Package Manager (GPM)]<br /> |-<br /> | Installs With LabVIEW || Yes || No || Yes || No<br /> |-<br /> | Created By|| JKI || JKI || National Instruments || MGI (Moore Good Ideas)<br /> |-<br /> | Open Source || No || No || No || Yes<br /> |-<br /> | Language Written In || G || G || C# || G<br /> |-<br /> | Free To Install || Yes || Yes Trial || Yes || Yes<br /> |-<br /> | API || No || Yes || Yes || Yes<br /> |-<br /> | Local repository management&lt;sup&gt;1&lt;/sup&gt; || No || Yes || Yes || Yes<br /> |-<br /> | Supports multiple LabVIEW versions from a single package || Yes || Yes || No || No<br /> |-<br /> | Scope of package installation&lt;sup&gt;2&lt;/sup&gt; || LabVIEW IDE || LabVIEW IDE || LabVIEW IDE || Per Project&lt;sup&gt;5&lt;/sup&gt;<br /> |-<br /> | Supports LabVIEW NXG || No || No || Yes || No<br /> |-<br /> | Create pallets as a part of the package creation || Yes || Yes || No || No<br /> |-<br /> | Supports Installation to symbolic paths (user.lib) || Yes || Yes || No || N/A&lt;sup&gt;6&lt;/sup&gt;<br /> |-<br /> | Supports Local and Global repositories&lt;sup&gt;3&lt;/sup&gt; || Yes || Yes || Yes || Yes<br /> |-<br /> | Support Structure || [https://forums.jki.net/forum/5-vi-package-manager-vipm/ JKI online support] || [https://forums.jki.net/forum/5-vi-package-manager-vipm/ JKI online support] || [https://forums.ni.com/t5/NI-Package-Manager-NIPM/bd-p/1023 NI Forums] || ?<br /> |-<br /> | Supports Pre Build Step || No || Yes, G Code || Yes - via Source Distribtuion, G Code || ?<br /> |-<br /> | Supports Post Build Step || No || Yes, G Code || Yes - via Source Distribtuion, G Code || ?<br /> |-<br /> | Supports Pre Install Step || Yes, G Code || Yes, G Code || No || ?<br /> |-<br /> | Supports Post Install Step || Yes, G Code || Yes, G Code || Yes - via exe or bat || ?<br /> |-<br /> | Supports Pre Uninstall Step || Yes, G Code || Yes, G Code || Yes - via exe or bat || ?<br /> |-<br /> | Supports Post Uninstall Step || Yes, G Code || Yes, G Code || No || ?<br /> |-<br /> | Supports N post install/pre uninstall steps || No || No || Yes || ?<br /> |-<br /> | Supports N Post Install All steps|| No || No || Yes || ?<br /> |-<br /> | Supports Automatic Dependency Scanning&lt;sup&gt;4&lt;/sup&gt; || No || Yes || No || No<br /> |-<br /> | Has a dedicated package manager application || Yes || Yes || Yes || Yes<br /> |-<br /> | Packages Searchable via Web Page || Yes || Yes || No || Yes<br /> |-<br /> | Has a community repository of packages || No || No || No || Yes<br /> |-<br /> | Can list packages created by other package managers as dependencies&lt;sup&gt;7&lt;/sup&gt; || No || No || No || No<br /> |}<br /> <br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Detail Number !! Additional Information<br /> |-<br /> | 1 || Repository types: A global repository is accessible to anyone. A local repository is created by an individual (company, etc.) and hosted on a local server.<br /> |-<br /> | 2 || Scope of Package Installation: determines if multiple versions of a package are allowed or if you may have only one version of a package. <br /> |-<br /> | 3 || Example<br /> |-<br /> | 4 || Example<br /> |-<br /> | 5 || LabVIEW IDE Coming Soon<br /> |-<br /> | 6 || Coming Soon<br /> |-<br /> | 7 || Only packages of the same type can be listed as dependencies. For example, a VI Package can only depend on other VI Packages. A VI Package cannot depend on a NI Package. <br /> |}</div>

Hooovahh https://labviewwiki.org/w/index.php?title=Package_Manager_Comparison&diff=8166 2019-06-28T13:33:42Z

<p>Hooovahh: </p> <hr /> <div>This is the comparison of package management solutions in the LabVIEW community.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Characteristic !! [https://vipm.jki.net/ VI Package Manager (Free)] !! [https://vipm.jki.net/ VI Package Manager (Pro $599/user/year)] !! [https://www.ni.com/en-us/support/downloads/ni-package-manager.html NI Package Manager] !! [https://gpackage.io/ G Package Manager (GPM)]<br /> |-<br /> | Installs With LabVIEW || Yes || No || Yes || No<br /> |-<br /> | Open Source || No || No || No || Yes<br /> |-<br /> | Language Written In || G || G || C# || G<br /> |-<br /> | Free To Install || Yes || Yes Trial || Yes || Yes<br /> |-<br /> | API || No || Yes || Yes || Yes<br /> |-<br /> | Local repository management || No || Yes || Yes || Yes<br /> |-<br /> | Supports multiple LabVIEW versions from a single package || Yes || Yes || No || No<br /> |-<br /> | Scope of package installation || LabVIEW IDE || LabVIEW IDE || LabVIEW IDE || Per Project (LabVIEW IDE coming soon)<br /> |-<br /> | Supports LabVIEW NXG || No || No || Yes || No<br /> |-<br /> | Create pallets as a part of the package creation || Yes || Yes || No || No<br /> |-<br /> | Supports Installation to symbolic paths (user.lib) || Yes || Yes || No || N/A (coming soon)<br /> |-<br /> | Supports Local and Global repositories || Yes || Yes || Yes || Yes<br /> |-<br /> | Support Structure || [https://forums.jki.net/forum/5-vi-package-manager-vipm/ JKI online support] || [https://forums.jki.net/forum/5-vi-package-manager-vipm/ JKI online support] || [https://forums.ni.com/t5/NI-Package-Manager-NIPM/bd-p/1023 NI Forums] || ?<br /> |-<br /> | Supports Pre Build Step || No || Yes, G Code || Yes - via Source Distribtuion, G Code || ?<br /> |-<br /> | Supports Post Build Step || No || Yes, G Code || Yes - via Source Distribtuion, G Code || ?<br /> |-<br /> | Supports Pre Install Step || Yes, G Code || Yes, G Code || Yes - via exe or bat || ?<br /> |-<br /> | Supports Post Install Step || Yes, G Code || Yes, G Code || Yes - via exe or bat || ?<br /> |-<br /> | Supports Pre Uninstall Step || Yes, G Code || Yes, G Code || ? || ?<br /> |-<br /> | Supports Post Uninstall Step || Yes, G Code || Yes, G Code || ? || ?<br /> |-<br /> | Supports N pre install/post install steps || No || No || Yes || ?<br /> |-<br /> | Supports Automatic Dependency Scanning || No || Yes || No || No<br /> |-<br /> | Example || Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example || Example<br /> |}</div>

Hooovahh https://labviewwiki.org/w/index.php?title=Package_Manager_Comparison&diff=8165 2019-06-28T13:30:59Z

<p>Hooovahh: </p> <hr /> <div>This is the comparison of package management solutions in the LabVIEW community.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Characteristic !! [https://vipm.jki.net/ VI Package Manager (Free)] !! [https://vipm.jki.net/ VI Package Manager (Pro $599/user/year)] !! [https://www.ni.com/en-us/support/downloads/ni-package-manager.html NI Package Manager] !! [https://gpackage.io/ G Package Manager (GPM)]<br /> |-<br /> | Installs With LabVIEW || Yes || No || Yes || No<br /> |-<br /> | Open Source || No || No || No || Yes<br /> |-<br /> | Language Written In || G || G || C# || G<br /> |-<br /> | Free To Install || Yes || Yes Trial || Yes || Yes<br /> |-<br /> | API || No || Yes || Yes || Yes<br /> |-<br /> | Local repository management || No || Yes || Yes || Yes<br /> |-<br /> | Supports multiple LabVIEW versions from a single package || Yes || Yes || No || No<br /> |-<br /> | Scope of package installation || LabVIEW IDE || LabVIEW IDE || LabVIEW IDE || Per Project (LabVIEW IDE coming soon)<br /> |-<br /> | Supports LabVIEW NXG || No || No || Yes || No<br /> |-<br /> | Create pallets as a part of the package creation || Yes || Yes || No || No<br /> |-<br /> | Supports Installation to symbolic paths (user.lib) || Yes || Yes || No || N/A (coming soon)<br /> |-<br /> | Supports Local and Global repositories || Yes || Yes || Yes || Yes<br /> |-<br /> | Support Structure || JKI online support || JKI online support || NI || ?<br /> |-<br /> | Supports Pre Build Step || No || Yes, G Code || Yes - via Source Distribtuion, G Code || ?<br /> |-<br /> | Supports Post Build Step || No || Yes, G Code || Yes - via Source Distribtuion, G Code || ?<br /> |-<br /> | Supports Pre Install Step || Yes, G Code || Yes, G Code || Yes - via exe or bat || ?<br /> |-<br /> | Supports Post Install Step || Yes, G Code || Yes, G Code || Yes - via exe or bat || ?<br /> |-<br /> | Supports Pre Uninstall Step || Yes, G Code || Yes, G Code || ? || ?<br /> |-<br /> | Supports Post Uninstall Step || Yes, G Code || Yes, G Code || ? || ?<br /> |-<br /> | Supports N pre install/post install steps || No || No || Yes || ?<br /> |-<br /> | Supports Automatic Dependency Scanning || No || Yes || No || No<br /> |-<br /> | Example || Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example || Example<br /> |}</div>

Hooovahh https://labviewwiki.org/w/index.php?title=Package_Manager_Comparison&diff=8164 2019-06-28T13:30:38Z

<p>Hooovahh: </p> <hr /> <div>This is the comparison of package management solutions in the LabVIEW community.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Characteristic !! [https://vipm.jki.net/ VI Package Manager (Free)] !! [https://vipm.jki.net/ VI Package Manager (Pro $599/user/year)] !! [https://www.ni.com/en-us/support/downloads/ni-package-manager.html NI Package Manager] !! [https://gpackage.io/ G Package Manager (GPM)]<br /> |-<br /> | Installs With LabVIEW || Yes || No || Yes || No<br /> |-<br /> | Open Source || No || No || No || Yes<br /> |-<br /> | Language Written In || G || G || C# || G<br /> |-<br /> | Free To Install || Yes || Yes Trial || Yes || Yes<br /> |-<br /> | API || No || Yes || Yes || Yes<br /> |-<br /> | Local repository management || No || Yes || Yes || Yes<br /> |-<br /> | Supports multiple LabVIEW versions from a single package || Yes || Yes || No || No<br /> |-<br /> | Scope of package installation || LabVIEW IDE || LabVIEW IDE || LabVIEW IDE || Per Project (LabVIEW IDE coming soon)<br /> |-<br /> | Supports LabVIEW NXG || No || No || Yes || No<br /> |-<br /> | Create pallets as a part of the package creation || Yes || Yes || No || No<br /> |-<br /> | Supports Installation to symbolic paths (user.lib) || Yes || Yes || No || N/A (coming soon)<br /> |-<br /> | Supports Local and Global repositories || Yes || Yes || Yes || Yes<br /> |-<br /> | Support Structure || JKI online support || JKI online support || NI || ?<br /> |-<br /> | Supports Pre Build Step || No || Yes, G Code || Yes - via Source Distribtuion, G Code || ?<br /> |-<br /> | Supports Post Build Step || No || Yes, G Code || Yes - via Source Distribtuion, G Code || ?<br /> |-<br /> | Supports Pre Install Step || Yes, G Code || Yes, G Code || Yes - via exe or bat || ?<br /> |-<br /> | Supports Post Install Step || Yes, G Code || Yes, G Code || Yes - via exe or bat || ?<br /> |-<br /> | Supports Pre Uninstall Step || Yes, G Code || Yes, G Code || ? || ?<br /> |-<br /> | Supports Post Uninstall Step || Yes, G Code || Yes, G Code || ? || ?<br /> |-<br /> | Supports N pre install/post install steps || No || No || Yes || ?<br /> |-<br /> | Supports Automatic Dependency Scanning || No || Yes || Yes || No<br /> |-<br /> | Example || Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example || Example<br /> |}</div>

Hooovahh https://labviewwiki.org/w/index.php?title=Package_Manager_Comparison&diff=8163 2019-06-28T13:29:49Z

<p>Hooovahh: </p> <hr /> <div>This is the comparison of package management solutions in the LabVIEW community.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Characteristic !! [https://vipm.jki.net/ VI Package Manager (Free)] !! [https://vipm.jki.net/ VI Package Manager (Pro $599/user/year)] !! [https://www.ni.com/en-us/support/downloads/ni-package-manager.html NI Package Manager] !! [https://gpackage.io/ G Package Manager (GPM)]<br /> |-<br /> | Installs With LabVIEW || Yes || No || Yes || No<br /> |-<br /> | Open Source || No || No || No || Yes<br /> |-<br /> | Language Written In || G || G || C# || G<br /> |-<br /> | Free To Install || Yes || Yes Trial || Yes || Yes<br /> |-<br /> | API || No || Yes || Yes || Yes<br /> |-<br /> | Local repository management || No || Yes || Yes || Yes<br /> |-<br /> | Supports multiple LabVIEW versions from a single package || Yes || Yes || No || No<br /> |-<br /> | Scope of package installation || LabVIEW IDE || LabVIEW IDE || LabVIEW IDE || Per Project (LabVIEW IDE coming soon)<br /> |-<br /> | Supports LabVIEW NXG || No || No || Yes || No<br /> |-<br /> | Create pallets as a part of the package creation || Yes || Yes || No || No<br /> |-<br /> | Supports Installation to symbolic paths (user.lib) || Yes || Yes || No || N/A (coming soon)<br /> |-<br /> | Supports Local and Global repositories || Yes || Yes || Yes || Yes<br /> |-<br /> | Support Structure || JKI online support || JKI online support || NI || ?<br /> |-<br /> | Supports Pre Build Step || No || Yes, G Code || Yes - via Source Distribtuion, G Code || ?<br /> |-<br /> | Supports Post Build Step || No || Yes, G Code || Yes - via Source Distribtuion, G Code || ?<br /> |-<br /> | Supports Pre Install Step || Yes, G Code || Yes, G Code || Yes - via exe or bat || ?<br /> |-<br /> | Supports Post Install Step || Yes, G Code || Yes, G Code || Yes - via exe or bat || ?<br /> |-<br /> | Supports Pre Uninstall Step || Yes, G Code || Yes, G Code || ? || ?<br /> |-<br /> | Supports Post Uninstall Step || Yes, G Code || Yes, G Code || ? || ?<br /> |-<br /> | Supports N pre install/post install steps || No || No || Yes || ?<br /> |-<br /> | Supports Automatic Dependency Scanning || No || Yes || Yes || No<br /> |-<br /> | Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example<br /> |}</div>

Hooovahh https://labviewwiki.org/w/index.php?title=Package_Manager_Comparison&diff=8162 2019-06-28T13:29:15Z

<p>Hooovahh: </p> <hr /> <div>This is the comparison of package management solutions in the LabVIEW community.<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Characteristic !! [https://vipm.jki.net/ VI Package Manager (Free)] !! [https://vipm.jki.net/ VI Package Manager (Pro $599/user/year)] !! [https://www.ni.com/en-us/support/downloads/ni-package-manager.html NI Package Manager] !! [https://gpackage.io/ G Package Manager (GPM)]<br /> |-<br /> | Installs With LabVIEW || Yes || No || Yes || No<br /> |-<br /> | Open Source || No || No || No || Yes<br /> |-<br /> | Language Written In || G || G || C# || G<br /> |-<br /> | Free To Install || Yes || No || Yes || Yes<br /> |-<br /> | API || No || Yes || Yes || Yes<br /> |-<br /> | Local repository management || No || Yes || Yes || Yes<br /> |-<br /> | Supports multiple LabVIEW versions from a single package || Yes || Yes || No || No<br /> |-<br /> | Scope of package installation || LabVIEW IDE || LabVIEW IDE || LabVIEW IDE || Per Project (LabVIEW IDE coming soon)<br /> |-<br /> | Supports LabVIEW NXG || No || No || Yes || No<br /> |-<br /> | Create pallets as a part of the package creation || Yes || Yes || No || No<br /> |-<br /> | Supports Installation to symbolic paths (user.lib) || Yes || Yes || No || N/A (coming soon)<br /> |-<br /> | Supports Local and Global repositories || Yes || Yes || Yes || Yes<br /> |-<br /> | Support Structure || JKI online support || JKI online support || NI || ?<br /> |-<br /> | Supports Pre Build Step || No || Yes, G Code || Yes - via Source Distribtuion, G Code || ?<br /> |-<br /> | Supports Post Build Step || No || Yes, G Code || Yes - via Source Distribtuion, G Code || ?<br /> |-<br /> | Supports Pre Install Step || Yes, G Code || Yes, G Code || Yes - via exe or bat || ?<br /> |-<br /> | Supports Post Install Step || Yes, G Code || Yes, G Code || Yes - via exe or bat || ?<br /> |-<br /> | Supports Pre Uninstall Step || Yes, G Code || Yes, G Code || ? || ?<br /> |-<br /> | Supports Post Uninstall Step || Yes, G Code || Yes, G Code || ? || ?<br /> |-<br /> | Supports N pre install/post install steps || No || No || Yes || ?<br /> |-<br /> | Supports Automatic Dependency Scanning || No || Yes || Yes || No<br /> |-<br /> | Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example<br /> |-<br /> | Example || Example || Example || Example<br /> |}</div>

Hooovahh https://labviewwiki.org/w/index.php?title=LabVIEW_Wiki:Questions&diff=6007 2019-02-13T14:58:46Z

<p>Hooovahh: updated wiki support link</p> <hr /> <div>__NOTOC__ __NOEDITSECTION__ &lt;!--<br /> ***************************************************************************<br /> <br /> Do not ask your question on this page! Rather, go to one of the<br /> listed pages instead.<br /> <br /> This page is among the most visible to viewers and the rest of the web.<br /> <br /> Please keep it very simple. Do not make major changes without first<br /> achieving a consensus on the discussion thread.<br /> <br /> ***************************************************************************<br /> --&gt;&lt;noinclude&gt;<br /> {| width=&quot;100%&quot; style=&quot;border: solid 2px #A3B1BF; background: #F5FAFF; padding: 15px;&quot; |<br /> |-<br /> | <br /> &lt;h2 style=&quot;background-color:#cedff2; border-bottom:0px; border: 1px solid #a3b0bf; text-align:center; padding-top:4px;&quot;&gt;Where to ask questions or make comments<br /> &lt;/h2&gt; &lt;!-- 3 line spacing of h2 is important for subsection edit links to work correctly, PLEASE DO NOT FIX --&gt; &lt;/noinclude&gt;<br /> <br /> You can find the answers to many of your questions at the following places:<br /> <br /> {| <br /> |- valign=top<br /> | style=&quot;width:50%; background:#F5FAFF;&quot;|<br /> === Finding LabVIEW information ===<br /> * '''[http://www.google.com/coop/cse?cx=002298365452121072909%3Am5q5tjdmdso Search]''' — for many questions it's fastest and easiest to use the [http://www.google.com/coop/cse?cx=002298365452121072909%3Am5q5tjdmdso search box].<br /> <br /> &lt;span style=&quot;font-size:90%;margin-left:2em;&quot;&gt;e.g. To find information on case structures, type ''case structure'' in the box on the left and click ''Search''.&lt;/span&gt;<br /> * '''[http://forums.lavag.org LAVA Forums]''' — for general LabVIEW questions (about anything other than how to use LabVIEW Wiki) you can ask LAVA community members.<br /> <br /> &lt;span style=&quot;font-size:90%;margin-left:2em;&quot;&gt; e.g. ''&quot;How should I design this user interface?&quot;''&lt;/span&gt;<br /> <br /> * '''[http://labviewsearch.com LabVIEWSearch.com]''' — A powerful search engine that is scoped to a small set of LabVIEW related websites.<br /> | style=&quot;width:50%; background:#F5FAFF;&quot;|<br /> === How to use LabVIEW Wiki ===<br /> * '''[[LabVIEW Wiki:FAQ|FAQ]]''' — Frequently Asked Questions about LabVIEW Wiki<br /> * '''[[Help:Contents]]''' — information about using LabVIEW Wiki.<br /> <br /> &lt;span style=&quot;font-size:90%;margin-left:2em;&quot;&gt; e.g. ''&quot;How do I add an image to an article?&quot;''&lt;/span&gt;<br /> === Asking questions or making comments ===<br /> * Each article has a '''Discussion thread''' — click on the '''article's''' '''''discussion''''' link at the top of the page &amp;mdash; for questions, reporting vandalism or discussions about the article.<br /> <br /> * '''[https://lavag.org/forum/54-wiki-help/ LabVIEW Wiki Support]''' is '''the''' discussion forum for many '''technical and policy issues'''.<br /> | style=&quot;width:50%; background:#F5FAFF;&quot;|<br /> |}<br /> <br /> '''Important notes:'''<br /> * LabVIEW Wiki is a volunteer-operated site.<br /> * There is no &quot;documentation service&quot; nor are there any paid staff to process inquiries about the content of articles (sources, accuracy, etc.).<br /> * Please write all inquiries to the relevant article discussion threads or post to the support forum indicated above.<br /> <br /> ''Please do not post your question on this page.''<br /> |}</div>

Hooovahh https://labviewwiki.org/w/index.php?title=NIWeek&diff=5918 2018-12-17T16:30:13Z

<p>Hooovahh: Added videos section</p> <hr /> <div>'''NIWeek''' is an annual technical conference hosted by [[National Instruments|National Instruments (NI)]] in Austin Texas. The conference focuses on showcasing NI's roadmap for software and hardware. The at NIWeek the new version of [[LabVIEW]] is showcased and its new features introduced. The convention also includes:<br /> <br /> *Keynotes from NI executive and other business leaders<br /> *Over 200 Technical Sessions, Case Study Presentations, and Panel Discussions led by industry innovators<br /> *Over 40 Interactive, Hands-on Sessions that allow you to try out the products<br /> *Over 50 Training and Certification Courses<br /> *Networking with over 3,200 industry peers<br /> *Over 100 Exhibits from leading Tech Companies<br /> <br /> ==This Year's NIWeek==<br /> [[File:NIWeek 2019 Logo.PNG|700px|frameless|link=http://niweek.ni.com]]<br /> <br /> NIWeek this year marks the 25&lt;sup&gt;th&lt;/sup&gt; NIWeek. It will be held in Austin, Texas, on May 20&lt;sup&gt;th&lt;/sup&gt;-23&lt;sup&gt;rd&lt;/sup&gt;, 2019. The conference officially starts on a Monday with Alliance Day focusing on NI's [[Alliance_program|Alliance Partners]]. There are activities for non Alliance Partners on Monday but the majority of closed door presentations are off limits. Tuesday through Thursday technical sessions, training, keynotes, and other social activities take place with a schedule that changes each year. If you are interested in attending NI Week check [http://niweek.ni.com NI's official page] for their schedule.<br /> <br /> ==Previous Years==<br /> The majority of the content at NI Week is the technical sessions. These can be presented by NI employees, or any member of the public after being approved by NI. Over the years several NI sessions have been recorded and are available for viewing online. Links are provided below.<br /> <br /> {| class=&quot;wikitable&quot;<br /> !Year<br /> !Logo<br /> !Dates<br /> !Tag<br /> !Links<br /> |-<br /> |2018<br /> |[[File:NIWeek 2018 Logo.png|200px|thumb|center]]<br /> |May 21-24, 2018<br /> |Future Faster<br /> |<br /> *[[NIWeek 2018]] (LabVIEW Wiki Page)<br /> *Technical Session Videos: [https://labviewvideo.tecnova.com/ Tecnova's LabVIEW Video] site, with the credentials Username: '''LabVIEW_Videos''', Password: '''LabVIEW'''<br /> |-<br /> |2017<br /> |[[File:NIWeek 2017 Logo.png|200px|thumb|center]]<br /> |May 22-15, 2017<br /> |Engineer Next<br /> |<br /> |-<br /> |2016<br /> |[[File:NIWeek 2016 Logo.png|200px|thumb|center]]<br /> |August 1-4, 2016<br /> |<br /> |<br /> |-<br /> |2015<br /> |[[File:NIWeek 2015 Logo.png|200px|thumb|center]]<br /> |August 3-6, 2015<br /> |<br /> |<br /> |-<br /> |2014<br /> |[[File:NIWeek 2014 Logo.png|200px|thumb|center]]<br /> |August 4-7, 2014<br /> |You and NI will.<br /> |<br /> |-<br /> |2013<br /> |[[File:NIWeek 2013 Logo.png|200px|thumb|center]]<br /> |August 5-8, 2013<br /> |All Systems. Go.<br /> |<br /> |-<br /> |2012<br /> |[[File:NIWeek 2012 Logo.png|200px|thumb|center]]<br /> |August 6-9, 2012<br /> |Worldwide Graphical System Design Conference<br /> |<br /> |-<br /> |2011<br /> |[[File:NIWeek 2011 Logo.png|200px|thumb|center]]<br /> |August 2-4, 2011<br /> |Worldwide Graphical System Design Conference<br /> |<br /> |-<br /> |2010<br /> |<br /> |August 3-5, 2010<br /> |Worldwide Graphical System Design Conference<br /> |<br /> |-<br /> |2009<br /> |<br /> |August 4-6, 2009<br /> |Worldwide Graphical System Design Conference<br /> |<br /> |-<br /> |2008<br /> |[[File:NIWeek 2008 Logo.png|200px|thumb|center]]<br /> |August 5-7, 2008<br /> |Worldwide Graphical System Design Conference<br /> |<br /> |-<br /> |2007<br /> |[[File:NIWeek 2007 Logo.png|200px|thumb|center]]<br /> |August 7-9, 2007<br /> |<br /> |<br /> |-<br /> |2006<br /> |[[File:NIWeek 2006 Logo.png|200px|thumb|center]]<br /> |August 8-10, 2006<br /> |Worldwide Virtual Instrumentation Conference<br /> |<br /> |-<br /> |2005<br /> |[[File:NIWeek 2005 Logo.png|200px|thumb|center]]<br /> |August 16-18, 2005<br /> |Worldwide Virtual Instrumentation Conference<br /> |<br /> |-<br /> |2004<br /> |[[File:NIWeek 2004 Logo.png|200px|thumb|center]]<br /> |August 17-19, 2004<br /> |Worldwide Virtual Instrumentation Conference<br /> |<br /> |-<br /> |2003<br /> |[[File:NIWeek 2003 Logo.png|200px|thumb|center]]<br /> |August 13-15, 2003<br /> |Worldwide Virtual Instrumentation Conference<br /> |<br /> |-<br /> |2002<br /> |<br /> |August 14-16, 2002<br /> |<br /> |<br /> |-<br /> |2001<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |2000<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |1999<br /> |<br /> |August 18-20, 1999<br /> |<br /> |<br /> |-<br /> |1998<br /> |<br /> |<br /> |<br /> |<br /> |-<br /> |1997<br /> |<br /> |August 19-21, 1997<br /> |<br /> |<br /> |-<br /> |1996<br /> |<br /> |August 6-8, 1996<br /> |<br /> |<br /> |-<br /> |1995<br /> |<br /> |<br /> |<br /> |<br /> |}<br /> <br /> ==Videos==<br /> <br /> The majority of the content at NI Week is the technical sessions. These can be presented by NI employees, or any member of the public after being approved by NI. Over the years several NI sessions have been recorded and are available for viewing online. These videos are available at [https://labviewvideo.tecnova.com/ Tecnova's LabVIEW Video] site, with the credentials Username: '''LabVIEW_Videos''', Password: '''LabVIEW'''<br /> <br /> [[Category:NIWeek]]</div>

Hooovahh https://labviewwiki.org/w/index.php?title=Actor_Framework&diff=5739 2018-11-30T15:45:16Z

<p>Hooovahh: </p> <hr /> <div>== Articles ==<br /> * [http://www.mooregoodideas.com/actor-framework/basics/AF-basics-part-1/ Actor Framework Basics: Part 1 - the Basics]<br /> * [http://www.mooregoodideas.com/actor-framework/basics/AF-basics-part-2/ Actor Framework Basics: Part 2 - the Actor]<br /> * [http://www.mooregoodideas.com/actor-framework/basics/AF-basics-part-3/ Actor Framework Basics: Part 3 - Launching and Communicating]<br /> * [http://www.mooregoodideas.com/actor-framework/basics/AF-basics-part-4/ Actor Framework Basics: Part 4 - Being Productive With Actors]<br /> * [http://www.mooregoodideas.com/actor-framework/basics/AF-basics-walkthrough/ Actor Framework Basics: Walkthrough - Creating a Logger Actor]<br /> -- by [https://www.linkedin.com/in/derek-trepanier/ Derek E. Trepanier], Moore Good Ideas<br /> <br /> ''Actors are a powerful tool when creating large, highly parallelized, scalable systems in LabVIEW, but the framework takes some effort to conceptualize and therefore takes some time to learn. This series of articles will walk you through all of the major concepts in the Actor Framework world and get you to a point where you can start building and using Actor Framework applications.''<br /> <br /> [http://www.labviewcraftsmen.com/blog/fun-with-the-actor-framework-pubsub Fun with the Actor Framework: PUB/SUB] - by [https://www.linkedin.com/in/jon-mcbee/ Jon McBee], LabVIEW Craftsmen Blog<br /> <br /> ''Communication between Actors is meant to be done by traversing the Actor tree.  Assuming we decide not to pass message enqueuers around to all Actors in the tree, we will end up with a lot of message classes and a lot of message routing.  The extra messages and routing, however, buys us robustness as Actor E has no way of knowing if Actor C currently exists.  But what if we could bypass the tree for certain types of messages in a way that allowed us to decouple our actors from each other...''<br /> <br /> &quot;[[Convert Queued Message Handler (QMH) to Actor Framework (AF)|Actor Framework is not as hard as you think and here is why…]]&quot; - by Quentin &quot;Q&quot; Alldredge, Q Software Innovations, LLC<br /> <br /> ''If you are familiar with the Queued Message Handler (QMH) Design Pattern and Object-Oriented Programming (OOP) then you already know everything you need to start with Actor Framework.  The purpose of this article is to show the parts of the Actor Framework that are comparable to the QMH Design Pattern and provide a step-by-step procedure for converting a QMH project to an Actor Framework project.''<br /> <br /> == External Links ==<br /> *[https://forums.ni.com/t5/Actor-Framework/ct-p/7001 NI Community].<br /> *[https://forums.ni.com/t5/Actor-Framework-Documents/READ-THIS-FIRST-to-get-started-with-Actor-Framework/ta-p/3493762 NI Introduction].<br /> *[http://forums.ni.com/t5/Labvolution/LabVIEW-Actor-Framework-Basics/ba-p/3476654 Actor Framework Basics by Labvolution].<br /> <br /> [[Category:Actor Framework]]<br /> [[Category:Frameworks]]</div>

Hooovahh https://labviewwiki.org/w/index.php?title=Object-oriented_programming&diff=5738 2018-11-30T15:35:34Z

<p>Hooovahh: </p> <hr /> <div>Object oriented software designs in LabVIEW follow many of the same programming principals as object oriented software in [https://en.wikipedia.org/wiki/Object-oriented_programming other programming languages]. In general object oriented software is done in LabVIEW by first creating a class. This class is an object that has has the ability to add functionality to data. This allows for abstraction of the underlining data and allows operations to happen on a more segmented part of the application. This often leads to better reusability and scalability.<br /> <br /> == Access Scope ==<br /> <br /> Object oriented software allows for specific data, or functions to have scope set to them which restricts access from other parts of the application. A common use for this is with internal references, or sessions, which if given to the rest of the application could be inadvertently closed. By keeping the internal references from being accessed externally, an object can have more control over who has access, and how its internals are accessed.<br /> <br /> == Inheritance ==<br /> <br /> Using object oriented software in LabVIEW allows for a class to inherit from another class. This child class has the ability to call all the parents functions, but then also can optionally override a parents call if the VI is setup to be dynamic dispatch.<br /> <br /> == Dynamic Dispatch ==<br /> <br /> Calling a parents initialize function might not be sufficient for all children, and so a dynamic dispatch call can override the parents call with the child's specific implementation. This child implementation can also call the parent's depending on how the VI is written.<br /> <br /> == External Links ==<br /> *[http://www.ni.com/white-paper/3573/en/ NI FAQ on Object Oriented Programming].<br /> *[https://forums.ni.com/t5/LabVIEW-Development-Best/Introduction-to-Object-Oriented-Programming-and-Hardware/ta-p/3519580 Introduction to Object Oriented Programming] by Elijah Kerry<br /> *[http://zone.ni.com/reference/en-XX/help/371361P-01/lvconcepts/creating_classes/ Creating Classes].<br /> *[https://forums.ni.com/t5/LabVIEW-Development-Best/When-Should-You-Use-LabVIEW-Classes/ba-p/3478257 When should you use classes].</div>

Hooovahh https://labviewwiki.org/w/index.php?title=Abstraction&diff=5737 2018-11-30T15:33:21Z

<p>Hooovahh: </p> <hr /> <div>Abstraction is a concept of software design which places the complexity of various parts of the application into its own self contained [[Object_oriented_software|objects]]. This is mostly commonly used on Hardware Abstraction Layers, which can allow for communicating with various hardware devices which all have common interfaces but have specific implementations.<br /> <br /> == External Links ==<br /> *[https://forums.ni.com/t5/Abstraction-Distraction/gp-p/grp-3010 Abstraction Distraction].<br /> *[http://www.ni.com/webcast/3431/en/ Hardware Abstraction Layer (HAL)] by Elijah Kerry - [https://forums.ni.com/t5/LabVIEW-Development-Best/Measurement-Abstraction-Plugin-Framework-with-Optional-TestStand/ta-p/3531389 Plugin Framework]<br /> *[https://www.youtube.com/watch?v=qrzBYIrA-cs JKI Hardware Abstraction Video].</div>

Hooovahh https://labviewwiki.org/w/index.php?title=Abstraction&diff=5736 2018-11-30T15:33:10Z

<p>Hooovahh: </p> <hr /> <div>Abstraction is a concept of software design which places the complexity of various parts of the application into its own self contained [[Object_oriented_software|objects]. This is mostly commonly used on Hardware Abstraction Layers, which can allow for communicating with various hardware devices which all have common interfaces but have specific implementations.<br /> <br /> == External Links ==<br /> *[https://forums.ni.com/t5/Abstraction-Distraction/gp-p/grp-3010 Abstraction Distraction].<br /> *[http://www.ni.com/webcast/3431/en/ Hardware Abstraction Layer (HAL)] by Elijah Kerry - [https://forums.ni.com/t5/LabVIEW-Development-Best/Measurement-Abstraction-Plugin-Framework-with-Optional-TestStand/ta-p/3531389 Plugin Framework]<br /> *[https://www.youtube.com/watch?v=qrzBYIrA-cs JKI Hardware Abstraction Video].</div>

Hooovahh https://labviewwiki.org/w/index.php?title=Abstraction&diff=5735 2018-11-30T15:32:16Z

<p>Hooovahh: Created page with &quot;Abstraction is a concept of software design which places the complexity of various parts of the application into its own self contained objects. This is mostly commonly used...&quot;</p> <hr /> <div>Abstraction is a concept of software design which places the complexity of various parts of the application into its own self contained objects. This is mostly commonly used on Hardware Abstraction Layers, which can allow for communicating with various hardware devices which all have common interfaces but have specific implementations.<br /> <br /> == External Links ==<br /> *[https://forums.ni.com/t5/Abstraction-Distraction/gp-p/grp-3010 Abstraction Distraction].<br /> *[http://www.ni.com/webcast/3431/en/ Hardware Abstraction Layer (HAL)] by Elijah Kerry - [https://forums.ni.com/t5/LabVIEW-Development-Best/Measurement-Abstraction-Plugin-Framework-with-Optional-TestStand/ta-p/3531389 Plugin Framework]<br /> *[https://www.youtube.com/watch?v=qrzBYIrA-cs JKI Hardware Abstraction Video].</div>

Hooovahh https://labviewwiki.org/w/index.php?title=Object-oriented_programming&diff=5734 2018-11-30T15:26:22Z

<p>Hooovahh: Created page with &quot;Object oriented software designs in LabVIEW follow many of the same programming principals as object oriented software in [https://en.wikipedia.org/wiki/Object-oriented_progra...&quot;</p> <hr /> <div>Object oriented software designs in LabVIEW follow many of the same programming principals as object oriented software in [https://en.wikipedia.org/wiki/Object-oriented_programming other programming languages]. In general object oriented software is done in LabVIEW by first creating a class. This class is an object that has has the ability to add functionality to data. This allows for abstraction of the underlining data and allows operations to happen on a more segmented part of the application. This often leads to better reusability and scalability.<br /> <br /> == Access Scope ==<br /> <br /> Object oriented software allows for specific data, or functions to have scope set to them which restricts access from other parts of the application. A common use for this is with internal references, or sessions, which if given to the rest of the application could be inadvertently closed. By keeping the internal references from being accessed externally, an object can have more control over who has access, and how its internals are accessed.<br /> <br /> == Inheritance ==<br /> <br /> Using object oriented software in LabVIEW allows for a class to inherit from another class. This child class has the ability to call all the parents functions, but then also can optionally override a parents call if the VI is setup to be dynamic dispatch.<br /> <br /> == Dynamic Dispatch ==<br /> <br /> Calling a parents initialize function might not be sufficient for all children, and so a dynamic dispatch call can override the parents call with the child's specific implementation. This child implementation can also call the parent's depending on how the VI is written.<br /> <br /> == External Links ==<br /> *[http://www.ni.com/white-paper/3573/en/ NI FAQ on Object Oriented Programming].<br /> *[http://zone.ni.com/reference/en-XX/help/371361P-01/lvconcepts/creating_classes/ Creating Classes].<br /> *[https://forums.ni.com/t5/LabVIEW-Development-Best/When-Should-You-Use-LabVIEW-Classes/ba-p/3478257 When should you use classes].</div>

Hooovahh https://labviewwiki.org/w/index.php?title=Rusty_nails&diff=5699 2018-11-29T13:54:14Z

<p>Hooovahh: Created page with &quot;&quot;Rusty Nails&quot; in the LabVIEW community is a reference to a LabVIEW feature that is undocumented, incomplete, and generally features of LabVIEW that NI doesn&#039;t intend for the g...&quot;</p> <hr /> <div>&quot;Rusty Nails&quot; in the LabVIEW community is a reference to a LabVIEW feature that is undocumented, incomplete, and generally features of LabVIEW that NI doesn't intend for the general audience to have access to. This expression originated from Greg McKaskle, and NI employee around the 1999 timeframe. When asked about undocumented INI settings in LabVIEW Greg had this to say:<br /> <br /> &lt;blockquote&gt;<br /> As mentioned, most of these configuration options are available from within the Preference dialog. There are also configuration options that aren't in that list because they are needed so early in LV's launch that the resources aren't open yet; so this isn't the complete list. The options that aren't in the preferences dialog are generally considered to be not useful or even harmful. They are sometimes there to allow us a backdoor or a workaround for when we change a behavior. They are also used to turn on obscure development features that we, the LV developers, use to make or debug LV. These obscure features are typically kind of like the attic or basement of a house, not finished out, not very interesting, and potentially harmful.<br /> <br /> We have never tried to hide any of these strings, and I don't believe you will gain any benefit from trying out various combinations of the settings. If you ask technical support what a setting is, they will likely tell you that they have no idea. They are telling you the truth. I don't even know what some of them do without checking the code. Others, such as exoticcontrols, no longer do anything. It was once used to show a control palette submenu that contained controls that were still in work and not ready for prime-time. They were experiments, unsupported features, and guaranteed to crash if you did much with them. Just the sort of thing that we need for development, but not useful to even advanced LV users unless they have a death-wish.<br /> <br /> If you experiment with the .ini file and you crash mysteriously losing hours of work, I'd suggest putting the file back to the way LV left it. Don't ask tech support to fix it or complain that the LV attic has rusty nails and splinters.<br /> <br /> As for whether or not Resedit is wonderful, I personally prefer Resorcerer, but that is a different story. It is a low level tool that in the right hands is useful, in the wrong hands, well, its in the wrong hands. For the person that likes taking a multimeter and a soldering iron to computers and household appliances, its exactly what you always wanted. If you start monkeying with things in the resources or the .ini file, use common sense and do it on a copy or you will just end up reinstalling LV.<br /> <br /> Once the fun and experimentation is over with, I think you will agree that the useful options, with very few exceptions are in the Preference dialog.&lt;ref&gt;[http://info-labview.org/ILVMessages/1999/05/27/Info-LabVIEW_Digest_1999-05-27_025.html Info-LabVIEW] archive, Subject: Complete list of Labview Options - May 27th 1999&lt;/ref&gt;<br /> &lt;/blockquote&gt;<br /> <br /> <br /> Back in the LabVIEW 5.x and 6.x era there was a new emerging technology that was [[VI_Scripting|LabVIEW Scripting]]. NI had created scripting for their own purposes but the community saw it and wanted to be able to automate editing, or creating LabVIEW code. With the help from Jim Kring and others, the basic tools for enabling scripting in LabVIEW were available. Discussing scripting often leads into discussing other [[INI|INI keys]] which enable private functions like the well known SuperSecretPrivateSpecialStuff. It is possible this is one of the keys Greg was referring to.<br /> <br /> After [[LAVA|LAVA's]] creation a subforum section was labeled Rusty Nails, and intended to be a place to discuss Scripting, ExternalNodes, XNodes, Private methods, and general LabVIEW hackery. Over the years several private functions have been made public, and scripting has become an official feature shipping with LabVIEW. Because of this the Rusty Nails and XNodes subforums were combined into what is now the VI Scripting section. Even over on the official NI forums, discussions about private functionality and XNodes has been relaxed since those early days. Asking for private methods and getting unofficial help is something users, and sometimes NI employees will participate in, without the heavy censorship seen earlier. Topics of scripting are encouraged now that the feature has been official supported.<br /> <br /> ==Notes==<br /> &lt;references /&gt;</div>

Hooovahh https://labviewwiki.org/w/index.php?title=VI_Scripting&diff=5686 2018-11-26T19:14:54Z

<p>Hooovahh: </p> <hr /> <div>[[File:Lv scripting.jpg|thumb|VI Scripting Nodes appear as Light Cyan]]<br /> '''VI Scripting''', also known as Scripting, deals with the ability of LabVIEW to use G to write G. VI Scripting contains several new [[VI Server]] classes, properties, methods, and events so you can create, move, and wire objects; edit the connector pane; create new VIs; and more. Scripting is useful for generating or editing VIs automatically based on simpler configurations. Examples of scripting include the code generated by Express VIs, the code generated for LVOOP Accessor VIs and the code generated by the NI Vision Builder. Because scripting requires recompiling the VI and may break it, you can not run scripting code on a VI which is reserved for running.<br /> <br /> __TOC__<br /> <br /> == History ==<br /> VI Scripting began shipping with LabVIEW beginning with [[LabVIEW 2010]]. However, it is available for download from the [http://sine.ni.com/nips/cds/view/p/lang/en/nid/209110 LabVIEW Tools Network] for [[LabVIEW 8.6]] and [[LabVIEW 2009|2009]]. Before [[LabVIEW 8.6]] scripting was an undocumented feature and was available to those that knew how to enable it as early as [[LabVIEW 7 Express|version 7]]. However, as it was not documented or supported to the greater community, it had the potential to be dangerous. Before scripting was official an NI employee famously refferred to it as something akin to [[Rusty_nails|Rusty Nails]].<br /> <br /> == Usage ==<br /> <br /> VI Scripting generally falls into three categories:<br /> # Using G to automate the generation of more G<br /> # Using G to create add-on tools (i.e. [[Quick Drop]], [[Shortcut Menu Plugins]], etc.)<br /> # Using G to inspect G (i.e. [[VI Analyzer]])<br /> VI Scripting uses properties and methods to create, locate, and operate on Block Diagram objects (i.e. primatives, structures, wires, and terminals), Front Panel objects (i.e. controls, indicators, decorations, splitters, panes, and panels), edit the Connector Pane and the VI.<br /> <br /> === Code Generation ===<br /> Many of the main application frameworks use VI Scripting to automate the generation of code, modules, messages, etc. Some examples of this include:<br /> * How [[Delacor Queued Message Handler (DQMH)|DQMH]] starts new projects and adds new modules<br /> * How [[Actor Framework]] creates new messages (see also [http://www.mooregoodideas.com/actor-framework/AF-Message-maker/ MGI's AF Message Maker])<br /> <br /> ==== General Guideline for Code Generation ====<br /> <br /> VI Scripting code can get large and complex very quickly. A guideline to VI Scripting is to start with a template, make a copy, and then edit the copy.<br /> <br /> Another common use case of VI Scripting is to automate repetitive tasks. For example, if the code required the generation of many similar VIs. It might be more efficient to create a template and then write the scripting code to copy, modify, and save the VI.<br /> <br /> === Creation of Add-on Tools ===<br /> The creation of add-on tools can improve efficiency by automating repetitive tasks or making tasks easier to accomplish. There are many hooks into the LabVIEW IDE to let you create add-on tools.<br /> <br /> Presentation to help create new tools:<br /> * [https://learn.ni.com/center-of-excellence/resources/1141/don-t-wait-for-labview-r-d-implement-your-own-labview-features Don't Wait for LabVIEW R&amp;D, Implement Your Own LabVIEW Features] - by Darren Nattinger, National Instruments<br /> * [https://forums.ni.com/t5/Top-of-Utah-LabVIEW-User-Group/Seven-Things-Your-Doctor-Won-t-Tell-You-About-LabVIEW-Scripting/gpm-p/3685320 Seven Things Your Doctor Won't Tell You About LabVIEW Scripting] - by Quentin Alldredge, Q Software Innovations<br /> Cool tools that currently exist:<br /> * More to come<br /> <br /> === Code Inspection ===<br /> Another use of VI Scripting is to automate inspection of code to ensure adherence to style guidelines and effective programming practices, to catch common errors, and improve performance, functionality, and maintainability.<br /> <br /> Such tools include:<br /> * [[VI Analyzer]] - The LabVIEW VI Analyzer Toolkit helps you improve the quality and readability of graphical code developed in LabVIEW software.<br /> * [http://sine.ni.com/psp/app/doc/p/id/psp-844/lang/en LabVIEW Unit Test Framework] - The Unit Test Framework Toolkit provides interactive tools to create, configure, manage, and execute tests that check VIs for functional correctness.<br /> * [https://github.com/JKISoftware/JKI-VI-Tester JKI VI Tester] - software test framework for LabVIEW that allows software developers to test their LabVIEW code; VI Tester is based on the industry standard xUnit software test architecture that is used in many other programming languages<br /> * [https://github.com/JKISoftware/Caraya JKI Caraya Unit Tester] - open source assertion and unit testing framework for LabVIEW; convert your manual test VIs you use for debugging into unit test cases with nearly no effort<br /> <br /> == Enabling VI Scripting ==<br /> [http://zone.ni.com/reference/en-XX/help/371361P-01/lvhowto/enabling_vi_scripting/ Instructions for enabling VI Scripting]<br /> <br /> == Getting Started ==<br /> * [http://zone.ni.com/reference/en-XX/help/371361P-01/lvhowto/scripting_quick_reference/ Common VI Scripting Tasks]<br /> <br /> * [http://zone.ni.com/reference/en-XX/help/371361P-01/lvhowto/scripting_tutorial_intro/ VI Scripting Tutorial]<br /> <br /> == Tips and Tricks ==<br /> [https://forums.ni.com/t5/LabVIEW-APIs-Discussions/Exploring-the-Depths-of-the-VI-Server/td-p/3844848 Exploring the Depths of the VI Server] - by Quentin Alldredge, Q Software Innovations<br /> <br /> This presentation goes into the depths of the [[VI Server]] including Basic LabVIEW, VI Scripting, and even the Private stuff, showing many of the Properties, Methods, and Events I have found useful in the creation of LabVIEW IDE add-ons.<br /> <br /> [https://delacor.com/5-steps-to-become-a-vi-scripting-ninja/ 5 Steps to Become a VI Scripting Ninja] - Fabiola De la Cueva, Delacor<br /> <br /> Why would you want to use LabVIEW Scripting? LabVIEW VI scripting allows LabVIEW Developers to programmatically generate, edit, and inspect LabVIEW code. You would want to use LabVIEW VI Scripting to create tools that would make you and your team more efficient, to enforce coding guidelines or to automate repetitive tasks.<br /> <br /> [[Category:Development Environment]]<br /> [[Category:VI Scripting]]</div>

Hooovahh https://labviewwiki.org/w/index.php?title=Aspects_of_error_handling&diff=5525 2018-11-15T18:11:18Z

<p>Hooovahh: </p> <hr /> <div>{{Template:ActiveDiscuss}}<br /> Writing VIs and SubVIs that incorporate error handling is considered good form, not only to allow the user indication of abnormal software execution, but also to allow the software to make decisions based on the status of previous operations. Including error clusters in your code assists in troubleshooting, modularity, and user friendliness.<br /> <br /> == The Error Cluster ==<br /> The error cluster is a predefined LabVIEW cluster that is used to contain error status information. The cluster contains the following three components:<br /> <br /> {| class=&quot;wikitable&quot;<br /> |-<br /> ! Name<br /> ! Data Type<br /> ! Description<br /> |-<br /> | Status<br /> | Boolean<br /> | Indicates if an error has occurred (TRUE = error, FALSE = no error).<br /> |-<br /> | Code<br /> | 32-Bit signed integer<br /> | A standardized error code specific to the particular error. LabVIEW has a table of default error codes, although the user is able to define custom error codes. See below for more information.<br /> |-<br /> | Source<br /> | String<br /> | Textual information often describing the error and the VI it occurred within.<br /> |}<br /> <br /> == Usage ==<br /> Although one of the most obvious methods of conditional code execution might be to unbundle the Status Boolean of the error cluster, and feed it to the conditional terminal of a case structure (figure coming soon...), the complete cluster can be wired to it instead (figure coming soon...). The functionality of the code in (figure coming soon...) and (figure coming soon...) is identical, although its readability is vastly improved as the second example colors the case structure green for the No Error case, and red for the Error case. Wrapping the entire code of a SubVI within a conditional case structure based on the error input allows VIs at higher levels to continue functioning, without executing code that could be useless or even dangerous when an error has occurred. Consider the simple report generation example shown in (figure coming soon...).<br /> <br /> A report is initially created, a file is then attached, the report is printed, and finally destroyed. The dataflow link between these SubVIs is the report’s reference number (refnum), which ensures each execute in a predefined order. If each of the SubVIs execute without error, then the process completes successfully. Conversely, if one of the SubVIs encounters an error, subsequent SubVIs are unaware of the problem and attempt to execute regardless. In the example above, an error in the Attach a File to the Report SubVI will not cause the Print the Report SubVI to fail, resulting in a blank report print. If effective error handling is introduced (figure coming soon...), the Print the Report SubVI will know if an error has occurred before its execution is requested. If the functional code inside the Print the Report SubVI is enclosed within a conditional case structure based on the error input, the printing code is bypassed, and the error cluster is passed on to the next SubVI.<br /> <br /> To attain a higher level of user interaction, standard SubVIs exist to alert the user to an error on the error cluster, and prompt for conditional actions. The Simple Error Handler.vi (figure coming soon...) allows for a basic level of error cluster status reporting, displaying detected errors in a dialog box, and prompting the user for an action based on the type of dialog input (for example, OK, Cancel, Stop, etc.).<br /> <br /> The Simple Error Handler.vi is a wrapper for the lower level General Error Handler.vi. The latter (figure coming soon...) is more configurable, and permits the dynamic definition of custom error codes, and error exception handling. LabVIEW 7.0 brings with it an addition to the error handling function palette, Clear Errors.vi (figure coming soon...). This VI is simply an error in control and an<br /> error out indicator, which are not linked on the wiring diagram, causing any errors on the wired error link to be cancelled. This VI can be useful when constructing custom error-handling VIs, including dialog boxes allowing user interaction that is not covered by the simple and general error-handling VIs, but should not be used alone. Although dumping the errors from the error cluster may be tempting, one must incorporate appropriate code to handle them.<br /> <br /> == Wiring Errors into a SubVI Connector Pane ==<br /> As described above, SubVIs have an associated connector pane, and the placement of error cluster inputs and output is generally in the lower quadrants (error in on the left, and error out on the right), with corresponding exclamation marks over the connectors on the SubVI’s icon (figure coming soon...).<br /> <br /> == Default Error Codes ==<br /> The LabVIEW execution system contains a large list of standard and specific errors, encouraging the reuse of generic codes across applications. A list of generic errors codes can be found under the LabVIEW Help menu (figure coming soon...). Another method of parsing a small number of errors is to select the Help Explain Error menu item. This will launch an interface that allows the user to enter an error code, and a brief explanation is displayed (figure coming soon...). This interface is also accessible by right-clicking on a front panel error cluster, and selecting Explain Error.<br /> <br /> == Custom Error Codes ==<br /> National Instruments has set several error codes aside for custom use. If an existing error code does not adequately describe the error condition, the user can define custom codes that are specific to the application. Codes between 5000 through to 9999 are available for use, and do not need to conform to any other application. Although General Error Handler.vi can be used to define custom error codes, one can also create an XML file in the labview\user.lib\errors directory that contains custom error codes and their descriptions. This method is particularly useful if the user requires custom error codes to apply to several applications, or if the codes are used by several software engineers in a team or are to be distributed with an application.<br /> <br /> For example, the XML filename must be in the format '''*-errors.txt''' (where '''*''' is user definable), and the internal file structure must adhere to the following format:<br /> <br /> &lt;blockquote&gt;&lt;br /&gt;<br /> &lt;?XML Version=&quot;1.0&quot;&gt;&lt;br /&gt;<br /> &lt;nidocument&gt;&lt;br /&gt;<br /> &lt;nicomment&gt;&lt;br /&gt;<br /> This is a custom error code definition file for my application.&lt;br /&gt;<br /> &lt;/nicomment&gt;&lt;br /&gt;<br /> &lt;nierror code=&quot;5000&quot;&gt;&lt;br /&gt;<br /> User Access Denied!&lt;br /&gt;<br /> Contact the Security Department to gain clearance to perform this function.&lt;br /&gt;<br /> &lt;/nierror&gt;&lt;br /&gt;<br /> &lt;nierror code=&quot;5001&quot;&gt;&lt;br /&gt;<br /> User Unknown.&lt;br /&gt;<br /> Contact the People Development Department.&lt;br /&gt;<br /> &lt;/nierror&gt;&lt;br /&gt;<br /> &lt;nierror code=&quot;5100&quot;&gt;&lt;br /&gt;<br /> Driver Unable to Contact Instrument Database.&lt;br /&gt;<br /> Contact the Software Engineering Department Helpdesk.&lt;br /&gt;<br /> &lt;/nierror&gt;&lt;br /&gt;<br /> &lt;nierror code=&quot;5200&quot;&gt;&lt;br /&gt;<br /> Plug-In Module in R&amp;D mode – not to be used in Production Environment.&lt;br /&gt;<br /> Contact the New Product Development Group.&lt;br /&gt;<br /> &lt;/nierror&gt;&lt;br /&gt;<br /> &lt;/nidocument&gt;<br /> &lt;/blockquote&gt;<br /> <br /> As can be seen, a file comment can be created within the &lt;nicomment&gt; tag space. Each custom error is defined as an &lt;nierror&gt; with it’s associated error code, and its error message is then placed inside the &lt;nierror&gt; tag space. Although hand coding a custom error code XML file is possible, the Error Code File Editor (Tools-&gt;Advanced-&gt;Edit Error Codes) provides a simple GUI for file creation and editing (figure coming soon...). Once custom error code files have been created and/or altered, LabVIEW must be<br /> restarted for the changes to take effect. It is often useful to define code bands during the project planning stage, setting aside bands for specific related error groups.<br /> <br /> ----<br /> '''Note''':<br /> This entire section of WIKI about &quot;Error Handling&quot; could benefit from a deep reading of the online help for the General Error Handler.vi. That VI has more facilities than folks typically know. FOR EXAMPLE: <br /> <br /> The General Error Handler.vi includes an input parameter for the type of dialog, one option is &quot;no dialog.&quot; I would STRONGLY recommended instead of calling &quot;Error Code Database.vi&quot;. The primary reason for the recommendation is that the translation of error code cluster into human readable strings involves much more than just looking up text in the database. The '''source''' string itself may include information to override or extend the database, and the text in either the '''source''' string or the database may include formatting commands, such as HTML tags for bold face. Encoding information in the '''source''' string is a technique that will become more common in the future. <br /> <br /> You may desire to display the text, fully formatted, in a string indicator of your own instead of in any dialog. Use the function of General Error Handler CORE.vi (found on the block diagram of General Error Handler.vi) to do this.<br /> <br /> == External Links ==<br /> <br /> *[http://www.ni.com/getting-started/labview-basics/handling-errors Error Handling Basics by NI].<br /> *[http://controlsoftwaresolutions.com/error-handling-strategies-labview/ David Maidman’s Blog Post].<br /> *[https://forums.ni.com/t5/LabVIEW-Development-Best/quot-SOLID-Error-Handling-quot-presentation-at-NIWeek-2017/td-p/3629639 SOLID Error Handling by Dmitry].<br /> *[http://www.ni.com/example/31253/en/ Structured Error Handler Express VI by NI]<br /> <br /> [[Category:LabVIEW fundamentals]]</div>

Hooovahh https://labviewwiki.org/w/index.php?title=Online_videos&diff=5524 2018-11-15T18:07:13Z

<p>Hooovahh: </p> <hr /> <div>&lt;span&gt;Below is a list of online videos related to LabVIEW topics. Most cover basic training but some cover specific LabVIEW topics.&lt;/span&gt;&lt;p class=&quot;mw_paragraph&quot;&gt;<br /> <br /> <br /> *[https://www.youtube.com/channel/UCJnMVoaGnTr0HNQwTP_GTww NI's LabVIEW Channel]<br /> *[https://youtu.be/90yKPBLmDJ4 LabVIEW Training Course by Hardware Thrift]<br /> *[[NI_week#Videos|NI Week and CLA Conference Videos]]<br /> *[https://www.youtube.com/channel/UCJ0jhJNGk9kjc12npjy6b4g/ GDevCon Conference Videos]<br /> *[https://www.youtube.com/channel/UCvC4jW38T9_UoV_3-bdlXvA LabVIEW ADVANTAGE]<br /> *[https://www.youtube.com/channel/UC2JvDufj1vB6GewXYMfpe-Q LabVIEW MakerHub]<br /> *[https://www.youtube.com/channel/UClKq6SMtR9qtOIutMcWSWDw LabVIEW Architects Forum]<br /> *[https://www.youtube.com/channel/UCD1Fm1HYETmjbBPyucbLRrw Delacor's Youtube Channel]<br /> *[https://www.youtube.com/channel/UCwgd_sopH-ll3odVtTXY4oA System Automation Solutions LLC]<br /> *[https://www.youtube.com/channel/UCVfW08kA4N3jytIitOnH9NQ Dr. James D Powell]<br /> *[https://www.youtube.com/watch?v=RuIN31rSO2k NI Video on Event Driven Design].<br /> *[https://www.youtube.com/watch?v=aT0obtY3PRk Sixclear Video on State Machines].<br /> <br /> [[Category:Lists]]<br /> [[Category:LabVIEW ecosystem]]</div>

Hooovahh https://labviewwiki.org/w/index.php?title=State_Machine&diff=5523 2018-11-15T18:06:05Z

<p>Hooovahh: Updated external links and categories</p> <hr /> <div>The '''State Machine''' is a convenient LabVIEW construct where a case structure is contained with a while loop. Execution of particular cases in the structure is determined by the output from the previous case (or in the instance of the first execution) by the control selector input. The control of the order of case execution is controlled through the use of a shift register. By wiring the output from one case as the determinate to the subsequent case (wiring to the shift register on the right hand side) and wiring the input to the case selector from the left hand side shift register, operations can be ordered according to which state is executed.&lt;br /&gt;[[Image:Simple_State_Machine.png]]&lt;br /&gt;<br /> <br /> The state machine has the advantage of allowing several steps to be linked in series so that each individual step can be executed (or debugged) easily. The trap for the inexperienced programmer is the use of the state machine to step in a haphazard fashion through the cases in the loop. This can lead to complicated pathways through the state machine reminiscent of convoluted goto statements in conventional text based languages. However state machines are a valuable tool and can be used very effectively with this in mind.<br /> <br /> State machines can be based around integers, strings or enumerated types. The relative merits of each have been discussed in detail elsewhere. In summary an enumerated type state machine has the advantage of being automatically updated when the enum is changed (if the enum is a [[Type Definition]]) but has the disadvantage of requiring careful checking of all the code if new states (enums) are added or redundant states deleted. A string state machine has the advantage of easily added or removed states, but has the disadvantage of spelling mistakes causing programming errors (Note: this can be reduced by including the &quot;Default&quot; state showing the misspelled case in a pop up dialog box, as seen below).&lt;br /&gt;[[Image:String_Based_State_Machine_Default_Case.png]]<br /> <br /> __TOC__<br /> <br /> == Controlling Order of State Execution ==<br /> There are three possible ways to order a LabVIEW state machine. The first and easiest method (although NOT recommended) is to use an integer. The integer output from one case is wired as the selector for the subsequent case. The disadvantage of this method is that the numbers themselves are not very helpful in tracking through the code and the case selector becomes somewhat meaningless. Either of the following methods are preferred and there are pros and cons for each of them. Debate (strong at times) arises on the list quite frequently as to the best of these methods, but in practice either will work very nicely.<br /> <br /> The second method is to use a string as the case selector. With the correct choice of string states, this has the advantage of labeling each case so that your state machine becomes self documenting. A further advantage of this method is that all cases need not be written in the first instance and it is somewhat easier to include new states should the need arise (especially in earlier versions of LabVIEW (&lt; 6.0)). The disadvantage is that it is easy to misspell a state and have the state machine buggy because of his. An easy way to overcome this disadvantage is to include a default case that pops up a warning including the spelling of the failed case.<br /> <br /> The third method is to use an enumerated type as the case selector. In preference this enum should be a [[Type Definition]] so that changes to the states are reflected easily and transparently when new states are added to the enum (via the LabVIEW auto update from [[Type Definition]] setting). Note that there are reports where this method causes problems in version of LabVIEW prior to 6.0, because the enum auto updating did not correctly handle newly inserted cases. This method has the advantage of the string method in code documentation, but requires the use of a default case if not all the cases are required to be written when the code is first created.<br /> <br /> == Passing Data Between States ==<br /> Data is commonly passed between the states of a state machine using a [[Shift Register]], similar to how the state variable is passed between states. It is a common practice to use a single [[Cluster]] (preferably a [[Type Definition]]) to hold all the data in a single [[Shift Register]], rather than multiple shift registers for multiple data elements.<br /> <br /> == Variations ==<br /> <br /> === Sequencer Pattern ===<br /> <br /> The Sequencer Pattern is a variation of the State Machine. Instead of a state leading to one or multiple states, the sequencer states are hard-coded in an array which dictates the order of execution. Only a state producing an error changes the sequence of operation by stopping the state machine. A state can be executed more than once by including it in multiple places in the hard-coded state array. See more on the [https://forums.ni.com/t5/Example-Program-Drafts/Sequencer-Template/ta-p/3842265 Sequencer Pattern].<br /> <br /> === VI Scripting Pattern ===<br /> <br /> The VI Scripting Pattern is a variation of the State Machine design specifically for writing [[VI Scripting]] code. It uses an enum as the definition of the sequence of events in which to traverse incrementing through the enum for each state. Therefore the sequence of state execution is hard-coded. The VI Scripting Pattern will not repeat a state due to an enum not being able to have two entries of the same name unless two enum values are used for the same state. An error occurring in any state will cause the state machine to end. See more on the [https://www.mooregoodideas.com/technical-discussion/vi-scripting-pattern/ VI Scripting Pattern].<br /> <br /> == See Also ==<br /> <br /> *[[Queued State Machine]]<br /> <br /> == External Links ==<br /> <br /> *[http://www.ni.com/tutorial/7595/en/ NI Tutorial on State Machine Basics].<br /> *[https://www.youtube.com/watch?v=RuIN31rSO2k NI Video Event Driven Design].<br /> *[https://www.youtube.com/watch?v=aT0obtY3PRk Sixclear Video].<br /> *[http://jkisoft.com/state-machine JKI State Machine] - An easy-to-use yet powerful state machine template from [http://jkisoft.com JKI Software].<br /> *[https://en.wikipedia.org/wiki/State_machine_(LabVIEW_programming) Wikipedia Article].<br /> <br /> [[Category:Design patterns]]<br /> [[Category:LabVIEW fundamentals]]</div>

Hooovahh https://labviewwiki.org/w/index.php?title=Getting_Started&diff=5522 2018-11-15T17:55:12Z

<p>Hooovahh: </p> <hr /> <div>&lt;span&gt;This page is intended to be a starting point and resource to help navigate all LabVIEW content on this Wiki and elsewhere.&lt;/span&gt;&lt;p class=&quot;mw_paragraph&quot;&gt;[[LabVIEW|General information about LabVIEW]]<br /> <br /> *Basic Topics<br /> **[[Training|Online Training]]<br /> **[[LabVIEW_style_guide|LabVIEW Style Guide]]<br /> **[[Community|Online Community]]<br /> **[[Contributing_online|Contributing Online]]<br /> **[[Finding_professional_help|Finding Professional Help]]<br /> **[[Tips_and_tricks|Useful Tips and Tricks]]<br /> **[[State_machine|State Machine Design Pattern]]<br /> *Advanced Topics<br /> **[[Object_oriented_software|Object Oriented Software]]<br /> **[[Abstraction|Abstraction]]<br /> **[[Actor_framework|Actor Framework]]<br /> **[[Error_handling|Error Handling]]<br /> **[[Source_code_control|Source Code Control]]<br /> **[[SOLID_principals|SOLID Principals]]<br /> **[[Unit_testing|Unit Testing]]<br /> **[[VI_analyzer|VI Analyzer]]<br /> **[[Virtual_machines|Virtual Machines]]<br /> *Connecting With Other Developers<br /> **[[User_groups|User Groups]]<br /> **[[NI_week|NI Week]]<br /> **[[Summits|Summits]]<br /> *[[LabVIEW_blogs|LabVIEW Blogs]]<br /> *[[Online_videos|Online Videos]]<br /> *[[Certifications|Certifications]]<br /> <br /> <br /> &lt;ul&gt;&lt;li&gt;[[data flow|Data Flow]]&lt;/li&gt;&lt;li&gt;[[LabVIEW tutorial|LabVIEW Tutorial]]&lt;/li&gt;&lt;li&gt;Hardware Basics&lt;/li&gt;&lt;/ul&gt;<br /> <br /> [[Category:Lists]]</div>

Hooovahh https://labviewwiki.org/w/index.php?title=Online_videos&diff=5521 2018-11-15T17:53:30Z

<p>Hooovahh: Updated categories</p> <hr /> <div>&lt;span&gt;Below is a list of online videos related to LabVIEW topics. Most cover basic training but some cover specific LabVIEW topics.&lt;/span&gt;&lt;p class=&quot;mw_paragraph&quot;&gt;<br /> <br /> <br /> *[https://www.youtube.com/channel/UCJnMVoaGnTr0HNQwTP_GTww NI's LabVIEW Channel]<br /> *[https://youtu.be/90yKPBLmDJ4 LabVIEW Training Course by Hardware Thrift]<br /> *[[NI_week#Videos|NI Week and CLA Conference Videos]]<br /> *[https://www.youtube.com/channel/UCJ0jhJNGk9kjc12npjy6b4g/ GDevCon Conference Videos]<br /> *[https://www.youtube.com/channel/UCvC4jW38T9_UoV_3-bdlXvA LabVIEW ADVANTAGE]<br /> *[https://www.youtube.com/channel/UC2JvDufj1vB6GewXYMfpe-Q LabVIEW MakerHub]<br /> *[https://www.youtube.com/channel/UClKq6SMtR9qtOIutMcWSWDw LabVIEW Architects Forum]<br /> *[https://www.youtube.com/channel/UCD1Fm1HYETmjbBPyucbLRrw Delacor's Youtube Channel]<br /> *[https://www.youtube.com/channel/UCwgd_sopH-ll3odVtTXY4oA System Automation Solutions LLC]<br /> *[https://www.youtube.com/channel/UCVfW08kA4N3jytIitOnH9NQ Dr. James D Powell]<br /> <br /> [[Category:Lists]]<br /> [[Category:LabVIEW ecosystem]]</div>

Hooovahh https://labviewwiki.org/w/index.php?title=List_of_LabVIEW_blogs&diff=5520 2018-11-15T17:52:00Z

<p>Hooovahh: Updated and merged blog links</p> <hr /> <div>*[https://forums.ni.com/t5/NI-Blog/bg-p/4001 NI's Blog]<br /> **NI's official blog, updated very frequently with news from NI<br /> *[https://automatedenver.com/blog/ System Automation Solutions] - 11/1/2018<br /> **Sam Taggart's Blog<br /> *[https://www.dmcinfo.com/latest-thinking/blog/articletype/categoryview/categoryid/6/labview DMC Blog] - 10/23/2018<br /> **LabVIEW category of DMC's official blog<br /> *[https://forums.ni.com/t5/Random-Ramblings-on-LabVIEW/bg-p/4012 Steve Watts Random Ramblings on LabVIEW Design] - 10/23/2018<br /> **Random Ramblings says it all but often good insight into designs and discussions we don't think about but should question why we use them and how<br /> *[https://thelvlab.wixsite.com/thelabviewlab The LabVIEW Lab] - 10/22/2018<br /> **Eric Maussion's blog<br /> *[https://www.digiajay.com/category/blog/labview/ Ajay Blog] - 10/10/2018<br /> **Ajayvignesh's LabVIEW blog<br /> *[https://www.winemantech.com/blog/topic/labview Wineman Technology Blog] - 10/10/2018<br /> **LabVIEW category of Wineman's official blog<br /> *[https://blog.jki.net/ JKI Blog] - 9/13/2018<br /> **Blog often highlighting JKI's activity including VIPM and other LabVIEW tips<br /> *[http://devs.wiresmithtech.com/ Wiresmith] - 9/25/2018<br /> **James McNally's Blog<br /> *[https://delacor.com/blog/ Delacor Blog] - 9/4/2018<br /> *[http://hooovahh.blogspot.com/search/label/LabVIEW Hooovahh's Blog] - 8/24/2018<br /> **Brian Hoover's blog focusing on LabVIEW and CAN<br /> *[http://www.bloomy.com/support/blog/blog-category/labview Bloomy's Blog] - 8/13/2018<br /> **LabVIEW category of Bloomy's official blog<br /> *[http://www.labviewcraftsmen.com/ LabVIEW Craftsmen] - 7/3/2018<br /> *[https://mgi.gitlab.io/articles/ MGI Blog] - 6/5/2018<br /> **Moore Good Ideas blog<br /> *[http://blog.eyesonvis.com/ Eyes on VIs] - 5/25/2018<br /> **Christina Rogers blog often focusing on LabVIEW's visual design UI's and UX's<br /> *[http://qcontrolsqsi.blogspot.com/ QControls] - 5/16/2018<br /> **Blog series on QControls, and open alternative to XControls<br /> *[http://www.walkingthewires.com/ Walking The Wires] - 5/11/2018<br /> **Chris Roebuck's Blog<br /> *[http://www.notatamelion.com/blog/ Not a Tame Lion] - 5/5/2016<br /> *[http://blog.sixclear.com VI High] - 11/3/2015<br /> **VI High is the LabVIEW Programming Video Blog presented by Sixclear. Most episodes are composed of common LabVIEW questions and techniques geared to beginner and intermediate developers.<br /> *[http://savvytestengineer.blogspot.com/ The Savvy Test Engineer] - 5/24/2015<br /> **Greg Dudgeon - This blog covers test engineering topics that interest me. About 25% of the time I discuss LabVIEW in one form or another.<br /> *[http://labviewartisan.blogspot.com/ LabVIEW Artisan] - 2/5/2015<br /> **Darren Nattinger's LabVIEW blog often highlighting lesser known features of LabVIEW<br /> *[http://culverson.com/category/lab-view/ Culverson Software's Blog] - 9/20/2014<br /> **LabVIEW category of Steve Bird's Blog<br /> *[http://themacview.blogspot.com The Mac View] - 8/4/2014<br /> **Marc - Virtual Instrumentation from a Mac perspective<br /> *[http://vishots.com VI Shots] - 7/31/2014<br /> **Michael Aivaliotis continues to build automated test systems for various industries since 1993. VI Shots brings you the latest news from the world of test, measurement and automation. You will find reviews, videos and insights not found anywhere else.<br /> *[http://mylabviewtshare.wordpress.com/ VIve LabVIEW] - 11/8/2013<br /> **Ezequiel Gonzalez - Newbie LabVIEW notes in Spanish.<br /> *[http://lvtechspeak.blogspot.com Technically Speaking] - 1/18/2013<br /> **This blog is shared among several technical writers/managers in the LabVIEW group. We post our views and insight on processes, new technologies that we think are cool, and other things we decide to write about.<br /> *[http://openmeas.blogspot.com/ Open Measurements] - 9/13/2010<br /> **Brian Powell - I'm a software architect on the LabVIEW R&amp;amp;D team at National Instruments.<br /> *[http://emertech.blogspot.com Emerging Technologies for Virtual Instrumentation] - 7/11/2010<br /> **Hall T. Martin - I investigate emerging technologies and apply them to the world of virtual instrumentation.<br /> *[http://ideasinwiring.blogspot.com Ideas in Wiring] - 7/18/2008<br /> **Joel Sumner - This is my storehouse of information that might be useful to the LabVIEW community. It's the stuff that falls somewhere between &quot;documentation&quot; and &quot;hallway conversation&quot; that you might find useful, entertaining, or just a way to kill some time. As with any personal Blog, I don't speak for NI, that would be way more pressure than I want to deal with. I like hearing from you.<br /> *[http://synergyenergy.blogspot.com/ Synergy Energy] - 4/18/2007<br /> **Pavan Bathla - For integrated design, simulation, test &amp;amp; measurement. Experiences of an Aerospace and Defense industry engineer. My main focus is test automation &amp;amp; simulation, using technologies such as LabVIEW, RTOS, FPGA, ADCs... Multi-disciplinary engineering topics, philosophy &amp;amp; economics always catch my attention.<br /> *[http://detritus.blogs.com/lycangeek/ Lycangeek] - 2/6/2007<br /> <br /> [[Category:Lists]]<br /> [[Category:Blogs]]<br /> [[Category:LabVIEW ecosystem]]</div>

Hooovahh https://labviewwiki.org/w/index.php?title=LabVIEW_style_guide&diff=5519 2018-11-15T15:45:54Z

<p>Hooovahh: </p> <hr /> <div>LabVIEW is a graphical programming language, and as a result emphasis is often put on how the code looks, as well as how it performs. Developers may have preferences on one style or another, but one good starting point is the following NI White Papers on Rules to Wire by:<br /> <br /> *[http://www.ni.com/white-paper/5560/en/ Rules to Wire By Part 1]<br /> *[http://www.ni.com/white-paper/4822/en/ Rules to Wire By Part 2]<br /> <br /> These guidelines in programming style are important and can be check through automated inspection using the [[VI_analyzer|VI Analyzer]] toolkit.</div>

Hooovahh https://labviewwiki.org/w/index.php?title=LabVIEW_style_guide&diff=5518 2018-11-15T15:45:16Z

<p>Hooovahh: Created page with links to Rules to Wire by and VI Analyzer</p> <hr /> <div>LabVIEW is a graphical programming language, and as a result emphasis is often put on how the code looks, as well as how it performs. Developers may have preferences on one style or another, but one good starting point is the following NI White Papers on Rules to Wire by:<br /> <br /> *[http://www.ni.com/white-paper/5560/en/ Rules to Wire By Part 1]<br /> *[http://www.ni.com/white-paper/4822/en/ Rules to Wire By Part 2]<br /> <br /> These guidelines in programming style are important and can be check through automated inspection using the [[VI_analyzer VI Analyzer]] toolkit.</div>

Hooovahh https://labviewwiki.org/w/index.php?title=NI_week&diff=5516 2018-11-12T15:49:55Z

<p>Hooovahh: </p> <hr /> <div>NI Week is a yearly technical conference hosted by NI in Austin Texas, where NI is headquartered. The conference focuses on showcasing NI's roadmap for software and hardware.<br /> <br /> = Schedule =<br /> The conference officially starts on a Monday with Alliance Day focusing on NI's [[Alliance_program|Alliance Partners]]. There are activities for non Alliance Partners on Monday but the majority of closed door presentations are off limits. Tuesday through Thursday technical sessions, training, keynotes, and other social activities take place with a schedule that changes each year. If you are interested in attending NI Week check [http://www.ni.com/niweek|NI's official page] for their schedule.<br /> <br /> = Videos =<br /> The majority of the content at NI Week is the technical sessions. These can be presented by NI employees, or any member of the public after being approved by NI. Over the years several NI sessions have been recorded and are available for viewing online. These videos are available at [https://labviewvideo.tecnova.com/ Tecnova's LabVIEW Video] site, with the credentials Username: '''LabVIEW_Videos''', Password: '''LabVIEW'''</div>

Hooovahh https://labviewwiki.org/w/index.php?title=NI_week&diff=5515 2018-11-12T15:49:21Z

<p>Hooovahh: Created NI Week page with link to videos</p> <hr /> <div>NI Week is a yearly technical conference hosted by NI in Austin Texas, where NI is headquartered. The conference focuses on showcasing NI's roadmap for software and hardware.<br /> <br /> = Schedule =<br /> The conference officially starts on a Monday with Alliance Day focusing on NI's [[Alliance_program|Alliance Partners]]. There are activities for non Alliance Partners on Monday but the majority of closed door presentations are off limits. Tuesday through Thursday technical sessions, training, keynotes, and other social activities take place with a schedule that changes each year. If you are interested in attending NI Week check [http://www.ni.com/niweek|NI's official page] for their schedule.<br /> <br /> = Videos =<br /> The majority of the content at NI Week is the technical sessions. These can be presented by NI employees, or any member of the public after being approved by NI. Over the years several NI sessions have been recorded and are available for viewing online. These videos are available at [[https://labviewvideo.tecnova.com/ Tecnova's LabVIEW Video] site, with the credentials Username: '''LabVIEW_Videos''', Password: '''LabVIEW'''</div>

Hooovahh https://labviewwiki.org/w/index.php?title=Online_videos&diff=5514 2018-11-12T15:35:08Z

<p>Hooovahh: Created Online_videos page with mostly links to various youtube channels</p> <hr /> <div>&lt;span&gt;Below is a list of online videos related to LabVIEW topics. Most cover basic training but some cover specific LabVIEW topics.&lt;/span&gt;&lt;p class=&quot;mw_paragraph&quot;&gt;<br /> <br /> <br /> *[https://www.youtube.com/channel/UCJnMVoaGnTr0HNQwTP_GTww NI's LabVIEW Channel]<br /> *[https://youtu.be/90yKPBLmDJ4 LabVIEW Training Course by Hardware Thrift]<br /> *[[NI_week#Videos|NI Week and CLA Conference Videos]]<br /> *[https://www.youtube.com/channel/UCJ0jhJNGk9kjc12npjy6b4g/ GDevCon Conference Videos]<br /> *[https://www.youtube.com/channel/UCvC4jW38T9_UoV_3-bdlXvA LabVIEW ADVANTAGE]<br /> *[https://www.youtube.com/channel/UC2JvDufj1vB6GewXYMfpe-Q LabVIEW MakerHub]<br /> *[https://www.youtube.com/channel/UClKq6SMtR9qtOIutMcWSWDw LabVIEW Architects Forum]<br /> *[https://www.youtube.com/channel/UCD1Fm1HYETmjbBPyucbLRrw Delacor's Youtube Channel]<br /> *[https://www.youtube.com/channel/UCwgd_sopH-ll3odVtTXY4oA System Automation Solutions LLC]<br /> *[https://www.youtube.com/channel/UCVfW08kA4N3jytIitOnH9NQ Dr. James D Powell]<br /> <br /> [[Category:Lists]]</div>

Hooovahh https://labviewwiki.org/w/index.php?title=Training&diff=5513 2018-11-12T15:12:44Z

<p>Hooovahh: Created Training page with mostly external links</p> <hr /> <div>{{see also|category:LabVIEW fundamentals}}<br /> &lt;span&gt;Below is a list of LabVIEW topics, and online resources for training. Most of these are in the form of free online training and tutorials covering features of LabVIEW. Professional training from NI or some of their partners is also available.&lt;/span&gt;&lt;p class=&quot;mw_paragraph&quot;&gt;<br /> <br /> *[http://www.learnni.com/ NI Learning Center]<br /> *[http://www.ni.com/getting-started/ NI Getting Started]<br /> **[http://www.ni.com/getting-started/set-up-hardware/ Hardware Basics]<br /> **[http://www.ni.com/tutorial/14621/en/ MyRIO Project Essentals Guide]<br /> **[http://www.ni.com/gettingstarted/labviewbasics/ LabVIEW Basics By NI]<br /> **[http://www.ni.com/getting-started/begin-application DAQ Application Tutorials]<br /> **[http://www.ni.com/compactriodevguide/ cRIO Developer's Guide]<br /> <br /> *[http://www.ni.com/tutorial/5247/en/ 3 Hour LabVIEW Introduction] (Alternate [https://drive.google.com/open?id=1a7siWTi_L0wuUG8krVsrt7ywpS8m0yvG Google Drive])<br /> *[https://drive.google.com/open?id=1CUsbKejyjvLQN7VyZ0dUg-32TVuZ7d4q 6 Hour LabVIEW Introduction] (Google Drive)<br /> *[http://www.ni.com/academic/students/learn/ Self Paced training for students by NI]<br /> *[http://sine.ni.com/myni/self-paced-training/app/main.xhtml Self Paced Training] Begginner to Advanced, requires SSP<br /> *[[Online_videos|Online Videos]]</div>

Hooovahh https://labviewwiki.org/w/index.php?title=Getting_Started&diff=5512 2018-11-12T14:53:11Z

<p>Hooovahh: Made basic and advanced heading topics, most pages don&#039;t go anywhere yet, I left Data Flow, Tutorials below which I think should be referenced in Online Training</p> <hr /> <div>&lt;span&gt;This page is intended to be a starting point and resource to help navigate all LabVIEW content on this Wiki and elsewhere.&lt;/span&gt;&lt;p class=&quot;mw_paragraph&quot;&gt;[[LabVIEW|General information about LabVIEW]]<br /> <br /> *Basic Topics<br /> **[[Training|Online Training]]<br /> **[[LabVIEW_style_guide|LabVIEW Style Guide]]<br /> **[[Community|Online Community]]<br /> **[[Contributing_online|Contributing Online]]<br /> **[[Finding_professional_help|Finding Professional Help]]<br /> **[[Tips_and_tricks|Useful Tips and Tricks]]<br /> *Advanced Topics<br /> **[[Object_oriented_software|Object Oriented Software]]<br /> **[[Abstraction|Abstraction]]<br /> **[[Actor_framework|Actor Framework]]<br /> **[[Error_handling|Error Handling]]<br /> **[[Source_code_control|Source Code Control]]<br /> **[[SOLID_principals|SOLID Principals]]<br /> **[[Unit_testing|Unit Testing]]<br /> **[[VI_analyzer|VI Analyzer]]<br /> **[[Virtual_machines|Virtual Machines]]<br /> *Connecting With Other Developers<br /> **[[User_groups|User Groups]]<br /> **[[NI_week|NI Week]]<br /> **[[Summits|Summits]]<br /> *[[LabVIEW_blogs|LabVIEW Blogs]]<br /> *[[Online_videos|Online Videos]]<br /> *[[Certifications|Certifications]]<br /> <br /> <br /> &lt;ul&gt;&lt;li&gt;[[data flow|Data Flow]]&lt;/li&gt;&lt;li&gt;[[LabVIEW tutorial|LabVIEW Tutorial]]&lt;/li&gt;&lt;li&gt;Hardware Basics&lt;/li&gt;&lt;/ul&gt;</div>

Hooovahh