Before Transferring Projects

This section describes what you need to know before you transfer.

Notes on Transferring Projects
When Transferring Project for the First Time
Transfer Methods
When Using SP5000 Series Open Box (Windows 10 IoT Enterprise Model), IPC Series, or PC/AT
When Using IPC Series or PC/AT

Notes on Transferring Projects

Data in the backup memory (SRAM) is erased, when transferring the project.
Before transferring a project, package, or data, first back up the existing project and project data.
When the previous project in the display unit has Operation Log enabled and if you transfer the new project, check if enough space is available in backup memory (SRAM) for the logged data to be exported. Otherwise, the data is removed.
Before transferring, if you do not check the categories and features supported by the display unit, it may result in performance issues in the display unit.
Support Model List
For safely transferring project files, see the following.
Cybersecurity
If you run transfer when a Web Viewer client is logged in, a logout operation is not recorded in the operation log.
Project file transferring is supported either from screen editing software to a display unit, or from a display unit to another display unit. You cannot transfer a project file from a display unit to the screen editing software.
If the display unit fails to accept the project in a transfer operation, use recovery mode.
Recovery Mode

When Transferring Project for the First Time

If you are transferring a project for the first time, refer to the following.

Transferring a Project for The First Time

Transfer Methods

The following transfer methods are supported. For the procedure of each transfer method, check the corresponding link destination.

When Using SP5000 Series Open Box (Windows 10 IoT Enterprise Model), IPC Series, or PC/AT

When the write filter (write protection) is set on the system card (C:\drive), you will need to disable the write filter settings before transferring a project.

Do not change the path of [ProgramData] folder from the Windows default setting.

When Using IPC Series or PC/AT

Precautions When Transferring Project File to Different Version Runtime

When using IPC Series or PC/AT, you cannot transfer the project files in following conditions.

If you transfer the project file in the following conditions, the error message appears in the screen editing software.

Runtime Version	Screen Editing Software Version	Error Message
Version 3.1 or earlier	Version 3.1 Service Pack 1 or later	[Unable to update using download operation. Use the installer to update run time to the latest version.]
Version 3.1 Service Pack 1B or later	Version 3.1 or earlier	[Panel type is different. Select the correct panel type and try again.]

In order to transfer, the run time must be re-installed with the version which does not apply to the above conditions.

Install the run time from the following path on the installation media.

"\BLUE_Setup\BLUERuntime\BLUERuntime.exe"

Important:

Installing the run time erases any previously transferred project files. After installation, transfer the project files again.
If .NET Framework is not already installed in the run time installation destination, or its version is older, .NET Framework is also installed. After .NET Framework is installed, the installation destination is restarted.

Note:

You can get the installer from the following.

https://www.proface.com/en/product/soft/blue/download

When installing the run time, there is not need to uninstall the previously installed run time.

For Secure Transfer (SHA2 Code Signature)

For security reasons, SHA2 code signatures are used during transfer. Confirm your operating environment supports SHA2. If not, run the security update program to install the SHA2 code signature.

Security Update Program

https://www.microsoft.com/en-us/download/details.aspx?id=46148

Checking if your environment supports the SHA2 code signature

From the Control Panel, select [System and Security] - [Windows Update] - [View update history]. In the update history, confirm listings of [Security Monthly Quality Rollup for Windows 7] from October 2016 onward. If these entries are listed, your environment supports the SHA2 code signature.

Update history example (64 bit operating system)

2016-10 Security Monthly Quality Rollup for Windows 7 for x64-based Systems

Update history example (32 bit operating system)

2016-10 Security Monthly Quality Rollup for Windows 7