LabVIEW for LEGO MINDSTORMS and LabVIEW for Education
Turn Off A Control?
create a local variable from the frontpanel or blockdigram boolean control.
This local can be written to.
Like my LabVIEW master always says rightclick and you can see.....
This only works when the boolean control has no mechanical latch function but then it would already fall back when read by the program. (latched booleans do on purpose not support local variables)
This local can be written to.
Like my LabVIEW master always says rightclick and you can see.....
This only works when the boolean control has no mechanical latch function but then it would already fall back when read by the program. (latched booleans do on purpose not support local variables)
Or ask in a forum.
It is documented ofcourse. But there is so much documentation that it takes months to just read it.
Jim Kring wrote a nice introduction 5cm thick at least and weghing 1610 gram.
But when you use LabVIEW professionally I advise you to follow a course instead. And try to follow the nuggets from Darren and the rest of the incrowd to understand better
http://zone.ni.com/devzone/cda/tut/p/id/5720 shows an overview of the first nuggets.
It is documented ofcourse. But there is so much documentation that it takes months to just read it.
Jim Kring wrote a nice introduction 5cm thick at least and weghing 1610 gram.
But when you use LabVIEW professionally I advise you to follow a course instead. And try to follow the nuggets from Darren and the rest of the incrowd to understand better
http://zone.ni.com/devzone/cda/tut/p/id/5720 shows an overview of the first nuggets.
Hi
The link to Jim's and Travis book is: http://www.labviewforeveryone.com/wiki/Main_Page
the second question is right. You always need a control or indicator, a local needs some storage defined.
But you don't need to show this on the frontpanel. From the diagram rightclick and hide control/indicator and only from the blockdiagram you can show it again.
It does not have to be connected to the connector pane and can even keep its info between calls but don't use that feature.
The link to Jim's and Travis book is: http://www.labviewforeveryone.com/wiki/Main_Page
the second question is right. You always need a control or indicator, a local needs some storage defined.
But you don't need to show this on the frontpanel. From the diagram rightclick and hide control/indicator and only from the blockdiagram you can show it again.
It does not have to be connected to the connector pane and can even keep its info between calls but don't use that feature.
No it will stay, but it is bad programming practice to use these features that are implied with the language.
If you do, you should document on the diagram that you are using the control this way.
There are better ways to check for something like first call.
This "feature" was invented when the "first call" function did not yet exist and people used such a control to keep track of the number of runs in their vi.
If you want a better way check the forum for functional globals or LV2 globals.
If you do, you should document on the diagram that you are using the control this way.
There are better ways to check for something like first call.
This "feature" was invented when the "first call" function did not yet exist and people used such a control to keep track of the number of runs in their vi.
If you want a better way check the forum for functional globals or LV2 globals.
