Here’s what more than 2,500 business decision-makers around the world say.Download the report
...with the Facility Hero app in hand! Discover how you can optimize your maintenance efforts today.Learn more
Access tailored services, 24/7 self-service and expert help. Anywhere, anytime, any project.Discover now
Everything you need to know about our IoT technology backbone.Learn more
Explore our global offerings or select your country from one of our five regions.Global
Découvrez nos offres globales ou sélectionnez votre pays dans l’une de nos cinq régions.
An OPC Client can browse and add tag items from a single cluster project successfully running on a SCADA machine, however it's not possible with a multi-cluster project.
This occurs in SCADA v7.20 (and previous versions). A workaround involves adding a cluster name manually as a prefix to tags in the OPC client (e.g. ClusterName.TagName) to resolve tag communication with SCADA OPC Server.
This problem has been addressed in SCADA v7.30 with new OPC DA server platform. Be aware that this means each tag name needs to be unique to a cluster.
If a v7.30 multi-cluster project has duplicate tag names (attached to different clusters), it would be necessary to define tag names with the cluster name in the format ClusterName.TagName in the OPC client to resolve a tag conflict.
Vijeo Citect v7.x
PowerLogic SCADA v7.x
Keywords: PLS, PLSCADA, PL SCADA, Power SCADA, StruxureWare PowerSCADA Expert, SPE, PSE, 7.1, 7.2, 7.10, 7.20, multiple clusters, Q6401
Sign up for all the latest solutions, offers and best practices straight to your inbox.
We are excited that you have joined the group. You will receive your welcome email soon describing the program and what to expect in the upcoming weeks. Enjoy!