LabVIEW Idea Exchange

Top Authors

User

Kudos

Post an idea

NXG Style Scrollbar

Through normal programming this can be done, but it does take someone that really understands the problem and how to deal with it. My proposal would be more useful for a new to intermediate user or when all that's needed is a simple and quick solution.

It would work like this:

A simple "Data Control" Express Node that could take data acquired using modules that run at different speeds (like a NI 9211 and a NI 9239 running on a cDaq chassis), that would automatically control the buffer size (through averaging as one option) to prevent a program crash. Then output the data at a equally consistent rate which could then be graphed or logged at a set rate as determined by a user.

As we know if a 9211 is running at 4Hz and a 9239 is running at 20Hz, that could produce a buffer over run. I'm suggesting that a "Data Control" node be written that a programmer could use to graph and log data at a selectable rate no higher than the slowest module. In my 9211 & 9239 example it would be 4Hz or less, and that would occur because internally it would be automatically averaging the 9239 data. If a lower speed is selected (like 1Hz) then both would get averaged before the data gets output at 1Hz.

View All (1)

Dear Hot Shot Devs!

thousands of us want to be able to build a mobile app from LabVIEW!!!

Can you imagine??

All that power with full responsive features on any device, like Swift and Android Studio??

you can “hook into” those tools to let us design the User Interface and evening do Bluetooth and Wireless with all’s y’all’s stacks and wizardry!!

Consider me as an Alpha tester. I know what is needed. Let me know the plans!

I have been using LabVIEW since before rev 3.0 when we could actually talk to Dr G!!

great work you are doing. Sometimes I do not enjoy the “abstractions” you do to make it easy. Kind of liked the good ole “bit banging” direct link to Comms and I/O but I understand.

View All (2)

I initially came here to suggest that there should be an exclusion added for error terminals when selecting the option in Tools > Options... > Front Panel. But then I thought, why not just let us configure which data types default to required and which default to recommended. I'm probably being nit picky here, but I think this would be a really cool thing to add.

Check the box, then a nested list underneath, where you can add exclusions, becomes un-grayed out. Data types you don't want to default to required.

It would be useful if the Search Results window would show the number of callers not in memory (screenshot 1).

1. The Search Results window, with extra information about the number of callers not in memory

Find all instances 1-edited.png

Screenshot 1 was generated by right-clicking the icon of 'SubVI.vi' and selecting 'Find all instances'. The dummy project is shown in screenshot 2. Screenshot 3 shows the Find Callers window that pops up when right-clicking SubVI.vi in the project and selecting Find>Callers.

2. The project

Find all instances 3.png

3. The Find Callers window

Find all instances 2.png

When refactoring, it is often necessary to find and replace all instances of a VI, before removing that VI from the project. A typical workflow for me would be:

Open the main VI of the application (to load in memory as many subVIs as possible)
Open the VI to be replaced/removed from the project, right-click its icon and select 'Find all instances'
Navigate to each instance replacing/removing the VI as necessary
Ctrl-Shift-E to select the VI in the project, right click the VI and select Find>Callers.
- This sometimes brings up callers such as tester VIs that are not loaded in memory by the main VI of the app. In this case:
  - Open each caller previously not in memory. Use 'Find all instances' again.
  - Final check: Use Find>Callers one last time to ensure no callers.
- This sometimes shows 'No items were found'.*
Remove VI from project and disk

*If the number of callers that are not in memory was displayed in the Search Results window, and if that number was 0, it would remove the need to check via 'Find>Callers' before removing the VI from the project.

The 'Find all instances' feature would become more complete if it displayed information about callers not in memory.

Thanks!

View All (2)

User Event return value

The idea is to add a return value option to user events:

Create User Event.PNG

Event Structure.PNG

Generate User Event.PNG

If there are multiple event registrations, the return value is passed through them. Pretty much like existing filter event.

Optional icing on the cake:

Spoiler

