01-21-2016 09:30 AM
Checking your previous post I saw that you are using a programmatic way to launch your VI, I am guesing that you took it from here:
http://digital.ni.com/public.nsf/allkb/A7DBA869C000B5AE862570B2007C4170
but from the documentation I am seeing a little difference, you are using the error cluster and the stop to handle the while loop stop condition, so have you checked if you have any error at the start up, becuase if you do the while wont execute and at the endo your VI won't start up.
Also please check on the troubleshooting steps that the documentation indicates, it may be that some situation pointed on the document is the reason of the issue you are having.
Here is another doc, that may interest you and help you:
http://digital.ni.com/public.nsf/allkb/F64D92E0BCA34162862573BD0072F807
Regards
M
01-21-2016 09:45 AM
The error cluster coming out of the Run VI call was not showing an error when the VI was not starting. So the loop did not terminate and the VI was not running after boot.
Just executing a blank VI in the startup rtexe cures the issue. The run VI call doesn't show an error and my top-level VI starts executing. The loop also doesn't terminate in this situation.
I've since added additional conditions to stop the loop which appear to be working well:
1. An error in the VI server between the host machine and the remote machine.
2. A local stop (Debugging)
3. The remote VI stops (Error or normally) detected using exec.state != Run Top Level
4. A stop notifier tells the loop to stop the remote VI
5. The stop notifier is destroyed
Thanks,
01-22-2016 08:19 AM
Hi,
Great to hear that is working after the changes that you did (I did not understood if you have more questions or you are saying that for now its wworking)
regards
M
01-22-2016 08:41 AM
Hopefully someone from NI will see this and investigate to see if there's a bug behind this issue. The workaround is easy enough...
Thanks,
XL600