OPC_STATUS_FAILED."? (you cannot get *precisely* that one unless the other product is also built with QuickOPC, because the message text comes from our product). What typo precisely was it then?Īlso, when you say "I also tried using another company's OPC client and get same results", does it mean that you got "RPC server is unavailable" (the text of this error comes from Microsoft), or an error similar to our ""Server failed. OPC_STATUS_FAILED." error? Have you made a typo that resulted in connection to a different OPC server, or a different machine - and a successful one? That seems quite unlikely. So, how could making a typo turn the "RPC server is unavailable" error into the "Server failed. OPC_STATUS_FAILED." indicates that in fact the connection was made, and it's just a problem reported over that connection. On the other hand, the error with "Server failed.
The "RPC server is unavailable" is most likely a symptom of "total" failure - we could not connect to the server at all. As such I have tried to be very specific in this case to avoid any more confusion. Please Forgive me, I should have been more careful with my description of events before. This has all been verified to be true and correct as I have explained it here. Please See screen shots attached for specific error messages.Īll DCOM and RPC services are running on both computers, and it makes no difference if the firewall is on or off. The response I get, after manually entering the machine "SCADA" and server name "Citect.OPC.1" is that long failure string. The response I get, after manually entering the machine "SCADA" and server name "Citect.OPCRemote.1" is "The RPC Server is not available". Also if I manually type in the Machine Name "SCADA", and manually enter the OPC server name, I cannot read nor write data to either "Citect.OPC.1" or "Citect.OPCRemote.1". When I do attempt to look for OPC Servers on "SCADA", I get the "RPC server not available message". However, I cannot browse for OPC Servers on remote machines. When I use your OPC demo application over the LAN from "Develop" to "SCADA": I can browse for machines and it does find them. When I use your OPC demo application locally on "SCADA": I can browse for OPC servers, and connect to both "Citect.OPC.1" or "Citect.OPCRemote.1" and reads and writes data to tags. And both work locally for data reads and writes. On "SCADA" I am interested in accessing data from either OPC server named "Citect.OPC.1" or "Citect.OPCRemote.1". One, Called "SCADA", which has several working OPC servers on it, and the other computer called "Develop" on the same Local area network as "SCADA".
I re-checked everything and came up with 2 screen shots that should help you to see whats going on. I may have also given you some slightly wrong information. The views and opinions expressed in this article are those of the author(s) and do not necessarily reflect the official policy or position of Schneider Electric.I am sorry for the confusion. This article shows a step-by-step process to enable and test the native OPC DA Server in supervision participant Citect SCADA 2018. The only way to enable it is from inside out using an include project. Another motivating force to have an OPC DA server enabled on supervision participant is that some projects could have calculate variables on supervision which does not exist on control project.Ĭurrently there is no option to create OPC DA Server from EcoStruxure Process Expert interface as below.
#CITECT OPC SERVER SOFTWARE#
These customers prefer third-party software collecting data from the supervision servers. This solution using OFS Server as an unique OPC DA Server to interface with other system works fine but some customers standard/ customers best practice doesn’t allow other systems to collect data direct from the controllers. Whenever a third-party software needs to collect data from EPE it can be done by connecting to OFS Server in either primary or standby operation server. The OFS is an OPC DA Server which is installed in the same server as the EPE operation server(s). In EcoStruxure Process Expert 2019 (former HDCS) and previous versions the communication between the supervision participant Citect Scada and Modicon PAC controllers are handle by OFS – OPC Factory Server. Elektrik Tasarım Dağıtım ve Uygulama Çözümleri.Motorabgangstechnik & Antriebstechnik Forum.Level and Pressure Instrumentation Forum.EcoStruxure Automation Expert / IEC 61499 Forum.APC UPS Data Center Backup Solutions Forum.APC UPS, Critical Power, Cooling and Racks.