Project Files

Movicon saves project files in one unique folder which is called the 'Project Folder'. In addition to the project files, sub-folders containing data relating to the project are also created in the Project Folder with the purpose to structure the project's architecture so that it is more coherent to the user.

All the Movicon project files are saved in XML format and, therefore, can be read and edited with any text or XML editor. This can only be done if the project files have not been crypted by the programmer.

The data and information of the Movicon projects are contained in files with '.movprj' extensions. Everytime a project is saved, Movicon makes a backup copy of the project file. The back-up copy will have the same project name but with 'movbak' as its extension.

If for any reason the project file is lost, simply open the backup file by renaming the extension from '.movbak' to '.movprj'.

Movicon also associates other files to the project, one for each Resource type. These files will be created in the same project folder.

The following table describes the types of files identified by their extensions:

File Extension

Description

.movprj

Project file

.movbak

Back-up copy of project file

.movalr

File containing the data and the configurations inherent to the 'Alarms List' Resource

.movdlrec

File containing the data and the configurations inherent to the 'Data Loggers & Recipe' Resource

.movevt

File containing the data and the configurations inherent to the 'Event Objects List' Resource

.movils

File containing the "IL General Logic" code of the project

.movnetclt

File containing the data and configurations inherent to the Client 'Network Services' Resource

.movnetsvr

File containing the data and configurations inherent to the Server 'Network Services' Resource

.movopcclient

File containing the data and configurations inherent to the OPC Client

.movrealtimedb

File containing the data and configurations inherent to the 'Real Time DB' Resource

.movsch

File containing the data and the configurations inherent to the 'Scheduler Object List' Resource

.movscl

File containing the data and configurations inherent to the 'Scaling Object List' Resource

.scrnav

File containing the data and configurations inherent to the "Screen Navigation" Resource.

string.language

File containing the Movicon text strings in the language specified in the file extension. If, for instance, the Italian and English language have been inserted in the Movicon String Table defining two columns as 'Italian' and 'English', this will create two files as follows:

ProjectNamestring.Italian

ProjectNamestring.English

string.language.bak

Backup file of files containing Movicon text strings

.actstr

File containing the actual language column name.

.constraints

This file consents you to define project editing restrictions. This file is generated while a new project is being created depending on the platform type selected (Win32/64, WinCE, etc). For further information please refer to the section on "Project Constraints".

.movrefactoring

This file contains the project's Cross References.

.hisupg

This file is created by the "HisLogUpdate.exe" tool when a control is carried out at project startup and when modifications are made to the Historical Log tables. This usually happens when projects originate from previous Movicon versions. This file will remain empty if no modifications are made to tables.

Some files have the above described description plus the "_c". For example:

ProjectName.movalr_c

These are compiled files which are used by Movicon at Runtime to enhance the performance velocity of the project being run. These are the same XML files that are compiled in binary format.

These compiled files are automatically generated by Movicon at runtime and re-created each time the project file they relate to is modified.

Warning: Modifying an "_c" compiled file direclty will change Movicon's behaviour according to the resource the compiled file refers to. Modifying compiled files for the Data Logger/Recipes, Event objects and Alarms, for instance by using an external tool like Notepad, these files will not be re-created at the next project startup and the project will run using the modifications made to the compiled files. However, a "_c" file of another resource type, such as the Screens resource for instance, will be recreated even if the compiled file differs from the project xml file.

.uxp

This file is created when a user password has been changed. Typically when the property to force password change at first login or when passwords expire has been enabled.

.rtusers

This file is generated when project runtime users haved been edited. Groups and the Users created at Runtime with the "EditUsr.exe" tool are saved in this file.

.zip

Project Backup File.

.movrtmembers

File contains the settings of the structure variable members.

.movopcuaclient

File containing the list of OPC UA Tags and relating link properties to the OPC UA Server and Real Time DB variables.

ServerConfig.xml

OPC UA Server data configuration file e.g. endpoints. Defines the server access security on 32/64 bit Windows systems

ServerConfigCE.xml

OPC UA Server data configuration file e.g. endpoints. Defines the server access security on WindowsCE systems

ClientUAConfig.xml

