AVEVA™ Edge 2020 R2 SP1 Patch 01 (20.0.2.1) Release Notes

Last revision: 4/13/2023

The AVEVA™ Edge 2020 R2 SP1 (20.0.2) Release Notes document is appended to the end of this document.

In This Document

Patch Installation

AVEVA System Platform Coexistence

New Features and Enhancements

Deprecated or Removed Features

Issues Resolved in This Release

AVEVA™ Edge 2020 R2 SP1 (20.0.2) Release Notes

Patch Installation

This patch is installed as a full installation. See Installation Guide below for instructions.

AVEVA System Platform Coexistence

AVEVA Edge and AVEVA System Platform both use Industrial Graphics. Because of this, AVEVA Edge 2020 R2 SP1 Patch 01 can only coexist with AVEVA System Platform 2020 R2 SP1 and AVEVA System Platform 2020 R2 SP1 Patch 01.

New Features and Enhancements

This is a summary of important features and enhancements that have been introduced in this version.

Communication Drivers

We added or significantly improved the following communication drivers in this release:

Driver

Description

IE104

Communication with devices using the IEC 60870-5-104 protocol.

This driver has been enhanced to allow the user to communicate with multiple Common addresses in the station field for the same driver instance.

 

ABCIP

Communication with Allen-Bradley Common Industrial Protocol (CIP) over Ethernet/IP for ControlLogix, FlexLogix, CompactLogix, and MicroLogix controllers.

Driver enhancements:

  • Better handling of invalid tags in the Main Driver Sheet read groups.

     

COSYS

TCP/IP and Serial Communication using PLC Handler CodeSys Library.

Driver enhancements:

  • Support for reading and writing numeric values to data types Date, TOD, and DT.
  • Updated PLC handler
  • New interface support for controllers that use Authentication

     

DNP

Communication with devices using the DNP3 protocol.

Improved reconnection logic and reduced the occurrence of timeouts.

 

MITSU

Communication with Mitsubishi FX Series devices.

This driver now supports TCP/IP and Serial Communication for the Linux runtime.

 

MQTT

Communication with devices that support Message Queuing Telemetry Transport (MQTT) protocol.

Driver enhancements:

  • Support for Azure IoT Hub and Amazon Web Services (AWS) IoT Core MQTT brokers.
  • Support for subscription/publish of UTF-8 payloads (previously ANSI).

     

TSAA

Communication with Triconex devices using the TSAA protocol over UDP/IP.

Driver enhancements:

  • Support for the Main Driver Sheet, which can automatically sort the I/O addresses and create read groups.
  • Support for Trident firmware v3.1 controllers.

     

For more information, see "Issues Resolved for Specific Communication Drivers" below.

Cybersecurity Enhancements

We continue to improve our product security posture. In particular, we have done the following:

Deprecated or Removed Features

This is a summary of features that have been deprecated or removed from this version.

Enable Enhanced Graphics

The Enable Enhanced Graphics option for Project Screens is now enabled and, in order to improve performance and security, the option to disable it has been removed. This feature provides anti-aliasing for lines, edges, gradient fills on Shapes, Text objects, and Button objects (with the exception of conical gradient fills). It also provides the ability to set opacity (Visibility property) for some screen objects. This feature is not supported in projects configured to run on the Embedded target platform.

File Import and Compatibility

In order to enhance project security, AutoCAD DXF files cannot be imported as linked external images.

Issues Resolved in This Release

This is a list of important issues that have been resolved in this version.

Issues Reported by Our Users

These are issues that were reported by our users and then logged in our customer relationship management system. If you reported an issue to us, you should have been given a case number at that time. You can look for your case number in the list below.

Please note that documentation changes are not counted as resolved issues, so if you reported an issue and it was resolved by a documentation change (e.g., by clarifying a step in a procedure), then it might not be included in this list.

Case No.

ID

Description

960102034

1441093

Symbol Flip Horizontal or Flip Vertical would not persist after closing and reopening screen.

960103901

1497309

Retentive tag values in Scheduler Worksheets were triggering a Tag Database popup when connecting to the runtime.

 

960112601

1543472

Secure Viewer intermittently failed to load the default user after an update.

960112904

1606912

The OPC UA Client connection was generating a BadWaitingForInitialData error after a reconnection.

960112904

1704166

Special characters in tags were not supported when using the built-in OPC UA Server.

960123268

1594527

OPC UA Client connections were not updating correctly to use the new connection format.

960123981

1596903

Copied grouped objects were shifting position within the group.

960129112

1632475

IDE reliability degraded after adding animation to a linked symbol.

960133491

1651012

Executing a Select Case script in the Viewer module exhibited erratic behavior.

960134402

1667736

Trend Worksheets linked with Historian were losing Store and Forward data when the runtime was restarted.

960134779

1655030

Enhanced Text Object and Animation Text Data Link resize feature in Mobile Access was applying the manually resized text to other text objects in the same screen.

 

960136561

1664648

Values entered in a Text Object were removed if the user clicked on a Combo Box after entering the values.

960137039

1667655

Mobile Access Smart Message object tag values were not updating on tag value change.

960137722

1682474

Mobile Access did not support the Binary Alarm History project setting.

960139223

1678949

Invalid members were able to be added to Class Array tags without reporting an error.

960139258

1682242

In applications running as a service, tags were not updating automatically.

960139258

1678974

Verify Project was taking too long for large projects.

960139548

1680335

Filter Expressions were not reading Time values correctly for Alarm/Event object Filters.

960141709

1716518

Mobile Access was stopping, even though STADOSVR and Studio manager were still running.

960143272

1696302

PDFCreate() was not executing properly when executed twice within a small time window.

960144651

1755384

Linked Picture objects were affecting Screen editing.

960144975

1706529

Grouped objects were not maintaining their shapes when being rotated and copied.

960146820

1733012

Trend data objects with a TXT file data source and Sort selected were not displaying data consistently using different Durations.

 

960149993

1730450

1500 tag licenses were not enabled for Embedded HMI.

960151585

1736280

Translation was not working for a Combo Box screen object using a database as Data Source.

960152167

1738912

Any missing OPC UA node generated OPC UA Client errors and required application restart.

960155273

1770952

ForceTagChange built-in function did not trigger events on Studio Manager side if the same value was set again.

960155356

1765311

Changing a service project's Startup Type caused an error.

960155407

1774936

Tag properties of tags created in AVEVA Historian by Application Server were overwritten when the trend logger saved data in AVEVA Historian.

 

