Ask Me About Webinar: Data Center Assets - Modeling, Cooling, and CFD Simulation Join our 30-minute expert session on July 10, 2025 (9:00 AM & 5:00 PM CET), to explore Digital Twins, cooling simulations, and IT infrastructure modeling. Learn how to boost resiliency and plan power capacity effectively.Register now to secure your spot!
Issue with Control Component in Graphics Editor (Power Operation 2022 U6)
Ask the Community
Ask questions, get advice from experts and peers on Digital Automation & Energy Management.
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2025-08-2103:38 PM
Issue with Control Component in Graphics Editor (Power Operation 2022 U6)
Hello everyone,
I am currently working with Power Operation 2022 Update 6 and I have run into an issue with the Graphics Editor, specifically with the Control component used for breaker/switch operations.
When I configure a Control button, the script inside the definition references the definition name instead of the instanced object name. This means that when I use the script to send information or change the state of a breaker/switch, the variable componentName in theconsole output shows the definition’s name, not the actual instance placed on the diagram.
In older examples (from previous versions of Power Operation), the Control button appears to behave correctly, but in those cases the examples include a script that explicitly calls a function. When I replicate that approach in my version, I still see the same behavior — the definition name is taken instead of the instance.
Has anyone experienced this behavior in Power Operation 2022 U6?
Is this expected, or is there a way to make the Control component reference the instanced object instead of the definition?
Could this be a limitation or change introduced in the newer versions of Power Operation?
Any insights, workarounds, or documentation references would be greatly appreciated.