I am troubleshooting a problem between LabView and an instrument driver. From the NI Spy, we see several RM session opened and several VI session opened to communicate to the instrument driver. Anyhow, what troubles us is that, intermittently, NI Spy would capture a call to viOpenDefaultRM() function and there is no corresponding viClose(). Also, assuming if everything opened and closed properly, I won't expect the value of the RM session handle and the value of the VI session handle would change, but, intermittently, the handle value would change and is going up.
So, to further troubleshoot, I am wondering is there a tool that I can monitor, in real time, shows me a list of RM session opened and list of VI session opened.
You are not able to understand the existing test program?
If what you describe is true, then whoever wrote the test program did a poor job.
Yeah, we are using LabView, calling third party, vendor drive. So, we don't have too much say on thier stuff. What we trying to determine what we see should cause alarm or not
I am not sure I understand what you mean.
Did you pay a third party to write the software?
I know of no instrument that requires repeated opening and closing of sessions to communicate.
My colleagues here use a test executive that is based on Python a scripting language. It does NOT do multiple opens and closes.