960156544

1788047

Scheduled database queries were failing, sometimes halting the application.

960158055

1778192

OPC XML/DA Client did not read when ScanScreen was enabled on Mobile Access.

960161920

1801380

The screen scan mode on the Main Driver Sheet was working erratically.

960163181

1803063

Hard-coded timeouts were causing Studio Database Gateway connection timeouts when connected to the Linux runtime.

 

960163839

1808877

"(Default Rights)" was a visible selection option when enabling the Security System "Display list of users at logon" option.

 

960164788

1809471

OPC UA was throwing COpcUaClientTask::OnDataChange exception.

960165931

1819262

Thin Client setup was missing dependencies.

960168811

2112705

Crashes were happening after applying the HF 2020.2.0.42.

960172977

1859481

Class Array tags were not being validated in certain graphic screen objects.

960177154

1874027

IDE performance degraded after opening the Object Finder in the Event Logger window.

960177154

1874033

Tag Integration was causing the IDE to be unresponsive.

960177204

1873964

There was no watchdog for OPC UA tag groups.

960178652

1890614

GetSecuritySystemStatus() did not support redundant Active Directory servers.

960178652

1906105

SetPassword() was failing.

960180794

1895743

Combo box screen objects behaved inconsistently when the "Require confirmation" option was selected.

960181070

1891886

OPC UA Tag integration was not working on Embedded HMI runtime.

960184389

1906212

DBCursorGetValue() was unable to detect and report errors at execution.

960186006

1913453

The CreateUser() function did not show the the complete list of available runtime groups in the Create User dialog in an Embedded HMI installation.

 

960186713

1924802

Alarm/Event objects with Type "Alarm History" were not displaying all seven characters in the Alarm worksheet Selection field.

 

960200534

1997577

Alarm/Event objects with Type "Alarm History" were not refreshing on Mobile Access.

960205278

2024455

Changing a tag to an array was causing problems in alarm and trend sheets.

960206247

2026990

Studio IDE shows artifacts of transparent color specified by Transparency Tracker on bmp files.

960210897

2044748

Hardkey license was not recognized if another USB dongle for licensing of 3rd party software was attached to the USB hub/port replicator.

 

960222794

2149174

MS SQL Server 2019 Express timestamps were incorrect.

960232071

2157531

PanelBuilder32 Import Wizard was not importing the Alarms worksheets to the project.

960233607

2176370

Auto Log off feature stopped working when the cursor was left outside the screen where LogOn() function was called.

 

960263713

2329033

Momentary button was launching E-Sign feature when the user did not have permissions to display this feature.

N/A

1613738

StudioTabBar.ocx was not working on AVEVA Edge 2020 R2.

N/A

2172169

AVEVA Insight Publisher included with 2020 R2 SP1 was outdated.

N/A

2186213

AVEVA Edge 2020 R2 SP2 was unable to switch the Insight Publisher storage mode from StoreForward to Server after restarting the runtime.

 

N/A

2348630

Event logging was not working as documented.

Issues Resolved for Specific Communication Drivers

These are the issues that were resolved for specific communication drivers.

Case No.

ID

Description

0002179841

583606

TSAA driver did not support Trident PLCs Firmware v3.1 CIM 3211 Comm Modules, and had slow communication due to smaller read block size.

 

960035991

1633552

TI500 driver had stability issues and driver logs were incomplete.

960076816

1292850

MQTT driver did not support Azure IOT Hub and Amazon Web services IOT Core MQTT brokers.

960082121

1354047

DNP driver stopped communicating with fast changing values when using continuous reads for MONITOR events.

960103571

960215285

 

1471502

2063779

COSYS driver did not support Authentication required by controllers that have embedded security management configured.

 

960106829

1527207

MOTCP driver did not show correct precision for floating point values.

960107712

1502031

ABCIP Tag Integration failed when there were structures with unsupported or invalid members.

960108385

1506164

OMRON Tag Integration continuously refreshed when verifying the application, creating duplicate classes with different StructureName properties for the imported tags.

 

960109588

1503498

SNMP driver failed when there were invalid items in a read group.

960111116

1512680

MQTT driver when using Sparkplug failed when exceeding 80 tags.

960117727

1591495

SCHNE driver was not able to correctly communicate with TOD datatype arrays with overlapping (drift) values.

960120016

1593504

CODESYS Tag Integration did not show Enumeration type variables when using Symbol File Browsing (Offline).

960124628

1631832

MQTT driver stopped requesting values for fast changing data on the broker and eventually stopped communication.

 

960129901

1804357

TI500 was not able to consistently reestablish connections.

960136124

1662656

ABCIP driver in physical mode was reading and writing to invalid array indexes.

960140258

1687602

COSYS and SOMAC drivers were reading incorrect values for Enumeration type tags.

960140264

1687393

ABCIP driver did not create groups for string tags correctly.

960144436

1730279

MELSE driver on Linux runtime did not communicate when there were two or more PLC stations on the main driver sheet.

 

960146100

1725158

TWCAT Tag Integration was not correctly parsing tags when there were some invalid tags.

960146359

1710667

MELSE driver was not correctly reading from and writing to bits of word registers.

960148214

1733097

SIETH and SITIA secure PG/PC and HMI communication option was not documented.

960148279

1717513

OMETH driver on Linux runtime was not able to communicate correctly and always returned Status Code "-15".

960149236

1736303

In ABCIP physical mode, string tags that expected Date and Time values were reading "0".

960150498

1731502

OMETH driver on Linux runtime printed out debug trace messages to the log.

960150512

1731513

OMETH driver halted Linux runtime on devices with x86 architecture.

960155494

1775829

MQTT driver was not correctly reading Arabic strings.

960156831

1789107

SNMP driver was not communicating correctly with secure and authenticated SNMP v3 devices.

960167935

1838041

SCHNE driver did not correctly read or write to boolean members of structs with mixed data types.

960193313

1964247

IE104 driver did not support multiple Common Addresses on Station for a single driver instance.

960218827

2088565

MELSE driver failed to write to consecutive PLC addresses when using group write.

960218844

2099465

MELSE driver gave a -39 INVALID BLOCK SIZE error when using mixed datatypes including strings.

960221257

2112410

TI500 driver crashes when it tries to write to multiple PID Loop Items, for example LTD1, LTI1, and LKC1.

960230642

2158239

OMETH driver did not correctly read chinese characters when using GB2312 encoding.

960241290

2204046

MACHA driver generated unexpected messages in Machine Advisor.

