ControlMaestro Upgrade guide

(1)

Version: CM2013 v1.0 Date: 4th July 2013

Redactor: Yves Brunel

Validation: Didier Pedreno

ControlMaestro Upgrade guide

From Wizcon to ControlMaestro

(2)

ControlMaestro 2013 - Upgrade guide 1.0.pdf Page 2

1 BEFORE UPGRADING THE APPLICATION

A Wizcon application can be upgraded from Wizcon 5 to ControlMaestro according to the following table:

From Through Through To

Wizcon 5 _{Wizcon 7.61} _{Wizcon 8.3.2.136} _{ControlMaestro 2013} Wizcon 7.0x /7.5x _{Wizcon 7.61} _{Wizcon 8.3.2.136} _{ControlMaestro 2013} Wizcon 7.6x _{Wizcon 8.3.2.136} _{ControlMaestro 2013} Wizcon 8.0/8.1/8.2 _{Wizcon 8.3.2.136} _{ControlMaestro 2013}

Wizcon 8.3 _{ControlMaestro 2013}

Wizcon 9.x _{ControlMaestro 2013}

For version before 8.3.x, the upgrade must be done with several steps using Wizcon 7.61 or/and Wizcon 8.32, Wizcon 7.61 and Wizcon 8.3.2.136 can be downloaded from Wizcon support site to the following address http://support.wizcon.com.

If you are using Wizcon DOS, Wizcon for OS2 and Wizcon/2, Elutions can help you to upgrade the application. Please contact us.

Please remind following points :

 On a network, all the stations should have the same Wizcon or CM version. The only exception is during the migration phase.

 The migration process must not be mixed with additional modifications to the applications. Ex: if you need to modify the applications, don’t do it at the same time you are upgrading; upgrade first all the stations to the same version and only after you can modify the applications.

Before upgrading it is important to take care about the following:

 Make sure that you have a development plug.

 Make sure that you have all account information (the username/password of the application, Windows administrator password …).

 Make that the system is able to support ControlMaestro 2013 (see hardware and software requirements)

(4)

ControlMaestro 2013 - Upgrade guide 1.0.pdf Page 4  Communication drivers:

- Custom drivers

If you are using a custom driver, please check if this driver is compatible with ControlMaestro. The driver provider must be able to give this information. It is recommended to backup the vpiwnxx.dll file and copy this file to the ControlMaestro system in case of driver issues.

- Standard drivers

Some drivers need some additional hardware. Please take care about this if you want to change the hardware or if you want to change the PC (for example, cards format can be ISA).

The list of drivers that the application is using can be checked by opening the wizvpi.dat file.

 Add-ons:

Most of the C or VB functions (Wizcon toolkit) are compatible with ControlMaestro. Yet, it is recommended to check if the used functions are still supported or have been changed. Make sure that the source code is available from add-ons that are used, to be able to check these addons. Vb’s addons has to be recompiled with ControlMaestro compatibility toolkit.

 Third party programs:

Your application can use some third party programs like Microsoft Access, Microsoft Excel, Micromedia Alert …

If it is necessary, you can upgrade these programs. Beware about modifications you need in order to keep compatibility between ControlMaestro and these programs.  Plug:

Upgrading an application will also need an upgrade of the plug. Elutions can provide upgrade codes (this upgrade is not free of charge). To perform the plug upgrade, the latest RUS utility needs to be used. You can download it from our Elutions web site at the following address: http://elutions.com (Member access part).

2 OVERVIEW

In order to perform an upgrade, you must:  Backup files.

 Install ControlMaestro 2013.  Upgrade the application.  Check the application.

(5)

3 UPGRADING THE APPLICATION TO CONTROLMAESTRO 2013

3.1 Backup files

 Backup the original application:

In case of any error during the upgrade, the backup will be available in order to restart the upgrade process. It is better to keep this backup during the testing period, even if the upgrade works well.

 Backup the system folder:

There are several reasons to keep this folder: - Custom driver(s) and patches.

- AAM configuration. - Problems during upgrade.

3.2 Install ControlMaestro  Uninstall the old version.

 Delete the “system” folder (keep the backup).  Install ControlMaestro 2013.

