more quick actions

minimize quick actions

Applies to:

PcVue 16.3.1, PcVue 15.2.12, PcVue 12.0.31

Summary:

Security features have been implemented in versions 16.3.1, 15.2.12 and 12.0.31 to protect PcVue networking messages. This feature causes a compatibility issue with older versions.

Details:

The discovery of vulnerabilites in the PcVue client/server networking feature resulted in major fixes (see the security bulletin SB2025-4).
These fixes include the addition of security features to ensure the confidentiality and integrity of the messages exchanged between PcVue stations.

As this security feature is activated by default for new projects but also for migrated project (e.g. from version 16.2 to 16.3.1), users may experience communication issues between PcVue stations.

An updated station won’t be able to communicate with a not updated station. This situation will remain until all the stations have been migrated.

During this transient stage, the following warnings are logged and displayed in the event viewer :

2025/09/01,10:37:27.760,3,D,,3388,,11,Networking message version of station SERVER1 = 163000
2025/09/01,10:37:27.760,3,W,,3712,,11, Networking, the version ‘163000’ of the remote station ‘SERVER1’ is not compatible due to security constraints
2025/09/01,10:37:27.760,3,W,,3072,,11,Client->server connection CLIENT10C -> SERVER10S is aborted
…
2025/09/01,10:37:46.228,3,I,,3070,,11,Server->client connection CLIENT10S -> SERVER10C is OK
2025/09/01,10:37:46.230,3,W,,3716,,11,Networking, connection CLIENT10S -> SERVER10C is not secure, the remote node ‘DATASERVER10’ must not alter the security or the local node must allow it
2025/09/01,10:37:46.230,3,W,,3142,,11,Server->client connection CLIENT10S -> SERVER10C is rejected

The Allow stations with altered security option has been implemented to disable the security feature if the migration is to be carried out in several stages and take some time.
This option can be found in the Networking settings :

or in the advanced part of a station node:

A whitelist filter has also been implemented to control which IP addresses are authorised to connect to the station.
This withelist is defined by the Networking configuration. This control can be disabled by selecting the Allow any node adresses option.

When selecting the allow stations with altered security option, keep in mind that the stations will be exposed to the discovered vulnerabilities.

Applies to:

All PcVue Versions

Summary:

An error dialog appears after selecting the EDE file. It explains the EDE file is not compatible, but the reasons of this error could be more various.

Details:

EDE Example

When using the Smart Genrator BACnet, sometimes, after selecting the EDE file, the following dialog appears :

The first reason explained is about the csv-delimiter used in the EDE file.
In this case, you just have to change this parameter in the advanced options:

Also, the problem could come from the contained of the EDE file :

According to KB 1101, if the device-object type is not present in the EDE file, PcVue won’t be able to create a device and associate objects to it.
As an EDE file is mainly provided by a manufacturer software, the format and structure of column could be different as expected, for example :
- The column title “Supports Cov” have to be written without dash between “Supports” and “Cov”.
- Extra columns could be presents but are not expected such as “schedule-type”,”schedule-state-text-reference” or “schedule-unit-code”. These columns are not defined in the EDE specification.
- Some mistakes (a title column is missing or not well written)

N.B : The v2.2 (released in 2007) and v2.3 (released in 2017) layout are supported.

Attached to this article, you will find a template of an EDE file provided by the BIG-E.U which can be perfectly imported in PcVue.
You can us it and compare it to your EDE file.

Applies to:

PcVue 16.0 onwards

Summary:

This article describes how to use PcVue SOAP interface and PcVue REST API

Details:

WST SOAP Developer manual
WST REST Developer manual

PcVue provides the ability to access data from the running project via Web Services technology.
All the provided functions and services are grouped together in a development kit, called Web Services Toolkit.

Web Services Toolkit allows third-party applications to exchange data with the supervisor. It is a server API (Application Programming Interface) that provides following accesses:

Authentication/session management
Realtime data access
Real time alarm access
Historical data access: logged events and trends
Graphical data: mimics and symbols

Web Services Toolkit is available for several technologies:

SOAP/XML since SV version 8.00
REST since SV version 12.0

Current article provides the developer manual for both technologies:

PcVue SOAP/XML API	WST_DeveloperManual.pdf
PcVue RESTful API	WST_REST DeveloperManual_1_0.pdf

Applies to:

PcVue 16 onwards

Summary:

This article will help you to communicate PcVue with the PostgreSQL database

Details:

PostgreSQL is “the world’s most advanced open-source relational database”. It’s made by PostgreSQL Global Development Group.

Unfortunately, PostgreSQL like some open source projects such as Maria DB does not offer a ready to use ADO.NET provider.

Once the binaries are obtained it is possible to install a third party provider with the tool : “ProviderInstaller.exe”.