N/A

584623

MOTCP driver could not read or write strings of 82 or more characters.

N/A

1996079

OMETH driver was not validating source node number on Windows or Linux runtimes.

N/A

2036341

2047710

 

MQTT 'Write Status', 'Write Completed', and 'Read Status' were not functioning correctly.

AVEVA™ Edge 2020 R2 SP1 (20.0.2) Release Notes

Last revision: 2021-11-18

How to Find the Latest Product Requirements and Compatibility Information

For important information about this product release, go to the AVEVA Global Customer Support (GCS) website. Information on the GCS website includes product requirements, compatibility, as well as downloads from previous releases. After you log in, you can filter search results by product name and the release/version.

AVEVA Edge Is Compatible Only with the Current Version of AVEVA System Platform

AVEVA Edge 2020 R2 SP1 is compatible only with AVEVA System Platform 2020 R2 SP1, because the Industrial Graphics feature in AVEVA Edge 2020 R2 SP1 uses some of the same components that are used by System Platform. If you want to install AVEVA Edge 2020 R2 SP1 on the same computer, you must either uninstall the previous version of System Platform or upgrade it to the current version.

New Features and Other Enhancements

This is a summary of important features and enhancements that have been introduced in AVEVA Edge 2020 R2 SP1.

This is not a comprehensive list of all enhancements.

Standardized Names for Software Components

We standardized the names of several of the components that make up our software:

Component

Name

Project Development Environment

Studio

Runtime for Windows and Windows Server

SCADA

Runtime for Windows Embedded Standard

Embedded HMI

Runtime for Windows Embedded Compact

Compact HMI

Runtime for Linux

IoT View

Communication Drivers

We added or significantly improved the following communication drivers in this release:

Driver

Description

MACHA

Communication with EcoStruxure™ Machine Advisor, which is Schneider Electric’s cloud-based platform. It enables machine builders to access, manage, and analyze machine data. The driver has been added for both SCADA and IoT View.

ROC

Communication with Emerson Remote Operations Controller (a.k.a. ROC Series). The driver has been added for both SCADA and IoT View.

ADPRO

Communication with AutomationDirect's Productivity Series devices. The driver now supports custom ports and Extended CSV files in both driver worksheets and tag integration.

KOYO

Communication with AutomationDirect's DirectLogic devices (a.k.a. DL Series). The driver now supports custom ports in both driver worksheets and tag integration.

OMRON

Communication with OMRON devices using the FinsGateway and/or SYSMAC Gateway. Along with the driver itself, the Tag Integration and Import Wizard features have also been added.

Please note the OMRON driver and its associated features are available only if you have purchased the appropriate license option and installed some additional files that are not normally included with this software. If you have not done so, these features will not work during project run time. For more information about the license option and additional files, or to ask about other communication drivers that might support your OMRON devices, contact your software distributor.

For more information, see "Issues Resolved for Specific Communication Drivers" below.

Improved Support for Mobile Access

We continued to improve support for our Mobile Access feature, which lets you use any HTML5-compatible browser to view project screens. More screen objects and built-in functions now work with Mobile Access, and the objects and functions that worked before work even better now. In particular, we have done the following:

We also continued to improve the Mobile Access web interface, similar to how we have updated the user interface (UI) for the project development environment.

Please note that Mobile Access is intended to be the next-generation replacement for our traditional, ActiveX-based thin clients. We recommend you update your projects to take advantage of Mobile Access, if you have not already done so.

Improved Version of IoT View

We continued to improve IoT View, the project runtime for Linux-based embedded devices. In particular, we have done the following:

Domain (LDAP) Security Mode

We replaced the existing Domain (LDAP) security mode with a new Local Plus Domain (LDAP) security mode, which changes how local groups and users are combined with domain groups and users. Also, we significantly improved the overall usability and performance of the mode. This includes the following:

Other Enhancements

Deprecated or Removed Features

This is a summary of features that have been deprecated or removed in AVEVA Edge 2020.

Support for Wibu-Systems Dongles on Windows Embedded Compact

Due to changes in the driver software, we can no longer support the use of Wibu-Systems dongles (a.k.a. hardkeys) to license the Compact HMI runtime for Windows Embedded Compact. There are two possible alternatives:

If neither of these alternatives are feasible for you, you should not upgrade to this version of AVEVA Edge.

Mixed Mode Cache

As part of the changes in the Domain (LDAP) security mode, the Mixed Mode Cache option has been removed. The functionality of that option is effectively included in the new Local Plus Domain (LDAP) security mode. For more information, see "New Features and Other Enhancements" above.

Issues Resolved in This Release

This is a list of important issues that have been resolved in AVEVA Edge 2020 R2 SP1. This is not a comprehensive list of all resolved issues.

Issues Reported by Our Users

These are issues that were reported by our users and then logged in our customer relationship management system. If you reported an issue to us, you should have been given a case number at that time. You can look for your case number in the list below.

Please note that documentation changes are not counted as resolved issues, so if you reported an issue and it was resolved by a documentation change (e.g., by clarifying a step in a procedure), then it might not be included in this list.

The ID is for internal use only.

Case No.

ID

Description

951185477

50253

Improved error message when service installation fails.

951188868

960059104

53925

Enhanced the Find/Replace Document Replace tool to replace tag names and other texts in Linked Symbol custom properties.

960005234

59755

Improved Security System to only notify a user once when attempting to access a screen without the necessary rights.

960005916

960058717

59756

Resolved issue with rotated Linked Symbols drifting after screen save.

960010464

63001

Enhanced the Embedded View runtime edition for Windows Embedded Standard so that it shows the correct connection status with the AVEVA Historian.

960012585

61559

Enhanced OPC UA Client by providing a dialog to choose what certificate errors to ignore when connecting to an OPC UA Server with known certificate issues.

960012644

59757

Removed unexpected characters from Logon and Logoff event messages for Japanese.

960022731

61664

Improved virtual keyboard usability by eliminating unexpected blinks when clicking keys.

960024645

60690

Enhanced the Support Information dialog box to show the License ID of the remote station.

960025715

61911

Improved Secure Viewer when loading screens while using the universal naming convention for a file shared over the network (e.g. \\server\folder\application.app).

960026857

61445

Enhanced StdSvcInst.exe so the service name is consistent with Studio and can successfully uninstall the service when created by Studio.

960030516

62044

Improved the Grid object to respect the SetDecimalPoints() built-in function when using the Virtual Keyboard.

960031282

62812

