01-19-2006 03:57 PM
01-20-2006 06:30 PM
Is there only one client accessing remote front panel or do other users have access to them? The Knowledgebase, How Do I Control the Number of Clients Remotely Connected To My VI? might be a good reference for you.
Let me know if this doesn't help.
01-27-2006 05:14 PM
I've been away for awhile. There is only one user, sometimes thru a wi-fi router. It's a troubling feature for our customer.
lew
02-01-2006 01:59 PM
02-01-2006 02:12 PM
Thanks,
I'll give this a try and see if it tells us more about what's happening.
lew
12-13-2007 03:39 PM
I'm having a similar headache with my Real-Time program. My users want access to the front panels of multiple VIs running at the same time on the real-time station (from a single host). If they open and close them at will, eventually they run out of licenses. I assume this is due to the fact that they have not released control before closing (which I do and don't run into the problem). Is it possible to programmatically release licenses to VIs that are not being actively viewed? There is no remote panel connection manager in the real-time OS.
Dan
12-14-2007 04:10 PM
12-14-2007 04:13 PM
Perfect.
This is exactly what I am looking for. I will tailor this to my needs. Thanks!
Dan
06-15-2009 02:01 PM
We are facing a similar problem using a CompactRIO in this configuration:
- PC and cRIO configured with static IP addresses
- cRIO connected directly using a crossover cable to the PC (to be sure that only one physical client accesses the cRIO at a time)
- Labview 8.6.1, NI-RIO 3.1.1 with scan engine
We are able to access our remote front panel using Internet Explorer from the PC during 1-3 days. After that period, when we open our front panel using IE, a message states that the number of open remote panels exceeds the number of licences. But nobody is actually connected to the system.
We have tried the "Close Remote Panel Connections.vi" without success as well (using "c:\ni-rt\startup\startup.rtexe\MainPanel.vi" as the VI path for the "Open VI Reference" function).
The only workaround working for us is to reboot or power-cycle the CompactRIO, which is not acceptable in a production environment.
Any idea ?
Best regards,
Arnaud Faucher
06-16-2009 10:03 AM