Why does that entire thread goes to sleep when we put a wait function in time critical loop?

Question

why does that entire thread goes to sleep when we put a wait function in time critical loop but not when it is not time critical

Answer 1

Norbert B wrote:
Ujjval,
in a RT system, priorities have (in general) increased effect on the execution of the application.
It is recommended that you only have a single task in your RT program at "time critical". If you have two task "time critical" (that means you are running into issues caused by your quoted "feature"), you have a flaw in your application architecture.
Since LV 7.1, it is recommended to work with Timed Loops in order to prioritize tasks on a RT system. Timed Loops are executed on priorities between "time critical" and "above normal". Each Timed Loop will execute its content in a single thread in order to keep a good overview of the timing (like finished late [i-1]). Using those structures (and according settings) in a reasoned manner will prevent your RT system to run into priority issues.
Ujjval Shah wrote:
[...]also i would really appreciate if i can get more documentations regarding how LV creates threads and assigns subvis to them[...]
You will have a real hard time to go into this very deep. This is the feature of LV: you can just use multithreading (multicores) without the needed knowledge of scheduling and load balancing. This makes LV programming in general very easy in comparison to e.g. ANSI C (in regard of multithreading). So creation of threads, distribution of tasks to the threads are abstracted and most often not visible to the programmer.
There are some switches and levers you can "play around" in order to make LV to behave differently in this matter. But this most often requires  deep LV knowledge and cannot be explained in a simple posting.....
hope this helps,
Norbert 
Amen to that!
The question can not be fully answered without digging into the internals of the OS LV is run on because LV works with the OS and lets it do the scheduling.
Yes that note applies to pre- LV 7 RT. When run under RT the ONE Time Critical loop was guarenteed to stay determinisitic.
Since then the Timed Loop was introduced that allowed multiple levels of priority and later allowed us to assign which CPU the code would run on.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction