LabVIEW
type in string, then okay, then type in another string, then okay
hi, i have this programming code, i was wondering if someone can help me with..
i have a frontpanel..
when i reach a mode in my screen..which i know how to get there..
at the stage where i want to input a STRINGr..
i type in the immediate command a STRING.
then click okay
when i type in another command,
then i click okay
then i click get Telemetry to see a graph..
i can do it using the input of my keyboard and click okay, it works fine..
but when i try to automatically do this with labview, i am not seeing a graph...
is there something i did wrong?
my "Okay" button, should i set it as something else?
i have some graph for you to look at..
thanks in advance
Message Edited by krispiekream on 03-18-2008 11:57 AM
Please attach the real VI (or a simplified version that shows the behavior) instead of a bunch of disconnected pictures. It is impossible to troubleshoot LabVIEW in this manner.
(All I see are stacked sequences and local variables, both should be used sparingly.)
sorry, my vi is about 14mb large with lots of subvi..i dont know how to make an example that would work..
i can only think that my issue is somewhere in this picture below
Message Edited by krispiekream on 03-18-2008 12:39 PM
krispiekream wrote:
i can only think that my issue is somewhere in this picture below
There is no right or wrong mechanical action setting. It all depends how it ties into the rest of the program.
There is no way in the world that we can troubleshoot your problem without seeing some real code. None of your images are helpful.
You might was well attach a picture of your memory stick containing the program. 😄
DISCLAIMER: This answer in no way supports this type of question without code..... 
If you're trying to simulate pressing a button via code than maybe you need to use the Value (signalling) property node instead of writing a local variable.
I'm assuming you have event structures somewhere....
BUT, if your VI is 14MB (!) then maybe you should solve some other problems first.
If you DO decide to go with the Valie (Signalling) property node then you'll have a new problem : Race condition......
A better way would to re-pack whatever part of your code is reacting to the button press in a sub-VI with the required string as input. This way you retain data flow.
Shane.
If you're trying to simulate pressing a button via code than maybe you need to use the Value (signalling) property node instead of writing a local variable.
I'm assuming you have event structures somewhere....
BUT, if your VI is 14MB (!) then maybe you should solve some other problems first.
If you DO decide to go with the Valie (Signalling) property node then you'll have a new problem : Race condition......
A better way would to re-pack whatever part of your code is reacting to the button press in a sub-VI with the required string as input. This way you retain data flow.
Shane.
