Ken Roach said:
...the PanelView Plus 6 (v6-v6.10) as well as the PanelView Plus 7 Standard terminals support only a single controller...
Ken,
I'm not saying that one should or should not do it, but it is possible, and supported, to connect multiple controllers to the PVP 6 & 7 terminals. However, determining how many is tricky. The following is some information on what's known as the RSLinx Enterprise Logix Data Provider. As it implies, it is more related to RSLinx Enterprise's interaction with Logix controllers, of which the MicroLogix family are of course not. It explains the old and new versions of the above and the effects on performance when using Logix controllers and their memory intensive User Data Types (UDT)...
624292 - PanelView Plus terminals running 6.10 or newer firmware exhibit slow application startup, slow runtime performance or RSLinx Enterprise errors
Access Level: Everyone
There are, as explained, a number of factors which can prohibit the number of controllers that may be used with one terminal. The size of the application and the amount of memory it uses up, or more importantly, leaves for other processes. The amount of tag referencing to each controller. The size and complexity of any referenced UDTs being used in the Logix controllers. The network used and its potential complexity and latency.
A data concentrator is a good alternative when the multiple controllers to one terminal setup is struggling. Exchange the multiple controller data with one controller, or Server, and then just assign one shortcut from there to the terminal.
roxusa,
But the MicroLogix controllers do not support UDTs. So that is not so much an issue here. What can be an issue is the number of available CIP connections. Each MicroLogix 1400 supports up to 16 incoming and 16 outgoing connections. You should always leave one connection spare for you to go online with the controller. So that really leaves 15. If the only device communicating with each controller is the one PanelView Plus terminal, then the terminal may use up to 5 connections per controller. So that now leaves 10 connections.
This is fine if each controller is only communicating with the one terminal. But, if the MicroLogix controllers were also communicating with other devices, such as each other using, for instance, messaging then those 10 connections might be used up quite quickly. It all depends on your final data exchange outlay.
It would be best to define "several" controllers. You could mean 5, you could mean 20?
If, for instance, each MicroLogix were also to be messaging with each of the other controllers, and there are more than 10, then it would be a different story.
Of course, I am hypothesizing your intended solution. But I'm just giving an example of something to consider or watch out for here.
There are no limits to the number of RSLinx Enterprise shortcuts you can add in an application. This, of course, does not mean that there are no practical limits to the number of devices you should add. Also, the number of displays, HMI tags and tag references you can create will limit a user, somewhat, but they could go wild if they wanted to. As I mentioned, lots of factors determine the final performance on a larger system.
Regards,
George