Just want to share our open source project "Labview Python Bridge".

Connect labview apps with python apps in realtime with multi-processing data queues.

https://github.com/jmor2000/labview_python_bridge

If anyone has any questions or suggestions for new developments / features, let me know.

Cheers

Jeff

So it works like you'd think.  There is a library of vector images you select from, pick the one you want, then pick the Control Type (which is a folder of CTLs), then click create and it creates the control setting the decal button, VI description (adding License text if needed) and sets the icon editor icon.

Dependencies

If you just run the Vector Boolean Control Creator you'll need OpenG Time, OpenG File, and the JKI State Machine toolkit installed in LabVIEW 2015 or newer.  The included libraries will work without anything else as long as you are in Windows (more on that later).  If you want to include your own controls there are a few more steps and I left a text file explaining that in the Template Controls folder, but I included several already.  If you want to add your own images I also left instructions in the Libraries folder.  I wrote a VI that can convert from SVGs to the needed PNG and EMF files as long as you download inkscape (again instruction text files included).  But inkscape is only a dependency if you want to use that utility to add your own libraries which are in SVG.

Demo

For good measure I made a Jing video showing how it works.

Windows Only...

So the Windows only part is an interesting one.  I started with my UI being just a single 2D picture control and as you type your search in the top, it would go and open each image that matched the result, shift them into rows and columns, detect the number of columns shown, then detect and show mouse selection, and all the other stuff that would be needed.  To say the least it was slow.  I tried several ways to improve it, but in the end it was slow and I couldn't come up with a solution I liked.  I could have added a search button but I really like the live search of typing it in and seeing it update as you type just like the icon editor glyphs do.

So for a first release I went with the cheap and hacky solution and that was to leverage some .Net to embed a Windows Explorer window into my front panel, which is just the search results of a folder on disk.  This now means you see the PNG images on the front panel, but it will only use that to show the UI to you, but then use the vector based EMF file when creating the control.

Doing the search was a bit weird too since I couldn't figure out how invoke a search with the Explorer .Net so instead I wrote to a temp location a saved search that is XML, which I tell the UI to navigate to which then shows the search results.

Oh and there is some .Net GDI resize going on so the PNG image is used as icon editor icon for the control but dependency could likely be removed with some G work.

Anyway hope people find this useful.

Vector Boolean Creator.zip

Still I went on my little journey trying to make my own in pure LabVIEW to see what I could do.  My first attempt failed immensely and I did not have the knowledge, to understand what was wrong, or how to debug it.  As a test of AI progression I decided to dig up this old code and start asking AI about what I could do to improve my code, and to finally have it working properly.  Well over the holiday break Google Gemini delivered. It was very helpful for the first 90% or so. It was great having a dialog with back and forth asking about edge cases, and how things are handled.  It gave examples and knew what the next steps were.  Admittedly it is a somewhat academic problem, and so maybe that's why the AI did so well.  And I did still reference some of the other content online.  The last 10% were a bit of a pain. The AI hallucinated several times giving wrong information, or analyzed my byte streams incorrectly.  But this did help me understand it even more since I had to debug it.

So attached is my first go at it in 2022 Q3.  It requires some packages from VIPM.IO. Image Manipulation, for making some debug tree drawings which is actually disabled at the moment.  And the new version of my Array package 3.1.3.23.

So how is performance?  Well I only have the deflate function, and it only is on the dynamic table, which only gets called if there is some amount of data around 1K and larger.  I tested it with random stuff with lots of repetition and my 700k string took about 100ms to process while the OpenG method took about 2ms.  Compression was similar but OpenG was about 5% smaller too.  It was a lot of fun, I learned a lot, and will probably apply things I learned, but realistically I will stick with the OpenG for real work.  If there are improvements to make, the largest time sink is in detecting the patterns. It is a 32k sliding window and I'm unsure of what techniques can be used to make it faster.

ZLIB G Compression.zip

🚀 𝐉𝐨𝐢𝐧 𝐭𝐡𝐞 𝐋𝐚𝐛𝐕𝐈𝐄𝐖 𝐒𝐎𝐓𝐀 𝐁𝐞𝐭𝐚 𝐓𝐞𝐬𝐭𝐞𝐫 𝐏𝐫𝐨𝐠𝐫𝐚𝐦 𝐚𝐧𝐝 𝐒𝐡𝐚𝐩𝐞 𝐭𝐡𝐞 𝐅𝐮𝐭𝐮𝐫𝐞 𝐨𝐟 𝐀𝐈 𝐃𝐞𝐯𝐞𝐥𝐨𝐩𝐦𝐞𝐧𝐭!
Are you passionate about artificial intelligence? Do you want to be part of a groundbreaking journey to revolutionize AI workflows? SOTA, the unified AI development platform, is looking for beta testers to explore its latest capabilities and provide valuable feedback.

𝐖𝐡𝐲 𝐉𝐨𝐢𝐧 𝐭𝐡𝐞 𝐒𝐎𝐓𝐀 𝐁𝐞𝐭𝐚 𝐏𝐫𝐨𝐠𝐫𝐚𝐦?
Be the First to Explore: Get early access to the 64th version of SOTA, featuring powerful tools like the Deep Learning Toolkit and Computer Vision Toolkit.
Collaborate and Innovate: Share your insights and ideas to help us refine and improve the platform.
Experience Unmatched Simplicity: Discover how SOTA’s graphical programming language, ONNX interoperability, and optimized runtime simplify complex AI workflows.

⭐ 𝐖𝐡𝐚𝐭’𝐬 𝐢𝐧 𝐢𝐭 𝐟𝐨𝐫 𝐘𝐨𝐮?
𝐄𝐱𝐜𝐥𝐮𝐬𝐢𝐯𝐞 𝐀𝐜𝐜𝐞𝐬𝐬: Be part of an exclusive group shaping the next generation of AI tools.
𝐄𝐚𝐫𝐥𝐲 𝐈𝐧𝐧𝐨𝐯𝐚𝐭𝐢𝐨𝐧𝐬: Test cutting-edge features before they’re released to the public.
𝐃𝐢𝐫𝐞𝐜𝐭 𝐈𝐦𝐩𝐚𝐜𝐭: See your feedback implemented as part of SOTA’s evolution.

💡𝐖𝐡𝐨 𝐂𝐚𝐧 𝐀𝐩𝐩𝐥𝐲?
Whether you're an engineer, researcher, or AI enthusiast, your voice matters. If you're curious, innovative, and ready to explore, we want you on board!

👉Contact us if you want to join the open beta!
https://lnkd.in/dWrckRJV or hello@graiphic.io or PM

Stay informed and follow us on our youtube channel !

👉 https://lnkd.in/dmP49rCa

Stay informed on our website !
👉 https://www.graiphic.io

This is a small tool that adds a shell menu 'Open with LabVIEW Compatible Version'

Very usefull when working with multiple LabVIEW versions.

It launch the appropriate LabVIEW Version if installed', otherwise, it prompts the user to select a more recent installed version.

Requirements :

LabVIEW 8.6.1 RunTime Engine

Use :

Right Click on a LabVIEW File

Select 'Open with LabVIEW Compatible Version'

Supported file formats :

.vi .vit

.ctl .ctt

.llb .lvlib

.lvproj .lvclass

.xnode .xctl

LabVIEW Shell Launcher 1.0.4.zip

I have implemented Kalman filter using LabVIEW 2016.

You can find the codes here: http://kataauralius.com/index_files/Kalman_filter_in_Labview.html.

Hopefully this is useful for those who struggle with the implementation of Kalman filter in realtime system.

Best,

Auralius

http://kataauralius.com

Well, I am writing a program for making hangman game in python but it shows some error at the time of its execution.

Here is my source code: 

import random
def select_word():
    words_in_computer_memory = ['magazine','stars','computer','python','organisation']
    word = random.choice(words_in_computer_memory)
    return word
def is_gussed(word, guessed_letter_list):
    count=0
    for letters in word:
        if letters in guessed_letter_list:
            count+=1
    if count==len(word):
        return True
    else:
        return False
def guessed_word(word, guessed_letter_list): 
    string=""
    for key in word:
        if key in guessed_letter_list:
            string+=key
        else:
            string+="_ "
    return string
def available_letters(guessed_letter_list):
  
    string=""
    count=0
    s='abcdefghijklmnopqrstuvwxyz'
    for letter in s:
        if letter in guessed_letter_list:
            count+=1
        else:
            string+=letter
    return string
def hangman_game(word):  
    length=len(word)
    print('''------------------WELCOME TO HANGMAN GAME---------------------------
                                    O   
                                   /|\  
                                   / \  
        ''')
    print("The word you have to guess is of ",length, "letters long.")
    chances=2*len(word)
    i=0:
    guessed_letter_list=[]
    while (chances!=0):     

        if word!=guessed_word(word, guessed_letter_list):
            print("You Got", chances, "Chances.")
            print("Letters you can enter should be from these ",available_letters(guessed_letter_list))
            guess=input("ENTER A LETTER ")
            print('\n'*50)

            guessInLowerCase = guess[0].lower()      
            if guessInLowerCase  in guessed_letter_list:
                print("SORRY! YOU HAVE GUSSED THIS LETTER ALREADY! ",guessed_word(word, guessed_letter_list))
            elif guessInLowerCase not in word: 
                print(" SORRY! THE LETTER IS NOT IN WORD",guessed_word(word, guessed_letter_list))
                chances-=1
            else:
                guessed_letter_list.append(guessInLowerCase)
                print("NICE YOU GUSESSED THE RIGHT LETTER! ",guessed_word(word, guessed_letter_list))
           
        elif word==guessed_word(word, guessed_letter_list):
            print("YOU WON!")
            break

    else:
        print('''
        ********************************************
   YOU LOSS!!
                                 O 
                                /|\  
                                / \  
     ******************************************''')
        print('The word was',word,)

