Movicon PowerHMI

Movicon Power HMI is a compact version of Movicon.  Even though PowerHMI projects can be developed with the same Movicon environment, it has certain limits that Movicon does not have and which must be taken into consideration beforehand. This limits are described below.  To make things simple for the programmer concerning those feature not supported by Power HMI, a  "Target License Type" project property has been provided with two options: to develop a Movicon project (Standard Option) or to develop a PowerHMI project (Power HMI option). When selecting the "Power HMI" opton, the system will be configured to hide or disable all those features not supported by Power HMI in order to stop the programmer from using them by mistake.

The "Power HMI" type project Runtime must be used with a "PowerHMI" type License for consistency, but in reality, regardless of the selection made in the "Device License Type" property, the Movicon functions will be enabled during runtime or Power HMI based solely on the license installed.

It therefore follows that if a Movicon project, which therefore has a Standard license type set in the "Device License Type" property, is started in runtime on a machine with a software license for Power HMI ("PowerHMI" License), this project will, however, be subjected to "Power HMI" type limitations.

The Licenses for "Power HMI" are Software type only and are generated based on the MAC Address of the device's network card.

Restart Movicon when switching over from one license type to another to ensure that it starts with the new settings.

Power HMI limited features compared to those of the Movicon full version

PowerHMI does NOT support any of the following features or resources:

• ODBC

• ActiveX/OCX

• OLE objects

• ROT

• Report

• AlarmDispatcher

• Power Templates containing Basic Script code

Detailed comparison table:

License Management

The Power HMI version runs on a license which can only be activated with a Softkey containing a code to unlock it. There are no hardware keys available for this version. Unlicensed Project runtimes will be executed in Demo mode only.

PowerHMI licences can be purchased in single quantities over the internet.

Startup in Runtime Mode

PowerHMI does not provide the use of a specific runtime module to run projects. Therefore, you must use the "/R" option to run the project.  For example, to run the "Test.movprj" project you should enter the following command line:

C:\Program Files (x86)\Progea\Movicon11.6\Movicon.exe /R C:\Documenti\Test.movprj

VBA (WinWrap Basic) Restrictions

The use of the Basic Script resources comes with some restrictions:

• Only two Basic Script resources can be loaded in Ram and executed at the same time.

• It is not possible to associate script code to Objects, Screens and Alarm Thresholds.

• The basic script expressions are not supported in object properties.

• Variable script events can be inserted in Basic Script.

• The use of Public Basic Scripts is supported.

• Direct access to the project variables is supported.

• Use of the project's RealTimeDB variable IntelliSense is not support. This means it will not be able read/write structure variables with <Variable>.<Member> syntax or byte array variables with <Variable>.<e>n  syntax.

• Basic Script Resources cannot be run in "Safe Mode".

• Basic Script Resources can access and use external libraries, but only libraries that do not require a licence.

• All the WinWrap Basic functions are supported in the Basic Script Resources

• Basic Script Resources can only access the methods and properties of the following interfaces:

DrawCmdTarget

SynopticCmdTarget

AlarmCmdTarget

AlarmThresholdCmdTarget

DLRCmdTarget

DBVariableCmdTarget

IOPortInterface

SchedulerCmdTarget

ScriptMEInterface

EventCmdTarget

PmeDocCmdTarget

ScalingCmdTarget

UIInterface

UserAndGroupCmdTarget

UserGroupCmdTarget

UserCmdTarget

Not all the methods and properties of the "DrawCmdTarget" interface are supported as described below.

The supported methods and properties of the "DBVariableCmdTarget" interface are:

• EnableInUseVarMng

• GetDynamicVariable

• GetNumDynTag

• GetNumStructDefinitions

• GetNumVariables

• GetVariableAddressInfo

• GetVariableDescription

• GetVariableSize

• GetVariableValue

• GetXMLSettings

• IsFirstDBInstance

• IsValidVariable

• PurgeDynTag

• PurgeDynTagTimer

• SetVariableValue

• UseSharedDynTag

• VariableInUse

All the events, methods and properties of the "ScriptMEIterface" interface are supported.

Variable restrictions

System Variables

The variables which are not by PowerHMI are:

_SysVar_:NumWebClientConnected

_SysVar_:PendingTraceEntries

_SysVar_:NumExpressions

_SysVar_:OPCServerNumClients

These variables will not be inserted in the  "_SysVar_" structure prototype when activating the command to add system variables.

Array Variables

The array variables are supported but indexes can only be numeric and not a variable.

Restrictions on System Variables

The following system variables are not managed by PowerHMI:

_SysVar_:NumWebClientConnected

_SysVar_:PendingTraceEntries

_SysVar_:NumExpressions

_SysVar_:OPCServerNumClients

The command used to add the system variable to the database will not add these variables in the "_SysVar_" structure prototype.

Historial Log table Restrictions

The Historical Log tables  (Alarms, Drivers and SysMsgs) created with the 10.x PowerHMI version are no longer compatible with the 11 version since the table structure for 11 version includes two additional fields. When upgrading to the Moving to 11 version, these tables will be re-created losing all recorded data.

Page Change command Restrictions

The "back history" screens list used for the "Close and Return back" commands is not available. The first time the "Close and Return back" commands are executed, the supervision returns back to the previous screen, and the second time it is executed it returns back to the start screen.

Restrictions on String Table

The columns of the String Table do not support the properties for the Reference Style  (Style Source Container) or the properties for Text -To-Speech ( TTS Engine, TTS Volume, TTS Rate. It is not possible to change the TTS engine for the Text-To-Speech function in the project language change.

Other restrictions

Other restrictions may be:

• PowerHMI cannot access in write a Movicon project variable with Trace comments enabled.

• PowerHMI is not able to acknowledge Movicon project alarms which have been enabled for acknowledgement comment entries.