Leaderboard

Welcome back!

Release the Notifier in your “stop” event case in the top loop; that will cause an error in the “wait on notification" in the bottom loop, causing it to shutdown (since the error is wired to the stop of the loop). That was the use case of the original post; to start and stop listening on FIFO for incoming data. I use secondary loops like this for things I have to wait on, such as a TCP connection. If instead you want a second loop to execute commands from the primary loop, then you are better off using a queue. But you can still use the destruction of the queue in the primary loop to trigger shutdown of the secondary.

Hello I have just passed the architect exam, and I just wanted to say that I have learned a lot from the posts on this site. Many thanks all. A special thanks to the lava member FAB to came over to the UK from the US to do the advanced architectures course at NI and was by far the best lecturer that I have had there.