word = select_word()
hangman_game(word)

Can anyone give their suggestions on this?

Thanks             

So, here is a small tool to automate the generation of code for reading and writing existing INI files.

• Download zip, open project, open and run GenINI_Main.vi.
• Point the top file control to an existing standard INI file (like the one included in the Test folder, for instance)
• Click the "Read File" button, and select the Key Type for each entry from the INI file.
• Click the "Generate Code" button to spit out the read and write VI's (saved in the same folder as the INI file).

There are a fair number of limitations and possible enhancements, but I would love to hear any feedback people might have before I complicate this too much.

Thank you kindly,

Joe Z.

GenINI.zip

It's basic and has limited options, I use them to load 'expected results' for my unit tests (I use caraya).

Feel free to use / comment / suggest improvements, if there is enough interest I'll create an open source repo on GitHub and post it on VIPM.io

write to file.vim example.vi csv.lvlib load from file.vim

Is someone know what possibility exist to distribute a library on LabVIEW. I mean, is there only VIPM tool ?

I would also like to know where I can find a complete guide on licensing and licensing policy. If i want to put licence on my product what are my option ? How it works (licensing tools) ? What are the different types of licenses possible ?

I would like to make several versions of my HAIBAL project with several licensing policies (student, lab and pro) and didn't find a document explaining all of this part.

As this is our first software sale on the NI store (or other platform) and I don't have a lawyer on my team, I have a lot of questions: is it complicated to sell my product online ?

What are the obligations attached to each type of license? Does JKI offer a solution for all this? If so, how much does it cost? Is it only an acquisition cost, or do you then take a royalty on sales?

Is someone can help me on this subject ?

Thanks !

Youssef

Similarly, though less frequently, there are times when you only need to update the value within a DVR without actually performing any logic inside of the IPE.  This situation is less frequent, at least for me, as I am usually using arrays or classes with DVRs such that I actually need to modify the existing data rather than simply replacing it.

A more preferable solution to the above situations would be to have Read/Get and Write/Set VIs for the DVRs to simplify the process of working with them. This way, and IPE on the block diagram would only be needed when you were actually modifying the existing data within the DVR, rather than simply overwriting or returning the current value.

Thanks to the power of malleable VIs and the type specialization structure that is now officially released in LabVIEW 2018, a better solution is now available. I’ve created two malleable VIs, Read  DVR Value (Parallel) and Write DVR Value that allow you to perform a write and a parallel read on any DVR data type.

 Now, you can use a single VI that you can insert via Quick Drop to read or to write DVR values.  

Download the attached ZIP file to access the two malleable VIs and example code, and please let me know your thoughts in the comments!

DVR Read and Write VIs 1.0.0.zip

I tested in in my use cases, but there will still be bugs and unsupported features. Please post issues at github.

If your are interested, visit https://github.com/kleinsimon/LV-Tiff

for now its just adding up the generic control refnum not the actual type .

What is easier?
- Modicon-style addressing instead of data address and function code.
- Data-type conversion built-in(eg. 32-bit float mapped to two U16 registers). Word swapping option.
- Poll list and cached data block. Allows you to poll a range of registers then lookup and convert the values elsewhere.

The code is up on GitHub: https://github.com/rfporter/Modbus-PLC-Client

Its a rough draft at the moment. Comments are welcome and appreciated.

I'm generating a DLL with this simple function 

I want to recover the clustrer through a DLL function, so i did it in project.

I build the DLL and when i call it, --> TALA CRASH 

To recover my cluster i supposed Type is "Adapt to type" and Data format "Handles by Values"

Of course it's not !

Someone know what are Type and Data format of my output should be ?

Thank you,

