Whitch is 800XA 5.1 RevC PLCConnectSevice using WindowsServices and DCS servers add on Windows
Windows 2008 server R2 standart
800XA 5.1 Rev C
Redundant Servers have Aspect server and Connectivity server installed together
PLC Connect service redundant working
Protocol PlcOpcClient version 5.0.1-0
OPC Server TriangeMicroworks installedon two servers on and have saperate license (its not redundandant)
Which PLC connect service is enable, thats servers OPC server service is running.
I need to learn, Whitch is 800XA 5.1 Rev C PLC Connect sevice using windows services and DCS servers add on Windows
I'm sorry but I don't fully understand your problem / question?
I'm no expert on PLC Connect, but as far as I know, PLC Connect does not have any services registered in Windows.
After adding of the PLC Connect System Extension, the 800xA System will know about and startup & monitor the "AdsScadaSrv.exe" process through the 800xA Service Framework infrastructure.
In turn, the "AdsScadaSrv" process will startup a few helper processes (AdsAbsDeplyMgr, AdsAeSrv, AdsClientSupport, AdsCsCommSrv, etc).
There should not be any need to restart any services, etc. in Windows.
Please consider contacting your regional ABB support center for further assistance.
Further to Stefans answer earlier: From you description I'm not sure you understand the difference between OPC servers and OPC clients.
Briefly: The OPC server is the source of the data, but it will only "send" data when an OPC client subscribes to the data. In your instance the OPC server is the TriangeMicroworks software. The OPC client is 800xA PLC connect.
In most cases it does not matter which "services" are running or not, but more of a poitn whether the OPC servers and Clients are compatible with each other, that is that the OPC client (PLC connect) can read the OPC servers data (TriangeMicroworks).
With PLC connect you can bundle individual data points (values) into "Tags" which act and behave like a standard DCS tag: multiple data points (eg PV, SP, High, Low etc) into a single Tag with its own faceplate and properties. Please read through the 800xA PLC connect documentation and also check up on what is represented by OPC as far as data types and so on. Also Alrming becomes an issue: is there an OPC AE server in TriangeMicroworks or does the 800xA system OPC client (PLC connect) have to handle and what is the timesource (PLC or 800xA?), are some of the common issues that need to be addressed too.