11-22-2004 09:48 AM
11-22-2004 10:00 AM
11-23-2004 05:43 AM
11-23-2004 09:06 AM
@Jim Kring wrote:
This is a known issue. A while back, I posted the solution here.
Good luck,
Jim
11-22-2006 04:38 PM
Hi, does any one have an update on that? I'm having the same problem, I'd like to know the number of sockets that are open on an RT (not running Windows but LabVIEW RT with Pharlap). Our system is quite critical - it controls trains. I use to get the error 11 before I add Max_Sockets=64. I want to be sure that this won't happen anymore, that's why I'd like to keep an eye on the number of socket open.
Thanks,
Patrick.
11-27-2006 05:37 PM
Hi Patrick,
I have looked into this, and there does not appear to be a method of
determining the total number of TCP open sockets on the Real Time Target.
I have sifted through the TCP VI's as well as property nodes in search of a
method of doing this, but there does not seem to be anything. I also
searched for a TCP scanner that can be used on the Pharlap OS, and there does
not seem to be anything along those lines either. There may be an indirect
method of accomplishing this, but I am not aware of such a method right now.
My best recommendation is to set your Max_Sockets = 100, this should give you
approximately 85 connections. I believe there are usually approximately
15-20 connections open at a given time.
Please do not hesitate to let me know if there is anything I can help you
with. Best of luck on your application, and have a great day!!