(i put the VI and project in attached file 

test DLL.zip

Output of my bat is written in a txt file. 

When i launch it directly in windows it works. When i try with LabVIEW cmd i have some restriction.

Is it possible to make it works with the good cmd ?

test.bat my_test.txt

• it is sloooow
• sometimes it is even slooooower
• additional 1px black line appears at each case (it is not an issue in alternative flash players as Gnash)
• tips appear even for objects in hidden cases (still don't know how to solve this)
• tips appear for each object (even not necessary, like comments) and often display sth stupid - this is for debug
• did I mention it is slow?
• many others

Any comments are welcome, particularly if someone has an idea how to speed it up a little. I already tried to convert it to non-recursive version. Although I had some problems, it seems that recursion is not the reason. I think now that a bottleneck is speed of switching cases externally. If it is true, the stack version of algorithm should work even slower.
And of course GUI in final version will not look like this.

[moderator note]

Attachments to this post are missing due to server error. We apologize for the trouble.

I try my luck here maybe someone will answer me

With VIPM when i try to package this example with a purchase url we have a proxy error. 

I tested with no proxy --> error, use system proxy settings --> error

Someone know about proxy parameters or what i have to fill to avoid this error ?

BR
TS

CRC.vi

I was not able to find them

 TDF is proud to announced the coming soon release of HAIBAL library to do Deep Learning on LabVIEW.

The HAIBAL project is structured in the same way as Keras.

The project consists of more than 3000 VIs including, all is coded in LabVIEW native:😱😱😱

• 16 activations (ELU, Exponential, GELU, HardSigmoid, LeakyReLU, Linear, PReLU, ReLU, SELU, Sigmoid, SoftMax, SoftPlus, SoftSign, Swish, TanH, ThresholdedReLU), nonlinear mathematical function generally placed after each layer having weights.
• 84 functional layers/layers (Dense, Conv, MaxPool, RNN, Dropout, etc…).
• 14 loss functions (BinaryCrossentropy, BinaryCrossentropyWithLogits, Crossentropy, CrossentropyWithLogits, Hinge, Huber, KLDivergence, LogCosH, MeanAbsoluteError, MeanAbsolutePercentage, MeanSquare, MeanSquareLog, Poisson, SquaredHinge), function evaluating the prediction in relation to the target.
• 15 initialization functions (Constant, GlorotNormal, GlorotUniform, HeNormal, HeUniform, Identity, LeCunNormal, LeCunUniform, Ones, Orthogonal, RandomNormal, Random,Uniform, TruncatedNormal, VarianceScaling, Zeros), function initializing the weights.
• 7 Optimizers (Adagrad, Adam, Inertia, Nadam, Nesterov, RMSProp, SGD), function to update the weights.

 Currently, we are working on the full integration of Keras in compatibility HDF5 file and will start soon same job for PyTorch. (we are able to load model from and will able to save model to in the future – this part is important for us).

Well obviously, Cuda is already working if you use Nvidia board and NI FPGA board will also be – not done yet.

We also working on the full integration on all Xilinx Alveo system for acceleration.

User will be able to do all the models he wants to do; the only limitation will be his hardware. (we will offer the same liberty as Keras or Pytorch) and in the future our company could propose Harware (Linux server with Xilinx Alveo card for exemple --> https://www.xilinx.com/products/boards-and-kits/alveo.html All full compatible Haibal !!!)

About the project communication: 

The website will be completely redone, a Youtube channel will be set up with many tutorials and a set of known examples will be offered within the library (Yolo, Mnist, etc.).

For now, we didn’t define release date, but we thought in the next July (it’s not official – we do our best to finish our product but as we are a small passionate team (we are 3 working on it) we do our best to release it soon).

This work is titanic and believe me it makes us happy that you encourage us in it. (it boosts us). In short, we are doing our best to release this library as soon as possible.

Still a little patience …

Youtube Video : 

This exemple is a template state machine using HAIBAL library.

It show a signal (here it's Cos) and the neural network during his training has to learn to predict this signal  (here we choose 40 neurones by layers, 5 layers, layer choose is dense).

This template will be proposed as basic example to understood how we initialize, train and use neural network model.  This kind of "visualisation exemple" is inspired from https://playground.tensorflow.org/ help who want to start to learn deep learning.

Features:

• Works on any scalar type, giving a 1D array buffer, or any 1D array, giving a 2D array buffer (could be extended to a 3D buffer of 2D arrays)
• Has VIMs that accept either a by-Value Buffer, or a DVR of a Buffer

Package contains simple examples.  Comments welcome.  

jdp_science_lib_malleable_buffer-0.1.0.5.vip

During a few last years I received multiple appeals to release AES library that I developed in 2011 into open-source. So, I've just done exactly this: https://github.com/IgorTitov/LabVIEW-Advanced-Encryption-Standard

I released it under MIT license (which means that there are no restrictions whatsoever). No VI passwords, no uglification.

LabVIEWishly Yours,

Igor Titov.

digclk.vi digclk Project.lvlps digclk Project.lvproj digclk Project.aliases dig.ctl

Little background: I was searching for an implementation (or at least a full explanation) of constructing an ellipse from 5 points. 5 points exactly define an ellipse, so it's not a data fitting problem. To my surprise, I couldn't find any solutions that can be used as it is or any full explanations. All I could find was pointers into the proper direction (matrix math) but my math is so rusty that I could not implement anything from those information ("just calculate the determinant with some symbolic math library or do it on paper haha and goodness comes"). I was a bit upset because I wasn't doing homework, I actually needed that function.

Anyhow, after finding a small hint in one of the threads, I could go through the thing and implementet the algorithm. Maybe it will be useful for anyone who is looking for exactly that thing.

It's not that nice, not optimised, I guess many of the math could be optimized/simplified, but it's working at least.

Precision: I'm not sure. For my needs, it's precise enough, I'm not an expert in condition of the matrix or other calculations.

I think the names are self explaining, but If you have questions, don't hesitate to ask. The formulas and the thread I found most usable are included on the block diagram.
Input: array of coordinates (x,y in a cluster).
Output:

• ellipse parameters: center, two radii and angle of the first axis
• the coordinates of the axis endpoints
• the five t parameter values of the input points (t parameter for the parametric equation of the ellipse), so for example you can draw ellipse arc between two of the points
• If the ellipse cannot be constructed, it results in some NaNs here and there... No extra checks added

2 subvis are also implemented, but maybe they are already in the LV base package and just missed them:

• parametric equation for arbitrary ellipses (or polar equation, my math is that rusty I can't even express properly what I mean)
• CCW angle between two vectors (result in 0....2 PI range), it's used to calculate the t parameters for the points. This is where I feel there's some redundancy or redundant trigonometric calculations.

Thank's for any feedback!

EDIT: I added a small demo program. You can move the 5 points on a graph.

2D_ellipse_parametric_equation.vi 2D_ellipse_from_5pts.vi 2D_ccw_angle.vi

Ellipse_Demo.vi

Both eyes are included and automatically synchronized, so you don't need to worry about contracting lazy eye.

Googly Eyes.ctl

The code still needs some work, but is in a decent place as far as the examples go, but is missing documentation and icons.  It requires LabVIEW 2020 or newer, and the last example requires both 64 and 32 bit versions of LabVIEW.  The basic examples all seem to work with the one I'm most interested in feedback on being the 64 Bit DLL calling code, but first the others.

Example 1 Client Host Together

This is the simplest demo showing the Client and Host in a single VI.  All that is needed is to specify what the Client and Host identification is.  Here it is hard coded as "Client Loop" and "Host Loop".  With it a Host can send a request for some work, and get a response.  The Client will sit in a loop and get a user event for the work, then send the response.

Example 2 Client Host Together

The next progression is a Client and Host that are separated in different instances or contexts.  The code is practically the same but each loop now has its own project and can be built into separate EXEs.  Here the IP address is localhost so both Client and Host need to be on the same computer.

Example 3 Remote Client

Here is where it starts getting fun.  The Host is ran on Windows (EXE or development) and then the Client can also be either ran from a separate EXE or development.  This Client can be another Windows PC on the same network or an RT target that has Network Streams installed through MAX.  The example project has an RT target.  And the Host has an IP address for finding the Client.

Example 4 64 Bit DLL Calling

And this brings me to the real fun.  So a 64 Bit executable can't call a 32-bit DLL directly.  It either needs some kind of wrapper, or another translation layer.  Since Network Streams supports talking between different versions of LabVIEW it also supports sending data to and from different bitness of LabVIEW too.  So what you can do is open the "Remote Client Test - Host Main.vi" under Example 4 in LabVIEW 64-bit.  Then run the EXE named "Remote Client.exe" which is a 32 bit EXE.  Instead of running this EXE you can also open and run "Remote Client Test - Client Main" in the 32-bit version of LabVIEW.

If both the Client and Host are running, and both show a Connected status on the front.  Then what you should be able to do is put a file in the Path control, then click "Get MD5 Method 1".  This will send the path of the file from that control (just the path not the actual data of the file) over a Network Stream to the Client, and tell it to run a series of Call Library Nodes to get the MD5 of the file.  You can also try clicking Method 2 which will instead of doing it in one call, it will read the file in chunk on the 64-bit side, then send that data over Network Streams to the 32-bit side, where the DLL calls are made.

I don't like that to make this work you basically need to duplicate your work.  On the 32-bit side you need to code talking to the DLL, and get the request data from the Host converting it to what you want, then getting the result and sending it back to the Host as the response.  Then on the Host side you need to write a subVI that takes inputs, flattens them down into sending the request, getting the response and unflattening.  At the moment I used Variant attributes because I wasn't being creative.

I'd love a more streamlined method that could work by specifying DLL inputs and data types.  Or just make it easier for developers, possibly with scripting?  XNodes replacing Call Library Nodes?  Or using them as a template?  Thoughts?

Also another issue is needing to run a separate EXE.  I'd love to be able to embed in the 64-bit VIs the needed 32-bit EXEs, and then have a daemon for starting up and stopping that EXE.  This will mean the first call to it will take several extra seconds, while the 32-bit EXE is started up in the runtime engine and gets ready to get a Network Stream request.  In a real application this could be done on start easily.

MD5 Details

No you shouldn't use this method to actually get the MD5 of a file from a 64-bit version of LabVIEW.  There are better alternatives.  But what I wanted was an example of getting a 32-bit binary to do some work, that a 64-bit version of LabVIEW could have it do.  By the way this code is lifted from a discussion here.

Actual Usage?

So as for the actual usage of a thing like this.  I have a few pieces of hardware that talk over a 32-bit DLL and don't have a way to talk to them once I go to LabVIEW 64-bit.  They aren't critical hardware, and are old so maybe I should just let it go.  But part of me wants to update these APIs so that all versions and types of LabVIEW can talk to them.  I also have a couple of customer DLLs that are 32-bit and are just black boxes that I need to use for security reasons.

Performance?

Untested, but probably not great depending on the amount of data that gets sent back and forth.

Alternatives?

If anyone knows of good examples of having a 64-bit version of LabVIEW call a 32-bit DLL I'd be interested.  Regardless the Network Streams portion of this code will likely be published at some point after the user group presentation.  Thanks.

1069999985_NetworkStreamsTrialand64DLLCalling.zip

Im using for PCAN Driver for communication with a CAN Device

I want to send via rs485 msg-s then to read them with the Peaksystems CAN 

I have an issue with reading the values from CAN.

My program reads only the first value. 

When I send msg and expect change there is no change in values I expect

Only E2 changes everytime I want to read, but not the next 2 values where I Expect change. 

I guess Im missing something, but I dont know what.

Here is my program.

RS.zip

The original version of the collection class was (and is) used as a collection of sequence steps. Each element can be either a sequence command (send message, wait timer, wait complete etc.) or another collection of commands (sub-sequence). That’s the reasons for the labels and search method. Otherwise it is just a fancy (Rube Goldberg) array.

Next method is recursive and it steps through all elements in the collection. Execute is only method, which requires override.

For now, it’s at least an exercise in new interfaces. I don’t know if it’s useful enough to be in the code repository, but I can polish it up if needed.

--
Marko H
Certified LabVIEW Architect
www.optofidelity.com

Iterable Collection LV2020.zip

It supports pretty much any latin codepage language and once upon a time did also support Chinese (but I have not tested that in quite some time).

Obvious disclaimer here: I just want to share what I made, but use at your own risk, and I am definitely not a UTF8/16 whatever expert so there might be some stuff that is just plain wrong.

1. Does something like this already exist?

2. Is this something that could be useful?

Every once in a while I need dynamic UI components that can be generated at runtime. One nice thing to use for this is a picture control; however it doesn't lend itself as well to keeping other pieces of function such as mouse click events and such. I put together a mini library of UI functions for this that has the ability to be extended. The UI can be generated dynamically at runtime and be any picture thing that you can draw.

Using Standard layout techniques that you might find in other GUI libraries. The hierarchy generation can always be simplified by using some type of templating string.

Allows any labview application on you computer to utilise your google drive and google sheets. This is achieved through a labVIEW executable (GDLVserver), that gets access to Google drive/sheets with a client secret json file, with OAuth 2.0 authentication. Other labVIEW applications can communicate with the executable, and request google drive and sheets function requests. A LabVIEW client library is included to add to your project files. The GDLVserver will work in the background and can be hidden.

I used an executable to handle all the Google Drive API commands, to lessen the file dependency in projects, and also to aim to stabilise the drive connection which has a tendency to freeze on connection. This is still a problem, but is rare, and is unavoidable as it is on the google API side. Once connected the connection is maintained flawlessly. I've run apps for days with data writing data every second with no issues. There is a quota on function calls per user per API, 100 calls per 100 seconds. 

All code is written in LabVIEW 2015 SP1

API: Google.Apis.Drive.v3.dll, Google.Apis.Sheets.v4.dll

Background: Origin of code maggie-otoole

Modification Actions:

• All VI's re-written
• .NET testAuth.dll replaced with JNET.dll
• New VI created for more API features
• All library references updated to .net45
• Google API widget, LabVIEW executable created 

Google Drive Functions:

• Get folder names / ID's, in root folder
• Get folder names / ID's, in specific folder 
• Get file names / ID's, in specific folder 
• Create new sheet

Google Sheet Functions:

• Append 2D array data
• Insert 2D array data
• Read 1D array data

Folders content:

• GDLVserver:  includes .exe, data folder with .lib references (you will need to place your JSON file here), and an icon folder
• GDLVclient: includes a LabVIEw project, GDLVclient library, and example VI's

Requirements:

• a LabVIEW 2015 SP1 32bit runtime engine is required to run the executable (here)
• a google email account
• Follow instructions in the "how do" pdf, (enable API's, create JSON, download & rename, run server (admin), try examples)

GDLVserver.zip

GDLVclient.zip

GDLV License.pdf

GDLV how do.pdf

I tried to create a template based on OOP for QMH. During development I have been confronted with infinite crashes of LabVIEW so I decided to slow down with this project and open it to the community. I finished my working example and stopped for now.

So if anyone is interested to play around with the code, see attached ZIP file (LV 2020).

Cu,
Peter

MHT.zip

This is a small miesweeper clone, a game that I implemented in every major languages I programmed in.
The code is not pretty I only had a day to make it, the game itself is a bit slow and I didn't optimize it (not sure if it's the logic, or that a huge table control is being formatted cell-by-cell), but I thought I share it anyway.

The window setup may be a bit strange but this is actually just a dialog in a bigger project, an easter egg.

All controls of the original Windows Minesweeper are implemented, flags and auto-explore (simulaneous left+right click on a discovered cell with matching number of flags around it) too.
 

Enjoy, if you are patient enough and try not to vomit if you look at the block diagram...

minesweeper.zip

Template Viewer.zip

For more information, see this page, which appears to describe the same format: https://www.mathemaesthetics.com/ResTemplates.html (Change the URL from https to http; the forum won't let me add http links for some reason.)

There is also a cross-section plotting for a 2D intensity chart:

This package is in LabVIEW 2015, and requires Messenger Library (latest, in the LAVA-CR) and JSON LabVIEW and Shortcut menu from Cluster (both in the LAVA-CR).

drjdpowell_messenger_ui_augments-1.0.0.8.vip

Single File capible(if function VI is removed) 

Contains tools for changing rules.(In the form of a spreadsheet)

It uses variant attributes for the variable name space.

Here it is:

Made a nice and simple evaluator should be compatible with older versions of LabVIEW as well. And even gave it some test cases:

Also check out the github page: https://github.com/taylorh140/LabVIEW_Eval

I've attached the Eval and Functions.vi should be LV 8.0 compatible.

Functions.vi Eval.vi

It all started when I found the built in graph controls to be limiting in terms of signal selection and control.  I wanted a way for a user to select the signals they want and then show those on a graph with a shared time scale.  The problem was at the time the checkbox selector on a graph could have a scroll that couldn't be controlled.  So I started with a single column listbox showing all signals and allowing multiple to be selected.  I wanted to see the current value so I added that.  Scope creep kept going until I'm left with this thing that isn't done, but isn't terrible. 

In this demo there is a subpanel mode, independent windows, pause and resume, the normal graph palette controls, independent Y axis scaling, coloring, buffer size control, visible signals selection and values, and a few other things.  It was intended to be used in places where speed and exact values weren't used.  It was more or less a place where all signals of a system could be seen slowly.  It uses a few things I've posted on LAVA before.  My Variant Repository, Array VIMs, and Circular Buffer.  Here is a video.

Circular Graph.vipc

Android Sliding UI Demo.zip

EDIT: Second version is posted; this one should work in LabVIEW 2014, and fixes some bugs. I also added copy/paste buttons for the front panel and block diagram resources, since LabVIEW's built-in copy/paste function didn't seem to work for some reason. Note that if you edit the front panel or block diagram in the VI without using copy/paste (and the size is different), you need to update the size (first 4 bytes) as well. You can do this by clicking Copy and then Paste.
 
Now this may not be too useful for you, considering it's not something you should use in production code or anything you don't want to break. (I say that a lot in my posts, don't I?) But if you're curious about how VI's work internally, it's perfect.
 
This requires OpenG. Also, special thanks goes out to Thomas Zeugner for making VI Explorer. You know, that tool for cracking VI passwords. Turns out he figured out how the VI checksum (in the BDPW block) is calculated, which helped me greatly.
 
Oh, one more thing, I do plan on improving it. I was just excited to share what I had. So keep in mind there may be bugs.

Latest version:

The latest version is posted on the tool's home page, here: http://flarn2006.dyndns.org/llvim/

Older versions:

Low-Level VI Manipulation rev2.zip
Low-Level VI Manipulation.zip

But my problem is with the Gcode Interpreter, the Gcode I generate with GRBL laser but labview can not understand the Gcode. 

Someone can help me? Please I really need for a Project in my university!!

Regards!

G Code Manager

GCM is a tool that makes the properties of Project Items in Project Explorer window more accessible, removing unnecessary waiting times and modal windows. In runs in window next to the Project Explorer window and shows the items properties immediately after selecting new item in the explorer.

GCM also allows you to create your own plugins to access those Project Items! 

Requirements

The package was built in LabVIEW 2014, it should also run in LabVIEW 2015.

How to start

Download

IMPORTANT NOTICE

This tool was made using some internal LV APIs which are not fully tested and documented

Version 1.11.0.61

veritech_labview_code_manager-1.11.0.61.vip

- Icon Editor: Added "Default Font Settings" which sets the font to 8 pt, centered, capitalized.
- Fixed the synchronization issue between plugins (icon edited in Icon Editor was not updated in Basic Documentation). 
- Added new incoming events for plugins to better handle items selection/deselection and plugin activation/deactivation (see the attached documentation)

Note: The plugins API was changed in this version. If you've made your plugin in previous versions, please refer to the updated documentation. If you have any problems, just contact me

Documentation:

GCM.pdf

 

Version 1.9.0.54

veritech_labview_code_manager-1.9.0.54.vip

See this document for more information:

GCM.pdf

Presentations

• My YouTube Channel of Presentations (bit.ly/ChrisCilino_Presentations) including:
  • My LabVIEW Champion Interview
  • NIWeek 2018 Keynote Presentation
  • Soliton Customer Testimonial
  • LabVIEW Architect's Forum Q3 2018 - LabVIEW Auto Documentation Software
  • LabVIEW Architect's Forum Q4 2016 - Automated Build Process
  • 2018 Certified LabVIEW Architect Summit - Everything a Software Engineer Needs to Know That Has Nothing to Do with Software Engineering
  • My First Keynote Presentation at VIP Days in Germany

Code - Reuse Libraries

• Automated Build System - Software Module Builder
  • Summary: A system that turns source into exports. The exports can be of any type. Also determines build order of hierarchical modules, updates dependencies, and allows you to move the exports to the location you need for your end users to find and install the export and its dependencies.
  • Download
  • BitBucket Repository: git clone https://ChrisCilino@bitbucket.org/ChrisCilino/software-module-builder.git
  • Dependencies
    • LabVIEW Container (see link below)
    • LabVIEW SCC API
      • Summary: An API designed to abstract server based source code control providers.
      • BitBucket Repository: git clone https://ChrisCilino@bitbucket.org/ChrisCilino/labview-scc-api.git
      • Distributed as a part of the Automated Build system
    • NI Package Manager Build Spec API
      • Summary: An API to programmatically interact with and edit the LabVIEW NI Package Build Specification.
      • BitBucket Repository: git clone https://ChrisCilino@bitbucket.org/ChrisCilino/ni-package-manager-api.git
      • Distributed as a part of the Automated Build system
    • Custom Install Step Launcher
      • Summary: Enables NI Package Manager to execute VIs as a Post-Install/Post-Install All/Pre-Uninstall action.
      • Download: Distributed as a part of the Automated Build system
      • BitBucket Repository: git clone https://ChrisCilino@bitbucket.org/ChrisCilino/custom-install-step-launcher.git
• Software Module Template - NIPKG and VIP
  • Summary: A template LabVIEW Project designed to be built into an NI Package and VI Package by the Software Module Builder (see above). With this template, a user need only put their code in the "source" directory and edit some build specification information and the build process will do the rest.
  • Distributed with the Software Module Builder
  • BitBucket Repository: git clone https://ChrisCilino@bitbucket.org/ChrisCilino/software-module-template-nipkg-vip.git
• Watchdog Framework
  • Summary: A software observer of "situations" that can notify when something of "interest" happens. The observer is the "WatchDog", the thing being observed is a "Perpetrator", and the notification is a "bark".
  • Download
  • BitBucket Repository: git clone https://ChrisCilino@bitbucket.org/ChrisCilino/labview-watchdog-framework.git
• Sequencer
  • Summary: A simple design pattern that organizes code on a single block diagram without the inappropriate/excessive use of subVIs.
  • Download
  • BitBucket Repository: git clone https://ChrisCilino@bitbucket.org/ChrisCilino/sequencer-pattern.git
• Auto Documentation
  • Summary: Think of this as Doxogen for LabVIEW. Given a Project, Lvlib or .class, this software generates report. The report is "printed" to a confluence page. The software is Object Oriented and designed to be extended through inheritance.
  • Download
  • BitBucket Repository:  git clone https://ChrisCilino@bitbucket.org/ChrisCilino/labview-auto-documentation.git
  • Dependencies
    • LabVIEW Atlassian / Confluence / Jira APIs
      • Summary: An API that allows you to control Atlassian assets such as Confluence and JIRA from LabVIEW
      • BitBucket Repository: git clone https://ChrisCilino@bitbucket.org/ChrisCilino/labview-atlassian-api.git
• LabVIEW Container
  • Summary: A dynamic data structure that combines the strengths of a cluster and an array.
  • Download
  • BitBucket Repository: git clone https://ChrisCilino@bitbucket.org/ChrisCilino/labview-container.git

History/Credentials/Social Media

• LabVIEW Champion Page
• LinkedIn
• LabVIEW Champion Badge
• Certified LabVIEW Architect Badge
• Twitter
• NI.com Profile

With this tool, you can set wire size without limits (with results similar to this), customize both wire layers with any 8x8 monochrome pattern, and also mess with different draw options. Strangely, a few of these settings seem to have no effect, and many of the options for one of them actually crash LabVIEW. (These ones are disabled in my tool, but you can re-enable them by editing a typedef.) Given that this is actually a documented, supported property that's officially supposed to work, I've reported this as a bug to NI; if any NI engineers see this and feel like investigating, you can refer to service request #7762024.

Latest version:

Wire Studio 2.zip

Old versions:

Revision 1

Ad-Hoc VI Scripting.llb

Description

Yes, a simple For loop (perhaps in a subVI) combined with a Build Array node would work just as well—and would really have simplified the code generation if I had thought to do it before—but I like making XNodes, and thought this would be a fun one. And yes, the usual disclaimer about XNodes applies—use it at your own risk; XNodes aren't supported by NI.

Merge 3D Objects.zip

Download the LLB below and place it in your <LabVIEW install dir>\resource\dialog\QuickDrop\plugins folder. Then press Ctrl+Space, Ctrl+S to open this dialog.

Select an item from the list and click OK, and there you go. There's some interesting/strange stuff in here!

EDIT: Couple things I forgot to mention. The first time you open this (and whenever you rebuild the list) it uses two private properties on the app reference, to get the list of controls and indicators in the palette. Since this is just a property read, I'm sure the worst that could happen is a crash when you try to open the dialog, but I can't make any guarantees. Also there's some false positives for hidden items, mainly with front panel controls/indicators that come in different styles.

Place by Style.llb

 I kept the basic functionality the same, but couldn’t resist changing some of the UI (in the old code, “Main” controls the UI; in the new code, published state messages from the Acquisition and Logging Actors set the UI).

Continuous Measurment and Logging with Messenging.zip

 Any comments appreciated.   Is this example less clear than the NI original?  Why?  How could I improve it?

In particular, is code like this (the most complicated interaction, I think) understandable without heavy documentation?  It’s a “Start Logger, then Start Acquisition, then Unset the Busy Cursor” three-actor chain message:

I’m thinking of making a “Send Chain Message” subVI (that accepts arrays of addresses and message labels) to replace the above code.

— James

StyledText-LV2010.zip

StyledText-LV2010.zip

A couple of weeks ago i had the need to put a small suite of applications i made in the tray area, but the VIs i could find to do this wasn't really very intuitive or was lacking the functions i needed.

The solution?

Another one of these put-your-LabVIEW-app-in-the-tray toolsets .. but this time, a little better wrapped than the example code you can find on NI's site.. ;-) (no offense)

So here it is for you to evaluate .. it's not anything near final, and one can always find a number of small features lacking, but hey..it's event based, and its pretty easy to add more events if ever needed :-)

Notes:

Code is currently for LV8.6 and requires at least .NET Runtime 2.0, but i know for a fact that it runs on Win7 and LV2010..

Installation:

Unpack / Extract contained "Notify Icon" folder into your user.lib and refresh palettes or restart LabVIEW..

Examples:

Browse into your user.lib -> Notify Icon palette and drag the "NotifyIcon Class Example" VI to your block diagram (or open it by browsing into the "user.lib\Notify Icon\Example" folder)

License:

Since i made this code in my sparetime, but planned to be using it at work, i've made arrangements with the grand-old-boss and put a BSD License on it..

Feel free to send me any comments / questions AND bugfixes / error-reports

Thanks

Stinus

Well..since FF4 doesn't want to play nice.. here is the code uploaded using good old IE :-/

Notify Icon.zip

https://github.com/taylorh140/LabVIEWCGen

I was working on some ideas to handle some more complex Items. Had some thought about using 

https://github.com/rxi/vec 

To handle strings and other arrays/vectors, I would like to pass these more complex data types by pointer. However I am looking for some ideas as to when to make a copy. I know LabVIEW has some internal item that manages this but I haven't found a way of accessing it quite yet. Let me know if you think this is worth some effort. Or if you have any ideas about the architecture that you think would be helpful.

Also i imagine that this will still only ever support a small subset of LabVIEW, the languages are quite a bit different, and i prefer that the code be as clean as possible.

I designed and created the software in 4 parts. 1) An Atlassian Confluence API, 2) An Atlassian JIRA API, 3) A Class Report generation API, and 4) Two very small "applications" the demonstrate the API's usage. Not only can the APIs \ examples document your code, you can also generate JIRA tickets for the parts of your documentation you're missing.

I hope you'll find this software as useful as we at Cirrus Logic have. I would consider it "mid alpha" quality, but intend on investing in it over time. You can find the software at http://bit.ly/ChrisCilino_AutoDoc

Here's an example of a generated report for the members of a class

The private data also has its own table that looks like

There are many more features to the report, not to mention the APIs used to generate the reports. Also I've created an application to generate JIRA tickets that list the missing parts of a report.

Enjoy!

There are several test VIs which are my attempt to port the Lazy Foo tutorials.

All images in the Test directory are taken from the Lazy Foo tutorials.

LabSDL2.zip

Overview

In order to quickly and efficiently prepare source for distribution, a build system was necessary to abstract away the conversion of source into the different types of deliverables (VIPackages, Executables, dlls, ect) as well as abstract away the build order of our software hierarchy.

Many have undertaken to solve this problem. I don't claim to have created a silver bullet. But I do hope that the system I've put together (and am releasing as open source) will act as a starting point for you to extend and customize to meet your needs. I've endeavored to employ good software development principles including separation of concerns, and the SMoRES principles.

I'll be the first to volunteer that it isn't perfect and as always, our best software is constantly a work in progress. However, I believe the build system is at a stage to be at least moderately helpful to a handful of people in our community. 

Release Notes

1.4.0-123 (Component Builder 1.4.0-123.zip)

1. Added new NI Package Manager API
2. Added new NI Package Manager BuildSpec Utils 
3. Added procedure and documentation for the component template and its anatomy

1.4.0-113 (Component Builder 1.4.0-113.zip)

1. Added documentation for the SCC API

1.4.0-111 (Component Builder 1.4.0-111.zip)

1.4.0-99 (Component Builder 1.4.0-99.zip)

1. Added a few new P4 API functions allowing the creation of a session if a user is already logged it. 
2. Added Log in and log out tests to the test suite. 
3. Adding new function to tag all p4 paths in a label with the label.
4. Resolving the input path to a p4 depot path
5. Adding quotes around p4 paths.
    

1.4.0-91 (Component Builder 1.4.0-91.zip)

1. The refactor of the LabVIEW SCC API is complete and the build process is linked to the new install location. The LabVIEW SCC API can now be used independently of the Component Build process. 
2. I've included a test suite for the P4 implementation of the SCC API. It assumes that you have checked in the two files in the "Build Instructions\LabVIEW SCC API\Test Suite\Tests\Test Dir" into perforce.

1.4.0-85 (Component Builder 1.4.0-85.zip)

1. This is a major refactor in the SCC API. I've modeled the p4 label with a new api. This release is primarily as an intermediary release. I intend on breaking SCC out of the component builder into its own separate component in the next release.

1.4.0-81 (Component Builder 1.4.0-81.zip)

1. Created a "proxy" api for VI Package manager interactions. Sometimes the VI Package manager api would hang. So I now call by reference and will kill and restart VIPM if it doesn't respond in time. 

1.4.0-75 (Component Builder 1.4.0-75.zip )

1. Fixed reference counting for executable builds. 

1.4.0-73 (Component Builder 1.4.0-73.zip)

1. In the case where a user has specifically unchecked "auto increment", the build process will auto increment the build. Builds must be auto incremented. 
2. I've released a new build of the container that has a minor bug fix.
3. Added file utility tools to aid with using "net use" to move and copy files across the network.

1.4.0-59 (Component Builder 1.4.0-59.zip)

1. Minor spelling error in component template: "componet".
2. Added documentation for the Custom Install Step Launcher.
3. Added build instructions for Custom Install Step Launcher.

1.4.0-58 (Component_Builder_1.4.0-58.zip)

1. Added the ability to export NI-Source Distributions, NI-Executables, NI-Insatllers, and NSIS Installers
2. Released a template component that exports an NI Package and VI Package including step by step instructions
3. Released "Custom Install Step Launcher" to execute VIs as pre install, post install and post install all actions for NI Packages.
4. Released comprehensive documentation included in the zip file.

Component_Builder_5_31_2018.zip

Component_Builder_10_11_2018.zip

What this program does is adds a icon in your system tray (by the clock) that you can right click, and launch any version of LabVIEW installed. If you try to launch a version of LabVIEW that is already running it will bring it into focus based on it's processor ID.

You can also right click the icon and launch any version of TestStand installed. This has not been tested very much and it may not work properly.

You can also right click the icon and kill any version of LabVIEW that may have hung or is unresponsive. This performs a taskkill on any one version, or all versions of LabVIEW running.

You can also right click the icon and abort any running LabVIEW VI in any version of LabVIEW (after you configure the program to use the right ports for you versions of LabVIEW). There is a limitation with this at the moment where it can't abort a VI that was opened from a project file. Not sure how to get around this any help is appreciated.

And lastly what this program does is whenever a VI is ran in windows (double click a VI) this program will take over, and determine what versions of LabVIEW installed it can be opened with. If more than one version is suitable then it will ask you what version to open it with. Here it will also show what versions are running and which one is the default version. By pressing (or holding) CTRL when the window comes up it will open the VI with the default version of LabVIEW. This can be changed by double clicking the icon in the system tray to open with the default version, and only ask which version to open it with by holding CTRL.

Now that you're interested here's how to use it. First you'll need to download and install an ActiveX component, that allows you to make icons in your system tray (posted by KileenC here).

http://forums.ni.com...IEWTrayIcon.zip

Then download LV Tray Launcher EXEs Only LV Tray Launcher EXEs Only 1.0.zip If you have LabVIEW 7.1 runtime installed, run LVTrayLauncher.exe. You should now have an icon in your system tray that looks like a space ship. If not check your task manager and see that both axsTrayIcon.exe and LVTrayLauncher.exe are running. If they aren't kill them both and start axsTrayIcon.exe, then start LVTrayLauncher.exe.

If you don't have LabVIEW 7.1 runtime installed I do have a runtime less EXE but I'm not sure if it's legal to post it since it contains files that are NIs and I would be copying them to my own server. Any opinions out there about the legality?

If you want to see the source, it's attached and saved in 7.1. There is also a readme in each of the attachments with a little more insite into the application. Alot of the source is just pieces of code from LAVA and NI's forums, I tried crediting everyone in the about window, but if you see some code that you think may be yours please let me know so I can give proper credit those that helped.

Any questions or comments are welcome, but I don't know how much spare time I'm going to have to support this. So sorry if this is the only version ever released.

EDIT: Forgot to mention, here the packages I used:

nirsc_html_help_common 2.0-1

oglib_array 2.7-1

oglib_error 2.3-2

oglib_lvdata 2.9-1

oglib_string 2.6-1

oglib_time 2.3-2

oglib_variantconfig 2.7-2

ogrsc_dynamicpalette 0.18-1

Tray Program Source 1.0.zip

I am getting error from SQLite while reading the database file. Error is
"Unable to open database file". I am using SQLite from last 1 month and didnt
encouter this error before. Suddenly, from yesterday SQLite is started giving
this error and is random.

What could be the resolution? Please find attached herewith my example code and
the SQLite error

SQLite error.zip

VariantArrayToCluster.zip

SetClusterElement.zip

SetClusterElementLV2013.zip

The ones pictured here are LV-Async.xnode and LV-Await.xnode. You can drag a VI onto LV-Async. It will open or check out (more on this later) a VI reference with code x100. LV-Await.xnode will Wait on Asynchronous Call, but instead of closing the reference it will check it in to a lookup table to be later used by LV-Async.xnode. The benefit of this is that when used with a reentrant VI, the asynchronous hierarchy will not go idle, so reference types created in the hierarchy will not go bad. There is an example in the VI package that demonstrates this behavior. The downside is that the memory the hierarchy uses does not get freed (subsequent async/await calls do not leak memory though since the hierarchy is being reused).

LV-Async-And-Forget.xnode opens the VI reference with code x80 and closes it after running the VI asynchronously.

LV-Async-Or-Show.xnode is meant for non-reentrant UI VIs. If the VI's front panel is not open, it will run the VI with option x80. If the front panel is open, it will bring the front panel to the front.

Attached is a VI package that will add these nodes to your palettes, along with a couple package dependencies.

Source code for LV-Async is here: https://github.com/erdosmiller/lv-async

LV-Async requires LabVIEW 2015 or later. Let me know what you think!

lv_async-1.0.0.12.vip

lv_scripting-0.7.0.6.vip

lv_vi-0.0.0.5.vip

That said, I've started on my first ever XNode and it's a cross between an unbundle by name node and the -> operator in C. It functions just like a normal UBN, however it was also pull items out of DVRs. Having to plop down a UBN to pull out the reference from the class, an in place node to dereference, and then another UBN to pull the data out gets tiresome after about the 100th property VI gets written.

So far I've gotten the node drawing completed (except for data type coloring of the labels), the type inferencing from the input wire, and the popup menu for selecting an item. Next up will be the menu selection code so that the names will finally show up in the terminals! Then I get the daunting task of scripting up the GenerateCode ability >_>

Anyone interested in something like this? Following this will be a match to the Bundle by Name node that serves the same purpose except to write the items.

Attached is a VI Package that will add LV-Control-Refs.xnode to your palette. This node, when dropped on the block diagram or double clicked, will update its output to a cluster of references to all controls in the VI. Controls in tabs show up as <Tab Control Name>:<Page Name>.Control Label. Nested tab controls with arbitrary depth are supported. You can bind the output of the node to an existing typedef by right-clicking on it.

I've used this node for awhile, but the tab support was added very recently and was a significant change. I've also attached a scripting library I maintain that this XNode depends on.

And source for the scripting library is here: https://github.com/erdosmiller/lv-scripting

I wrote this node because several times I've found myself bundling nearly all the control references in a VI into a cluster. It requires LabVIEW 2015 or later. Let me know what you think!

lv_scripting-0.7.0.6.vip

• Listing running VIs along with memory usage and refnum
• Aborting a running VI
• Showing or hiding a block diagram or front panel

I have searched on google and the NI forums with no luck.

Update:

Bitbucket Repository - https://bitbucket.org/lavag/labview-task-manager

Code Repository Page - http://lavag.org/files/file/245-labview-task-manager/

I was sad to see that it was dismissed as being classes. I think there are differences, and that having these kinds of types in LabVIEW could be nice, so I jank implemented them using XNodes:

LV-Define-Tagged-Union.xnode takes an enumeration and a cluster as inputs. If certain enum values have data associated with them, the cluster should contain an element with the appropriate type and the same name as the corresponding enum selection. The output of this node is an enum & variant cluster or "tagged union". This output can be bound to an existing typedef by right-clicking on the node.

LV-Construct-Tagged-Union.xnode takes a tagged union created by the define node at the top input and gives you a drop down menu. The input type adapts appropriately.

LV-Case-Tagged-Union.xnode goes inside a case structure. It's output type adapts based on the frame it is in.

Source code can be found here: https://github.com/erdosmiller/lv-tagged-union

I've attached a VI package that will add these XNodes to your palette, along with a package that will install a scripting library that this depends on. I wrote this awhile ago, so I don't remember all the details, but some types like .NET references may not be supported yet.

LV-Tagged-Union requires LabVIEW 2015 or later. Let me know what you think!

lv_tagged_union-0.0.0.7.vip

lv_scripting-0.7.0.6.vip

LV-Create-Signals.xnode takes a cluster at the input, and outputs a cluster of a DVR with the input cluster in it, and an event for each element in the cluster. The output can be bound to an existing typedef by right-clicking on the node.

The data is accessed via LV-Read-Write-Signals.xnode. It's similar to a property node, and allows access to cluster elements, array elements, and array subsets. If you write an element and change its value, the corresponding event is generated.

Attached is a VI package that will add these nodes to your palette, along with a scripting library that these nodes depend on. LabVIEW 2015 or later is required.

The source code can be found here: https://github.com/erdosmiller/lv-signals

I made these because I commonly use a DVR & user events for exposing data from a module. Let me know what you think!

lv_signals-0.0.1.7.vip

lv_scripting-0.7.0.6.vip

CompactIndexArray.zip

im working on labview

im trying to make a logic like.. i have few string which contains serial data to a firmware for a handle movement , handle moves in circular motion. like 30, 60, 90 degrees..

if 30 is pressed\enterd the string corrrosponding to 30 degree should be sent on my serial port. and vi should count numbers on each string sent 

thanks in advance and hoping for quick and positive replies

I thought I'd put this out into the wild before completion because I'm not going to get around to it again for another few months and as I've not seen anything else around; thought it might be useful.

It's a partial implementation of the OBEX protocol with an example of the OBEX Object Push Profile over bluetooth for sending files to mobile devices (vards,vcalendars, images,music etc).

Load up the BT Push File.vi (top directory) and set the address and you should be good to go to send files to your mobile phone.

The example has been tested on both the Microsoft and Widcomm stack to send files to samsung (U600, i8510) and nokia (N95,N81) phones without any problems, but (as with any new software) I am expecting a few teething problems so let me know and (no promises) I'll see what I can do.

If you are using the Widcomm stack. I would suggest pairing first because Widomm requires authentication and the authentication manager takes quite a while to pair so you will time out. The Microsoft stack doesn't require authentication first so need to pair at all.

Download File:post-15232-1240155321.zip

Path controls have an API for dragging and dropping Files/folders from the OS, or correctly formatted strings from Excel. While an acceptable drag-and-drop operation is underway the path control adds a dotted box to the control (I'm calling this a target box). However this behavior is not available for other objects such as panes or other controls. So Bodging time.

DragandDropBodge.vi (attached to the original lavag.org post) has a transparent Path control (set to 'Scale object with pane') that in all the use cases where a drag and drop is possible is set to Visible=True, and in all the use cases where the user would click on an object within the pane is set to Visible=False. I am using a shift register and the Timeout case to Visible=False the Path control, but for a more complex VI or when you have an existing need for the Timeout Case, you can manage this with a user event.

Other implementations:

This could be used to bodge drag-and-drop for a xy graph or other indicator instead of the pane at large. Or by capturing the cursor position at the moment of 'value update' for the path control a drag and drop could update a specific line in a tree/table/array.

Hope this helps when you are searching with the same keywords I was and found no solutions!

NSz

DragandDropBodge.vi

https://github.com/3esmit/LabVIEW-MongoDB

Name: LabVIEW MongoDB

Category: Database

LabVIEW Version: 2013

License Type: BSD

MongoDB Is a NoSQL database. It store documents in collections instead rows in tables. Tow collection documents don't need to have the same structure, and a document can store another document or an array of documents. Each document is persisted with "_id"  containing a special type called ObjectID. 
This lvclass deals with .NET dlls drivers from version 1.8.3.9. Later versions maybe cannot be used (I could'nt make them work in anyway) since LabVIEW 2013 ignores important functions from later drivers maybe for not supporting some .NET feature it uses.
The 1.8.3.9 driver got a bug in list collections that is worked around in the lvclass method.

Features:

• Deamon Start/Shutdown
• Insert Document
• Find by ObjectID
• Aggegate
• List databases & collections
• Create Collection
• Remove by ObjectID
• Find by Regex
• Find By Equal
• Get Document Part
• Update Set
• Insert Variant

Planned features

• Find Variant
• Aggregate to Variant
• LVOOP ObjectID
• LVOOP BSON
• LVOOP Query
• LVOOP Aggregate

I've had some issues with a laptop that is used for data acquisition. Sometimes the people unplug the power and don't plug it in again. To not loose too much data, I had to find a was for LabView to know the power source and the fill level of the battery.

This vi is done with LabView 7.1 and uses a call to the windows library kernel32.dll to get the data. It should work on any windows system since Windows 2000. Maybe it is useful to other LV users as well.

The second vi just calls the first one in 500ms intervals and shows the results.

If you have ideas for improvement, let me know.

kruemi

PowerStatus.vi

ShowPowerStatus.vi

I developed a simple and quick unit tester.  

My reason for developing this was NI's unit test framework is way to slow.  

Here is the download on the NI community site

https://decibel.ni.com/content/groups/ast-unit-tester?view=overview

I also included a VI Package file

Any feedback would be appreciated

Thanks

automated_software_technology_lib_ast_unit_tester-1.0.0.30.vip

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Provide-a-better-way-to-implement-a-polymorphic-VI/idi-p/920487

I was inspired to create VI macro(s) to attempt to address the problem mentioned in the request.  Attached is my first attempt and I'm looking for feedback since I know people here have strong opinions.   The benefit of this method is that a single vim (or 2 could replace a polymorphic VI with over 48 separate VIs....unless I'm missing something.  I know that VI macros are not officially supported by NI, but that hasn't stopped us from using unsupported features before.  Some people have probably already done something like this, but I couldn't find an example.

To use the files, unzip them and copy them all to your \LabVIEW (version)\user.lib\macros\ directory.  

Open the Example Changed.vi and review.

Changed Example.zip

Older project meant for a simple command and control system based around pastebin. Includes a Pastebin auto archiver example

Features

Bypasses developer API - Uses the same web interface as your browser

Auto Archiver "Pastebin Archive Main.vi" - Working 02/15/16 Searches the archives and downloads all unseen messages to disk. Avg of 25GB per week if I remember correctly. Saves to c:\pastes

Check archives for messages "Pastebin - Archive.vi" - Working 02/14/16

Search for messages "Pastebin - Search.vi" - Working 02/15/16 - Max results per page 10 and pages are zero indexed

Fetch "Pastebin - Fetch.vi" - Working 02/15/16 - Downloads the contents of a paste

URL "Pastebin - URL.vi" - Working 02/15/16  Grabs basic information about a paste using the URL

Post "Pastebin - Post.vi" - Broken/Detected 02/15/16 - Posts are nolonger set as public and have triggered anti-bot measures. Need to check what differs between my post and my browser post as this has changed. More than the new key location has changed.

Needed improvements

More examples

Documentation

Fix Post

Add create dir when saving if does not exist to archive example

Operation

Pastebin.zip

Simple Mandelbrot explorer that I wrote a few years ago. Just did a little cleanup and saved in 2015.

Features

Many predefined color pallets

Rolling color pallet to produce motion effect

Ability to customize the color pallet

Log color mapping

Keyboard or mouse control

Basic shortcut keys

Saving high res images

Needed improvements

Documentation

Clustering

Save settings

Operation

Load project in LabVIEW 2015 32/64 bit

Start program using Mandelbrot Main.vi

Moved to Code Repository

 Following my previous attempt with Google maps, Here is a websocket based link between LV and Google maps.

Websocket class by S.Marlow http://evexiallc.com/index.php

JSON API by drjdpowell

Javascripts and demo application are based on the Webpanel demo application.

Instructions:

1. Obtain a Google maps API key. 

2. Edit the WP_Googlemaps.html and add the key to the relevant script tag.

3. Start the demo vi (google maps demo.vi)

4. Open the WP_Googlemaps.html with a modern browser.

I have tested it with Chrome and Safari on iPhone 4.

You might have to point to the correct path of some VIs, they are included in the vi directory.

gmaps_websockets_LV2013.zip

But these UI's relied on button controls, to be configured and made a specific way, and if you needed to update tabs, buttons, or groups, it had to be done manually.  So I wanted to come up with a way to make a ribbon like UI, but all that was required, was to provide the tabs, groups, and buttons, and the UI would be drawn.

The end goal was to make an XControl with value change events when the user presses one of the buttons, but for now this is just a demonstration of what is possible.  The idea was the XControl would also be smart enough to only redraw the parts of the image that were changed.  Like if I changed the top tab background color it wouldn't have to redraw all the bottom parts of the UI.

Here is a video demonstration.  Here I show the default settings, then change some of the color and text settings.

http://screencast.com/t/daan9D78vqV

Some of the challenges that you don't really think about, that the API needs to be able to handle, is the text being of an unknown length, and number of rows.  Things like the top tabs needed to be able to expand right, or down as needed, and all other tabs, and images needed to shift to compensate.  Same thing when it comes to the button and group text.  Here you also have the added complications with the fact that the text might fit in the space already needed, like if the button is wider than the text.

Images are scaled using .NET and the GDI resize.  This is also where images are combined, since some may have alpha layers, much like the included images do.

I knew image scaling might take a while, and wouldn't be the type of thing I would want to redraw as a mouse moved over a button.  So for that reason I draw all the button states on startup, and then just combine the appropriate images for when the mouse is over, or down on a group, button, or tab.  This means a pretty fast response on the UI but means more memory is needed to hold all the button states in memory. 

Doing the gradients efficiently for me meant doing them natively in LabVIEW.  I found some .NET code that would do it, but much slower than LabVIEW just drawing horizontal lines, and using math to determine the next color of the line.

Several times images or parts of images needed to be shifted and translated.  Instead of converting a picture back into image data, then performing the move, then converting back, I used the code posted by Norm here.  It needed to be updated for a few opcodes but for the most part is fantastic and made the image processing quicker.

Other than mashing this into an XControl, I also didn't get around to creating a way to disable or disable and grey out buttons.  This would take more image manipulation magic and possibly more images to hold in memory.  Since disabled buttons are probably going to be somewhat rare, I thought I might draw these on-the-fly instead of on init like all the other button states.

Anyway I hope someone finds something in this helpful, because I doubt I'll be able to do anything with it for a while.  Back saved to 2013, and remember this is very unfinished code, be gentle.

EDIT: Attachment removed, re-uploaded with example images below.

LV2013: Timing Probe.vi

A more minor upgrade is making “Execute SQL†polymorphic, so as to return data in a number of forms in addition to a 2D-array of strings.  See the upgraded example “SQLite Example 1 — Create Table.vi†which uses the new polymorphic VI, including showing how to return results as a Cluster.

For Attributes, I had to make some choices in how to store the various LabVIEW types in SQLite’s limited number of types.   The format I decided on is:

1) all simple types that already have a defined mapping (i.e. a “Bind†property node) are stored as defined (so strings and paths are Text, DBLs and Singles are Float, integers (except U64) are Integers.

2) Timestamps are ISO-8601 Text (the most standardized format of the four possibilities)

3) Enums are stored as the item text as Text, rather than the integer value.  This seems the most robust against changes in the enum definition.

4) LVOOP objects are stored flattened in a Blob.