Improved Alarm/Event Control object refresh when alarms are configured to blink on specific situation.

960032065

960040652

63470

Enhanced the Compact HMI runtime edition for Windows Embedded Compact to support the SaveScreenShot() built-in function.

960032219

62666

Enhanced Mobile Access trend control so that data is loaded when "Save on trigger" is configured as Minute

960036018

62045

Improved the SetPassword() built-in function return value when the user name does not exist when using Remote Security System.

960036138

63278

Improved Indirect Tags so that Tags configured as "Screen" scan consistently update when switching between popups.

960037143

62925

Added support for configuring custom colors for alarm messages on the Alarm/Event Control object for Mobile Access.

960038073

62781

Enhanced Alarm/Event Control object "Search in columns" filters to behave the same way for Database and Proprietary history formats

960041850

63477

Improved the GetUTC() built-in function so that the return values are consistent.

960042463

63280

Improved connection management of Database/ERP worksheet using ODBC Connection so that users can open the MS Excel while the Database/ERP task or the Studio Database Gateway is running.

960043731

63114

Enhanced Mobile Access to support rotation of static text, as configured in the project development environment.

960043756

63131

Enhanced Mobile Access so that Grid column "Label" can be named as "ID".

960044110

63474

Improved access control so that only access granted users can change the start screen of a project if the security system is enabled.

960044913

63341

Modified the way the OPC UA modules handle time stamps to use the Source time stamp.

960045191

63130

Improved the Project Explorer tree view so that you can delete worksheets and screens when Industrial Graphics is not installed.

960045565

63170

Improved scalability of Report templates by removing the size limitation.

960045683

63142

Improved Custom Widgets so that they can be loaded in runtime when they are created on a new blank project.

960046873

63331

Improved the OPC HDA Server runtime task so that it starts properly.

960049868

64748

Enhanced the Mobile Access runtime task so it successfully starts when using Data Protection and History Format is set to "Database".

960050462

64256

Improved the Paste feature in worksheets to support internationalization.

960050852

64625

Improved stability of runtime.

960051401

63759

Improved reliability of OPC UA Client when "Ensure cache synchronization" is disabled

960051538

65898

Added support for resizing text object in Mobile Access.

960052201

63762

Improved OPC UA Client internationalization so that it supports comma separated decimal values.

960056133

64483

Improved OPC UA Server task reliability so that is sends the tag's current value once the subscription is reestablished.

960056193

64510

Improved TCP/IP Client worksheet so that it can read all the configured tags from the remote TCP/IP Server task.

960056693

64487

Improved DB Connection management so that you can set the connection string in the Startup Script.

960057423

65737

Improved the SetAppHstPath() built-in function so that it can be called from Startup Script.

960059524

65071

Improved Thin Clients so that Tag Values are updated when toggling Tag Properties from B0 to B31 from another Thin Client.

960062779

59315

Enhanced Mobile Access to support auto logoff.

960063261

65156

Improved Trend task reliability when multiple objects attached to the default database have connection errors.

960069576

66838

Improved scripts configured on the Graphics Script, Graphics_OnEnd() procedures, to execute when the user closes the runtime through one of the background tasks.

960072118

66076

Enhanced the Format() built-in function so that returned numbers are formatted as expected.

960072118

68996

Enhanced the Format() built-in function so that returned numbers are formatted as expected, without adding an unexpected leading zero, when the decimal value is less than 0.

960073005

67375

Improved Alarm and Event Control object filters to support '*' as a wildcard.

960074369

69918

Resolved issue with the Command animation, with the "On While" not working properly in certain specific conditions.

960074592

66736

Improved Mobile Access module, when running on Windows Tablet mode, so that focus is set on the "Password" field when the Logon page was displayed.

960078423

66544

Resolved issue with the RDFIleN() built-in function not working properly on Web Thin Clients, more specifically when clicking on the "Close" system button.

960078770

67301

Improved stability of the Trend Control object when the user configured a Tag property as one of the pens.

960079301

68469

Enhanced TreeView custom widget with a new onLoadSettings Event that is triggered when the settings are loaded and the treeview is created.

960081629

66814

Improved the TagsDBGetClassMember() built-in function so that it returns the expected value when a class member does not exist.

960083908

69556

Enhanced OPC UA Client so that self-signed certificate RSA Key size can be specified.

960093842

69147

Resolved issue with the Trend task that was generating some duplicated records in certain specific situations.

960099053

67848

Improved the Alarm task startup performance on IoT View.

960099054

67926

Resolved issue with the WriteOutOfRange() built-in function not working as expected when the tag was being used in a communications driver in IoT View.

960100841

68572

Enhanced Mobile Access to support "|" character in the alarms message.

960102371

70285

Improved cookie size when running Industrial Graphics screens.

960102667

69962

Improved text bottom alignment in Industrial Graphics so that all content is displayed.

960112903

69503

Enhanced Alarm worksheet field called Total Unack not being calculated correctly in some circumstances.

960123222

70553

Corrected LogWin so that information is logged without requiring runtime service to be restarted.

Issues Resolved for Specific Communication Drivers

These are the issues that were resolved for specific communication drivers.

Case No.

ID

Description

1475230

583664

Fixed issue of Schneider Electric tag integration not opening on the Object Viewer when the .XSY file contains a tag with any of its element descriptions missing.

2267077

585807

Added support for custom communication ports when using the KOYO tag integration.

960005518

1227786

Fixed an issue with the MOTCP driver crashing IoT View when the device is disconnected.

960007171

548215

Added support for custom communication ports when using ADPRO tag integration; the ports can be defined as part of the station field.

960008106

562128

Improved the OMRON driver to handle the exception thrown when using Write Trigger on Standard Driver Sheets.

960010169

574560

Enhanced the ADPRO driver to support Extended CSV files during driver commuication and when using ADPRO tag integration.

960032053

829205

Fixed an issue with the SCHNE driver showing invalid block error when communicating with boolean bits of Word-type tags.

960035511

1050710

Fixed an issue with TXRX driver reconnection not handling ungraceful disconnects with the device.

960037135

834968

Fixed an issue in the SRTP driver not reading arrays correctly in Symbolic mode.

960038952

916423

Fixed an issue with the KOYO driver not closing UDP communication ports when the connection to the device is lost.

960040527

1044945

Fixed an issue with the TI500 driver not showing the correct local timestamp for Alarm objects during communication.

960040542

859598

Fixed an issue with the TWCAT driver not showing the correct local date and timestamp for tags during communication.

