Normally 31999 (as real devices are supposed to use numbers between 1 and 32000 non included from what I know) but main limit will be number of IP sockets that can be handled by master in same time. With latest firmware in Duet, I think that limit is pretty high, at least 300 or 400. Someone may confirm exact limit ?
The question is how many maintained TCP connection (TP's and other dievices) can Netlinx connect to simultaneously. LIke "vincen" said how many sockets can be open at once and further more how many socket can be open at once w/o ill effect to system resources.
As Dirty Harry might say ? "A master?s got to know its limitations."
From TechNote 469:
Note: The maximum number of TCP/IP connections supported by a single master is 200 simultaneous TCP/IP connections.
And from the AMX programming class:
This includes connections to Netlinx Studio, Netlinx Diagnostics, Internet Inside Applications, URL List entries, and Ethernet devices such as the TPI4 and Modero panels.
Maybe the limit has been increased with DUET but I haven?t run across any documentation stating so.
I just did the Programming II online test (ran out of excuses) and one of the questions was how many IP connections can be made simultaneously. Failing to find this information in the manuals, I wrote a program and on my non-Duet NI700 it failed at connection 201.
We have a system that has 40 or so TPI-4s, we have 7 remote masters and we have found that the NI-3100 will not allow over 200 TCP connections. The big problem is that each TPI takes 4 connections and the same for the remotes. We have found that with the ME-260/64 it will crash with older firmware, newer it will slow down and disconnect all devices. With a 3100 it will stop allowing any more connections into the system. So bottom line is do a "show max buffers" if the TCP connections on the IP mgr list is over 190 you are in big trouble. AMX has not given any good data on this and it would appear that they know about it but are not sure how to fix it. We have tried this with duet and not.
...we have found that the NI-3100 will not allow over 200 TCP connections... AMX has not given any good data on this and it would appear that they know about it but are not sure how to fix it.
Scroll up to post #6 in this thread. AMX has documented the 200 simultaneous connection limit in both Tech Notes and in programming class.
AMX has not given any good data on this and it would appear that they know about it but are not sure how to fix it. We have tried this with duet and not.
You write as if it is a bug that needs fixing. I see it as a feature, but not a nice one.
You could install an additional NI700 and it will give you an extra 196 IP channels at minimal cost and only a very small change in the code. I think.
Joe Hebert wrote:
Scroll up to post #6 in this thread. AMX has documented the 200 simultaneous connection limit in both Tech Notes and in programming class.
And that number refers to all TCP/IP sockets not just TPs or DMS but any IP connection to equipment, RSS feeds, Email and basically anything that uses an IP_CLIENT_OPEN socket connection.
The connection manager can only manage 200 sockets and that's it.
We have a system that has 40 or so TPI-4s, we have 7 remote masters and we have found that the NI-3100 will not allow over 200 TCP connections.
On re-reading your post I see that you have 7 remote masters. Each one could give you an additional 196(ish) IP connections. You don't need to originate all of the IP connections to the TPI4s at your central controller. I believe that there is no performance implication in "hosting" the TPI4s remotely.
The problem I have is that they tell you it is 200 connections so one thinks that would be 200 devices right?? What really is going on is that each TPI takes 4 connection so the limit really is about 50 devices. I am not the programmer so not sure how to make the remote master take the TPI off the main master, if I take a remote TPI off line the number of connections does not go down, when I take a remote master off line the number goes down by 4.
Comments
Vinc
192.168.x.1 -> 192.168.x.254
The question is how many maintained TCP connection (TP's and other dievices) can Netlinx connect to simultaneously. LIke "vincen" said how many sockets can be open at once and further more how many socket can be open at once w/o ill effect to system resources.
Fully wrong as your panels don't need to be in same subnet, I connect some panels to remote masters through Internet
Vinc
From TechNote 469: And from the AMX programming class: Maybe the limit has been increased with DUET but I haven?t run across any documentation stating so.
I'd hate to be the coder who has to do it, debugging would be a nightmare and I'll bet the processors would get pretty bogged down.
We have a system that has 40 or so TPI-4s, we have 7 remote masters and we have found that the NI-3100 will not allow over 200 TCP connections. The big problem is that each TPI takes 4 connections and the same for the remotes. We have found that with the ME-260/64 it will crash with older firmware, newer it will slow down and disconnect all devices. With a 3100 it will stop allowing any more connections into the system. So bottom line is do a "show max buffers" if the TCP connections on the IP mgr list is over 190 you are in big trouble. AMX has not given any good data on this and it would appear that they know about it but are not sure how to fix it. We have tried this with duet and not.
You write as if it is a bug that needs fixing. I see it as a feature, but not a nice one.
You could install an additional NI700 and it will give you an extra 196 IP channels at minimal cost and only a very small change in the code. I think.
The connection manager can only manage 200 sockets and that's it.
On re-reading your post I see that you have 7 remote masters. Each one could give you an additional 196(ish) IP connections. You don't need to originate all of the IP connections to the TPI4s at your central controller. I believe that there is no performance implication in "hosting" the TPI4s remotely.
The problem I have is that they tell you it is 200 connections so one thinks that would be 200 devices right?? What really is going on is that each TPI takes 4 connection so the limit really is about 50 devices. I am not the programmer so not sure how to make the remote master take the TPI off the main master, if I take a remote TPI off line the number of connections does not go down, when I take a remote master off line the number goes down by 4.