5) any other LV type is, contained in a Variant, flattened and stored in a Blob.  Using a flattened Variant means we store the type information and LabVIEW version.

drjdpowell_lib_sqlite_labview-1.6.0.51.vip

LabVIEW 2011-2015

The Attribute stuff grew out of a project where SQLite files held the data, one for each “Runâ€, and the Runs had lots of small bits of information that needed to be stored in addition to the bulk of the data.   When and where the measurement was taken, what the equipment setup was, who the Operator was, etc.  I purpose-made a name-value look-up table for this, but realized that such a table could be made into reusable “attributesâ€.

LV2013: ProjectTree.vi

XYChart.zip

In case you're not familiar with Gold: GOLD is a free parsing system that you can use to develop your own programming languages, scripting languages and interpreters. It strives to be a development tool that can be used with numerous programming languages and on multiple platforms.

I use it mostly to build AST out of strings of text that represent short snippets of code. The Source comes with an Top level example of how  a recursive evaluator can be implemented. But it can be used for many LabVIEW things including a 100% native XML parser, 100% native Scripting language... and the idea is that its native so that's nice. 

Performance:

I haven't tested long source strings for performance but currently it is working really quite quickly. Sub milliseconds for the numerical evaluation example. LabVIEW can be really sneaky making extra copies when you don't really need them. I have tried to do somethings to increase performance more. Alot of the items in the parsing VI are subroutines. And I have added Swap Values as a common performance tool. It is really cool. especially when working with class private data that doesn't deserve an in class function. eg. Tokens contain other tokens that can be evaluated recursively, however it doesn't make sense to put the eval function in the token class. As AristosQueue posted here http://forums.ni.com/t5/LabVIEW-Idea-Exchange/New-in-place-element-structure-option-class-property-node-read/idc-p/2515866#M24026 