To be detected by PcVue, each ADO.NET provider must be installed in the Global Assembly Cache (GAC) of the .NET framework and referenced in the machine.config file. The tool “ProviderInstaller.exe” is there to facilitate this task.

— How to install PostgreSQL ADO.NET Provider —

1. Download Attachment “Npgsql 8.0.7 install.zip”

2. Extract “Npgsql 8.0.7 install.zip” to “Npgsql 8.0.7 install”

3. Open CMD prompt as Administrator

4. Change directory to be in “Npgsql 8.0.7 install” directory

cd “C:\Users\Dev\Desktop\Npgsql 8.0.7 install”

5. Run following command:

ProviderInstaller.exe /install

6. Restart your computer and then PcVue

— How to configure a PostgreSQL connection in PcVue —

1. At PcVue side, with Application Explorer, navigate to General > Data connections

2. Add a new SQL Connection as below

The connection string should be as below :

Host=localhost;Port=5432;Database=postgres;Username=postgres;Password=******************************

Fill these informations in according to your database connection informations.

Like that you can get a successful connect to your postgres database server by clicking on test connection button.

— Some usuals Sql queries —

.Create a table

CREATE TABLE MyTable (col1 INT)

. Insert a value

INSERT INTO MyTable (col1) VALUES (1)

. Display table content

SELECT * FROM public.mytable

Attached file	Description
Npgsql 8.0.7 install.zip	Npgsql 8.0.7 install

Applies to:

PcVue 12 onwards

Summary:

The goal of this article is to show how to display milliseconds in timestamp in an export file

Details:

By default, the exported file does not display sample timestamp with milliseconds, even though export sampling is done in milliseconds.

To display milliseconds, you generally need to change the date format of the language configured in Data Export.

The default time format is: HH :mm :ss (even if nothing is selected).

You therefore need to modify the time format of the language configured for export as follows:

HH :mm :ss .fff

In this example, the language is set to configuration 1:

TimeFormat setting

Export setting

Useful links:

https://www.pcvue.com/ProductHelp/PcVue/fr/Content/AE/Project/Languages_settings.php

https://www.pcvue.com/ProductHelp/PcVue/fr/Content/AE/DataExport/Advanced.php

Applies to:

PcVue 16.2 onwards

Summary:

To prevent PcVue from crashing when opening a 3D mimic if the required DLL is missing, a function can be used to check for the presence of the file. This check allows access to the mimic to be controlled via a status variable. In next version PcVue should no more crash if this dll is missing.

Details:

Issue

PcVue may crash when opening a 3D mimic if a required DLL is missing at initialization.

Cause

The absence of the DLL at mimic startup causes a critical error, as the file is required for certain 3D functionalities.

Solution

To avoid this issue, the FSTAT instruction can be used in a PcVue program to check for the presence of the DLL during initialization (in the initialization program).

Steps to follow:

Create a verification function in a PcVue program:
- Use the FSTAT instruction to test for the presence of the DLL.
- FSTAT returns 0 if the file is missing, and 1 if it is present (as it provides the file size and last modification date).
Control a bit variable:
- If the DLL is present → the variable is set to 1.
- If the DLL is missing → the variable is set to 0.

image

sub verif()
DIM res as integer;
DIM bufh as LONG; ‘buffer handle
CONST ALLOC=22; ’22 is the minimum required
Dim str_path as str;
Dim name as str;
Dim chemin as str;
CONST ALLOC=22; ’22 is the minimum required
str_path = GetApplicationDir();’for the access path
chemin = ADDSTRING(str_path,”\\D3DX9_43.dll”);’ the complete access path
bufh=ALLOC_BUFFER(ALLOC);
res=0;
res= FSTAT(chemin,bufh);
print(res);
print(bufh);
if (res=!0) then
@DLL_present =1;
end if
FREE_BUFFER(bufh); ‘free buffer
end sub

Configure the Link/open animation of the mimic:
- In the Interlock condition field, insert the status variable.
- Define the access condition (e.g., allow access only if the variable = 1).

image

Applies to:

FrontVue 16

Summary:

This article was last updated to include information related to FrontVue 16.3.0. It contains the so-called “readme first” information for FrontVue 16. Files attached is the readme file as shipped with the DVD.

Details:

File	Description
ReadMe.pdf	The readme file in English

This document contains information about version 16:

What’s new in 16.0 – An overview of the main new features in version 16 Initial Release (16.0.0)
What’s new in 16.1 – An overview of the main new features in the 16.1 Feature Release (16.1.0)
What’s new in 16.2 – An overview of the main new features in the 16.2 Feature Release (16.2.0)
What’s new in 16.3 – An overview of the main new features in the 16.3 Feature Release (16.3.0)
System requirements
Installation

What’s new in 16.0

HMI

