In WVS Screen Move center function doesn’t behave as Service Engine (Desktop)
Description
The "Screen:
Move center" function opened a Wordview Screen and moved to the indicated
station position in the Service Engine, but not in the WVS.
The issue has been addressed and the WVS behavior is
now the same as in the Service Engine.
To benefit from this fix:
- Update
your zenon Software Platform to the latest build of zenon 14or higher.
Item ID: 284607
Version: 14.00 Build: 275981
Related Articles
FAQ: Installation of Service Engine 12 Build 162015 in Ubuntu 22.04 LTS as Docker container
Refer to the attached file: Docker on Ubuntu 22.04 - FAQ.pdf This guideline is solely shared for demonstration and educational purposes. Feel free to contact COPA-DATA Support for further clarifications.
FAQ: How can I backup the Service Engine data, the data created during Service Engine?
The path of the Service Engine folder can be amended in the project properties and it is set into zenon6.ini (VBF30=) when the start project is set in Engineering Studio or in zenon Startup Tool. In the Service Engine folder, there is the subfolder ...
Checklist: Data Missing in Service Engine
Time estimate: 60 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick hints] ...
after project conversion -> world view comes to the foreground when running "screen move center" function
Description After a project conversion, when the function "Screen: Move center" is called, the screen of the type Worldview is brought to the foreground. This covers the navigation screen, which can no longer be operated. This behavior has been ...
FAQ: When I change something in the Recipegroup Manager via the programming interface in Service Engine, these changes are not updated in the screen. Why is that?
To understand this, you have to know that each time you access the RGM (Recipegroup Manager), you are working with a copy of the RGM data. So every screen that is opened in the Service Engine, has it's own copy of the RGM data. Also each instance ...