800xA Generic OPC Server Node Limitations?
Hi... I have an 800xA v6.0.3 system; four nodes: two combined Aspect/Harmony Connect, two client nodes. I'd like to use the Generic OPC Server object to interface to third party OPC server communicating to a BACNET gateway. My intent is to collect about a dozen signals for monitoring purposes, not control.
According to the 800xA System Technical Guide, no other connectivity services can be combined in the same node with Harmony Connect. Does this apply to the Generic OPC Server object, or just PLC Connect (which I'm not planning on using)?
The 800xA Configuration manual, Section 2, Data Access states under Hardware Setup that "800xA does not impose any restrictions on which machine the third party OPC server is to be installed. It can be installed directly on the 800xA connectivity server or a separate dedicated server." Does this imply that it cannot be installed on a client node?
thanks..
According to the 800xA System Technical Guide, no other connectivity services can be combined in the same node with Harmony Connect. Does this apply to the Generic OPC Server object, or just PLC Connect (which I'm not planning on using)?
The 800xA Configuration manual, Section 2, Data Access states under Hardware Setup that "800xA does not impose any restrictions on which machine the third party OPC server is to be installed. It can be installed directly on the 800xA connectivity server or a separate dedicated server." Does this imply that it cannot be installed on a client node?
thanks..
Asked 1 month ago
Answers
2
This here is an excellent example of why systems should run on Virtual Servers. Just spin up another VM copy - you'll be done in 30 mins.
Anyway, As a rule of thumb, OPC servers will *usually* all live happily on the same node - right up until the point where they don't. Some combinations are known to cause problems - like mixing AC800M and Advant Master. This problem is much more common on "older" connectivity types like Master, MOD and Harmony. So generally it's "safer" not to mix connectivity server types on the same node.
The "Generic OPC Server" however interface is typically pretty good and doesn't cause problems - because really it's just an OPC Client wrapper running over the top of someone else's third party OPC server. There are a couple of choices in your case that should work just fine ...
Anyway, As a rule of thumb, OPC servers will *usually* all live happily on the same node - right up until the point where they don't. Some combinations are known to cause problems - like mixing AC800M and Advant Master. This problem is much more common on "older" connectivity types like Master, MOD and Harmony. So generally it's "safer" not to mix connectivity server types on the same node.
The "Generic OPC Server" however interface is typically pretty good and doesn't cause problems - because really it's just an OPC Client wrapper running over the top of someone else's third party OPC server. There are a couple of choices in your case that should work just fine ...
- Run the 3rd Party OPC client on an external machine that is inside the ABB domain, but not a member of the 800xA system. Install the "Generic OPC connect" network on your existing AS/CS Server(s) and connect to the remote OPC Server.
- Install VMware Workstation somewhere and spin up a new server on that. Install everything on the new VM.
Answered 1 month ago
2
Hi,
In my humble opinion you'll be fine using Generic OPC, for this small number of monitoring signals.
Having that said I'm not familiar with Harmony Connect and the demands nor limitations of the third party supplier. Using AC800M Connectivity I found no problems of using Generic OPC to access data from a third party OPC Server.
In earlier versions (SV5) there where recommendations not to install the third party OPC on a "normal" Connectivity Server, but I think that was mainly in respect of compability, installation and performance issues.
If you set up a OPC Service, the provider can be local or remote. The choice of remote OPC will put emphasis on carving out the correct security access settings (DCOM) for your system.
Remember that there can be only one Generic OPC Server Network per system (in the Control Structure).
Using a client node is possible, but not quite suitable from a system point of view. Operator stations may be up or down, restarted more often than server nodes etc, which might lead to loss of data. I recommend to use a server node for this functionality.
Regards
In my humble opinion you'll be fine using Generic OPC, for this small number of monitoring signals.
Having that said I'm not familiar with Harmony Connect and the demands nor limitations of the third party supplier. Using AC800M Connectivity I found no problems of using Generic OPC to access data from a third party OPC Server.
In earlier versions (SV5) there where recommendations not to install the third party OPC on a "normal" Connectivity Server, but I think that was mainly in respect of compability, installation and performance issues.
If you set up a OPC Service, the provider can be local or remote. The choice of remote OPC will put emphasis on carving out the correct security access settings (DCOM) for your system.
Remember that there can be only one Generic OPC Server Network per system (in the Control Structure).
Using a client node is possible, but not quite suitable from a system point of view. Operator stations may be up or down, restarted more often than server nodes etc, which might lead to loss of data. I recommend to use a server node for this functionality.
Regards
Answered 1 month ago
0
I appreciate the answers.
Rob - we've discussed virtualization here, but have gotten in a good routine of physical installation and just don't have people with enough spare time to explore virtualizing systems yet. I wish we could. I assume your second bullet item suggestion was to virtualize a new 800xA connectivity server node in the physical system?
BEAB - thanks for point about only being allowed one Generic OPC Server Network in a system. I wasn't aware of that!
Rob - we've discussed virtualization here, but have gotten in a good routine of physical installation and just don't have people with enough spare time to explore virtualizing systems yet. I wish we could. I assume your second bullet item suggestion was to virtualize a new 800xA connectivity server node in the physical system?
BEAB - thanks for point about only being allowed one Generic OPC Server Network in a system. I wasn't aware of that!
Answered 1 month ago
1
I suspect Harmony can key their feature to block other roles. System Installer might not accept adding what you want.
Overriding the System Installer is likely a possibility but may backfire a future day.
Agree mostly with all others. If possible, apply rule of K.I.S.S.
I've seen "meltdowns" when 3rd party adds something incompatible making the first on scene OPC server fold. This may not show up in the beginning, or worse at some update long after commissioning.
I've seen competitors claiming one of the few fixed TCP/UDP port numbers used by System 800xA.
Make a working proof of concept, then take decision.
Overriding the System Installer is likely a possibility but may backfire a future day.
Agree mostly with all others. If possible, apply rule of K.I.S.S.
I've seen "meltdowns" when 3rd party adds something incompatible making the first on scene OPC server fold. This may not show up in the beginning, or worse at some update long after commissioning.
I've seen competitors claiming one of the few fixed TCP/UDP port numbers used by System 800xA.
Make a working proof of concept, then take decision.
0
The use of Generic OPC Server (as opposed to PLC Connect) is not something identified during system installation, correct? If I'm creating a new node in the system that will be a server node solely for the purpose of running a third party OPC server... it doesn't have a connectivity assigned to it in the System Configuration Console?
I guess I'm struggling to understand that if a new server node is needed to be defined in the system to run a third party OPC server, and I'm NOT using PLC Connect, what node function is defined for this in the System Configuration Console?
I guess I'm struggling to understand that if a new server node is needed to be defined in the system to run a third party OPC server, and I'm NOT using PLC Connect, what node function is defined for this in the System Configuration Console?
Answered 1 month ago
Add new comment