The Generate user event could be split up in a send and receive part.

A time out could be added to the receive as well.

Waiting for return data could be optional. The data will still propagate though all registered event structures.

The Generate user event could be split up in a send and receive part. A time out could be added to the receive as well. Waiting for return data could be optional. The data will still propagate though all registered event structures.

Disclaimer

Spoiler

I've read all "User Event" search hits on the idea exchange. Closest\only related one I could find was Register-User-Event-as-Filter-event, which is mostly concerned about discarding the event. But the idea exchange search is terrible, so it could be right under my nose...

I have two arrays I'd like to pivot into an array of clusters of a particular typedef. I could index and bundle it myself, but it's just weird that I can't use this builtin function just because the typedef has an element that's an array.

Also, it's kinda weird that it won't take a typedef as prototype. Casting it after takes up about as much room as doing the bundle in a loop!

I can see some reasons that letting us pass in 2D arrays would lose the tight optimization of the original (maybe it can compile-time determine the size of the cluster elements if none of them are arrays... except that you can put in object data. I guess either that's a reference under the hood, or there's some other reason)

Or maybe it's that it could cause confusion between making a 1D array of clusters with 1D arrays, or making a 2D array of clusters of single elements? That seems like it could be solved either by only doing the former, or requiring a typedef in that case, to disambiguate.

If you are instantiating classes dynamically or calling VIs dynamically through VI server, you may need to include the source files under "Always Included" when creating a build. If you are dealing with a large number of files in a multi-developer environment, you might also be using an auto-populated virtual directory. The problem with this is that everything under directory will be included in the build. Say you are building a hardware abstraction layer with 100s of different instrument drivers, you will likely have all sorts of different files like programming manuals, unit tests, project files, lower level instrument libraries, and VI trees. You might not want all of these files included in the build. Some of the files might not even compile (ie. VI Trees), which will prevent you from creating a successful build. If you are instantiating the classes dynamically, all you really need to do is include the lvclass files since that will automatically bring in the dependencies for that class. You could separate these files, but it would likely be a less cohesive directory hierarchy. For example, if a developer is implementing a driver they will probably want to access the programming manual under the same directory hierarchy, while at the same time, a programming manual probably wouldn't be beneficial to a user when the build is deployed so you might not want it included. Being able to define 1 or more file type patterns on either auto-populating virtual directories or on the build specification UI for source files, would quickly resolve this issue.

Delete Directly from Class

When right-clicking on a VI in a class, there's an option to "Remove From Library". This option removes the VI from the library, but leaves the file on disk.

95% of the time that I'm removing a file from a class, I'd also like to delete it from disk.

The wording might need a bit of work, but it'd be great if there was an option to simply "Delete" or "Remove From Library and Delete".