Web browser control – A new built-in graphic control to display web content and Pdf files in a mimic.

Installation and deployment

Support for Microsoft® Windows 11 and Windows Server 2022.

What’s new in 16.1

Feature enhancements and fixes.

What’s new in 16.2

Support for the visibility animations on more graphic elements, including symbols and most graphic controls.
Feature enhancements and fixes.

What’s new in 16.3

The Comment property is now available as a runtime tooltip for all animations.
Multiline tooltips that automatically combine the Comment property values of all animations linked to a graphic element into a single tooltip at runtime.
Feature enhancements and fixes.

System requirements

Operating systems

Only operating systems from the Microsoft® families of Windows 10, Windows 11, Windows Server 2016, Windows Server 2019 and Windows Server 2022 are supported.

We recommend you use Windows Client versions for operator stations and Windows Server versions for server stations.

Supported and operational

Windows 10 version 1607 or later – Professional and Enterprise Editions
Windows 11 – Professional and Enterprise Editions
Windows Server 2016 – Essentials, Standard and Datacenter Editions
Windows Server 2019 – Essentials, Standard and Datacenter Editions
Windows Server 2022 – Essentials, Standard and Datacenter Editions

All operational versions of Windows Server shall be installed with the ‘Desktop Experience’ option.

Operational but may have limitations in use

Please contact the technical support before using:

Windows 10 IoT Enterprise LTSC 2016 or later, Windows 11 IoT Enterprise, Windows Server IoT 2019, Windows Server IoT 2022, Windows Server for Embedded Systems and all other embedded systems
Any operating system hosted in a system virtual machine such as Microsoft® Hyper-V and VMWare® virtualization products

NOT supported

All other versions of Windows 10 and Windows 11 – In particular Windows 10 version 1507 (RTM) and 1511 (Nov 2015 update) are not supported
Windows 10 IoT Core
Windows Server installation in Nano Server or Server Core mode

For all operational versions of Windows 10 and Windows 11, only the x64 processor architecture is supported.

The software requires .NET Framework 4.8 and cannot run on an operating system if .NET Framework 4.8 is not preinstalled or cannot be installed separately.

For all platforms, we recommend that you apply any critical updates available from the Windows Update web site.

For any other Microsoft® operating system, please contact the Technical Support.

Recommended minimum PC configuration

Processor – x64-compatible AMD or Intel CPU (or equivalent) – 1.4 GHz dual core minimum.
System Memory – 4 GB of RAM.
Available hard disk space – At least 10 GB.
Graphics – 1024×768 display for Windows Server platforms. In addition for Windows Client platforms, support for DirectX 9 graphics device with WDDM driver.
Network Interface Card – At least 1.
Drives – A DVD drive, as appropriate, is required for installation from disc.

The above figures represent the minimum requirements. For advice on specific applications, please contact the Technical Support.

Installation

For information about the Microsoft® Windows user privileges required to install and run the product, see the following topic in the online help: Operating system related considerations.

See the Installation help for more information and help about prerequisites and the installation process itself.

Microsoft and Microsoft Windows are trademarks of Microsoft Corporation.

Last edit: May 16th, 2025

Applies to:

PcVue 16

Summary:

This article was last updated to include information related to PcVue 16.3.2

It contains the so-called “readme first” and the Release Notes information for PcVue 16.

Files attached are the readme files as shipped with the DVD.

Details:

File	Description
ReadMe.pdf	The readme file in English
ReadMe.zh-CHS.pdf	The readme file in Chinese
ReadMe.ru.pdf	The readme file in Russian
ReadMe.fr.pdf	The readme file in French
ReadMe.ja.pdf	The readme file in Japanese
Release Notes PcVue 16.3.2.pdf	The Release Notes

This document contains information about version 16:

What’s new in 16.0 – An overview of the main new features in version 16 Initial Release (16.0.0)
What’s new in 16.1 – An overview of the main new features in the 16.1 Feature Release (16.1.0)
What’s new in 16.2 – An overview of the main new features in the 16.2 Feature Release (16.2.0)
What’s new in 16.3 – An overview of the main new features in the 16.3 Feature Release (16.3.0)
System requirements
Installation

What’s new in 16.0

Featured Smart bots – Digital assistance
Smart Bots helps users follow operational and maintenance procedures based on no-code workflows that you have defined with a visual programming tool. Users can interact with a bot in SnapVue and in the desktop Instant Messaging client, and task completion is reported automatically.

Key use cases:

Application forms

Job orders

Field service management

On-site inspections

Smart assistants

The Smart Bot feature was available in preview since version 15.

Featured BIMOps – A BIM platform for operations
Support for integration of BIM data into the project. This new feature includes the ability to render and animate Ifc-based models to help users navigate and interact with the 3D model, locate alarms, and access information based on the references and geometry of a BIM model.

