There are methods available to covert from .sif files commonly used with InField to .tdm or .tdms but not the other way around. It has been suggested by customers to provide a method for this conversion.
Given a multiframe flat sequence, there is sometimes the need to remove one of the frames because it is not needed. This is currently hard.
We can add frames, merge frames, insert frames, and remove the entire frame structure, but if we try to remove a single frame, it drags it's entire contents with it to neverland.
IDEA: When removing a frame of a flat sequence, the code should stay, just the frame should disappear.
This is a more natural operation. Deleting the code first or later if desired is trivial.
(Originally I was only thinking of edge frames (Inner frames can already simply be merged). Another option would be to split the existing sequence into two sequences if an inner frame is removed. Would that be useful too? Maybe!)
Reading this idea on auto-Shift-Registers, I thought of another use case that seems to be implemented wrongly. When selecting "Replace with Tunnels" on a valid (i.e. wired and not broken) Shift Register, then the tunnels should be created as Non-Auto-Indexing so that the code remains unbroken. However, if the Shift Register contains an array, then there should be the option on the right-click-menu to create either Indexed or NonIndexed terminals, as either may be wanted.
There seems to be a control missing in LabVIEW: an intensity plot that will accept data that has been sampled at a variable rate.
It should be possible to specify the time stamps of each block in the plot (like with the XY Graph) so that you can present such data without having to resample it at a fixed rate.
Excuse me if this has already been added in a later LabVIEW version but I have found no references to it in any documentation. I am still developing with LV 8.6.1. I have found out that the Plot Name text is not editable in the legend during run-time. I am using the XY Graph but the missing features seem consistent among other graph types, too. If you select the entire graph in development mode, and change the text format with the drop down text formatting menu, all text in the graph is changed, including the legend. I found property nodes for formatting the text of labels, captions, scale names, and markers. I know there are many posts concerning annotations needing similar formatting capabilities. I also suggest the legend text have property nodes to format the text independently (size, color, font, etc). This would be very useful, as changing the text size, also appears to resize the small legend pictures displaying the format of the plot. This would be most useful when a UI allows window resizing and when other UI items are referenced in position with the legend line items.
An additional feature is to also allow the X scrollbar width to be adjustable during run-time as well. Or this could resize with the graph as the window grows. It does not scale in LV 8.6.1.
Window as designed for minimum resolution in my app (Minimum.jpg)
Window expanded showing misalignment of legend to other controls referenced to legend line items. Also showing X Scrollbar not scaling to window resize (Expanded.jpg)
I tried posting this in "Additional NI Software Idea Exchange", but could not find the the "Post New Idea" button.
When looking for LabVIEW Embedded for microcontrollers, it is difficult to find the product. When searching LabVIEW Embedded, this often refers to LabVIEW Real-Time and FPGA modules. Searching for LabVIEW Embedded for ARM results in search finds, burt then the generic product handles any 32-bit microcontroller.
My idea is to better identify this product by calling it "LabVIEW Embedded for Microcontrollers" or "LabVIEW Microcontrollers", to keep it consistent with LabVIEW Real-Time and LabVIEW FPGA naming convention.
When replacing a bundle by name function with an Unbundle by name function or vice versa, the element names should be maintained. Currently when you replace this function with the other, LabVIEW does not maintain the same element names.
I've been messing around with DVR LVOOP and have found that the inplace node makes proper error handling a bit tedious. First I need to handle errors passed into the vi, Then I need to handle multiple errors from the read elements then the write elements.
For example if I have two DVR LVOOP Items and I want to move a string from one and concat it onto the string in another I need to do this (see initial.png attachement)
I propose the following (might benefit from some more graphical tweaks), which is functional equal to the above (see improved.png attachment).
Note: No data is modified if an error is passed into the inplace node or if any readers produce an error. Any warnings passed in are maintained. If multiple errors are produced from the readers or writers the highest on the inplace node is the one reported. This would also work with errors from the Variant to/from elements (and variant attributes if those ever get added to the inplace node).
It would be really nice for plotting multiple waveforms to be able to turn on and off each waveform's visibility on the graph with a simple radial button. This could be easily added to the plot legend. Here's a picture of what I mean:
This would be great so if the data of one channel is very closely aligned with another, you can disable the plot on top and view underlying data.
I find the color of the Reorder Button on the front panel a little confusing. The colors of the two circular arrows being gray gives me the impression that the buttons is disabled for some reason, especially considering the related buttons to the left have some color with green and yellow boxes. It causes me a slight mental block every time I want to use it. I would suggest that the Reorder button be given some color, such as green, so that it mentally gives the impression that it is allowed to be pressed.
Up to LV 2010 the "Nonlinear Curve Fit.VI" has an Input for the data weighting. For sure this could somehow be related to measurement errors of the data, but as this is not documented and not for a daily user well known it would be nice to have an additional instance were the input is not the "Weight" but the "Std. Dev. of y".
In a similar way it is not totally straight forward to calculate the standard deviation for the "best fit coefficients" from the "covariance matrix". So an additional output "Std. Dev. of best fit coefficients" would be very helpful.
The current Graph Properties Including a Boolean for "Show plot legend":
I'm suggesting to add more options here:
I've added an Enum:
Sometimes, the graph is empty, there are no plots, so I don't want the plot legend to be visible.
The same is true for the plot legend scroll bar - If there is only one plot I don't need the scroll bar.
It could be nice if I wouldn't have to do it programmatically.
LabVIEW has a good starting point for a text-based run-time menu. How about the option for a run-time toolbar in the same fashion with a base to start customizing from. It would have the "typical" buttons: New, Open, Save, Cut, Copy, Paste. The LabVIEW project explorer already has all of these icons, I would just like to see an option for an easily customizable toolbar similar to the run-time menu.
When working with Arrays via VI Server (similar to a previous idea) it's challenging to get at a single element of the array.
My workaround involves setting only one array cell visible and then changing the index to move to different elements....
Why can't we read / write the current active index of the array via Property node?
Doing a long finite acquisition in DAQmx results in the manner shown below results in a all the data from the acquistion residing in a 2D array of waveforms that the user must rearrange to begin working with. Since a 2D array of waveforms is not really useful with any processing functions in LabVIEW, why not come up with an automatic way to get the datatype you want (a 1D array of waveforms with the new samples appended to the Y array of the appropriate channel.)
Give the user the ability to create a "waveform autoindexing tunnel" via a context menu option. This tunnel would automatically output the appended waveforms, 1 per channel. This could be done behind the scenes in the most memory efficient way possible so as to save users the headache of trying to modify the 2D array they currently get.
Zoomed in Images
As I had mentioned/asked here, it will be very much useful to have the above feature in future LV versions. It ll be similar to the one already present in NI's Digital Waveform Editor tool. When we have to navigate/play with more digital signal lines, the graph gets too much cramped to view the digital signals.
I wonder why NI has NOT implemented/given this feature till now, for the developers?