Back

Topic

[KB220]Migrating a PcVue project from PcVue2 to PcVue32

Tags: Migration

Upgrade issues
14 years ago
By RM
Options
Print
Applies to:

PcVue version 6.00 onwards.
Summary:

This article provides some tips on migrating an application from PcVue2 (version 2 to 5) to PcVue32 (version 6 onwards).
Details:

Note

These are just a selection of tips and are not intended as a definitive list.

Hardware

The latest generation of PCs are not suitable for PcVue2 as there are compatibility problems with the standard serial port.

Example

A communication problem occurred between PcVue2 and a PLC using Modbus protocol through a converter (though that makes no difference, judging by tests made directly in RS232 with a Modbus/JBUS Slave emulator). The PC system used was as follows:

  • PC: COMPAQ PIII 866Mhz.
  • PcVue2 version: 3.08a.
  • PLC: TSX or a Modbus/JBUS emulator (YAPI)

Comprehensive tests were performed, including some with modified parameters in the BIOS. The outcome was that:

  • PcVue2 did not work either with the PLC or with YAPI.
  • Pcvue32 worked correctly in both cases.
  • YAPI worked correctly with the PC COMPAQ and with PCVUE32 on a portable PLC.
  • PcVue2 worked correctly with an ordinary IBM Pentium PC.

Configuration

To avoid problems with the variable database.

Run the project under PcVue2 (502f for example) and:

  1. In Administration.Compatability deselect the option Use tagnames in the historic data files.
  2. In Administration.Format select the Extended format option for the variable database file.
  3. From the same menu, in Options, deselect all files (except Histo.dat).
  4. Save the variable database.

Then run the project under PcVue32 and:

  1. Save the variable database once more.

Mimics

To avoid problems with mimics in PcVue V7 onwards.

Run the project under PcVue2 (502f for example) and:

  1. Save each of the mimics individually.

Run the application in an intermediate version (e.g. PcVue V6.04).

  1. Save each of the mimics again

Then migrate the application to PcVue V7.

Animations

Color animations using a blinking color do not always transfer correctly.

Images

Distorted BMP format images should be converted to JPEG format.

Communication

General limitations

  • A problem occurs with real or double word frames because the two words are reversed by default. Check and reconfigure the frames if necessary.
  • In Modbus, the frame size has been reduced from 1700 bits to 1600 bits. Any frames were are greater that 1600 bits will have to be split into two.
  • The drivers for third party communication cards such as ETHWAY or FIPWAY may not work in the operating systems used by PcVue32.

Applicom

The general procedure is as follows:

  1. Install the Applicom CD.
  2. In the CONFIG folder: copy all of the APPLICONF.APX files.
  3. Restart PCCONF.

For example from Aplicom V3.2 to V3.6:

If the card is ISA PC2000ETH, with Applicom V3.2.0:

  1. You can effect the transfer via Applicom version 3.6 and PCI 2000ETH and obtain the configuration of the ISA card.
  2. However you must take account of the card type in the Applicom console (by changing ISA to PCI).
  3. Also enter the type of connection (to transfer the AUI connection to RJ45, as required for the AUI/RJ45 converter).

Historic data

General

The state of the bit used to trigger a back-up may be reversed in PcVue32 compared to PcVue2.

Transferring historic data configuration

  1. Using PcVue (version 6, 7 or 8) create a new project.
  2. From the dialog Configure.Compatibility, select the option Use version 2 for historical data.
  3. Shut down PcVue and then copy the files VAREXP.DAT and HISTO.DAT to the new project.
  4. Restart PcVue.
  5. From the dialog Configure.Compatibility, de-select the option Use version 2 for historical data
  6. Check that the file HISTO.DAT is properly populated.

Created on: 26 Nov 2010 Last update: 13 May 2024