Key features:

BIM graphic control for rendering Ifc-based models

Configuration editor to define groups of Ifc objects, color animations and mimic links

SCADA Basic scripting with the new instruction BIMDISPLAY

Featured Video-protection – ONVIF camera support
Support for integration of ONVIF cameras, including AV streaming and camera control. ONVIF cameras are pre-defined with the Application Explorer as part of the Security devices configuration. AV streams can then be displayed at runtime with the ONVIF control, including camera PTZ commands and stream control (resolution, volume, etc.).

Key features:

Support for ONVIF Profile S cameras

Security device configuration in the Application Explorer

ONVIF graphic control and camera command animation

Preset management

Guard tour mode

Capture snapshots

SCADA Basic scripting with the new instruction CAMERADISPLAY

This new feature also comes with a generic video control designed to:

View and control an RTSP AV stream
Play AV files (mpeg, avi, etc.)
Capture snapshots
SCADA Basic scripting with the new instruction VIDEODISPLAY.

Data acquisition drivers

Featured OPC UA client (new) – Data Access services. Support for data acquisition server redundancy and OPC UA server redundancy.
Honeywell Galaxy SIA (new) – Supports the Galaxy Dimension and Galaxy Flex systems (intrusion detection and access control)
Omron FINS Ip (new) – For communication with OMRON PLCs
OCPP (new) – Support for versions 1.6 and 2.0.1 of the OCPP specifications to monitor and control EV charge points. Includes a library of ready-made templates.

Configuration & Diagnostics

Application Explorer:

Featured Re-designed configuration for Equipement data acquisition drivers
They can now be configured using the Application Explorer and modelled using the Application Architect – Network, devices and frames.
To make life easier, drivers are now categorized by Type (Serial, Tcp/Ip, etc.) and Manufacturer, and legacy drivers are only displayed after the activation of a global setting.
Certificates management for OPC UA

Application Architect:

Import/export of templates and parameters

Libraries:

New library for PV plant monitoring

WebVue – Several fixes and enhancements including:

Support for the Map control

Geolocation

A zone and its actions can now be displayed in SnapVue even if it is not associated to any geo-tag. This makes perfect sticky zones users can always access for actions of general interest such as displaying a production line status of energy dashboard.
Local chat rooms to make chatting easy to users located in the same zone.

HMI

Featured Web browser control – A new built-in graphic control to display web content and Pdf files in a mimic. SCADA Basic scripting with the new instruction WEBBROWSER.

Installation and deployment

Support for Microsoft® Windows 11 and Windows Server 2022.
Support for Microsoft® SQL Server 2022.
Silent installation – You can now take advantage of the silent install capabilities to automate the installation and the update of the product.

Performances

Improvements to the mimic rendering performances of WebVue.

Add-ons and tools

OPC UA Gateway 1.5.11 (updated)
Dream Report 2023 (updated)

Features in preview

Notification Publisher (preview for testing) – A module designed to support the Push Notification technology. This feature is in Preview for testing. You must run the installation package in mode Custom to install it. Please contact us if interested.

What’s new in 16.1

Featured Grid control – Support for extended attributes
Extended attributes can be displayed as columns in the Grid control when using the variable tracking mode. Depending on the configuration of the Grid control and user permissions, the value of Extended attributes can also be changed directly from the Grid. The same goes for the Simulated property of variables.

Featured Central project management
Tags can now be associated to versions of your project and libraries, and you can start your project based on a tag instead of a version identifier or state. With version tagging, the application designer can skip the use of the built-in versioning state machine. And by controlling project startup based on tags, the designer drives the version loading and can apply a versioning policy even if the built-in state machine do not completely fit.

Smart bots – Digital assistance
Smart bot workflows can now interface with O365 calendars to manage tasks and find the most suitable team mate according to availability and occupation for task assignment. The Smart bot plug-in now also implements a Web API client so that you can interface with Web Server endpoints as part of your workflows: Telegram, Line, REST API, CMMS API…

Configuration & Diagnostics

Application Explorer:

Featured The Mapping dialog for Equipment data acquisition drivers can now be used to map variables on frames' sub-addresses, making it easier to map data structures onto a series of variables of diverse types using a single frame. For example, you can now use the Mapping dialog to map Register and Bit variables onto the same Word or Double word frame. The drivers' runtime already supported this feature, but it required changing the mapping configuration manually.
The labels used to designate extended attributes can now be fully customized. Customized labels are then used everywhere extended attributes are displayed.

Data acquisition drivers

