Cart

{{ successMessage }}
{{item.orderingCode}}
Qty: {{ item.quantity }}
{{currencySymbol}}{{item.pricing.totalPrice | intlNumber('en-HK','USD')}}
Subtotal ({{totalQty}} {{totalQty === 1 ? "item" : "items"}}):
{{currencySymbol}}{{cartSummary.total | intlNumber('en-HK','USD')}}
TEST SITE
You will not be charged yet.

AvensorOPC

Introduction

The AvensorOPC functionality enables software with an OPC Unified Architecture client, for example a SCADA system, to read the data and alarms from Avensor. The AvensorOPC follows an OPC UA machine to machine communication protocol for the industrial automation.

The following information is available through the AvensorOPC:

  • The stations and devices data
  • Alarms data from connected devices
  • Operational data from connected devices

AvensorOPC supports the following protocols, security modes, and policies:

  •  TCP
  • Sign and encrypt
    • Basic256Sha256
    • Basic256
  • Sign
    • Basic256Sha256

System requirements

Windows

  • .NET framework 4.61 or later is required to run the AvensorOPC as a Windows service
  • Powershell installed
  • Google Chrome to access the AvensorOPC WebUI

Devices compatible with AvensorOPC

The devices with a CCD gateway connection, and the devices connected to the CCD 401 through signal leads are compatible.

Related FAQs

Many users have had similar questions about Analytics, Live Data, API and AvensorOPC.