960042813

860335

Fixed a corruption issue on the ABCIP driver connection when communicating with more than 390 integer type bit addresses.

960044143

923044

Fixed an issue with the SCHNE driver creating invalid blocks when using tag integration reading incorrect values for the items.

960050130

1000673

Fixed an issue with the SRTP driver showing "Error Malformed Packet" when using both symbolic and physical addresses from the same PLC.

960053876

1281011

Fixed an issue with MQTT driver not managing reconnections to the broker when using Standard Driver Sheets.

960055387

1052274

Enhanced the MQTT driver to support group writes when using Store and Forward.

960055817

1055335

Fixed an issue with the RSLogix 5000 tag integration not correctly processing some large .L5K files.

960059928

1124167

Fixed an issue with the SCHNE tag integration causing run-time crashes when the .XSY file includes arrays of String-type tags.

960067659

1225072

Upgraded the SNMP driver API to fix vulnerabilities that caused run-time crashes.

960084226

1372173

Fixed MODBU documentation alignment to show correct information in tables.

960101497

1440848

Fixed an issue with the RSLogix 5000 tag integration where it was unable to retrieve multi-dimensional arrays.

N/A

584620

Fixed an issue on the TWCAT driver unable to commuicate with multiple PLCs when running on Windows Embedded.

Other Issues Resolved During Development

These are other issues that we identified and resolved during product development.

Type

ID

Description

Feature

50350

Added support for on-premise AVEVA Historian for IoT View.

Feature

61964

Created new Machine Advisor communication driver (MACHA) that provides connectivity to Schneider Electric's EcoStruxure Machine Advisor.

Feature

62243

Enhanced IoT View to support Trend decimation.

Feature

62244

Added support for NGINX and Lighttpd web servers as part of the IoT View install script.

Feature

64267

Improved encrypted communication so that TCP Server only uses TLS 1.2 and higher cypher suites

Feature

64268

Enhanced TCP Server so that Fully Qualified Domain Name is supported on the Server's certificate Subject Alternative Name Field.

Feature

64274

Added support for LDAP in IoT View.

Feature

67807

Added support to new built-in function OpcUaBrowseToJson() for Viewer and Mobile Access.

Feature

1527388

Added support for custom serial ports when using the MELSE and OMETH drivers. This allows for serial communication on all runtime platforms.

User Story

55247

Improved the SetAppHstPath() built-in function so that it no longer requires restarting the runtime to take effect, when running in Embedded HMI.

User Story

60112

Improved IoT View so that Alarm/Event control on Mobile Access shows the expected Alarm group color, Alarm State and Previous Value.

User Story

60511

Improved the stability of the TCP/IP Server when using LDAP.

User Story

61641

Enhanced IoT View Remote Agent to only send incremental new files to the remote device.

User Story

61658

Enhanced IoT View to support Custom Widgets.

User Story

61812

Improved Quick Access Toolbar to display the appropriate icon for the Archive feature.

User Story

61833

Enhanced LogWin with support for TCP/IP Messages advanced settings.

User Story

62267

Added support for the ForceTagChange() built-in function in IoT View and Mobile Access.

User Story

62295

Modified the IoT View installation and configuration to allow both the remote agent and the project runtime to run with a non-root user.

User Story

62332

Added NGINX web server support for Mobile Access in IoT View.

User Story

62506

Enhanced Mobile Access Alarm/Event Control object to support alarm groups when running over IoT View.

User Story

62552

Enhanced IoT View Driver Engine to support station fields longer than 80 characters.

User Story

62898

Enhanced StudioManager to load the associated user profile when running as a service.

User Story

63182

Enhanced PanelMate Import tool to support the import of array tags.

User Story

63592

Enhanced IoT View to support tag dead band property.

User Story

64961

Implemented the option to disable the Status Check Connection for Database features.

User Story

65649

Added support for the Dead Band configuration in Trend worksheets for IoT View.

User Story

66195

Added support for the Total Alarms and Total Unack advanced fields of the Alarm worksheet for IoT View.

User Story

66281

Improved Studio Database Gateway connection management to prevent closing connections that are in use.

User Story

66287

Added support for the Lighttpd web server for Mobile Access.

User Story

66292

Implemented the Account Lock-up feature on IoT View and Mobile Access.

User Story

66293

Implemented support for the UnblockUser, BlockUser, and GetUserState built-in functions for IoT View and Mobile Access

User Story

66361

Improved the CreateUser() built-in function so that it shows Groups when running on Windows Embedded.

User Story

66379

Improved performance of Symbol Library navigation.

User Story

66549

Modified the GetIPAll() function signature displayed on the Object Finder window so it no longer includes an obsolete parameter.

User Story

66723

Improved Screen Groups so that a Screen Group can open during project run time when at least one of the screens has a dot as part of the screen name.

User Story

66818

Improved error message when Mobile Access is restarting and one tries to stop the Runtime.

User Story

66982

Improved Grid usability so that data is not saved when "Save on data change" option is disabled and you navigate to another screen.

User Story

66984

Added support for the "Scan" parameter configured on the OPC UA Client worksheets for Mobile Access.

User Story

67173

Improved stability of Studio when running as a Windows Service.

User Story

67438

Improved LDAP so that the locked users query returns a complete list of locked users.

User Story

67512

Modified the Viewer runtime module to properly retrieve the Alarm, Event, and Trend information after the SetAPPHstPath() or SetAppAlarmPath() are called.

User Story

67998

Enhanced IoT View so that alarm enable and disable functions as documented.

User Story

68194

Improved reliability of the Embedded HMI runtime edition for Windows Embedded Standard when using Database Gateway.

User Story

68245

Enhanced the Grid Control for Mobile Access to hide the grid column when the grid column width is 0.

User Story

68442

Added support for the Dead Band configuration in Trend worksheets for IoT View.

User Story

68497

Enhanced IoT View Remote Agent to only send incremental new files to the remote device.

User Story

68885

Added support for the Total Alarms and Total Unack advanced fields of the Alarm worksheet for IoT View.

User Story

68887

Enhanced IoT View Remote Agent to only send incremental new files to the remote device.

User Story

69005

Improved TCP Sheet reliability so that all tags are updated.

User Story

70287

Enhanced Mobile Access to allow user input to text boxes even when using Industrial Graphics screens.

Defect

62790

Improved the Keypad() built-in function in Mobile Access to show the current tag value when the Keypad is open.

Defect

62791