Configuration file belonging to the OPC UA Client.

ADPending.xml

The "ADPending.xml" file memorizes messages pending in the queue that are to be sent to the Dispatcher by Movicon and created in the project's DATA folder. In cases where Movicon is restarted with messages still to be sent, the Alarm Dispatcher will also be automatically restarted.

WebCfg.xml

The "WebCfg.xml" file sets the paths to reach the "* .DER" and "* .KEY" Certificates files used during HTTPS access to the WebSocket Server via the HTML5 Web Client.

Filter.opcua

Stores the Filter strings used in the OPC Browser Window. This file is located in the project's DATA folder.

As already mentioned above, in addition to the project files, Movicon also creates folders that will contain information on data saved and recorded at runtime:

Folder Name	Description
ALARM	Files with the '.alr' extension which contain information on alarms at runtime are inserted in this folder. A file will be created for each project alarm with the following syntax: ProjectName_ThresholdName_VariableName.alr
DATA	In this folder you can find the following file types: ".var" Contains information relating to the variables declared as retentive are inserted into this folder. A file will created For each retentive variable in the project with the following syntax: ProjecNamet_VariableName.var ".watch" Contains the configuration information of the Watch window available in the project's Runtime debug phase. These files will have the following names: Watch 1.watch Watch 2.watch Watch 3.watch Watch 4.watch ".mdb" You will also find the Database file for the "Real Time DBMS Settings" management. This file will be created in this folder for default with the following name: ProjectName_RealTimeDB.mdb You will also find the Database file for the "Variable Trace" management. This file is created only when the ODBC has been activated to record data and not the IMDB. This file will be created for default in this folder with the following name: ProjectName_TraceDB.mdb ".dat" You will also find this file type for the "Variable Trace" managment. This file is created only when when the IMDB has been activated to record data and not the ODBC. This file will be in text format and can also be encrypted when desired. A file will be created for each variable being traced with the following name: VariableName.dat ".xml" You will also find this file type for the "Variable Trace" management. This file is created only when when the IMDB has been activated to record data and not the ODBC. This file will be in xml text format and one will be created for each variable being traced with the following name: VariableName.xml ".sxml" or ".tsxml" These files are "Symbol Configuration Files" of objects. ".shp" This file contains the programming of a Sheduler which was done by means of using the Scheduler Window. The name of the file identifies the scheduler in question. ".sst" This file contains the execution status of a Scheduler command. The name of the file identifies the scheduler in question. ".settings" This file contains the ODBC plug-in configuration information. The file name identifies the database type. ".TraceDBEx" These files contain flush data for variables being traced in incidents where errors were detected in the ODBC connections. The names of the files will be the same names used by the variable trace tables. These Flush files will be automatically deleted by Movicon, after data has been restored in the database once the ODBC connection is re-established. .upldsettings This file contains the settings of the last PlugIn used to transfer the project to a remote device. "Browsed.endpoint" This file contains the list of OPC UA Server Endpoints that were browsed using the OPC UA Browser window. You may find credentials for non-anonymous accesses to OPC UA Servers among the recorded information. Therefore, you can encrypt or not to encrypt the file when adding or editing the Endpoint list based on the value set in the Project's "Encrypted Project Resources" property.
DLOGGERS	The following file types can be found in this folder: ".mdb" This database file contains the project's Data Loggers and Recipe tables. This file will only exist if the selected format is in MS Access. If another database is used, such as the SQL Server, this file will be created based on the provider's characteristics. Furthermore, this file will be created only when the ODBC has been activated to record data and not the IMDB. This file will have the following name: ProjectName_DLR.mdb ".dat" This file type is used to manage the project's Data Loggers and Recipes. This file is created only when the IMDB has been activated to record data and not the ODBC. The file will be in text format and can also be encryted if desired. A file will be created for each Datalogger and Recipe with the following name: DataLoggerName.dat RecipeName.dat ".xml" This file type is used to manage the project's Data Loggers and Recipes. This file is only created when the IMDB has been activated to record data and not the ODBC. This file will be in xml text format. A file will be created for each Datalogger and Recipe with the following name: DataLoggerName.xml RecipeName.xml ".DataLoggerEx" These files contain the data flashed from DataLoggers' when ODBC connection errors are detected. The names of the files will be the same names used by the Datalogger tables. These Flush files will be automatically deleted by Movicon as soon as the ODBC connection has been re-established and data have been restored to the database.
LOGS	This folder contains log files in the ASCII format which report information related to the different project components, such as system messages, OPC messages, user activation messages, etc. All these files have the '.log' extension and their names indicate their contents type. When the IMDB has been activated to record data and not the ODBC, a file in the Database MS Access format will be created in this folder containing data related to the project's Historical Log. This file will have the following default name: ProjectName_HisLog.mdb When the ODBC has been activated to record data and not the IMDB, files with the ".dat" and ".xml". extensions will be created in this folder containing data relating to the project's Historical Log. The ".dat" files will be in text format and can be encrypted. ".HisLogEx" These files contain the data flashed from the Historical Log when ODBC connection errors are detected. The names of the files will be the same names used by the Historical Log tables. These Flush files will be automatically deleted by Movicon as soon as the ODBC connection has been re-established and data have been restored to the database.
NETLOG	This folder contains log files in the ASCII format which report information related to the Networking communications which include information on active connections, variable changes executed by Clients or Servers, and other.
RESOURCES	This folder contains files related to the project's Multiple resources (Screens, Accelerators, Menus, Parameterization Files, Basic Scripts and Embedded Reports). Movicon will create a file with the resource's name and extension, based on the resource type, for each resource inserted in the project: Screens = .movscr Accelerators = .movacc Menu = .movmenu Basic Script = movbas Parameter Files = movpar Embedded Report = movrep A file named "<Screen>_c.jpg" will be created for each Screen resource. This file is used to preview screens during design mode and is used in Embedded Screen objects when the "Embedded Screen Style Properties" property is enabled. In addition to this, the same tree structure that has been created in the 'Project Explorer' window for Multiple Resource Groups will also be reproduced in this folder with the resource group folders. The files containing any enabled communication driver settings will also be kept in this folder. These files will have the following names: DriverName.drvsettings: file containing the Communication Driver settings DriverName.dynsettings: file containing the list of the Communication Driver's dynamic tasks DriverName.dyndrv: file containing the list of tags created dynamically in the variables
IMAGES	Images used in the project are kept in this folder. Each time an image is associated to a Movicon screen or object, it will be automatically be copied to this folder and its related path will be used to retrieve it.
Exclusion.lst	The Movicon 11 Websocket Server checks whether any directory traversal attacks have been made to gain unauthorised HTML5 Web Client access to the system. This is the reason why it is not possible to use any unexpected files, such as a logo image, in HTML page customizations. To allow the use of files in HTML5 page customizations, you can add their name to the list indicated in the "Exclusion.lst" file which must be created within the Movicon installation "WebClientPages" folder. For example, a content of this kind would be: <?xml version="1.0" encoding="ISO-8859-1" ?> <FileList> <Filename>/css/logo.bmp</Filename> <Filename>custofile.png</Filename> </FileList> Where each indicated file is used to customize the HTML page to be opened on the HTML Web Client side.

The Project Folders listed above are those which Movicon uses for default. However, they can be customized and new ones can be created in different paths by means of using the "Project Path Settings".

Project Backup

Movicon keeps a build count of the project it saves in the ".movprj" file's <ProjectBuild> xml tag. When the project's "Increase Project Build Number" execution property is enabled, the project's internal build number will increase by 1 each time the project is saved. When this property is not enabled, the build number will remain always the same. When the project's "Save Backup" execution property is enabled, a backup of all the project's files and resources will be made in the ".zip" file with the name of <Project Name>_<Project Build> each time the project is saved. Therefore, as a result, when the project's "Increase Project Build Number" execution property is enabled, a new ".zip" file will be created at each project save. Otherwise, the ".zip" file will remain with the same name but overwritten each time the project is saved. The folder containing the project will also contain all the backup files of the saves taken place. The ".zip" format has been used because to it does not occupy too much disk space. In addition, the zip file contains files with their paths which makes it easier to extract them.