OPC UA client – Support for method calls. A new Helper is available at design time to test method calls, and the SCADA Basic instruction OPCUA has a new mode called METHOD able to perform method calls.
PIMA (new) – Supports the PIMA IPGuard Receiver software (intrusion detection).
SATEC (new) – Supports Satec PM130 devices, in particular the PM130P, PM130E and PM130EH series (power meters).
SNMP Manager – An extension to the driver enables mapping variables onto tabular OIDs of varying length, typically to manage dynamic lists of events or alarms.

Add-ons and tools

OPC UA Gateway 1.5.14 (updated)
Dream Report 2023 Patch1 (updated)

Features in preview

What’s new in 16.2

Featured Sql grid
A new built-in graphic control to display data returned by a pre-defined Sql query. The Sql grid control can be scripted using the SCADA Basic instruction SELECTOR.

Featured Sql query wizard
Sql queries can now be easily configured using a wizard. The wizard is available for SQL Server.

Pdf and Xps Printing
Support for Microsoft Windows Pdf and Xps printers for alarm & log printing.

WebScheduler
Support for adding calendar-based recurring triggers.

HMI

Support for the visibility animations on more graphic elements, including symbols and most graphic controls.
Visibility based on zoom levels and layers is now also supported for most graphic controls.
Command level for the Form controls – Variable command levels and the corresponding user rights can now be enforced when operating a Form control based on variable values.

Configuration & Diagnostics

Application Explorer:

Improvements of Sql query snippets.

Application Architect:

Data Export – Data Export configuration elements can now be added to a template, including Trend and Log pages.

SCADA Basic

New instructions:

JSONPATH – To process Json formatted data.
FTPS – To copy a file to or from an FTP server using FTPS.

Smart Bot

New features:

Featured Smart bots can now be typed depending on how you need them to operate:
- Smart bots designed to interact with users as part of a chat-room.
- System bots designed to operate in background without user interaction.
- Assistant bots designed to interact with one or more users in a customized UI on mobile devices.
- Template bots designed for reusability. They are able to perform predefined operations and are called by other bots with parameters to set the context.
Featured Machine learning – A bot operation to train a machine learning model on the local database using one of the available trainer algorithms.
Web Hook – A bot condition that allows bots to catch and handle external webhooks.

Data acquisition driver

Featured OCPP – Support for OCPP proxy.
ICCP – Support for the ICCP security layer.
OPC UA – Fixes and enhancements.

Security

HDS – To manage connections to SQL Server databases, the HDS now supports the Microsoft OLE DB Driver for SQL Server (MSOLEDBSQL). The MSOLEDBSQL driver comes with support for TLS to ensure confidentiality and integrity of the data flow to SQL Server.

Features in preview

What’s new in 16.3

Featured SimuLock
SimuLock is a handy new tool for viewing and controlling any variable used within the displayed mimic.

It makes it easy to test mimic animations when data acquisition sources are down or not available. It also proves useful when you need to simulate values for one or more variables due to inaccurate I/O data at the process level.

Accessible directly from the WebVue system toolbar, SimuLock gives you the ability to:

Instantly set and reset the simulation mode of any variable.
Adjust the simulated values in real-time.
Specify an expiration date for when the variable simulation will automatically terminate.

It comes with strict user permissions enforcement, ensuring only authorized individuals can set simulation modes at runtime.

Configuration & Diagnostics

Application Explorer:

New variable simulation properties and settings to support the SimuLock component.
SQL query wizard for Oracle and the REST built-in provider.

Application Architect:

Sql queries – Predefined Sql query configuration elements can now be added to a template, including Sql connections and Sql queries.

HMI

The Comment property is now available as a runtime tooltip for all animations.
Multiline tooltips that automatically combine the Comment property values of all animations linked to a graphic element into a single tooltip at runtime.
Added support for simulation-related properties in the Grid control.

Smart Bot

New conditions added for Schedule elements.
Ability to generate and process QR codes.
Improvements to triggers and historical data requests.

Data acquisition driver

IEC 61850 – Support for dynamic data sets, setting group control blocks, and originator customization.

Security

HDS – To manage connections to SQL Server databases, the HDS now supports the Microsoft OLE DB Driver for SQL Server version 19 (MSOLEDBSQL).
New settings to control the exposure of multiple interfaces including the OPC DA server, DDE client & server, and COM servers.
New Security administration permission in profiles to control who can adjust sensitive security-related configuration.

Add-ons and tools

OPC UA Gateway 1.6.1 (updated)
MQTT Add-on – New custom publish format

Features in preview

System requirements

Operating systems

Only operating systems from the Microsoft® families of Windows 10, Windows 11, Windows Server 2016, Windows Server 2019 and Windows Server 2022 are supported.

We recommend you use Windows Client versions for operator stations and Windows Server versions for server stations.

Supported and operational

Windows 10 version 1607 or later – Professional and Enterprise Editions
Windows 11 – Professional and Enterprise Editions
Windows Server 2016 – Essentials, Standard and Datacenter Editions
Windows Server 2019 – Essentials, Standard and Datacenter Editions
Windows Server 2022 – Essentials, Standard and Datacenter Editions

