Our team often gets questions about the extent to which our products can be used. It’s important to differentiate between technical versus practical limits when discussing what is and is not possible.
Continuing our Tech Support Corner blog series, I will be providing some insights into how many channels, devices, and tags it is technically possible to set up in TOP Server while also highlighting some practical rules of thumb to observe to ensure the best performance.
If you're a TOP Server user, you're likely accustomed to connecting to a device configured in TOP Server that is sending real-time data through one of its many available drivers. But did you know you can setup devices in a "Simulated" mode for a variety of client testing purposes when a live device isn't available?
Continuing our Tech Support Corner blog series, this post covers how the "Simulated" device property works, why you might implement it into your testing and a brief walkthrough on connecting a variety of client applications to a simulated device in TOP Server.
Many AVEVA™ users are probably already aware of the native connectivity options they have for interfacing with different systems. Many AVEVA users have also turned to TOP Server over the years, both for standardizing device connectivity in a single server and for drivers/protocols not available as native AVEVA options.
Those users of AVEVA System Platform have traditionally connected to TOP Server directly via either its native SuiteLink interface or OPC DA Classic. AVEVA's OI Gateway provides those users the additional option of connecting to OPC UA data sources, for easier and more secure remote connections to such data sources.
In this blog post, we will cover the basic steps to connect AVEVA System Platform to TOP Server via OPC UA, expanding device connectivity options for AVEVA users.
AVEVA™ users already have a wide range of connectivity options for interfacing with different systems. For many years, OmniServer has been expanding that connectivity to include non-standard, non-PLC type devices that don't have an existing off-the-shelf communications driver. Users of AVEVA System Platform have traditionally connected to OmniServer via either the native SuiteLink interface or OPC DA Classic. AVEVA's OI Gateway provides those users the additional option of connecting to OPC UA data sources, for easier and more secure remote connections to such data sources.
In this blog post, we will cover the basic steps to connect AVEVA System Platform to OmniServer via OPC UA, expanding non-standard device connectivity options for AVEVA users.
AVEVA™ users already have a wide range of connectivity options for interfacing with different systems. Cogent DataHub® also supports an extensive selection of connectivity to different systems that users sometimes need to access from AVEVA System Platform. Users of AVEVA System Platform have traditionally connected to DataHub via OPC DA Classic. AVEVA's OI Gateway provides those users the additional option of connecting to OPC UA data sources, for easier and more secure remote connections to such data sources.
In this blog post, we will cover the basic steps to connect AVEVA System Platform to Cogent DataHub via OPC UA, expanding connectivity options for AVEVA users.
Are you an AVEVA™ System Platform user but you also have some other client or system (HMI, SCADA, other) and need that system to access data from System Platform? It's a use case that sometimes occurs if your company is acquired another company and a non-AVEVA HMI/SCADA came as part of the assets. Or perhaps your company merged with another and now your AVEVA system is expected to integrate with other systems. Your options for sharing data largely depend on what software interfaces these "other systems" support.
In this blog post, I'll discuss how to share your AVEVA System Platform 2020 (or newer) data via OPC UA (without using OI Gateway) using the TOP Server OPC UA Client driver for situations where you have another non-OPC UA capable client application that needs access to process data in your AVEVA system.
A common use case that we encounter with many AVEVA™ users is the need to share data from System Platform with some other client or system (HMI, SCADA, other). It's not uncommon for a company to be acquired by another company and its assets and a non-AVEVA HMI/SCADA came as part of the assets. Or perhaps a system is being add with limited interfaces for external connectivity. Your options for sharing data largely depend on what software interfaces these "other systems" support.
In this blog post, I'll discuss how to share your AVEVA System Platform 2020 (or newer) data via OPC UA (without using OI Gateway) using the OPC Router for situations where you have another non-OPC UA capable client application that needs access to process data in your AVEVA system such as an ERP system, IIoT platform, web service and more.
Are you or have you ever been in a situation where you were working with both an AVEVA™ solution and some other client or system (HMI, SCADA, other) and needed to share data? Perhaps your company acquired another company and its assets and a non-AVEVA HMI/SCADA came as part of the assets. Or perhaps your company merged with another and now your AVEVA system is expected to integrate with other systems. Your options for sharing data largely depend on what software interfaces these "other systems" support.
In this blog post, I'll discuss how to share your AVEVA System Platform 2020 (or newer) data via OPC UA (without using OI Gateway) using the Cogent DataHub® for situations where you have another non-OPC UA capable client application that needs access to process data in your AVEVA system.