Improved the return value of DBCursorGetValue() built-in function on Mobile Access when receiving NULL values from the Database.

Defect

62792

Improved internationalization of virtual keyboard to support other languages than English.

Defect

63107

Enhanced OPC UA client to persist the "automatically add server certificate to certificate store..." configuration

Defect

63231

Improved reliability of IoT View Remote Agent download so it does not time out during long running operations.

Defect

63615

Improved IoT View stability when using MQTT with group writes enabled.

Defect

64838

Improved Mobile Access Grid object so that you can scroll when a line is selected.

Defect

65207

OPC UA Client can read the value of the tag used to define the connection URL.

Defect

65900

Improved scalability of Mobile Access Trend object when loading multiple pens with a large count of points.

Known Issues and Workarounds

This is a list of known issues that remain in AVEVA Edge 2020 R2 SP1, with appropriate contingencies and workarounds.

This is not a comprehensive list of all known issues.

ID

Description

1631020

Issue: Some communication drivers (e.g., MOTCP) have not yet been improved to support long strings, which means they are limited to 81 characters per read operation.

Workaround: Divide long strings into shorter strings of 81 characters or less per string, and then store those shorter strings in multiple device registers.

N/A

Issue: Text Box objects are drawn incorrectly in project screens that are viewed through Mobile Access.

This might be due to scaling of the user interface in AVEVA Edge. As computer displays have achieved higher resolutions, operating systems have implemented UI scaling to ensure that text, apps, and other items are displayed large enough to be usable. However, this UI scaling can affect the behavior of some apps, especially those that include drawing or rendering functions.

Workaround:

Exit AVEVA Edge.

Go to the Display control panel in Windows, and then make sure Scale and layout is set to 100%.

Run AVEVA Edge.

Save your project screens as HTML, and then test your project again.

If the issue persists, restart your computer to make sure the scale is applied correctly.

Installation Guide

This is a brief guide to installing AVEVA Edge 2020.

Upgrading from a Previous Version

If you are upgrading to AVEVA Edge 2020 R2 SP1 from a previous version, please note the following recommendations.

You can have more than one major version of AVEVA Edge installed on the same computer, because each major version is installed in its own appropriately named program folder. For example, this major version is AVEVA Edge 2020, so by default it is installed in the following location on your hard drive:

C:\Program Files (x86)\AVEVA\AVEVA Edge 2020

Many users keep a previous major version installed on their computer while they become familiar with the changes in the latest major version. You can run only one version at a time, however, so you should remove the previous version when you no longer need it.

You cannot have more than one minor version of AVEVA Edge installed on the same computer. A major version includes all of its minor versions — i.e., its subsequent updates, patches, and hot fixes — and they are all installed in the same location on your hard drive.

If you already have AVEVA Edge 2020 installed on your computer and you want to update it to its latest minor version, we actually recommend that you remove the software from your computer and then use the latest installer to perform a clean installation. Removing the software will not affect your software license, and it will not modify or remove your projects folder, so there is no risk in doing this. To remove the software, you can use the Apps & features control panel in Windows. You can also use the Modify, Repair, Remove feature in the previous version's installer, if you still have it on your computer.

Note: The preceding paragraph applies only to updates and patches. It does not apply to hot fixes, which are distributed with specific instructions and only under special circumstances.

When you upgrade from a previous major version to the latest major version, you also need to upgrade your software license(s). To purchase a license upgrade, contact your AVEVA Edge software distributor. To apply that upgrade to the software, use the Protection Manager utility that is installed with the software (Start > AVEVA Edge 2020 > AVEVA Edge 2020 Register). For more information about licensing, see AVEVA Edge 2020 Help Manual.

If you do not upgrade your software license(s), you can still run the software in its full-featured Evaluation Mode for up to 40 hours. After that time expires, however, you can only run the software in its limited Demo Mode.

When you update a major version to its latest minor version, you do not need to update your software license(s). The license is for the major version, so it includes all of the subsequent updates, patches, and hot fixes for that major version.

Finally, when you open an existing project for the first time in a new version of AVEVA Edge, that project is automatically and permanently updated to the new version. This is true regardless of whether you have upgraded your software license(s). Therefore, you should back up your existing projects before you open them in the new version. Each major version of the software creates a corresponding projects folder (e.g., AVEVA Edge 2020 Projects) in your user directory, so you can simply copy (not move) your projects from the old projects folder to the new projects folder.

System Requirements

This section describes the system requirements and additional considerations for installing AVEVA Edge 2020.

Requirements to install and run the full AVEVA Edge software:

We recommend the "Pro" and "Enterprise" editions of Windows, because they include Internet Information Services (IIS) as a pre-installed feature that can be turned on. You can use IIS to make your projects accessible to thin clients and mobile devices. Do not use the "Home" and "Education" editions of Windows, because they hide or disable many features.

Only Windows 10, Windows Server 2016, and Windows Server 2019 are under what Microsoft calls "mainstream support", which means they are actively maintained and additional service packs might be released for them in the future. Windows 8.1 and Windows Server 2012 R2 are under what Microsoft calls "extended support", which means they are no longer actively maintained. For more information, go to: https://docs.microsoft.com/en-us/lifecycle/faq/windows

You can install the full AVEVA Edge software on a Windows Embedded Standard device, as long as it meets the system requirements listed above, but if you do not plan to develop projects on that device then you should install Embedded HMI instead. Embedded HMI is the runtime edition for Windows Embedded Standard. For more information, see AVEVA Edge 2020 Help Manual.

Regardless of which version or edition of Windows you are using, update it before you install AVEVA Edge. Updating Windows installs all of the latest security fixes and system components.

The operating system, storage, and memory requirements will necessarily increase for larger projects; the minimum requirements listed above are only for projects of up to 4,000 tags. The following table shows the complete requirements:

Project Size

Operating System

Storage

Memory

up to 4,000 tags

Windows, Windows Server, Windows Embedded Standard

2 GB available

1 GB available

up to 64,000 tags

Windows, Windows Server

4 GB available

2 GB available

up to 10 million tags

Windows Server only (multi-core)

8 GB available

4 GB available

Your computer needs to meet only the minimum requirements when you first install the software and begin to develop your project, but the requirements will increase as your project grows. Furthermore, every other Windows computer on which you plan to run your project needs to meet the same requirements.

The following items are optional but recommended:

Finally, you need to have administrator privileges on your computer in order to install any software. If you are not already signed on as a user with administrator privileges when you run the AVEVA Edge 2020 software installer, you can choose to run the installer as an administrator: right-click the installer program file (setup.exe), and then on the shortcut menu, click Run as administrator. You will be asked for the appropriate user name and password.

