Open Automation Software
Moving Data From Anywhere to Anywhere
1-303-679-0898

Basic Networking

Basic Networking can be used directly with any client application without any additional setup.  This configuration can be used when the data server(s) have fixed IP Addresses, registered domain names, or network node names that can be accessed from every remote client.

IoT Edge Computing Network

.NET Tag Access

Using the Tag Browse dialog from any .NET, Excel, or service client enter the IP Address, Network Node Name, or registered domain name in the Network Node field and click on Select.

Networking

You can then browse for the Tag name and property (most common is Value) to return the following.

.NET Tag access is applicable for the following

  • WPF HMI .NET
  • WinForm HMI .NET
  • Trend .NET
  • .NET Data Connector
  • PCL iOS and Android HMI
  • Microsoft Excel
  • Data Logging
  • Recipe
  • Calculation Tags
  • Tunnel Target Tags

 

Web Tag Access

In the web page specify the IP Address, Network Node Name, or registered domain name that has the HTML HMI registered over your desired port in the serverURL config property.

Specify the tag names in the HTML code as local tags.  The web browser can be run locally or remotely, it will communicate to the server specified in the serverURL as a relative path for the tag values.  In this example the tags would be running on the same server as 192.168.0.1.

TagName.Value

Web Tag access is applicable for the following

  • Web HMI
  • Web Trend
  • HTTP API for Tag data
  • HTTP API for Trend data

 

.NET Alarm Access

Using the Network Node Browse dialog from Alarm Logging, Alarm Notification, or Alarm .NET control enter the IP Address, Network Node Name, or registered domain name in the Network Node field and click on Select.

Networking

You can specify multiple network nodes in the AlarmNetworkNodes.

.NET Alarm access is applicable for the following

  • Alarm .NET
  • Alarm Logging
  • Alarm Notification

 

Web Alarm Access

In the web page specify the IP Address, Network Node Name, or registered domain name that has the HTML HMI registered over your desired port in the serverURL config property.

Web Alarm access is applicable for the following

  • Web Alarm
  • HTTP API for Alarm data

 

OPCSystems.NET OPC Server Access

When providing Tag access to remote third party OPC Clients install OAS setup on each OPC Client PC to install the OPCSystems.NET OPC Server.  You can use a Custom installation to install only OPCClient.NET if you prefer not to install everything on the OPC Client PC.

Modify the file NetworkNodes.txt with Notepad or other text editor to add the IP Addresses, Network Nodes Name, or registered domain names that have the OAS server tags running.  The file will be in C:\Program Files (x86)\Open Automation Software\OPC Systems.NET\.

You can then browse for the Tag name and property (most common is Value) directly in the OPC Client in the Network folder to return the following to the OPC Client as and OPC Item.

Networking

OPCSystems.NET OPC Server access is applicable for the following

  • OPC Client Connector

 

.NET Configuration Access

The OPCSystems component provides free access to all configuration settings of a service including Tags, Data Logging, Alarm Logging, Alarm Notification, Security, etc.

Each method of the OPCSystems component has an optional NetworkNode parameter.  When you specify this parameter it will perform the configuration access to the remote service specified by IP address, network node name, or registered domain name.

VB Example:

C# Example:

.NET Configuration access is applicable for the following

  • OPCSystems .NET component (free to use)

Web Configuration Access

View the REST API documentation on how to access configuration information via web interface.