Classic HMI (Basic / Comfort / Advanced)

Screens, pop-up windows, templates and slide-in screens become FabyaVision pages. Screen groups become page groups, and screen layers are carried over with their names. Objects are converted to their counterparts in the Studio library.

• Visibility animations are converted as a range or a single bit.
• Appearance animations carry the color ranges and blinking.
• The ProcessValue link of objects such as the I/O field is bound to the value of the object. A link that is a script or an expression is not transferred.

The click, press, release and activate events are converted to Studio event functions: set, reset and invert bit, set bit while pressed, write a tag value, increase and decrease, open a screen, pop-up window or slide-in, previous screen, log on and log off, close the program, acknowledge alarm and a call to a user VBScript.

• Tag tables become folders in Studio. Tags come with their name, data type, read cycle and start value; address resolution is described on the tags and addresses page.
• Text lists and graphic lists are converted to Studio lists.
• Read cycles become cycle records in Studio.
• Connections are created with the names the tags use. If the IP address is not known, you enter it in Studio.
• The graphics in use are added to the project as images.

Each VBScript becomes a VBS module in Studio. Script calls in events call the procedure of this module; parameters of calls with parameters are not transferred. If a script contains calls specific to WinCC (ShowSystemAlarm, Alarms, file objects), the report writes an Info row.

Studio’s script engines cover a subset of the WinCC environment. Check the scripts in Studio with Compile (F9) and try them in Live.

• Alarm definitions, recipes, users and archives are not converted because Openness cannot deliver them; you define them again in Studio, for example under HMI alarms and the other sections.
• The symbol library (ActiveX), faceplates and function keys are not converted.
• Screen events, PropertyAnimation animations and object enabling animations are not converted.
• Of the object events, only click, press, release and activate are carried over. Some system functions such as StartProgram are not converted either.
• In a SetTag function that reads its value from another tag, a constant value is written and the report warns.
• Object types that are not in the table above become placeholders; the details are on the conversion report page.