All operational versions of Windows Server shall be installed with the ‘Desktop Experience’ option.

Operational but may have limitations in use

Please contact the technical support before using:

Windows 10 IoT Enterprise LTSC 2016 or later, Windows 11 IoT Enterprise, Windows Server IoT 2019, Windows Server IoT 2022, Windows Server for Embedded Systems and all other embedded systems
Any operating system hosted in a system virtual machine such as Microsoft® Hyper-V and VMWare® virtualization products

NOT supported

All other versions of Windows 10 and Windows 11 – In particular Windows 10 version 1507 (RTM) and 1511 (Nov 2015 update) are not supported
Windows 10 IoT Core
Windows Server installation in Nano Server or Server Core mode

For all operational versions of Windows 10 and Windows 11, only the x64 processor architecture is supported.

The software requires .NET Framework 4.8 and cannot run on an operating system if .NET Framework 4.8 is not preinstalled or cannot be installed separately.

For all platforms, we recommend that you apply any critical updates available from the Windows Update web site.

For any other Microsoft® operating system, please contact the Technical Support.

WebVue & WebScheduler – Supported Web browsers

Desktop web browsers:

Google Chrome™ 126 and later
Mozilla Firefox™ 126.0 and later
Microsoft Edge™ 126 and later
Apple Safari® for MacOS® 17.5 and later

Mobile web browsers:

Google Chrome™ for Android™ 126 and later
Microsoft Edge™ Mobile 126 and later
Apple Safari® for iOS™ 17.5 and later
Android WebView™ 126 and later

TouchVue & SnapVue – Supported Mobile operating systems

At the time of writing, the list of supported platforms for the TouchVue and SnapVue mobile apps is:

Android™ 9.0 onward (RAM 2 Gb minimum)
iOS™ & iPadOS™ 16.4 onward

TouchVue and SnapVue are available on Google Play™ and the App Store. Please refer to the relevant store to check compatibility with your mobile device.

Microsoft® SQL Server

Using the HDS for database archiving requires one of the following SQL Server versions:

SQL Server 2014
SQL Server 2016
SQL Server 2017
SQL Server 2019
SQL Server 2022

The HDS supports the following OLE DB drivers from Microsoft:

MSOLEDBSQL up to version 19 included (recommended)
SQLOLEDB

Depending on your needs and their specific constraints, any of the following editions can be used for each of the above: Express, Workgroup, Web, Standard, Business Intelligence, Enterprise and Datacenter.

SQL Server administration requires Microsoft® SQL Server Management Studio.
For more information and download, refer to https://docs.microsoft.com/sql/ssms/download-sql-server-management-studio-ssms

Recommended minimum PC configuration

Processor – x64-compatible AMD or Intel CPU (or equivalent) – 1.4 GHz dual core minimum.
System Memory(*) – 4 GB of RAM.
Available hard disk space – At least 10 GB (project and archive data not included).
Graphics – 1024×768 display for Windows Server platforms. In addition for Windows Client platforms, support for DirectX 9 graphics device with WDDM driver.
Network Interface Card – At least 1.
Drives – A DVD drive, as appropriate, is required for installation from disc. An available USB port is required if you use a hardware protection dongle.

(*) If you are using SQL Server, additional memory may be required. See the following topic in the online help for more information: Microsoft SQL Server related considerations.

(*) If you are using RDS (Remote Desktop Services) or IIS (web server), please contact the Technical Support for advice about memory requirements.

The above figures represent the minimum requirements. For advice on specific applications, please contact the Technical Support.

Installation

For information about the Microsoft® Windows user privileges required to install and run the product, see the following topic in the online help: Operating system related considerations.

See the Installation help for more information and help about prerequisites and the installation process itself.

Microsoft, Microsoft Windows and SQL Server are trademarks of Microsoft Corporation.
Android and Google Play are trademarks of Google LLC.
iPadOS is a trademark of Apple Inc.
iOS is a trademark of Cisco Inc and is used under license.

Last edit: May 16th, 2025

Applies to:

PcVue 16.2 onwards

Summary:

This article shows how to configure PcVue to retrieve data from SOFREL’s “LogUP” DataLogger using the REST API and LX CONNECT platform. The data can be archived using a SQL database or a proprietary type archive.

Details:

This exchange with the LX CONNECT platform is possible thanks to PcVue’s REST Provider.

Note that the use of the Provider is subject to an option on the license.

Download and install the latest version of the Provider proposed in this article.

Follow the instructions given in the article on how to install ADO.Net Providers to install this Provider.

The steps are as follows:

Declare a connection in PcVue,

Go to General -> Data connections -> Add SQL connection

