wannabecontroller
-
Posts
16 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Gallery
Posts posted by wannabecontroller
-
-
A subvi is nothing more then a function
so because the blinking LED is wrapped into a function labview falls on its face
The reason I am
annoyed and don’t understand what the problem is , to my understanding was suppose to be able to run parallel functions with ease
in your post above you mentioned that as long as they are not wired together they should run independently.
Now you say they are dependent on execution.
That is not parallel that is concurrent
Loop1 shouldn’t care what loop 2 is doing.
So essentially creating a sub vi that has a continuous task is useless you are telling me because there is no way to execute it? Is that correct
I thought the whole point of being a good developer was to build re-usable code in the form of functions that can be used over and over. Is that not the case for continuous functions that never complete like wave form generator or the like
thanks for your reply
-
This is what i am doing. Its just a simple state machine example project
The second while loop is calling a sub VI that does nothing but blink an LED on the front panel to show the state machine did initialize
Its more for looks and practice then anything.
It will not execute. I know the VI runs fine on its own. Its been tested
The state machine also runs fine with no issue until i try and make the LED blink
I know this is dumb but i really appreciate the help
Loop 1 in the Main VI
This is the Sub VI in Loop 2, just for an LED blink
This is Loop 2 in the main VI
The Sub VI for blinking LED is the one pictured here
-
tried it
still wont run
-
1 minute ago, JKSH said:
Make sure you have a Wait node in both loops: https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P82BSAS&l=en-AU
Without a Wait node, one loop will consume 100% of a CPU core. This could be why your 2nd loop is unable to run.
trying now, thank you so much for your idea
-
can anyone help?
i am loosing my mind over this
No matter what i do, two totally independent while loops will not execute
they share only one "shared variable" I can not even comprehend why something so simple is turning out to be so difficult
-
I tried to while loops with no wires connected what so ever. They still will not execute independently
Putting a probe on the second while loop still says not executed.
The only thing between them is a single shared variable of type bool
Frustrated that after 2 days i cant get two while loops to execute.
-
Thanks
Much Obliged
Ill give that a whirl.
I have a few small functions that do some simply things like blink an LED for a status indicator. I cant put them in the main while loop because they onbiously never complete being continuous functions.
Aka the LED never stops blinking so the while loop never iterates. I wanted to put it in its own loop is what i was up to.
-
Hello
I have two independent while loops i want to run in one VI
Both loops run continuous tasks such as running a wave form generator or similar
The second one wont start because the first has not "completed"
Is there a way to have two while loops run independent in one VI?
Thanks
-
Thanks very much for your reply.
I got it to work but cant even remember what i did.
I will try and track it down and post for others my mistakes
-
Thank you both, the first post is valuable the second post is what did it
-
I am having a difficult time with while loops
For example
I have a task in a while loop and the condition for the while loop to stop is just a button.
The while loop will never loop at my stop button because the SUB VI inside of the while loop has not completed.
So for example, say i want to do something simple like a continuous task inside of my while loop
Like Run a sine wave generator.
The while loop will never iterate because it is waiting for the sine wave generator sub VI to "complete" or return so to speak
So what signifies a function has returned to iterate the while loop if its a continuous task.
I need the while loop to iterate because it will not look at my stop condition until it does. When i probe my stop condition all it does is says not executed and i assume its because its waiting for the "continuous task" to complete"
-
Having an issue trying to connect a reference to a sub VI.
I have creaed a control refnum on the front panel of the sub VI and changed its properties to type bool
Then connected the control ref to a front panel terminal.
When i try and connect the reference from the main to the sub vi i am getting an error that says wire conflict class.
-
So i have taken some items from an example and of course they work just fine
When i try and recreate them myself they dont.... naturally
I have created a bool type refnum
However when i create a property node and select value on my version of it, it gives me "value" as a variant data type
In the example the property node value has type bool so it works fine
I dont understand why i cant change it bool type from variant
Any help?
Thanks
-
I find this hard to believe. I am unable to find any documentation on the web including youtube on what the heck a refnum is
Can someone please point me towards some documentation or perhaps a quick explanation?
Thanks in advance
-
I cant seem to find an example of this.
I have seen in several programs where a type def has multiple things included in it
Perhaps a numeric constant and a string constant
How can i create this?
Thanks
two while loops one VI
in LabVIEW General
Posted
Thank you for your continued support
Just for kicks i have taken out the SUB VI and just recreated the stuff in the subVI in loop 2.
It runs now
However i have created a new mess that is now causing issue
I have tried to add a few states to the state machine. Of course i broke it.
I will have to post the VI's some how. It is clear i am not understanding this execution.
The state machine works fine with one function. I did not add any new functions just the cases for them and now im back to my initialization loop not running.