3.3 Upgrade the application

 Check in the file wizcfg.dat the paths to make sure that they are correct.

 Make sure that no upper level directory structure is used in the path configuration of the file wizcfg.dat ( ..\ ), see example:

(6)

 Check if application has been packed for Runtime plugs. Delete the w2pack.dat file (if it exists)

 Rename (if it exists) the file “wizmenu.dat” to “wizmenu.bak”.

 In order to increase the upgrade speed and in order to avoid serial port problems, you can use a dummy driver without serial port.

- In Wizvpi.dat file, replace the G+ W+ A+ options by G- W- A- - In Wizvpi.dat file, replace COMx by NUL

- In Wizvpi.dat file, replace VPIWNxx by VPIWNDUM - Backup the Wiztune.dat file

- Check the Wiztune.dat file (that paths used in there are correct and in case ODBC datasources are used that you can create them with the same name.  Open and check the wiztune.dat file.

The option WIZ_SHOWMMW must be YES. If WIZ_SHOWMMW=NO, replace NO by YES:

(7)

(8)

ControlMaestro 2013 - Upgrade guide 1.0.pdf Page 8 Do not stop the upgrade process.

If there is a problem during this period and you need to interrupt the startup, you will experience problems with the application in a later stage. In case you need to start the upgrade process again using the backup, delete the application folder and restore the backup.

If there are errors messages during the upgrade process please check the following: - Is the application directory or the application Read-only? Remove this.

- Wizum.mdb and wizdata.mdb have to be in the same folder as the .wpj file. If this is not the case then change this and edit the wizcfg.dat file accordingly. - Check that the paths in the wizcfg.dat are correct, if this file does not exist

then save the paths in the Studio in order to create this file.  Log the application as User (password).

Wizcon will create a new user named “user” (password =password) if this user doesn’t exist. This user must belong to the administrators group.

 Assign Administrator group to your application administrator.

If the application administrator is not the user named ‘user”, you have to add this user to the ‘Administrator’ group, otherwise this user will not be able to access the user management.

 Define the default user.

The default user password is sometimes now encrypted. You need to reinsert and ‘save’ again this password in order to be compliant with the new version.

(9)

ControlMaestro 2013 - Upgrade guide 1.0.pdf Page 9 - Write the password:

 Change the ‘Application setup’ settings if addons or CMLanguage, CMSoftPLC are used, for example:

CMLanguage.exe (ControlMaestro language) and CMSoftPlcRt.exe (CMPLC

runtime) are now stored (by default) in the “x:\Program

Files\Elutions\ControlMaestro\ControlMaestro\bin and

ControlMaestro\cmSoftPLC\bin” folder.

(10)

ControlMaestro 2013 - Upgrade guide 1.0.pdf Page 10  Stop the application.

 Restore communication parameters to CMVPI.DAT file (the new Wizvpi;dat file).  Rename Wizmenu.bak to Wizmenu.dat file.

 Clean the application folder.

Delete *.bak, errors, errors.dat, groups.dat, lrm.dat, Wizgates.dat, WizGates.mdb, users.dat, users.bak files if they exist.

 Repair Wizdata.mdb file (Optional).

Sometimes the Wizdata.mdb becomes very large. In order to avoid this problem, you can repair the Wizdata.mdb file. It is possible to perform this action using Microsoft Access or a Microsoft ODBC link. We recommend using the ODBC driver in order to repair this file.

(11)

- Add an ODBC user DSN:

(12)

- Select the ‘Repair’ option and perform the repair action based on the wizdata.mdb.

- Cancel the ODBC setup.  Restart the application.

 Upgrade the web application.

It is recommended to upgrade the web part of the application. This can be done by running the Appupgrade tool which can be found under: \Utilities\Application Upgrade.

Start the appupgrade (only one time) and the program will perform the upgrade:

AppUpgrade will open and save all viewports and all html files.  Printer definition.

You need to define printers. The old system using direct LPT port is not supported.

3.4 Check the application

Check the following items of the application:

3.4.1 Tags

 Check group definitions.

3.4.2 Alarms

 Check alarm texts. If alarm texts are missing then do the upgrade process again from scratch.

(13)

3.4.3 Application language

Save the application language in order to check it: - $GROUPS is not supported.

- You need to take care about the path used in EXIST or SHELL functions. - It is possible to replace system Tags like $DAY, $MINUTE… by @SYS_DAY,

@SYS_MINUTE. “$” systems tags are still supported.

3.4.4 SoftPLC

 Convert to the new CMSoftPLC 3.0 version with the CMSoftPLC converter tool:

(14)

 Compile the project and change the Directories if necessary, which can be done from the Project -> Options :

 To create a new Bootproject, Login to the CMSoftPLC Runtime and when this is in the ‘RUN’ state, create the bootproject from the CMSoftPLC Development:

(15)

 Keep in mind that in the New CMSoftPLC version some libraries are in a different location and that some FB’s have been put in other libraries or are not used anymore.  If CMSoftPLC was already used in Wizcon then the global variables “Wizcon(R) “

need to be removed manually.

 Change the ‘shutdown on ControlMaestro exit’ mechanism if used.

3.4.5 Image

 In the Wizcon versions 8 and 9, layers have to be associated to groups. In case no objects are visible from an image after an upgrade then set the image in ‘edit’ mode and check in case layers are used that groups/users are assigned to the layer(s).  The basket.dat file has to be deleted. Otherwise an image crash can happen.

 Check the text alignment. If this is not correct, use the ImageTextSettingsTool.exe which can be found under: \Utilities\Image Tools and has different settings to be checked which one works best.

3.4.6 Macro

(16)

 You have to take care about the path folder in a macro command.

3.4.7 Addons

 Some old Wizcon API’s are not supported anymore.

 According the add-on design, you can have some compatibility problems.

This is the case if the add-on uses direct Wizcon file access, user management, printer management…

3.4.8 OPC

 Add .00002 at the end of the OPC tags as this is the item value in newer OPC versions (as of OPC 2.0).

 Check if there are macro’s used to replace long OPC addresses.

 Take care about the Wizcon OPC server name. The OPC server name has been changed.

4 UPGRADING THE APPLICATION TO WIZCON 7.61 OR WIZCON 8.3.2.136

The upgrade to Wizcon is quite similar than the upgrade to ControlMaestro 4.1 Backup files

 Backup the original application.  Backup the system folder.

4.2 Install Wizcon 7.61 (or Wizcon 8.3.2)  Uninstall the old version.

 Delete the “system” folder (keep the backup).  Install Wizcon.

4.3 Upgrade the application

 Check in the file wizcfg.dat the paths to make sure that they are correct.  Rename (if it exists) the file “wizmenu.dat” to “wizmenu.bak”.

 In order to increase the upgrade speed and in order to avoid serial port problems, you can use a dummy driver without serial port.

(17)

 Open and check the wiztune.dat file to replace WIZ_SHOWMMW=NO by

WIZ_SHOWMMW=YES.

 If the original application is Wizcon 5 application, copy blank <ProjectName>.wz7 and <ProjectName>.wza files into the application. In order to build blank wz7 and wza files, you can create a blank application and pick up these files.

 If original application is Wizcon 5 for OS/2 application, open Wizvpi.dat files and replace vpi by vpiwn.

 Start Wizcon.

Do not stop the upgrade process. If there is a problem during this period and you need to interrupt the startup, you will experience problems with the application in a later stage.

In case you need to start the upgrade process again using the backup, delete the application folder and restore the backup.

 Log the application as User (password).

Wizcon 8.3.2 will create a new user named “user” (password =password) if this user doesn’t exist.

This user must belong to the administrators group.

 With Wizcon 8.3.2 assign Administrator group to your application administrator

If the application administrator is not the user named ‘user”, you have to add this user to the ‘Administrator’ group, otherwise this user will not be able to access the user management.

ControlMaestro Upgrade guide

ControlMaestro Upgrade guide

From Wizcon to ControlMaestro

Table of Contents

1

BEFORE UPGRADING THE APPLICATION

2

OVERVIEW

3

UPGRADING THE APPLICATION TO CONTROLMAESTRO 2013

4

UPGRADING THE APPLICATION TO WIZCON 7.61 OR WIZCON 8.3.2.136