Redundant AS+CS machine.....Redundant machine OPCDA always in error state
I couldn’t make the secondary machine service provider in service state. Always it is going to Error. Let me know if I am doing any mistake.
In the Special configuration of OPCDA service provider I selected the Kepware OPCServer name(Kepware.KEPServerEx.V5)….In the Configuration tab… I made enable checked and Node as the secondary node machine name….
Note that what I did is…..Installed Primary and secondary Aspect+ Connectivity machine……created system in Primary…load the system extension….Added the redundant server(secondary to primary) through configuration wizard….create a project…..through control network created OPCDA SG and SP(Primary)….UpLoaded the 3 rd party server using OPCupload in control structure…….Manually created second service provider for control network(secondary machine node)……Manually created second service provider for OPC server network(secondary machine node)…..
Note that the manually created Service providers of secondary machine is always in error state….
Any Special setting need to done…..?
All other redundant services are up and running fine….
I was trying to test the redundancy…..please see the attached pics.
Let me know whether I am doing anything wrong…Note that AC800MOPCserver and Kepserver are running fine in both machine…I can see the smiley face for AC800MOPCserver…
Remote Node setting shall only be set if OPC DA Connector and OPC Server does NOT share same computer and thus require DCOM.
For AC 800 we recommend running AC 800M OPC Server and OPC DA Connector service provider in the same computer, a so called "Connectivity server for AC 800". Remote Node field must be left empty!
Often, multiple different OPC servers may share same computer, a so called "Combined Connectivity server" to reduce system footprint. Even aspect server may be let in, so called "Combined Aspect (multiple) Connectivity server".
If KepWare must be run in a dedicated non-800xA computer the Remote Node setting becomes required. DCOM permission must be defined properly (often in both ends to allow both outgoing calls and returning data callbacks). OpcEnum.exe must be available in remote node (see Configuration User's guide for DCOM requirements).
I don't know so much about KepWare but I assume you can have AC 800M OPC server and remote (DCOM based) KepWare Connectivity sharing the same computer.
For true redundancy you will need two KepWare nodes and point to them from the respective service providers in a 1:1 fashion.
For redundancy to work, the two OPC servers MUST SHARE IDENTICAL name spaces!
Try wiping all OPC DA service groups and start from scratch using the OPC Data Source Definition aspect's "wizard" (on the control network object in the Control Structure) to create new service groups and providers. For KepWare you must probably add the service group and at least one provider AND then set Remote Node before returning to the wizard and being able to browse & select the (remote) OPC server program ID.
Additionally PLC Server Configured as follows:
Remember to additionally configure the PLC server when using PLC Connect...