Select the data source “Built-in providers”,

Then select the data provider “. NET Framework Data Provider for REST”:

Finally, go to the second tab (Built-in) to configure the connection as below:

REST API CONNEXION 2

REST API CONNEXION 3

Legend:

5: https://lxconnect-ihm.sofrel.com/auth/realms/Lxconnect/protocol/openid-connect/token

6: your ClientID received from SOFREL: Example in my case PCVue-STC

8: your ClientSecret received from SOFREL

9: https://lxconnect-ihm.sofrel.com/lxc-as-appm/lxconnect/api/

The LX CONNECT platform has two versions of APIs to retrieve data.

The v1 API allows you to:

• Retrieve list of all devices

• Retrieve information from a device

• Retrieve a device configuration

• Retrieve archives with Unix date format

The v2 API allows you to:

• Retrieve archives in ISO8601 date format

2. Create SQL Read query

• Retrieve equipment list

REST API QUERY All DEVICES

Select * from [get_v1/devices]

QUERYSTRING(“deviceType=LogUp“)

• Retrieve information from an equipment

Select * from [get_v1/devices/9fec58d9-c7a6-4e48-974d-77352f2345c9]

QUERYSTRING(“deviceType=LogUp”)

Note: 9fec58d9-c7a6-4e48-974d-77352f2345c9 = deviceUID retrieved from previous query result

• Retrieve configuration of an equipment

Select * from [get_v1/devices/9fec58d9-c7a6-4e48-974d-77352f2345c9/configuration]

QUERYSTRING(“deviceType=LogUp”)

• Retrieve telemetry archives of equipment in Unix timestamp format

Select * from [get_v1/devices/9fec58d9-c7a6-4e48-974d-77352f2345c9/telemetry/AI_1_SCALING_VALUE]

QUERYSTRING(“deviceType=LogUp&startTimestamp= 1733907061000000&endTimestamp= 1733907961000000“)

Note: AI_1_SCALING_VALUE is a «telemetryName» obtained from the result of the previous query on the configuration. The correct start and end date will be required.

PcVue tolerates a maximum of 5000 cells as a result of a read query with SQL connections. Please play on the time interval to stay in this constraint.

• Retrieve telemetry archives of an equipment in ISO8601 format (Remember this work with V2 of API)

Select * from [get_v2/devices/9fec58d9-c7a6-4e48-974d-77352f2345c9/telemetry/AI_1_SCALING_VALUE]

QUERYSTRING(“deviceType=LogUp&startDateTime=2024-12-23T08:51:00.000Z&endDateTime=2024-12-23T09:06:00.008Z“)

3. Retrieval of all archives from the LX CONNECT platform

The LX CONNECT platform only stores data from the last three months.

To retrieve all archive data from the platform, you can refer to KB1105 : Repeat Query for Sql variables.

Attached file	Description
sv-adonet-provider_Rest_1.0.667.zip	Version 1.0.667 of REST provider
Provider Rest – GuideLine – draft	The documentation

Applies to:

PcVue 11.0 onwards

Summary:

When using a temporary dongle the time-stamp that the dongle was last used is recorded. Subsequently, when starting PcVue, if the current time is earlier than the recorded time-stamp then PcVue will not start, you will get an error message saying that the system clock has moved backwards since the last use. Originator: ND

Details:

In case a User has legitimately changed the system clock and is no longer able to start PcVue the following procedure can be useed to reset the dongle. THIS PROCEDURE CAN ONLY BE USED ONCE ON A PARTICULAR DONGLE

Create a shortcut to the License Utility and add the –clock command line argument. Example:
C:\ARC Informatique\PcVue 11.1\Bin\LicUtil.exe -clock
Double check that the system clock is set to the current time as this reset can only be used once.
Start the License Utility, plug in the dongle, and select the menu item Reset date of last use.
After that you will be able to start PcVue again.

Applies to:

PcVue 11.2 onwards

Summary:

During the life of a PcVue project, it may be necessary to change the archiving mode from proprietary archiving to HDS archiving. This document deals with the possibility of retrieving archived data in proprietary format and injecting it into HDS tables. This document only applies to trended data. A similar procedure can be performed for archived data via log lists, but this is not covered in this art.

Details:

The procedure in this article is complex. We recommend that you back up your data before starting and contact our technical support team if you have any questions.

I- BASIC PRINCIPLE

PcVue’s proprietary archiving was not designed to interact with third-party tools. As a result, only PcVue can retrieve the information contained in such archiving units.

However, there are 2 proprietary archiving formats:
-> ASCII, which can be read using a text editor
-> BINARY, which can only be read by PcVue.

To migrate a proprietary archive into an HDS archive, the principle is as follows:
1) Creation of the target unit (archive unit, tables)
2) Extraction of packets of historical data
3) Generate files in HDS import format
4) Use the “DBImport” utility to inject logs into HDS tables