After creating a grammar This example uses Devin Cook's Operator Precedence example. As you can see a string goes in and a number comes out. Parser engine has an application to test and verify grammars. This engine only except egt format.

The above grammar has 15 symbols. I think of content as leaves on a AST (abstract syntax tree) and Nonterminals as Branches that have more leaves.

Productions are a list of how each NonTerminal can be configured I like to think of it as a list of cases to handle.

It turns out that this makes a pretty simple recursive evaluation scheme 

If the Token is Content I see what type by getting the table index and using a typedef with all of them listed. In the case of an integer i get the value from the string and return it.

However if the Token is a NonTerminal, It can be handled by Sending the Tokens contained by the token into the recursive function and  using the values. You can see that the Production:

<Muiti Exp> ::= <Multi Exp> '/' <Negate Exp>

Contains 3 tokens.

I want to evaluate the Value associated with the <Multi Exp> so i get the sub token at index 0

and <Negate Exp> at index 2. 

You can find the Code here: https://decibel.ni.com/content/docs/DOC-41064

Hi,

recently I posted an idea in the exchange forum for adding support of sortable headers in bookmark manager: http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Bookmark-Manager-Sort-by-column/idi-p/3136830

So I started to develop a small addin you only need to place somewhere near your code to get the sorting for Listbox, MCListbox, Tree and Table (Table with [shift]-Click).

