In the Bundle and Unbundle Functions ones the input cluster wire is connected the function automatically bundle/unbundle the all the element.
we cant select the elements ,there is no drable option.
but in the document shows the dragable option.
if NI adds the Fuctional Global Variable (FGV) tempalte in design pateren tempates in hte New window, it is easy to create FGV VI's.
and Helps the programmers, no need to create from the begining of VI.
Even it is usefull for CLD Exam also.
A feedback node is like a shift register. Both elements can retain the past N values. For a shift register you can access the entire internal memory by dragging down the left side terminals. This is cumbersome if you just want a circular buffer.
A feedback node is much more elegant for this task, however there isn't a way to access that memory. If you could, you would make it extremely easy to make a simple circular buffer (oldest element is discarded, newest element is put onto the array). It would be very useful, especially because the feedback node is polymorphic, and can take any data type.
The polymorphic function: Continuous Random.vi has a different behavior than expected on the 'a' input for the Weibull distribution.
Referring to the wikipedia article https://en.wikipedia.org/wiki/Weibull_distribution , describing the scale and shape parameters, 'a' doesn't match up to lambda. But b does match up to k (also known as beta).
Usually, beta (k in the wikipedia article) is the shape parameter, and alpha (lambda in the wikipedia article) is the scale parameter. But alpha (or lambda) doesn't match up to the 'a' input, even though 'a' is described as the scale parameter in the LabVIEW documentation.
I did some figuring out and it appears that I can use the LabVIEW Weibull function if I calculate a from alpha and beta using the following equation.
a = exp( beta * ln(1/alpha) )
alpha = 1 / (a^(1/beta))
Since the behavior on other LabVIEW Weibull functions is not the same as described in what I can find as common literature, I have resorted to making some of my own Weibull functions in LabVIEW. If they were better documented, then I could have used them. Now that I figured out how to calculate 'a' from alpha and beta, I think I can also use the other Weibull functions in LabVIEW.
If the Label Position is changed from default position there should be the option to retain the position, because finding the label in a very huge block diagram code is difficult as label is the only identification for the item
I would like the option of seeing the order number of controls in a cluster while I'm editing the FP, not just when I'm ordering the control itself. Select> visible items> control order. Like this:
Sometimes I only need access to one or only a few controls in a cluster. If I know the ref array index/order number this would be a lot easier.
Hello to everyone,
here is one more idea, which I'd like to propose.
As for me, it would be useful to have the following: when all components (functions, wires, subVIs, etc.) are selected on the block diagram (like, after ctrl+A), operator could do right-click, and in the menu would appear menu item "Disable everything". After it, all the code could be placed into Disable structure.
Of course, I can add Disable structure to block diagram manually, and cover whatever I want, but with right-click menu it would be much faster.
Also, it can be modified to disable only selected items - then each of them can be placed into separate Disable structure, and, for example, additionaly in the enabled case of Disable structure, corresponding wires will be connected. Sometimes it is needed for testing - just to disable couple functions, and test subVI. Or to disable subVI fully (it's faster, then disable place, where it is called. Especially, if subVI is used in many places).
It will not make debugging difficult, because anyway Disabled structures are used; such functionallity can just make life a little bit easier...
The only way I know of getting the call chain of a VI is with the Call Chain primitive, which only works on *this* VI (the VI calling the primitive). It would be nice to expose that as a VI server property, so we could get the call chain of any VI by reference.
I started to use Labview Web Service and I have a couple of suggestions
In the Startup Vis you are able to monitor the status of the web service, but you are not able to close it. It says that labview will automatically close the Labview Web Service when closing a standalone exe, but there are some schenarios where you might want to close programatically the web service. e.g.:
- When building a standalone exe and you want to be able to close the service programatically.
As soon as the web service receives a URI that doesn't have a Web Resource, it throws an error without been able to handle it. Been able to handle the error could be beneficial when trying to make a dynamic routing system e.g. Many web frameworks.
In the For Loop,While Loop we can see the Loop Iteration and Loop Condition properties.
but right click and open object properties. in this Label Visible Check box Grayed condition (not able to enable)
NI need to Enable this to write some Lable or commect for the Loop Condition.
same like Addition and Subtraction Functions.
Notice that this does *not* trigger the value change event. However, editing the value and then pressing enter triggers the ValueChange event.
Ahh, but you point out "Well, in that case, the value *did* actually change, so that's why the event fired." And you're right.
But then try this:
Seems super minor, I know. But I found myself in a situation where I want to trigger an event if a user hits "enter" in a numeric field, regardless of whether the value changed or not (e.g. it should be able to reassert the current value). Yes, the obvious solution is to handle the enter key press separately, but that means when the enter is used to assert a different value, I end up with *two* events.
This idea directly comes from this issue : http://forums.ni.com/t5/LabVIEW/Issue-when-using-S
More and more devices are equipped with embedded webservers. And some of them require more controls HTTP protocol capabilities.
It would be nice to give the access to these VIs diagrams or to give more options set header fields !
I am Facing the problem when VIs Having the visual Images in Front panel for Operator Instruction screens.
( such a connecting the Cables, Visual Inspection of Components etc)
If you use these type of visual images the total Executable size increasing huge (my case 150MB beacuse of many products and many Images,images are copies from the *.Jpeg or .png Images.if the LabVIEW can find these image copied on the front panel and able to compress . we can reduce the EXE file size almost 30% of the total size and also taking more time to build and compile
NI have to find is there any technique(now a days many image compression models are avilable) , first compile the code and later add images to front panel once compile.
When deciding to replace several occurences of an enum constant by the corresponding strings in a diagram (say, in a state machine), there currently is no simple way.
From a logical point of view, it should be possible to select the enum constant, right-click and choose Replace >> String constant and get a string constant displaying the selected denomination of the enum constant. Unfortunately, currently, one only gets an empty string:
The shame is that if you had this enum connected to a Case Structure for instance, the item names are preserved:
while I would have liked to get:
my suggestion (part 1): Allow replacing an enum constant by a string constant containing its item name.
A natural extension of this suggestion would be, in case this enum is a typedef, to be able to perform a similar action in the Search Results window, where, after finding all copies of the typedef constants, the Replace All button would perform the action above on each individual copy:
Suggestion Part 2: Allow selecting all copies of a typedef refnum constant within a diagram and replace them with string constants containing their item names.