.NET Framework

You need to have both .NET Framework 3.5 and .NET Framework 4.8 (or later) turned on in order to install and run AVEVA Edge 2020 R2 SP1.

If Windows is fully updated on your computer then the latest versions of .NET Framework should be installed already, but they might not be turned on. In fact, in recent versions of Windows and Windows Server, .NET Framework 3.5 is turned off by default. Use either the Windows Features control panel in Windows, or the Server Manager console in Windows Server, to confirm that both versions of .NET Framework are turned on before you install the software.

In some cases, it might not be possible to keep Windows fully updated through normal means. For example, if your computer is on a private network without access to the Internet, it might not be able to contact the Windows Update service. You can use another computer to download an offline installer for .NET Framework 3.5 and then copy it to your computer.

For more information about how to install and/or turn on .NET Framework 3.5, go to: https://docs.microsoft.com/en-us/dotnet/framework/install/dotnet-35-windows-10

For more information about .NET Framework in general, go to: https://docs.microsoft.com/en-us/dotnet/framework/index

Selectable Features

On the Select Features page of the AVEVA Edge 2020 R2 SP1 installation wizard, you can select which features and software components to install. If you deselect features that you know you will not use, you will decrease the amount of hard drive space required for installation.

Feature

Description

Program Files

The main program files for the project development environment, the project runtime software for Windows and Windows Server, and the thin client software for viewing project screens.

You cannot deselect this feature.

Custom Widget Framework

Additional software that is required to develop HTML5-based widgets and then use them in project screens.

You cannot deselect this feature.

AVEVA Historian

Additional software that is required to save historical data from your project to an external database, such as AVEVA Historian.

If you want to use this feature in your project, you must have .NET Framework 4.8 (or later) installed and turned on.

BDE for PanelMate™ Import Wizard

Borland Database Engine (BDE), which is required to import a PanelMate Plus or PanelMate Power Pro program into a new project.

This feature is not selected by default, because it is used only in some cases.

Demo Projects

Pre-made projects that demonstrate the capabilities of AVEVA Edge.

Hardkey Support

Additional software that supports the use of Wibu-type hardkeys (a.k.a. dongles) with AVEVA Edge. You may deselect this feature if you are using either Sentinel-type hardkeys or softkey licenses. For more information, see "Third-Party Software Installed with AVEVA Edge" below.

Industrial Graphics

The Industrial Graphics editor and symbol library, which works as a companion to our native graphics tools.

Mobile Access Runtime

Add-on software for Internet Information Services (IIS) that lets you use HTML5-compatible browsers to view your project screens. If you select this feature, the installer will try to confirm that IIS is installed and turned on in Windows, and if it is, the add-on software will be installed.

Regardless of whether you select this feature for installation, a separate Mobile Access Runtime software installer (MobileAccessSetup.exe) will be copied to your AVEVA Edge 2020 program folder. You can run that installer at a later time.

OPC Components

Additional components that are required for communication with other OPC-compatible devices. This includes OPC DA (a.k.a. OPC Classic), OPC XML-DA, and OPC UA.

PDF Printing

Additional software that lets AVEVA Edge projects save run-time reports as PDF files.

Runtimes – Additional > IoT View

This is the platform-agnostic project runtime software for Linux and other operating systems.

Selecting this feature will not actually install IoT View on your computer at this time. It will only copy the installation files to your AVEVA Edge 2020 program folder, so that you can install IoT View on another computer or device at a later time.

Runtimes – Additional > Windows Embedded Standard

Also called Embedded HMI, this is the project runtime software for Windows Embedded Standard computers.

Selecting this feature will not actually install Embedded HMI on your computer at this time. It will only copy the installation files to your AVEVA Edge 2020 program folder, so that you can install Embedded HMI on a Windows Embedded Standard computer at a later time.

Runtimes – Additional > Windows Embedded Compact

Also called Compact HMI, this is the project runtime software for Windows Embedded Compact devices. Check the manufacturer's documentation for your device to see which processor it uses.

Selecting this feature will not actually install Compact HMI on your computer at this time. It will only copy the installation files to your AVEVA Edge 2020 program folder, so that you can install Compact HMI on a Windows Embedded Compact device at a later time.

Symbol Library

A large library of pre-made but customizable screen objects such as pushbuttons, toggle switches, gauges, dials, and indicator lights.

Items Added to the Start Menu

This is a list of the items that are added to your Start menu during the installation of AVEVA Edge 2020.

Item

Description

AVEVA Edge 2020 Help Manual

A complete technical reference and user guide for AVEVA Edge and its components.

AVEVA Edge 2020 Quick Start Guide

A brief, printable guide to the project development environment, including a step-by-step tutorial for how to develop and deploy a simple project.

AVEVA Edge 2020 Register

A utility program that you can use to view and change your software license settings.

AVEVA Edge 2020 Release Notes

The document that you are reading now.

AVEVA Edge 2020 Remote Agent

A utility program that lets other stations remotely manage the project runtime when it is running.

AVEVA Edge 2020 SCADA

A shortcut that automatically runs the most recently opened project.

AVEVA Edge 2020 Studio

The project development environment, project runtime and/or project viewer. Its actual capabilities are determined by your software license settings.

The software installer also creates a shortcut for AVEVA Edge 2020 Studio on your desktop.

Third-Party Software Installed with AVEVA Edge

When you install AVEVA Edge 2020 R2 SP1, some third-party software components are installed with it in order to support its operations on your computer.

You may see that some or all of the following items have been added to the Apps & features control panel in Windows. Do not manually remove any of these items until after you have removed AVEVA Edge 2020.

Item(s)

Description

Microsoft Visual C++ Redistributable (multiple versions)

These items are required to run C++ applications that were developed using Visual Studio. Several different versions (e.g., 2012, 2013, 2015–2019) may be installed.

Do not remove these items even after you remove AVEVA Edge, because they may be used by applications other than AVEVA Edge.

novaPDF SDK 10 Printer Driver

novaPDF SDK 10 COM (x64)

novaPDF SDK 10 COM (x86)

Studio PDF3

These items let AVEVA Edge projects save run-time reports as PDF files. They are installed when you select the PDF Printing feature for installation; for more information, see "Selectable Features" above.

Sentinel Protection Installer 7.6.9

