Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Search instead for
Did you mean:
Do you have an idea for LabVIEW NXG?
Use the in-product feedback feature to tell us what we’re doing well and what we can improve. NI R&D monitors feedback submissions and evaluates them for upcoming LabVIEW NXG releases. Tell us what you think!
The result of the computation is used in statistical process control.
I think that LabVIEW should have its VI's compatible with NIST, and "engineered for process control", seeing how they control processes. The control shouldn't exclusively about operation, but should also have bounds, and quick/effective alerting for out-of-control condition. (OOC).
When using the waveform datatype in my applications I noticed that the T0 field of this datatype is getting out of pace with the system clock of the machine of where it is running on.
The origin of this behaviour is that time synchronisation only takes place at the start of a measurement session after which waveform timestamps are derived from the measurement device's clock and not from the system's clock. Small differences in clock accuracy cause the clocks to run out of phase.
This effect is especially noticable on applications that are running 24/7 e.g monitoring Industrial continuous processes for weeks at a time.
When this happens and data is saved for analysis afterwards there could be problems synchronizing this saved data with data of other sources because timestamps are different.
The only way to prevent this is stopping the task and starting it again but this is not always possible due to the nature of the processes monitored.
It would be very nice to have an option in the AIread function that can automatically synchronizes waveform timestamps with the systemclock on a timely basis.
Funtionally this would be something I programmed in the attached VI.
A customer of mine want to create multilingual applications. They are sloving this right now by im- and exporting strings. They found a tool in the Internet, that can extract texts which can then be processed and be imported again. The VI has then to be saved and compiled, which is very time consuming.
He programmed a tool for a Windows Applications which is working similar. In that tool it is then possible to change the language. But we would need some soft of language lists.
His Idea to slove it easily is to implement subtitles (maybe around 5) in every forntpanelelement in which you could set the translation similar to a button text. The same way could be applied for the tips and the description. These Subtitles should then be switchable during the test to get the proper language version.
Still today in LV2016 there is a limit to the number of characters read before an error is thrown (It does allow for lines if '\n' exists in the file). The limiting input here is an I32 which allows for the (-1) entry meaning all characters. Why couldn't this be a U64 today? When would you ever want to read '0' characters from a file that you opened? Have any '-1' entry coerced to '0' which will now mean ALL Characters. I understand that this I32 methodology has been kept for entries into loops which still maintain the I32 basis. Shouldn't those also be considered for updating to U64 with any negative number input coerced into 0?
When I build, I like to test each step. That means that I make a bunch of "debugging" indicators. Some might prefer probes and breakpoints, but I like the "build as you go" and "don't use too many tools". The challenge here is that about 80% of indicators that I make, I have to delete.
I wish there were a version of "diagram disable" that is specified in the block diagram, that worked for the front pane, and left me some tiny asterisk instead of the indicator, that didn't hit program execution times, and that when I configure execution the asterisks can be made to disappear.
This would allow me to revisit my code, to access all of my debugging methods very quickly and intuitively, and to not necessarily change the final layout of the front panel after my debug is done.
Normally, in the development environment, I make everything nonreentrant just to facilitate debugging. But sometimes, there are small VIs that are called frequently from many callers where it would be nice if I could make them reentrant so they don't block each other when running as an executable.
Much like the control+shift+left click hold and drag to move the page around, is there any possibility of adding the function of making this possible using the middle mouse button? Since middle mouse button click has basically the same function as left click, this seems like a good idea to help navigate through VI easier.
LabVIEW on just looks awful. Here's a little gallery of horrors. In my opinion it makes LabVIEW looks very unprofessional. These are all taken from a "stock" LV2016 Full license, installed on Windows 7, taken from some of the windows I see all the time. This list could go on forever!
A lot of these problems seem to originate from using LabVIEW-style controls and indicators into its own windows and panels, which are not rendered correctly. Please save LabVIEW from itself!
If you copy an animated gif to the clipboard, then paste in a pict ring, the animation is pasted as a single image file. How about having an option to split the animation frames into successive pict ring elements?
After reading Restore High Contrast Icons I procrastinated as long as possible before installing LV2016. When I finally did, I was disappointed by the additional space required for the palettes; all of them! I have been using LabVIEW since 5.0 and switched to an Icon view of the palettes shortly after getting comfortable with the graphics. Now, I have to move my mouse further to get to each sub-menu and VI selection. It's a waste of developer's time and apparently done for absolutely no good reason except to make a change; very similar to the washed out icons.
This extra space needs to be removed or at least an option provided to set the spacing back to the condensed spacing always available.
These images to show the relative size of the palettes LV2016 vs. 2015.
Yes, this might seem trivial, until you think about traversing several palettes to get to your needed VI.
*Random example, if one were doing FTP development they'd pin the menu.
** The original size of the above graphic is 1030 pixels wide; less than 800 for 2015.
Quit messing with what works and has become the standard with regards to options. At least when that ridiculous "default" setting for icons instead of terminals was introduced we could undo the setting in Options.
It seems that NI has hired some non-G experts to mess up the interface simply so they can enumerate all the "great" improvements they've made. Or, was all the extra space to make sure newbies couldn't miss the folder tab, since connecting the "right arrow" on an icon to it being a sub-folder would be too difficult for children?