For Listbox and MCListbox all seems fine, for Tree sometimes you get a crash (I nutshelled this behaviour to the "Sort Children"-Node and reported it). With Table integrated the stopping of this remote VI seems to be delayed. Don't know why.

I'm not sure if I'm on the right way...

Peter

Edit:

Bugfixing:

• added wait for Frontpanel not closed -> Rev.156 (now works in LV2014)
• added little bit error handling
• reworked example

(File LV2014)

SortTable(rev.156).zip

QSM Evolution.zip
Code used in presentation video detailing why the typical QMH is fraught with issues that we have all run into

Credit to Daklu for it's creation and sharing

ni_tool_tlb`-1.2.0.23.vip Most up to date version of TLB`

Rebirth of the LabVIEW State Machine.pptx

TLB` Application Template.vipc

Is X = Y +/- some acceptable tolerance?

And that worked perfectly for my use case. That is, I knew that the max. value was 1000 and the min value was 0 and the resolution (or increment) was 0.01. A tolerance of 0.001 was sufficient.

This got me thinking. Wouldn't it be nice to have some reusable VIs for testing if floating point values are almost equal? Unfortunately this meant taking a broader view of the problem and lead me to this interesting blog post:

http://randomascii.wordpress.com/2012/02/25/comparing-floating-point-numbers-2012-edition/

I've attached VIs for the Absolute Epsilon comparison, Relative Epsilon comparison and the ULP comparison described in the blog post for double precision floating point values.

Perhaps this would be a nice addition to the somewhat barren OpenG Comparison Pallet?

Uploaded package to Code Repository: http://lavag.org/files/file/259-floating-point-almost-equal/

AlmostEqual_LV2013.zip

AlmostEqual_LV86.zip

Disclaimer 1: Private methods are not supported by NI and should not be used in build applications, and are generally only used for tools of development.  

Disclaimer 2: This set of code contains an EXE (pv.exe) and will be saved and executed from the system temporary folder %temp%.  Information about this EXE can be found here.

Disclaimer 3: As stated in the main VI, this will taskkill the version of LabVIEW running, and all unsaved work will be lost.

Any feedback is appreciated, thanks.

EDIT: This code uses OpenG File Library.

Enable Disable Private Methods.zip

Example usage and download:

LabVIEW 2014 version:

Sort Using Other Array.zip

LabVIEW 2009 version, uploaded by request:

Sort Using Other Array.zip

I know that many of LabVIEW's dialogs are implemented as VI's, and I was curious if the statechart module's state configuration dialog was implemented in this way as well. Sure enough, it was, which meant it was possible to create an editable block diagram as part of a VI's front panel. It didn't take long to figure out that the input/output nodes on the left and right were really unbundle/bundle by name nodes, as it was literally as easy as putting the mouse over one and looking at the context menu! I didn't at first know how it prevented them from moving left and right or being copied to another VI, however. I realized it had something to do with the object's flags through experimenting in Heap Peek. Then I found the private property called "RestrictLRGrowMove", which had this exact effect.

So yeah, this is basically just a VI I created as a demonstration of this technique. It's possible to put a block diagram in a subpanel through a scripting method, and it's also possible to enable editing in that subpanel through a private property or hidden menu item. Of course, the latter means this isn't officially supported by NI, but it's still an interesting technique. Perhaps someday it will have official support.

And if you're wondering why the unbundle/bundle nodes only show the text, it's actually very simple: there is no way to scroll in the subpanel unless scroll bars are enabled, and the rest of it is simply out of the viewable portion! The subVI that generates the embedded VI is kind of messy, but I put a step-by-step explanation of how it's generated on its block diagram as well for that reason.

Subpanel Diagram Example.zip

We'd like to renew this conversation by opening up a discussion of what projects might interest the community. That discussion is posted here:

https://decibel.ni.com/content/thread/23441

If you have any thoughts or feedback, feel free to post here or in that discussion. We're very interested in hearing from you.

Convert Range.vi

That is to take into account double quotes and commas inside double quotes and multiple-line entries. This is essential if you plan on storing user-input text data or storing numbers that may have a comma as a decimal point.

From what I can tell, this is the same format that Open Office, Libre Office and Microsoft Excel use for their CSV file export. Therefore, using this format, you can export from LabVIEW to CSV, open it in Excel, make changes, export from Excel to CSV then import it back to LabVIEW without everything being broken by a missing double quotation mark or an extra comma.

Attached is the VI to parse a CSV formatted string to a 2D array of strings for LV 2013, 2012 and 8.6. I've also attached an example CSV file (inside Test1.zip) exported from LibreOffice to demonstrate some of the tricky cases that most CSV parsers can't handle.

Please give it a try and let me know your thoughts.

Update: I've posted the finished library to the Code Repository Database & File IO catagory here http://lavag.org/files/file/239-robust-csv/

I've put together a small library to convert JSON formatted messages into something more useful in LabVIEW: variant attributes. It's still in progress (more scripting to go...), but you can see it at: http://code.google.com/p/jsonlv/downloads/list. Grab and unzip the .zip, open the json_example.vi, and work from there.

Because JSON is a pretty variable format, I'm looking for JSON (valid or not) that breaks the parser. If anyone wants to give it a try, please feel free to contact me here, or at joe@underflowsoftware.com.

(Side note: LV crashes if you try to create a very, very deeply nested cluster using scripting. So... don't do that!)

Thanks,

Joe Z.

This VI sends the message string along with a time stamp and the call-chain to listeners of the "stdout" event (only if the specified verbose level less than or equal to the globally set verbose level).

The message received by the stdout event handler is an instance of the "LV_Printf Msg" class. The data is available though property nodes or it can be flattened to a string through the dynamically dispatched "Receive Message" method. You can create a child of this class and override the "Receive Message" method to format the message differently.

Please try it out and let me know your thoughts.

Source & Example Usage - LabVIEW 2013: LV_Printf - 2013.zip

Source & Example Usage - LabVIEW 2011 (not tested): LV_Printf - 2011.zip

LVS_Basic.zip

Probably the easiest method I've found is to create separate dynamic accessors which can be dropped either before or after the FGV vi which stores the data. This isn't too bad but doesn't give the simplicity and ease of use I was hoping for.....

Any ideas???

Let me know what you think. I've possibly made this far more complicated than it needs to be but its been a bit of fun anyway.....

Cheers,

Pete

Universal FGV.zip

I was wandering if it would be a good idea to have the "variant to data" behave the same way, instead of returning an error 91, shouldn't it try and see what does match between the data available in the variant and the data type passed to the "Variant to Data" primitive?

I find it not easy to explain what I mean so here's an example :

And here's the code.

my variant to data.zip

I know there are some limitations, not all data type are supported (refnums, arrays, waveforms, etc...) and unique names are required.

If someone wants to know when this can be useful, the answer is this : when you develop custom steps for VBAI and you want to add some parameters without losing all the ones that were already there.

Maybe there are other use cases for this?

Any feedback will be much appriciated.

For those not familiar with it, markup allows inline text to modify the displayed properties of the text. For instance, **bold** becomes bold, _italics_ becomes italics, etc.

The code currently supports:

• Bold
• Italic
• Underline
• Colors (in #XXXXXX format)
• Text sizes (verysmall, small, large, verylarge)
• Strikethrough
• Some font setting

Of course, it's still limited by the string control capabilities (no hyperlinks, no superscripts, no embedded lists).

If people think it's worthwhile, I'll develop it into a somewhat more complete solution (or, of course, they can!). An X-control that supports it seems like an obvious extension, but I'm open to ideas.

Note: this was developed in LV2011, and back-ported to LV2009. If you spot a problem with it, please notify me.

Use: open and run LVMark_TestString.vi for a demonstration.

Thanks,

Joe Z.

LVMark2009.zip