II- CREATING A DATABASE ARCHIVE

This chapter outlines the steps to be followed when creating an HDS trend for a variable initially archived in proprietary format.

Step1: Database declaration, i.e. at least
– a database
– a trend table
– a trend group

Step 2. Creation of a database archiving unit

Step 3. Variable trending

Step 4. Handling the “Primary” option.

Please note! The proprietary trend MUST be primary for extraction.

III- EXTRACTION

III.1- Extraction tool for proprietary ASCII archives:

When archives are in ASCII format, a tool is available to extract data directly from files

directly from the files, bypassing PcVue and generating HDS import files.

This tool only supports proprietary ASCII archiving units whose date format is expressed in expressed in UTC with the following syntax: yyyyMMddThhmmss.lllZ

How it works :
1) each “data” file in the source directory is read
2) trend and log tags are interpreted
3) a trend export file is generated if at least one trend exists
4) an export file for logging is generated if at least one logged event exists, and specified by the input parameters.
Please note: the list separator must be “ ; ” on most French OS.

Insert the path for the varexp file
Note: the varexp.dat file path is only required for exporting alarm logs.
Select “Load” to load the file
Source folder: insert the source folder where the proprietary unit is located
Target folder: Select the target where the file convert should be saved
Convert: Select convert to start the conversion

III.2- Proprietary archives in any format:

Whatever the format of the proprietary archive, PcVue itself is able to extract the data.

This chapter describes the end-to-end procedure for implementing this solution.

III.2.1. Setting up the library
The file supplied is a PcVue library which will need to be integrated into the project with access to the :

Step 1. Unzip and place the library in the project’s local user libraries.

Step 2. From the PcVue project, declare this library :

III.2.2.Export procedure

III.2.2.1.Description

The procedure uses the SCADA Basic “SVTREND” instruction to retrieve archived variable data from buffers, regardless of the read-accessible archiving format.

The procedure exports all trending variables declared in the project’s C\HISTO.dat file.

Exports take place between a start date and the current date. The start date can be configured via the @EXPORT_TO_HDSFILES.ConfigExport.StartDate variable (format DD/MM.YYYY).

As data extraction may take more or less time, it is possible to configure an extraction step expressed in days. Variable : @EXPORT_TO_HDSFILES.ConfigExport.ProcessStepInDays

Once extracted, the data is written to a CSV file in the format expected by the HDS tables. Depending on SQL Server regional options, decimal and list separators may change. The @EXPORT_TO_HDSFILES.ConfigExport.DecimalSeparator and @EXPORT_TO_HDSFILES.ConfigExport.ListSeparator variables can be used to adapt the export.

Note: maximum number of variables to export = 4000

Below is the list of internal variables:

III.2.2.2.Start export

Step 1. Open the “ExportSystemMimic” screen of the installed library:

The synoptic allows you to:
[1] Load SCADA Basic programs (“LOAD”)
[2] Create internal system variables for export (“IMPORT”)
[3] Modify export configuration (“GET CONFIGURATION”)
[4] Start and stop the export procedure
[5] Access the export directory and launch the “DB Import” tool

Step 2. To trigger the export, follow the steps below:
a) Click on “Load” to load the SCADA Basic programs
– L_EXPORT_FOR_HDS/CONFIGURATION.SCB
– L_EXPORT_FOR_HDS/EXPORT_TRENDS.SCB

b) Click on “Import” to create the variables.

The procedure triggers an XML import that can be deleted from the Smart Generator.

c) Relaunch the “ExportSystemMimic” screen: variables are displayed in the grid.
d) Set import parameters (ConfigExport branch)
e) Click on “Get Configuration” to load the configuration
f) Click on “Start” to launch export
Variables are exported one after the other to the destination directory

Step 3. Click on “Open folder” to check the arrival of the files.

III.2.3.Notes

Exporting can be a lengthy process, depending on the depth of the archive.
SCADA Basic has an infinite loop threshold which can be used to stop any program whose execution time exceeds this threshold.

Although the SVTREND instruction for retrieving archives is asynchronous, the processing of result buffers is synchronous. You must therefore ensure that the processing of a request does not exceed the threshold defined in the project (default: 30 seconds).

If necessary, you can use the parameter of the variable : @EXPORT_TO_HDSFILES.ConfigExport.ProcessStepInDays.

IV- IMPORT

DBImport can be used to inject exported files into HDS tables in the following format (for trends) :

Notes:

1) The list separator and decimal separator may vary according to OS regional options.
2) Export files must have a “.dat” extension to be taken into account by “DBImport”.

IV.1. Procedure

Step 1. Click on “Start DBImport” to launch the utility (or via the start menu).