1 Controller 800M for 2 800xA System
Hi,
Is it possible for a 800M controller to have OPCDA subscription from 2 800xA System? (Consider the 2 system has similar software/rollup version).
it has been mentioned in Compact Control Builder manual that "a controller can handle up to 3 OPC Server" what is that mean?
I have a customer that expect to have 2 system of 800xA for their power plant. in this case 2 identical system that running at the same time.
Because they don't want to depend on a redundant server(2oo3) for the whole power plant.
BR
Hansen
Is it possible for a 800M controller to have OPCDA subscription from 2 800xA System? (Consider the 2 system has similar software/rollup version).
it has been mentioned in Compact Control Builder manual that "a controller can handle up to 3 OPC Server" what is that mean?
I have a customer that expect to have 2 system of 800xA for their power plant. in this case 2 identical system that running at the same time.
Because they don't want to depend on a redundant server(2oo3) for the whole power plant.
BR
Hansen
Asked 1 year ago
Answers
0
Hi,
I think your customer doesn't understand the product - having said that they have concerns over availability and you need to consider that.
I have an 800xA system, and it is distributed across two separate plants - so i built two separate OPC server pairs - therefore 4 OPC servers - 2 in each plant.
So each controller has 4 OPC servers pulling data.
you mention 2oo3 - well thats the Aspect system, not the OPC server system.
The ABB 800xA ssytem is extremely reliable, resilient and highly available if you keep it clean, cool and repair faults as they happen.
Server platforms with redundant supplies, RAID drives with hot spares provide continuous operation.
Reboot windows servers on a regular basis - and restart the OPC service occasionally to check redundancy and flush memory.
I have servers that have run for over 10 years - the only failure being hard drives.
I think your customer doesn't understand the product - having said that they have concerns over availability and you need to consider that.
I have an 800xA system, and it is distributed across two separate plants - so i built two separate OPC server pairs - therefore 4 OPC servers - 2 in each plant.
So each controller has 4 OPC servers pulling data.
you mention 2oo3 - well thats the Aspect system, not the OPC server system.
The ABB 800xA ssytem is extremely reliable, resilient and highly available if you keep it clean, cool and repair faults as they happen.
Server platforms with redundant supplies, RAID drives with hot spares provide continuous operation.
Reboot windows servers on a regular basis - and restart the OPC service occasionally to check redundancy and flush memory.
I have servers that have run for over 10 years - the only failure being hard drives.
Answered 1 year ago
0
In theory, yes.
In practise, no.
The AC 800M OPC server is dependent on receiving a memory map from the Control Builder M after it has downloaded to the AC 800M controller. In System 800xA, the FSD service is used for this distribution. FSD only work within one (1) system.
Having two separate systems, you must manually transfer the needed information from system A to system B after you download to the controller from system A, otherwise the system B would be blindfolded. There exist no official procedure how transfer the required information across systems.
During Online Upgrade of AC 800M, both the old and the new upgraded system will momentarily be using the same memory map. There is a restriction, the old system must not download to the controller.
I believe you should take hints from the first answer to your question.
About how many AC 800M OPC servers you can connect to an AC 800M controller is more like "how many eggs can you put in a box?". The answer is, it depends on the size of the eggs and the box and how dense you "pack" them. There is also likely some eggs that does not fit in a box. What I mean to say, it boils down to how much CPU load you have in your controller, how many concurrent MMS connections does it needs to handle and at what frequency those MMS transactions arrives at. A PM891 can handle more than a PM851...
In practise, no.
The AC 800M OPC server is dependent on receiving a memory map from the Control Builder M after it has downloaded to the AC 800M controller. In System 800xA, the FSD service is used for this distribution. FSD only work within one (1) system.
Having two separate systems, you must manually transfer the needed information from system A to system B after you download to the controller from system A, otherwise the system B would be blindfolded. There exist no official procedure how transfer the required information across systems.
During Online Upgrade of AC 800M, both the old and the new upgraded system will momentarily be using the same memory map. There is a restriction, the old system must not download to the controller.
I believe you should take hints from the first answer to your question.
About how many AC 800M OPC servers you can connect to an AC 800M controller is more like "how many eggs can you put in a box?". The answer is, it depends on the size of the eggs and the box and how dense you "pack" them. There is also likely some eggs that does not fit in a box. What I mean to say, it boils down to how much CPU load you have in your controller, how many concurrent MMS connections does it needs to handle and at what frequency those MMS transactions arrives at. A PM891 can handle more than a PM851...
0
Hi Stefan, thank you for explanation.
in the case if compact control builder is used for the application of controller and the map of project stored in the common server (Application server) will this method allow 2 OPC Server from 2 different system to pulling data at the same time?
in the case if compact control builder is used for the application of controller and the map of project stored in the common server (Application server) will this method allow 2 OPC Server from 2 different system to pulling data at the same time?
Answered 1 year ago
0
In theory, yes.
In practise, no.
The AC 800M OPC server need "a map of the terrain" of the applications running in the controller. This map is generated by Control Builder M during download to the controller. In 800xA, the FSD service is used to distribute this map to dependents (from Control Builder M to AC 800M OPC server).
FSD only work within one (1) system.
If system A and B were to use the same AC 800M OPC server, the transfer of "maps" between A and B must be manually made after each download to the controller(s) - there exist no official documented routine for this.
The simultaneous use of same map is taking place momentarily during online upgrade of AC 800M, but then its is clearly documented that no download must be made (as it would blindfold the other system).
The maximum number of OPC servers per controller is more a "how many eggs can you fit in a box" question. It depends how large the eggs are and how dense you pack them. You can probably find an egg does not even fit in a regular box.
In practise, no.
The AC 800M OPC server need "a map of the terrain" of the applications running in the controller. This map is generated by Control Builder M during download to the controller. In 800xA, the FSD service is used to distribute this map to dependents (from Control Builder M to AC 800M OPC server).
FSD only work within one (1) system.
If system A and B were to use the same AC 800M OPC server, the transfer of "maps" between A and B must be manually made after each download to the controller(s) - there exist no official documented routine for this.
The simultaneous use of same map is taking place momentarily during online upgrade of AC 800M, but then its is clearly documented that no download must be made (as it would blindfold the other system).
The maximum number of OPC servers per controller is more a "how many eggs can you fit in a box" question. It depends how large the eggs are and how dense you pack them. You can probably find an egg does not even fit in a regular box.
1
This one of those cases where you need to educate your customer about how redundancy works in an 800xA system. A standard 800xA system is a fully redundant solution that meets your potential customers needs. Two independent systems pretending to be redundant is not a solution, and probably cannot even get regulatory approval.
If your customer doesn't want to listen then walk away. Supplying a badly engineered "solution" that doesn't work will damage your reputation and bottom line far more than not getting the sale.
If your customer doesn't want to listen then walk away. Supplying a badly engineered "solution" that doesn't work will damage your reputation and bottom line far more than not getting the sale.
Answered 1 year ago
Add new comment