(In the meantime, I'll continue to "Explore...", then "Remove From Library", then delete from my file system.)

I think it would be really useful to have a Quick Drop shortcut installed by default that toggles label visibility for selected items. I know you can select multiple objects and right click> Visible items> Label but this takes me several seconds.

How I imagine it would work
Select GObjects on front panel or block diagram --> Ctrl+space, Ctrl+L --> label appears if it wasn't visible or disappears if it was visible.

If multiple items selected with a mixture of visible and non-visible labels, use the same logic as what happens when you try to embolden partially bolded text : toggle all to the opposite of the most frequent state.

I might write something that does this, but it would be really great if it was standard. 🙂

View All (4)

Adaptive alignment for subdiagram label

It would be great if we could close the documentation editor window by entering <Shift> + Enter. Several other LabVIEW IDE dialogs and text entry objects work this way already. We can open the properties with a keyboard shortcut, and if we were last using the documentation, no mouse work is needed, except to close the dialog. When I already have both hands on the keyboard, it would be nice to not have to grab the mouse just to close the dialog.

Edited to suggest using unused modifier key, Ctrl is already taken.

Enable input on property node

We often use property nodes to change controls appearance/behavior in a while loop but because of their added overhead, we don't want to do it every iteration, just when other values change. To get this effect you have to wrap the property node in a case structure and ti in the appropriate variables. this is bulky and hard to read at times especially because it encourages using "no names". Or you can create a sub VI with the right rappers on the inside but you have to pass in a reference. It would be great if there was a built in enable input on a property node (ideally without increasing the sizeof the top part). I even toyed with using the error in to get the desired effect (tying in a error or no error constant chosen by a case structure) but thought better of it (I think it gives the desired effect but sometimes you want to use the error input for timing control or actually as an error.

It seems like a simple request that would really clean up a lot of my code or improve performance if you are setting properties every cycle.

View All (2)

In many software packages, if you do a cut (ctrl+x) then paste (ctrl+v) it will move the item and then sometimes subsequent paste operations will make copies (sometimes they act like the clipboard is empty after a single paste)

In labview it is more like it makes a copy and deletes the original. This is somewhat unexpected behavior for me (maybe others find it normal). I would like to use it to move items around without having to drag somewhere in between (say if I want to move a terminal or local variable from one case to another I have to drag out while braking wire connection change cases and drag back in)

For a control, if it had property nodes, connections in connection pane, events, or local variables all these connections brake or are deleted, and the new item is no longer connected to anything. If you do it on a property node, the new node is un-linked to anything. A local variable is the worst of all in my opinion. It deletes the original local variable but makes a new control that the new local variable is linked to. this seems like it would rarely if ever be desired behavior (you get the same problem just copy/paste on local variable as well). On the other hand just making a new local variable linked to the same control would be great for both cut/paste or copy/paste.

View All (1)

LabVIEW do a lot of background changes on all VIs in the memory even if the user did not change anything.

You can recognize this when you close a VI and LabVIEW asks you for storing it or some of its SubVIs.

The can be prevented by enabling the options "Tread read-only VIs as locked" and "Do not save automatic changes".

Having an active read-only flag on several thousand VIs and removing / setting it manually is not really funny during daily development work. Wouldn't it be possible to prevent storing automatic changes independent from the read-only flag of the VI?

My use case: I have to open my Project sometimes in LV32 and sometimes LV64 to develop / run and compile the code. Each time LV wants to store all VIs when they have been stored with the other Bit-Version before. In each case I'm using LV2019SP1. The compiled code is already removed from all my VIs.

View All (9)

Include project file in zip

If I create a zip file for my build distribution in a LabVIEW project, I can choose "Zip entire project" for Source Files. In this case, the lvproj file is included. However, if I don't check that box and instead pick specific files to include, the lvproj file is not included.

Sometimes, there may be installers and other drivers included in the project that I don't always want to include for size reasons during development.

I'd like to be able to choose whether or not to include the lvproj file when making a zip.

View All (1)

LabVIEW Idea Exchange

NXG Style Scrollbar

Express Node for Data Control - to average different data speeds and prevent buffer over runs

When adding an event to an event case, place the cursor in the "filter" field.

LabVIEW to Android .apk for apps or to Apple mobile

Array FP Controls and Indicators can show/change array dimensions

Add "Exclusions" Option for "Connector pane terminals default to Required"

Search Results window should display the number of callers not in memory when triggered by 'Find all instances'

User Event return value

Let Index & Bundle Cluster Array produce typedefs and 1D array members

Allow the specification of file type patterns under Always Included for Build Specifications or Auto-Populated Virtual Directories

Easier access to class override functionality

Delete Directly from Class

Quick drop shortcut to toggle label visiblility

Adaptive alignment for subdiagram label

Close documentation window with Shift + Enter

Enable input on property node

cut (ctrl+x) then paste (ctrl+v) does not move like in may other software packages

"Do not save automatic changes" also for non-read-only VIs

Default Value for the In Place Get/Replace Variant Attribute

Include project file in zip