Last revision: 6/26/2024
For important information about this release, go to the AVEVA Global Customer Support (GCS) website. Information on the GCS website includes product requirements, compatibility, and downloads from previous releases. After you log in, you can filter search results by product name and the release or version.
Antivirus software should be implemented as part of a defense-in-depth strategy to secure your Industrial Control Systems. AVEVA Support Article #33002 (https://softwaresupportsp.aveva.com/#/knowledgebase/details/000033002?lang=en_US), available from the AVEVA Global Customer Support (GCS) web site, lists important information about antivirus software. Enter your GCS credentials to access the Support Article.
AVEVA Edge 2023 R2 and earlier versions of AVEVA Edge (back to AVEVA Edge 2020) use different versions of Industrial Graphics that cannot coexist. If more than one version of AVEVA Edge with Industrial Graphics is installed on the same computer, Industrial Graphics won’t work for any of them, and attempting to use Industrial Graphics may cause an abnormal program termination.
To install AVEVA Edge 2023 R2 with Industrial Graphics on a computer that already has an earlier version of AVEVA Edge installed, first uninstall the earlier version of AVEVA Edge or use the installer (setup.exe) to modify the previous installation to remove Industrial Graphics.
AVEVA Edge and AVEVA System Platform both use Industrial Graphics. Because of this, AVEVA Edge 2023 R2 can only coexist with AVEVA System Platform 2023 R2.
AVEVA Edge 2023 R2 is compatible with AVEVA Historian Server 2023 and later. If you are using an older version of AVEVA Historian Server, upgrade to AVEVA Historian Server 2023 or a later version.
We added or significantly improved the following communication drivers in this release:
Driver |
Description |
ABBTF |
ABB Totalflow devices that support the native DB2 serial protocol using the TCI (Totalflow Communication Interface) library over TCP/IP. Driver restored in this release. |
ABKE |
Serial Communication with Allen Bradley devices Using DF1 protocol. Driver restored in this release. |
BACSL |
Communication with master stations using the BACnet/IP or BACnet MS/TP protocol. Driver restored in this release. |
DNP |
Communication with slave devices (outstations) using the DNP3 protocol. Driver restored in this release. |
XVGU |
USB Communication between Studio and Schneider Electric Harmony XVGU Tower Light devices. Driver restored in this release. |
For more information, see Issues Resolved for Specific Communication Drivers below.
The AVEVA Enterprise Licensing system is a common platform that allows you to manage AVEVA Enterprise Software product licenses. It is composed of a browser-based License Manager and a License Server that together allow you to share and deliver licenses for your installed products. It has the following features:
Note: Legacy licensing options (softkey and hardkey) are not deprecated.
Note: AVEVA Enterprise Licensing installation requires your Windows operating system to be up to date.
Note: The License Manager requires internet access. See the AVEVA Enterprise Licensing Guide for more information and workarounds.
Note: If you are using AVEVA Enterprise Licensing for AVEVA Edge and you have more than one license type, you must create a device reservation for every device running AVEVA Edge.
Choosing the AVEVA Enterprise Licensing option during installation will copy the files to the <installation folder>\Redist\AEL\AVEVA Enterprise Licensing <version number> folder, and install the License Server and License Manager. You will also be prompted to run the Configurator at the end of the AVEVA Edge installation process.
You can install the License Manager on another machine to manage License Servers on this and/or several other machines. For more information, see the AVEVA Enterprise Licensing Guide (AELicenseManagerGuide.pdf) in the AVEVA Enterprise Licensing <version number> folder.
AVEVA Enterprise Licensing 4.0.1
This release upgrades AVEVA Enterprise Licensing to version 4.0.1, which incorporates the following components and enhancements of AVEVA Enterprise Licensing 4.0.
License Manager
Once installed, a link to the AVEVA Enterprise License Manager can be found in the AVEVA folder on the Start menu. It can also be accessed by pointing your browser to the following URL: http://<nodename>/AELicenseManager, where <nodename> is localhost or the name of the node where the AVEVA Enterprise License Manager is installed.
License Server
The AVEVA Enterprise License Server can be installed separately from the AVEVA Enterprise License Manager.
AVEVA Enterprise Licensing Known Issues and Workarounds
There are two known issues involving the Configurator. Refer to the AVEVA Enterprise Licensing Guide for more information.
There is improved support for Industrial Graphics in this release.
The Industrial Graphic Editor supports import of Scalable Vector Graphics (SVG) as Industrial Graphics. A list of supported SVG elements can be found at SVG Github. You can perform the following:
Limitations of SVG Support at the time of this release
The following features are not supported at the time of this release:
Grid Object Improvements
TreeView Custom Widget Improvements
The TreeView custom widget, which is included as part of the Custom Widget Library, has been improved as follows:
There are several improvements to the Linux runtime.
Alarm, Event, and Trend History
Standard Driver Sheet Support
In addition to the MAIN DRIVER SHEET (MDS), you can create several standard driver sheets (SDS) for each driver. The standard driver sheets provide additional fields, which you can use to control communication.
Tag Integration
You can browse the following Tag Integration sources to import device registers or server items directly into your project.
Global Procedures, Startup Scripts, and Background Scripts can now be written in Python using the new Python editor, in addition to the existing VBScript functionality. Features of the Python editor are:
Limitations of Python Support in this Release
This is a summary of features that have been deprecated or removed from this version.
AVEVA Edge has supported two OPC DA interfaces: OPC DA Client (legacy) and OPC XML/DA. OPC XML/DA is a newer and more powerful OPC DA Client interface that is compatible with the older OPC DA Client (legacy) interface. Starting with this release, OPC DA Client (legacy) is disabled by default in new projects, though projects created in previous versions that use OPC DA Client (legacy) will function. OPC DA Client (legacy) will be fully deprecated in a future release of AVEVA Edge. To prepare for the upcoming full deprecation, convert OPC DA Client (legacy) to OPC XML/DA.
The Import option for all Global Procedures worksheets (accessed on the context menu) has been removed.
This release resolves the following issues reported by our users. 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.
Documentation changes are not counted as resolved issues, so if you reported an issue and it was resolved by a documentation change (such as by clarifying a step in a procedure), then it might not be included in this list.
Case No. |
ID |
Description |
960126845 |
1616311 |
GetUserPwdAging() function Return Values were not completely documented. |
960148620 960149050 |
1721779 1899490 |
The Symbol Object Properties dialog "Use linked size" feature and special considerations for resizing linked symbols were not properly documented. |
960167245 |
2061373 |
The Industrial Graphics graphics refresh rate was not documented. |
960188673 |
1974501 |
Industrial Graphics editor was freezing when saving certain symbols. |
960193543 |
1981211 |
Custom zoom property was not working on iOS thin clients. This item was resolved in a previous release. |
960195902 |
1969637 |
Executing SetPassword() on Embedded HMI generated unexpected characters in Event Logger events. |
960210402 |
2044600 |
The limit of 999 Standard Driver Sheets for each project was incorrectly documented. |
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. |
960216850 |
2070393 |
The DBCursorOpenSQL and DBExecute interaction with SQL Stored Procedures was not documented. |
960218655 |
2133076 |
Industrial Graphics editor was freezing when saving certain symbols used in multiple screens. |
960220573 |
2145930 |
Rectangle object caption was not aligning correctly on Mobile Access. This item was resolved in a previous release. |
960220573 |
2149151 |
The zoom action was not working correctly on Mobile Access. This item was resolved in a previous release. |
960222794 |
2149174 |
MS SQL Server 2019 Express timestamps were incorrect. |
960226126 |
2172147 |
On Mobile Access, the Alarm Control Object (set to History) did not refresh the alarm list if using a tag as dynamic filter. |
960246843 |
2261531 |
Event log was recording incorrect previous value on tag changes received from an OPC UA client. |
960250352 |
2270051 |
Simultaneous Requests were no longer working. |
960257526 |
2307786 |
Momentary Pushbutton events were not correctly blocked by security level. |
960257939 |
2306538 |
Closed Polygon objects were changing shape and size when dragged from one place to another on a screen. |
960259629 |
2312147 |
Using Trend worksheet Save On Trigger -> Second and Save On Tag Change at the same time generated redundant records. |
960259790 |
2314194 |
Projects with several screens with background images caused abnormal program termination. |
960263713 |
2329033 |
Momentary button was launching E-Sign feature when the user did not have permissions to display this feature. |
960267281 |
2354232 |
On Touch, On Touch Start, On Touch Delta, and On Touch Completed Command animation options were not available for Windows Embedded applications and were not properly documented. |
960278144 |
2391954 |
Corrupted HST files were preventing normal startup and operation. |
960279156 |
2400336 |
HTML5Render.exe was not able to process 3D image rendering as well as Google Chrome or Microsoft Edge could. |
960280975 |
2407175 |
The Studio hardkey was conflicting with a third-party hardkey, causing Studio not to recognize the hardkey license. |
960287427 |
2441271 |
VBScript variables used in Command animations were logging false positive errors. |
960288515 |
2471217 |
E-Signature Time-out feature of the security system was not working as documented. |
960289940 |
2486513 |
Linked symbols appeared larger in Mobile Access than in the runtime, changing the look of grouped polygons. |
960292366 |
2464074 |
When adding tags to an OPC UA Client worksheet using the UA browser, FLOAT/REAL types from the OPC UA server were not supported. |
960298019 |
2486476 |
On Double Click Command animation was not working properly when applied to a Text Box object. |
960300547 |
2493189 |
OPC UA client write commands were returning Bad Type Mismatch and resetting the tag to the old value. |
960303387 |
2504795 |
OPC UA client write commands were timing out. |
960307522 |
2517119 |
The TreeView custom widget did not refresh without trigger, and it did not include the ability to search for specific nodes using a search bar. |
960309252 |
2538426 |
Startup value of class tag was missing on thin clients when the Scope was set to Local. |
960315071 |
2550599 |
Linux runtime was logging Windows error messages during startup. |
960315402 |
2554314 |
Combo Box Object was showing incorrect values and incorrect formatting when the values of the array tag data source changed. |
960316637 |
2564118 |
Alarm message colors were not updating correctly when the tag value changed from alarm at the same time as it was acknowledged. |
960316737 |
2558581 |
Simultaneous Requests were no longer working on Windows Embedded. |
960317463 |
2559666 |
HTML tags were not being removed properly from URL screen parameters. |
960317592 |
2582578 |
When extending the LDAP schema to allow saving security rights, writing to the "proprietarySCADAInfo" attribute did not work correctly and generated an error stating "Warning! Security rights data from LDAP server is corrupted." |
960319515 |
2572470 |
Trend data output with HST2TXT included 00:00:00 data from the day following the specified date range. |
960320795 |
2591305 |
Studio Database Gateway errors occurred on Turkish OS. |
960327206 |
2603727 |
Saving and closing certain Industrial Graphics screens was slow because of tag validation. |
960331853 |
2626378 |
The failure of the Open() function to work correctly if passed incorrect data type parameters was not fully documented. |
960333263 |
2634114 |
Reload LDAP settings upon LogOn feature was not updating user information as designed. |
960338903 |
2811965 |
OPC UA Advanced setting Status tag was updated with WriteResponse > ResponseHeader > ServiceResult, but not with each individual Results StatusCode. |
960338934 |
2758270 |
.NET controls created in previous releases were not loading properly. |
960339640 |
2787574 |
As a Web Thin Client enhancement, a user can now disable screen reloading when tags are updated or when changes are made to the application. The screens will reload after the application is restarted, allowing the updates to be delayed until a downtime period. |
960342121 |
2832078 |
Screen performance slowdown due to many Smart Message objects was not documented. |
960342874 |
2841767 |
When security was configured with LDAP in an application running as a service, the application would not run on Mobile Access. |
960345533 |
2895571 |
LDAP Server Status tag values "7" and "8" were not documented in the Help Manual Security chapter. |
960345776 |
2863211 |
The built-in function FTPGet() return value "-9" was not documented. |
960346459 |
2857275 |
The Azure IoT Hub Connections folder was not visible in the Project Explorer Tasks tab when the language was not set to English. |
960348461 |
2869957 |
Alarm History objects stopped updating with new records after 3:00 pm in the Japan time zone (UTC+9). |
960351092 |
2874437 |
In applications created in previous versions of Studio, embedded images were not displayed on Industrial Graphics screens. |
960351445 |
2881960 |
Historical trend data Min and Max values were not displaying properly at single-day periods. |
960352001 |
2901314 |
During application development, the local viewer was not always able to open Industrial Graphics startup screens. |
960354729 |
2966350 |
In a Windows Embedded application, simultaneous viewing of Trend objects on local Viewer and Mobile Access, caused the Trend object to stop updating. |
960355262 |
2899485 |
Industrial Graphics AddItem function was not working properly. |
960355695 |
2896682 |
In trend objects on Mobile Access, the start time string tag did not update when changed during runtime by using a pointing device (such as a mouse). |
960356766 |
2918563 |
OPC UA Client did not support several security policies. |
960356879 |
2906287 |
Linux runtime Trend object store and forward operation to AVEVA Insight was not deleting files after forwarding data as documented. |
960359982 |
2916114 |
Using '$" in screen animation Tag/Expression fields was no longer supported. |
960360389 |
2925120 |
OPC UA connections were causing abnormal program termination. |
960362398 |
2927252 |
OPC DA structures accessed through tag integration were being shown in the Studio tags database as string tags with no members. |
960368891 |
3054410 |
Studio Database Gateway was not closing the Excel file when the Studio runtime was stopped. |
960369466 |
2981510 |
Pushbutton objects were not consistently updating the button state image when pressed and released quickly. |
960371544 |
2984616 |
Grid objects were not updating SQL source table when values were entered on Mobile Access. |
960371873 |
2988257 |
Database access was not working for Windows Embedded applications. |
960380583 |
3044737 |
On Mobile Access, clicking a checkbox object caused the screen to move with the cursor. |
960383961 |
3058751 |
The License Server feature stopped working on 20.0.3.1 and 23.0.0. |
960387544 |
3055452 |
The built-in function LookupLoad numColKey parameter was interpreted differently on Mobile Access screens. |
960389148 |
3081294 |
Trend object was not displaying correctly when the History Format was Historian. |
960392668 |
3111301 |
If the project security system Security Mode was configured as "Distributed – Server" or "Distributed – Client," Mobile Access did not start. |
960394484 |
3198401 3267858 |
An abnormal program termination occurred when more than one client accessed a Mobile Access screen containing objects with invalid database connections. |
960394797 |
3236833 |
Create User dialog box cut off information on the right if the language was French. |
960399858 |
3239438 |
Trend Control objects were not displaying data correctly on Mobile Access. |
960403291 |
3258244 |
Symbols using polygons could not be enlarged even if "Use linked size" was unchecked. |
960413346 |
3305218 |
The file paths for Remote Agent were not updated in the documentation. |
960423229 |
3360115 |
The OPC UA server security setting tag integration limitation was not documented. |
960424041 |
3359142 |
The built-in language Database/ERP function limitation of 16000 rows per operation was not documented. |
N/A |
2269924 |
DataProtect.exe utility was not working with the "INIT" option. |
N/A |
2320902 |
Hidden characters in class member descriptions corrupted the application folder. |
N/A |
2351662 |
The OPC UA Client had a latency when sending write commands. |
N/A |
2651413 |
Input enabled grid object cells were not working on Mobile Access. |
N/A |
2832105 |
There was no documentation explaining the translation requirements for Alarm/Event Control object filtered Message values that include string expressions. |
N/A |
2836720 |
Linked picture object properties were changed to lowercase. |
N/A |
2869187 |
The Studio Database Gateway stopped responding to requests and required a restart. |
N/A |
2893638 |
There was no documentation explaining how to open native screens as screens from Industrial Graphics screens. |
N/A |
2972882 |
Tag datatype and unit changes in Historian were not being updated in Studio. |
N/A |
3007092 |
Studio license evaluation time was not being tracked correctly. |
Case No. |
ID |
Description |
960321155 |
2582531 |
In the MELSE driver, hexadecimal addresses were not reading values correctly. |
960340962 |
2837118 |
In the MQTT driver, parallel processing of legacy MQTT and Sparkplug I/O addresses was not working correctly. |
960343079 |
2842327 |
The ABBTF driver was unable to get data from multiple devices that are connected to a single controller. |
960343858 |
2855351 |
The OMRON driver stopped working when trying to read tags that were not present on the device. |
960371580 960393308 |
3009505 3186658 |
The SCHNE driver did not communicate with tag names with a Station that included an XSY file parameter. |
960372142 |
3001223 |
Drivers do not support serial encapsulation on the Linux runtime. This was not documented clearly. |
960375350 |
3001818 |
The MODSL driver manual was not updated to the latest version. |
960377805 |
3079576 |
After a network connection failure and recovery, SIETH driver communication did not resume. |
960380543 |
3034912 |
The OMDIR driver failed to write string or float values correctly to the device using the Standard Driver Sheet. |
960389238 |
3061236 |
The OMDIR driver failed to read blocks with an invalid address on the Main Driver Sheet. |
960396369 |
3196930 |
The MQTT driver was unable to publish more than 82 characters when the Main Driver Sheet tag Action was set to Read+Write. |
960403163 |
3314675 |
The MOTCP driver was unable to write an odd number of characters when using the Header STS. |
960409236 |
3283162 |
The OMDIR driver communication failed when there were structured tags with incorrect syntax on a driver sheet. |
This is a list of known issues that remain in this version, with appropriate contingencies and workarounds.
ID |
Description |
1135583 |
Issue: Only the first 512 characters of a String tag are saved when selecting the Retentive Value string tag property for projects running in the Embedded HMI runtime edition on Windows Embedded. Workaround: Limit String tags to 512 characters when running projects in the Embedded HMI runtime edition on Windows Embedded.
|
1631020 |
Issue: Some communication drivers (e.g., MODBU) 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 or fewer characters per string, and then store those shorter strings in multiple device registers.
|
1788460 |
Issue: Screen viewer performance suffers if SetTagDisplayUnit function is called more than 21 times by a screen. Workaround: Limit the number of times a screen calls to function SetTagDisplayUnit to 21 or fewer.
|
2376863 |
Issue: If your Windows Display settings the Scale and layout scale is set to a value other than 100%, the Industrial Graphics editor dialog controls may not display properly. This might be due to scaling of the user interface. 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. This UI scaling can affect the behavior of some apps, especially those that include drawing or rendering functions. Workaround:
|
2400387 |
Issue: On Mobile Access, when Zoom Mode is set to Custom Zoom, the user can use touch gestures on the screen to zoom in, zoom out, or navigate over the screen content. On iOS devices, if you do this and your finger touches an object that has a command assigned to it, this command will be executed.
|
2487802 |
Issue: Verify project can end up taking more than an hour if there are unused tags in the project. Workaround: Use the Remove unused tags tool before using Verify.
|
N/A |
Issue: If you install Studio without a license, you can open a project in evaluation mode or demo mode. If you try to open another project, the project will not be opened. Depending on the method used to open the project, you may see an evaluation or demo mode notification, or an error message may be generated. Workaround: Close and restart Studio and open the project. Studio will open with the last opened project in evaluation mode or demo mode.
|
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. 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. This UI scaling can affect the behavior of some apps, especially those that include drawing or rendering functions. Workaround:
|
N/A |
Issue and Workaround: Industrial Graphic function SetCustomPropertyValue(name, "value", isConstant): If the second parameter (value) is an array with an array index tag, the function will not work unless you format the parameter as a constant by enclosing it in quotes.
|
N/A |
Issue: Industrial Graphic function SetCustomPropertyValue(name, "value", isConstant): If the second parameter (value) is an array with a array index tag, the function will not work if either the array or the array index has the prefix HMI:. Workaround: Because the preifx HMI: is optional, do not use it for these tags. As noted above, you may also need to enclose the parameter in quotes.
|
N/A |
Issue: If a screen containing a custom widget is opened simultaneously in the Windows Viewer and in a web thin client browser on the same machine, the custom widget will work only in first viewer opened. Workaround: Do not open a screen containing a custom widget simultaneously in the Windows Viewer and in a web thin client browser on the same machine.
|
N/A |
Issue: When migrating the ITMEViewApp object from version 2023 to version 2023 R2 following the normal process (importing the aaPKG file that corresponds to the newer version), you may end up with a broken ITMEViewApp object in the galaxy due to file conflicts. The importing process will not report an error, but the System Platform IDE Templates navigation tree will display a cross icon (indicating an error) next to one or more of the ITMEViewApp derived templates. Workaround: See AVEVA Support Article #42308 (https://softwaresupportsp.aveva.com/#/knowledgebase/details/000042308?lang=en_us), available from the AVEVA Global Customer Support (GCS) web site, for more information and detailed resolutions steps. Enter your GCS credentials to access the Support Article.
|
Removing Previous Versions or Previous Versions of Industrial Graphics
Different versions of AVEVA Edge can coexist on the same machine, but some components cannot coexist. See Software Coexistence for more information. Because of this, one of the following actions is recommended before installing the new version:
Licensing
When upgrading 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 software distributor.
If you do not upgrade your software license(s), it will still run 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 (such as AVEVA Edge 2023) to its latest minor version (such as AVEVA Edge 2023 R2), you do not need to update your software license(s). The license is for the major version, so it includes all the subsequent updates, patches, and hot fixes for that major version.
Existing Studio Projects
Finally, when you open an existing project for the first time in a new version, 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 (for example, "AVEVA Edge 2023 Projects") in your user directory, so you can copy (not move) your projects from the old projects folder to the new projects folder.
This section describes the system requirements and additional considerations for installation to develop projects, or to use the computer as a project runtime server and/or thin client.
Standard Requirements
Optional Items
This item is optional because softkey licensing is also available.
This item is optional because many newer device protocols use Ethernet communication (TCP or UDP) instead of serial communication.
One of the following operating systems:
Use the "Pro" or "Enterprise" editions of Windows because they include Internet Information Services (IIS) as a pre-installed feature that can be turned on. Do not use the "Home" and "Education" editions of Windows, because many features are hidden or disabled in these editions.
You can install the full software on a Windows Embedded device if it meets the system requirements listed above. If you do not plan to develop projects on that device, install Embedded HMI instead. For more information, see the Help Manual.
Update Windows before you install the software so that you have the latest security fixes and system components.
If you are using IoT View on a Linux target station, here are the software and hardware requirements. For more information on installing, running, and using IoT View, see the Help Manual.
Processor |
Minimum Versions of Required Libraries |
Location of Redistributable Software |
aarch64 arm64 |
libc: 2.23 libstdc++: 6.0.21
|
<program folder>\Redist\IoTView\Linux\aarch64-2.23-6.0.21\ |
armv7l armhf |
libc: 2.23 libstdc++: 6.0.21
|
<program folder>\Redist\IoTView\Linux\armv7l-2.23-6.0.21\ |
x86_64 amd64 |
libc: 2.23 libstdc++: 6.0.21
|
<program folder>\Redist\IoTView\Linux\x86_64-2.23-6.0.21\ |
If your architecture is not covered by the table above, contact your software distributor. IoT View can be compiled for most modern operating systems.
This software requires .NET Framework 4.8 (or later) installed and enabled.
If Windows is fully updated on your computer, the latest versions of .NET Framework should be installed, but they might not be enabled. Use either the Windows Features control panel in Windows or the Server Manager console in Windows Server to confirm that .NET Framework 4.8 is enabled.
In some cases, it might not be possible to update Windows 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 and then transfer it.
This item is optional because it is not required to develop a basic project and then run it on a standalone device, but it is required to use more advanced features.
This item is optional because you can always use the built-in Viewer program to view project screens.
This item is optional because you can always use the built-in Viewer program to view project screens.
Previous versions of Internet Explorer are no longer supported. In some cases, you can use Microsoft Edge in Internet Explorer (IE) mode, which enables backward compatibility for legacy websites and applications like Web Thin Client. It is supported with limitations, however, and you might see unexpected behavior while viewing project screens. For more information, go to: https://www.microsoft.com/en-us/edge/business/ie-mode
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. Every computer or device that you plan to use as a runtime station is subject to the same requirements.
If you are using Industrial Graphics screens, the project should be hosted on a dedicated Windows system with IIS installed. The additional system recommendations for this dedicated system are:
These recommended requirements are suitable for a system with ten clients, browsing pages with approximately 40 dashboard/charting components with ~250 I/O tags on the page. Pages may take a longer time to display on the first visit. The display time depends on graphics and script complexity. Additional clients can be supported by increasing the number of CPU’s, CPU speed, and Memory.
You need to have administrator privileges on your computer to install Studio. If you are not already signed on as a user with administrator privileges when you run the software installer, you can choose to run the installer as an administrator. To do this, 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 username and password.
On the Select Features page of the 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 application, project runtime server, and project runtime client. This feature cannot be deselected.
|
Custom Widget Framework |
Installs files for the Custom Widget Framework, which is used to create HTML5-based widgets and use them in project screens. This feature cannot be deselected.
|
AVEVA Enterprise Licensing |
Enables AVEVA Edge to be licensed using an AVEVA Enterprise License. Installs the License Manager and a License Server. Requires running the Configurator after the installation. Legacy licensing options do not coexist with Enterprise License. By selecting this option, you will not be able to use either hardkeys or softkeys. AVEVA Enterprise Licensing installation requires your Windows operating system to be up to date. The License Manager requires internet access. See the AVEVA Enterprise Licensing Guide for more information and workarounds.
|
Database Gateway and Historian Integration |
Installs Studio Database Gateway, AVEVA Historian integration, and AVEVA Insight integration. This feature is required for any database communication. This feature requires .NET Framework 4.8 (or later) installed and turned on.
|
Demo Projects |
Sample projects that demonstrate the capabilities of the software.
|
Hardkey Support |
Additional drivers to support the use of hardkey (USB) software licenses. For more information, see Third-Party Software below.
|
Industrial Graphics |
Industrial Graphics is a powerful modern graphic editor that enables creation of portable graphic libraries that can be reused in products that use this platform-agnostic solution. It acts as a companion to our native graphics tools.
|
Mobile Access Runtime |
Additional software to make the project runtime accessible to mobile devices such as tablets and smartphones, using HTML5-compatible browsers to view the project screens. This feature requires Microsoft .NET Framework 4.8 and Microsoft IIS--with ASP, ASP.NET, and ISAPI Extensions enabled--installed and turned on. This required software will be installed if necessary. Whether or not this feature is selected during installation, a separate Mobile Access Runtime software installer (MobileAccessSetup.exe) will be copied to the program folder. This installer can be run at a later time.
|
PDF Printing |
Additional software for printing runtime reports directly to PDF files.
|
Python |
Installs required files for the Python editor, and for the Windows and Linux runtimes.
|
Runtimes – Additional > IoT View |
Installs files for the IoT View runtime, the platform-agnostic project runtime software for Linux and other operating systems. Selecting this feature will not install it on your computer at this time. It will copy the installation files to the program folder, so that the runtime files can be installed on another computer or device at a later time.
|
Runtimes – Additional > Embedded HMI |
Project runtime server and client software for Windows Embedded, also called Embedded HMI. Selecting this feature will not install it on your computer at this time. It will copy the installation files to the program folder, so that the runtime files can be installed on a Windows Embedded computer at a later time.
|
Security System Device Driver |
Installs device driver for security system to lock the keyboard (kbdlock).
|
Symbol Library |
A library of premade but configurable screen objects such as pushbuttons, toggle switches, gauges, dials, and indicator lights.
|
The installer creates a shortcut on your desktop and adds the following items to the Windows Start menu:
Item (AVEVA Edge 2023 R2 folder) |
Description |
|---|---|
AVEVA Edge 2023 R2 Help Manual |
A comprehensive technical reference and user guide.
|
AVEVA Edge 2023 R2 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 2023 R2 Register |
A utility program that you can use to view and change your software license settings.
|
AVEVA Edge 2023 R2 Release Notes |
The document that you are reading now.
|
AVEVA Edge 2023 R2 Remote Agent |
A utility program that lets other stations remotely manage the project runtime when it is running.
|
AVEVA Edge 2023 R2 SCADA |
A shortcut that automatically runs the most recently opened project.
|
AVEVA Edge 2023 R2 Studio |
The project development environment, project runtime and/or project viewer. Its actual capabilities are determined by your software license settings.
|
If you have installed the AVEVA Enterprise Licensing feature, you will also have a Start menu AVEVA folder containing the AVEVA Enterprise Licensing menu items. See the AVEVA Enterprise Licensing Guide for more information.
Item (AVEVA folder) |
Description |
|---|---|
Configurator |
A program used to configure the AVEVA Enterprise License for AVEVA Edge on this machine.
|
Enterprise License Manager |
A link to the license manager installed on this machine.
|
Enterprise Licenser Manager User Guide |
A comprehensive technical reference and user guide for the AVEVA Enterprise Licensing components.
|
Operations Control Management Console |
A set of Microsoft Management Console (MMC) snap-ins that provide management and diagnostic capabilities, such as a log viewer.
|
These third-party software components are installed along with the software, most of which are added to the Windows Apps & Features list. Do not uninstall these components unless this software has been uninstalled already; see the table below for more details.
Component |
Description and notes |
|---|---|
Microsoft Visual C++ Redistributable (multiple versions) |
These components are required to run C++ applications that were developed using Visual Studio. Several different versions (2015–2022) may be installed. Do not uninstall these components; they may be used by other applications.
|
novaPDF SDK 10 Printer Driver novaPDF SDK 10 COM (x64) novaPDF SDK 10 COM (x86) Studio PDF3
|
These components let projects save runtime reports as PDF files. They are installed when you select the PDF Printing feature for installation; for more information, see Selectable Features above. These components will be uninstalled when this software is uninstalled unless they are being used by another installed software package.
|
Sentinel Protection Installer 7.7.1 |
This component supports the use of Sentinel-type hardkeys (a.k.a. dongles). It is installed when you select the Hardkey Support feature for installation. This component is not uninstalled when you uninstall the software, but it can be uninstalled manually.
|
CodeMeter Runtime Server |
Wibu Systems' CodeMeter Runtime is installed on your computer when you select the Hardkey Support feature for installation. It supports the use of Wibu-type hardkeys (a.k.a. dongles), which 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 components described above, the CodeMeter Runtime Server is not added to the Windows Apps & Features list. It runs as a background process named CodeMeter Runtime Server, which is found in the Windows Task Manager. When you uninstall this software, the CodeMeter Runtime Server is also uninstalled automatically.
|
This section describes issues that might occur during installation.
"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 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 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.
"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:
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.
The following documentation is installed in the program folder, which means you do not need an Internet connection to access it:
Document |
Description and Location / Access |
Release Notes (Readme.html) |
The release notes document summarizes product news and installation information. To access this document:
|
Help Manual (TechRef.chm) |
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 access this document:
|
Quick Start Guide (QuickStart.pdf) |
The Quick Start Guide provides a tour of the project development environment, descriptions of essential concepts, and a simple project development tutorial. All of this information is also included in the Help Manual. To access this document:
|
Driver documents (<driver name>.pdf) |
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. If you download an updated driver package from our website, that package should include an updated driver document. Each driver has its own separate <driver name>.pdf document. For example, the driver document for the basic Modbus driver (MODBU) is MODBU.pdf. To access there documents:
|
License document (License.pdf) |
The License document provides legal information regarding your license to use AVEVA Edge. You are asked to agree to this document when you install the software. To access this document:
|
Copyright document (Copyright.pdf) |
The Copyright document provides legal information regarding the copyrights of the incorporated third-party software. You are asked to agree to this document when you install the software. To access this document:
|
|
© 2015-2024 AVEVA Group Limited or its subsidiaries. All rights reserved. | Contact Us |