This item supports the use of Sentinel-type hardkeys (a.k.a. dongles) with AVEVA Edge. It is always installed regardless of whether you select the Hardkey Support feature for installation; for more information, see "Selectable Features" above.

CodeMeter Runtime Server

When you select the Hardkey Support feature for installation, Wibu Systems' CodeMeter Development Kit is installed on your computer. It supports the use of Wibu-type hardkeys (a.k.a. dongles) with AVEVA Edge.

Wibu-type hardkeys are offered as alternatives to Sentinel-type hardkeys. For more information about the differences between Sentinel and Wibu, ask your software distributor.

Unlike the other items described above, CodeMeter Development Kit is not added to the Apps & features control panel in Windows. Instead, it runs as a background process called CodeMeter Runtime Server, which you can find in Task Manager.

When you remove AVEVA Edge from your computer, CodeMeter Development Kit is also removed automatically.

Possible Issues During Installation

This section describes issues that might occur during the installation of AVEVA Edge 2020 R2 SP1.

"Failed to complete script based install"

You might receive the following message during installation: "Error 1628: Failed to complete script based install." For more information about this issue and how to resolve it, go to: https://community.flexera.com/t5/InstallShield-Knowledge-Base/Error-1628-Failed-To-Complete-Script-Based-Install/ta-p/4014

"CodeMeter Development Kit is already installed"

If you try to install an earlier version of AVEVA Edge on a computer that already has a later version installed, you might receive the following message during installation: "Version x.x.x.x of CodeMeter Development Kit is already installed. Downgrading to Version x.x.x.x is not possible, installation will be aborted." CodeMeter is supplemental software used by AVEVA Edge to manage hardkey licenses. To resolve this issue, use Task Manager in Windows to stop CodeMeter Runtime Server (CodeMeter.exe) before you install the earlier version of AVEVA Edge.

"The local print spooler service is not running"

If you select the PDF Printing feature for installation but the Print Spooler service is not running on your computer, you might receive the following message during installation: "The local print spooler service is not running. Please restart the spooler or restart the machine." You can click OK to acknowledge the message and finish the installation, but the PDF Printing feature will not be installed correctly. To resolve this issue, do the following:

  1. Use the Services app in Windows make sure the Print Spooler service is running.
  2. Run the AVEVA Edge 2020 R2 SP1 setup again and then use the Repair command to repair the installation on your computer.

Restore from a System Restore point

If the installation fails for any reason, you can use the System Restore feature in Windows to revert your computer to a previous restore point. For more information, go to: https://support.microsoft.com/en-us/help/12415/windows-10-recovery-options

Where To Find More Information

After you have installed AVEVA Edge, you can find more information at the following places.

Documentation Installed with the Software

The following documentation is installed in the AVEVA Edge 2020 program folder, which means you do not need an Internet connection to access it:

AVEVA™ Edge 2020 R2 SP1 Release Notes

The document that you are reading now. These notes are revised for each update (e.g., version 20.0.2), but not for each patch (e.g., version 20.0.2.1).

To open the Release Notes from the Start menu in Windows, go to Start > AVEVA Edge 2020 > AVEVA Edge 2020 Release Notes.

To open the Release Notes from within the project development environment, go to the Help tab of the ribbon and then click Release Notes.

Assuming AVEVA Edge 2020 is installed at its default location on your hard drive, the actual file for the Release Notes is located at:

C:\Program Files (x86)\AVEVA\AVEVA Edge 2020\ReadMe.html

AVEVA™ Edge 2020 Help Manual

The Help Manual provides comprehensive and searchable help for the project development environment, instructions for how to develop and deploy projects, and complete descriptions of all of our built-in functions.

To open the Help Manual from the Start menu in Windows, go to Start > AVEVA Edge 2020 > AVEVA Edge 2020 Help Manual.

To open the Help Manual from within the project development environment, go to the Help tab of the ribbon and then click Help.

Assuming AVEVA Edge 2020 is installed at its default location on your hard drive, the actual file for the Help Manual is located at:

C:\Program Files (x86)\AVEVA\AVEVA Edge 2020\Bin\TechRef.chm

AVEVA™ Edge 2020 Quick Start Guide

The Quick Start Guide provides a tour of the project development environment, descriptions of essential concepts, and a tutorial for how to develop a simple project. All of this information is included in the Help Manual, but it is organized and presented differently in the Quick Start Guide in order to make it easier for you to access.

To open the Quick Start Guide from the Start menu in Windows, go to Start > AVEVA Edge 2020 > AVEVA Edge 2020 Quick Start Guide.

Assuming AVEVA Edge 2020 is installed at its default location on your hard drive, the actual file for the Quick Start Guide is located at:

C:\Program Files (x86)\AVEVA\AVEVA Edge 2020\Bin\QuickStart.pdf

Driver documents

Each communication driver has its own document that describes the protocol used by the driver, how to configure the communication settings for the driver, how to format station IDs and I/O addresses in driver worksheets, and any other technical requirements for connected devices.

To open a specific driver document from within the project development environment, go to the Help tab of the ribbon and then click Communication Drivers.

Assuming AVEVA Edge 2020 is installed at its default location on your hard drive, the actual files for the driver documents are located at:

C:\Program Files (x86)\AVEVA\AVEVA Edge 2020\Drv\<driver name>.pdf

For example, the driver document for our basic Modbus driver (MODBU) is MODBU.pdf.

If you download an updated driver package from our website, that package should include an updated driver document.

License

The License document provides legal information regarding your license to use AVEVA Edge 2020. You are asked to agree to this document when you install the software.

Assuming AVEVA Edge 2020 is installed at its default location on your hard drive, the license document is located at:

C:\Program Files (x86)\AVEVA\AVEVA Edge 2020\License.pdf

Copyright

The Copyright document provides legal information regarding the copyrights on all of the third-party software that is incorporated into AVEVA Edge 2020. You are asked to agree to this document when you install the software.

Assuming AVEVA Edge 2020 is installed at its default location on your hard drive, the copyright document is located at:

C:\Program Files (x86)\AVEVA\AVEVA Edge 2020\Copyright.pdf

Demo Projects Installed with the Software

When you install the full AVEVA Edge 2020 software, several demo projects are also installed at the following location:

C:\Users\Public\Documents\AVEVA Edge 2020 Demo

These projects demonstrate many of the features in AVEVA Edge 2020. You can open any of them to see how objects are used in screens, how functions are used in scripts, and so on.

 

© 2023 AVEVA Group plc and its subsidiaries. All rights reserved.   |   Contact Us