Networking

October 18, 2016August 21, 2021

One Way Networking

The One Way Networking feature provides communications of tag values from the local server and remote server within the same DMZ to receiving servers through communication networks that only allow one direction through a communication diode. The receiving server need to have a fixed IP address. The data source servers can be fixed or dynamic.

Each data source server can broadcast to multiple receiving servers. Each receiving service can receive values from multiple data source servers.

Client application can then connect to the Tag values on the receiving services with local access, Basic Networking, Live Data Cloud Networking, and / or Network Forwarding.

View Getting Started Getting Started-Unidirectional Network Gateway on how to setup the data source to transmit values, and the receiving service Tags to receive values.

October 18, 2016September 29, 2020

Network Forwarding

The Network Forwarding feature makes it possible for client devices to reach data servers live data through multiple redirect servers, as many as you like, to bridge multiple networks together end to end. If the data servers do not need a fixed IP address it can be used in combination with the Live Data Cloud feature.

In order to use Network Forwarding you just need to install Open Automation Software on each redirect server. If you plan to use different TCP port numbers through the forwarding use Configure-Options-Networking to set the source TCP Port Number and Configure-Options-Remote Services to set the client TCP Port Number.

.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

Then using the Forwarding button define as many redirect servers as you like, each one having Open Automation Software installed and running.

Networking

You can optionally specify a Live Data Cloud data server as well if that is the final data server. Of leave the Live Data Cloud data server blank if it has a fixed IP address.

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

In the following example 192.168.249.128 is the first redirect server that forwards communications onto www.opcsystems.com, and then finally the Live Data Cloud server OAS_SONY.

With a Live Data Cloud Node:

\\192.168.249.128\RemoteSCADAHosting.www<dot>opcsystems.com<dot>com_SUBNODE_OAS_SONY.TagName.Value

In the following example 192.168.249.128 is the first redirect server that forwards communications onto www.opcsystems.com were the tag resides.

Without a Live Data Cloud Node

\\192.168.249.128\RemoteSCADAHosting.www<dot>opcsystems.com<dot>com_SUBNODE_LIVE DATA CLOUD NOT USED.TagName.Value

There is additional syntax to note when using Network Forwarding.

[list]
[li]The network nodes following RemoteSCADAHosting use <dot> in replace of any period. For example and IP address would be represented as 192<dot>168<dot>0<dot>1 instead of 192.168.0.1.[/li]
[li]All redirect servers are separated by _SUBNODE_.[/li]
[li]The last server must either be a Live Data Cloud data server or the words LIVE DATA CLOUD NOT USED.[/li]
[/list]

Note: If you are using Calculation Tags, Data Logging, or other service to service communications where the Live Data Cloud server is performing data functions on remote data from data servers you do not need to specify the first server IP address.

With a Live Data Cloud Node:

RemoteSCADAHosting.www<dot>opcsystems.com<dot>com_SUBNODE_OAS_SONY.TagName.Value

Without a Live Data Cloud Node:

RemoteSCADAHosting.www<dot>opcsystems.com<dot>com_SUBNODE_LIVE DATA CLOUD NOT USED.TagName.Value

.NET Tag access is applicable for the following

WPF HMI .NET
WinForm HMI .NET
Cross-Platform HMI
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.

serverURL: 'http://www.192.168.249.128.com:58725'

Specify the tag names in the HTML code as RemoteSCADAHosting tags without the first network node portion as the Live Data Cloud server is already reached through the serverURL.

With a Live Data Cloud Node:

RemoteSCADAHosting.www<dot>opcsystems.com<dot>com_SUBNODE_OAS_SONY.TagName.Value

Without a Live Data Cloud Node:

RemoteSCADAHosting.www<dot>opcsystems.com<dot>com_SUBNODE_LIVE DATA CLOUD NOT USED.TagName.Value

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.

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

Then using the Forwarding button define as many redirect servers as you like, each one having Open Automation Software installed and running.

Networking

You can specify multiple network nodes in the AlarmNetworkNodes.

With a Live Data Cloud Node:

\\192.168.249.128\RemoteSCADAHosting.www<dot>opcsystems.com<dot>com_SUBNODE_OAS_SONY

Without a Live Data Cloud Node:

\\192.168.249.128\RemoteSCADAHosting.www<dot>opcsystems.com<dot>com_SUBNODE_LIVE DATA CLOUD NOT USED

.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.

serverURL: 'http:// 192.168.249.128:58725'

In the alarm_bindings specify the networkNodes property with RemoteSCADAHosting.

With a Live Data Cloud Node:

RemoteSCADAHosting.www<dot>opcsystems.com<dot>com_SUBNODE_OAS_SONY

Without a Live Data Cloud Node:

RemoteSCADAHosting.www<dot>opcsystems.com<dot>com_SUBNODE_LIVE DATA CLOUD NOT USED

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\Open Automation Software\OAS\.

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

Network.www.opcsystems.com.RemoteSCADAHosting.OAS_SONY.TagName.Value

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 and RemoteSCADAHosting parameter. When you specify these parameters it will perform the configuration access to the remote service specified by IP address, network node name, or registered domain name through the Live Data Cloud server to the Live Data Cloud data server.

VB Example With a Live Data Cloud Node:

ResultString = OPCSystemsComponent1.TagCSVImport(CSVStrings, "192.168.249.128", ErrorString, "RemoteSCADAHosting.www<dot>opcsystems.com<dot>com_SUBNODE_OAS_SONY")

VB Example Without a Live Data Cloud Node:

ResultString = OPCSystemsComponent1.TagCSVImport(CSVStrings, "192.168.249.128", ErrorString, "RemoteSCADAHosting.www<dot>opcsystems.com<dot>com_SUBNODE_LIVE DATA CLOUD NOT USED")

C# Example With a Live Data Cloud Node:

ResultString = OPCSystemsComponent1.TagCSVImport(CSVStrings, "192.168.249.128", ErrorString, "RemoteSCADAHosting.www<dot>opcsystems.com<dot>com_SUBNODE_OAS_SONY");

C# Example Without a Live Data Cloud Node:

ResultString = OPCSystemsComponent1.TagCSVImport(CSVStrings, "192.168.249.128", ErrorString, "RemoteSCADAHosting.www<dot>opcsystems.com<dot>com_SUBNODE_LIVE DATA CLOUD NOT USED");

.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.

October 18, 2016February 2, 2022

Live Data Cloud Networking

The Live Data Cloud feature makes it possible to host live data on local hardware. It can be used with a standard Internet connection at the data servers provide access from any client application with an Internet connection. The data servers do not need a fixed IP address.

The Live Data Cloud feature is also commonly used to connect networks together to provide end to end connectivity where each source and client cannot communicate directly with each other.

In order to activate the Live Data Cloud networking you first need to install Open Automation Software on a central server that both servers and clients will have direct access to.

Note: If it is not possible to have direct access from clients to the Live Data Cloud server you can use Network Forwarding on any number of servers until you can complete the communication path through your network.

If you wish to host data from your local hardware on the Internet and do not have a server that is directly accessible on the Internet you can obtain a Virtual Private Server either dedicated or shared from hosting providers like GoDaddy. The operating system must be Windows. No license of OAS is required on the central Live Data Cloud Server(s). You can have as many Live Data Cloud servers as you like. Each data source server can host data through multiple Live Data Cloud servers, and each client can obtain data through multiple Live Data Cloud servers.

At each data source server follow the simple steps in System Configuration-Live Data Cloud-Getting Started-Live Data Cloud. You can then access data from each client application type as follows in each access type.

Remote 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

Then using the Live Data Cloud pull down list select your desired data source server.

Networking

You can then browse for the Tag name and Variable (most common is Value). See Tag Variables for a complete list of all variables possible.

\\www.opcsystems.com\RemoteSCADAHosting.OAS_SONY.TagName.Value

Remote Tag access is applicable for the following

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.

serverURL: 'http://www.opcweb.com:58725'

Specify the tag names in the HTML code as RemoteSCADAHosting tags without the first network node portion as the Live Data Cloud server is already reached through the serverURL.

RemoteSCADAHosting.OAS_SONY.TagName.Value

Web Tag access is applicable for the following

.NET Alarm Access

Networking

Then using the Live Data Cloud pull down list select your desired data source server.

Networking

You can specify multiple network nodes in the AlarmNetworkNodes property.

RemoteSCADAHosting.www.opcsystems.com.RemoteSCADAHost.OAS_SONY

.NET Alarm access is applicable for the following

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.

serverURL: 'http://www.opcsystems.com:58725'

To host remote OAS alarms from different nodes than the serverURL specify the NetworkNodes: property in the Alarm Bindings.

networknodes:[
        "RemoteSCADAHosting.www.opcsystems.com.RemoteSCADAHost.OASNode1", 
        "RemoteSCADAHosting.www.opcsystems.com.RemoteSCADAHost.OASNode2", 
        "RemoteSCADAHosting.www.opcsystems.com.RemoteSCADAHost.OASNode3", 
        "RemoteSCADAHosting.www.opcsystems.com.RemoteSCADAHost.OASNode4"
    ]

Developers sometimes miss the point that the serverURL has already obtained the central Live Data Cloud server so the following is more common for LDC hosted.

RemoteSCADAHosting.localhost.RemoteSCADAHost.OASNode1

Web Alarm access is applicable for the following

OPC UA and OPC DA Client Access

The OAS Engine has the Open Automation Software OPC UA Server included. Connect to server url opc.tcp://localhost:58728 if OPC UA Client is on same PC, or opc.tcp://<NetworkNode or IP Address>:58728.

opc.tcp://192.168.0.1:58725'

Use Remote Tag Access syntax listed above for Live Data Cloud networking. The OPC UA Client will be able to browse for RemoteSCADAHosting under Local or Network as a folder to browse to remote OAS Tags.

When providing Tag access to remote third party Classic 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.

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

Network.www.opcsystems.com.RemoteSCADAHosting.OAS_SONY.TagName.Value

OPCSystems.NET OPC Server access is applicable for the following

OPC Client Connector

.NET Configuration Access

The OASConfig 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 OASConfig component has an optional NetworkNode parameter and RemoteSCADAHosting parameter. When you specify these parameters it will perform the configuration access to the remote service specified by IP address, network node name, or registered domain name through the Live Data Cloud server to the Live Data Cloud data server.

VB Example:

ResultString = OASConfig1.TagCSVImport(CSVStrings, "www.opcsystems.com", ErrorString, "OAS_SONY")

C# Example:

ResultString = OASConfig1.TagCSVImport(CSVStrings, "www.opcsystems.com", ErrorString, "OAS_SONY");

.NET Configuration access is applicable for the following

OASConfig component (free to use)

Web Configuration Access

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

October 18, 2016April 29, 2021

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.

Remote 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 Variable (most common is Value). See Tag Variables for a complete list of all variables possible.

\\192.168.0.1\TagName.Value

Remote Tag access is applicable for the following

Web Tag Access

In the web page set the serverURL to the IP Address, Network Node Name, or registered domain name of the Linux or Windows devices where the OAS Engine located.

serverURL: 'http://192.168.0.1:58725'

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

If the tag is located on a different system than the serverURL or you want to host data from multiple OAS Engines use the Remote Tag Access syntax.

\\192.168.0.2\TagName.Value
\\192.168.0.3\TagName.Value
\\192.168.0.4\TagName.Value
\\192.168.0.5\TagName.Value

Web Tag access is applicable for the following

Remote Alarm Access

Networking

You can specify multiple network nodes in the AlarmNetworkNodes.

192.168.0.1

.NET Alarm access is applicable for the following

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.

serverURL: 'http://192.168.0.1:58725'

To host remote OAS alarms from different nodes than the serverURL specify the NetworkNodes: property in the Alarm Bindings.

networknodes:[
        "192.168.0.2", 
        "192.168.0.3", 
        "192.168.0.4", 
        "192.168.0.5"
    ]

Web Alarm access is applicable for the following

OPC UA and OPC DA Client Access

The OAS Engine has the Open Automation Software OPC UA Server included. Connect to server url opc.tcp://localhost:58728 if OPC UA Client is on same PC, or opc.tcp://<NetworkNode or IP Address>:58728.

opc.tcp://192.168.0.1:58725'

Use Remote Tag Access syntax listed above for Basic networking. The OPC UA Client will be able to browse for Network as a folder to browse to remote OAS Tags.

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

Network.192.168.0.1.TagName.Value

OPCSystems.NET OPC Server access is applicable for the following

OPC Client Connector

.NET Configuration Access

The OASConfig 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 OASConfig 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:

ResultString = OASConfig1.TagCSVImport(CSVStrings, "192.168.01", ErrorString)

C# Example:

ResultString = OASConfig1.TagCSVImport(CSVStrings, "192.168.01", ErrorString);

.NET Configuration access is applicable for the following

OASConfig component (free to use)

Web Configuration Access

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

October 18, 2016August 25, 2021

Getting Started – Unidirectional Network Gateway

The UDP Broadcast feature is used to transfer values through Unidirectional Network Gateway with communication diodes that only allow traffic to go one way.

This networking feature is only needed when bidirectional communications is not allowed. The feature is included for free in all OAS systems.

The feature supports broadcasting data from any tag variable from a the local server or remote servers within the DMZ to unlimited number of receiving servers. Each receiving server can be setup to receive data from multiple broadcast servers providing many to many data transfer.

Use the following steps to setup servers to broadcast data and receiving services to update local and remote tag variables from the broadcasting nodes.

The receiving nodes need to have a fixed IP address, registered domain name, or network node name. The broadcasting nodes do not need to have a fixed IP address.

Step 1

OAS Start Configure OAS application.

Step 2

From the data source service select Configure-UDP Broadcast.

Step 3

Select the Local OAS Service by selecting the Select button next to the Network Node drop down.

Step 4

Click the Checkbox to Enable UDP Broadcast and enter the Server Port number and Broadcast Rate which is the rate all values from this service will be broadcast to the receiving clients.

Click on Apply Changes.

Click the Add Button and enter each receiving client IP Address and Port Number in the popup window and click OK.

Step 5

Choose to send all tag values from the local service on each broadcast or uncheck the property Send All Local Tags to define a list of tags from the local system, remote systems, and all variables.

By defining which tags to broadcast has the following benefits over Send All Local Tags.

Reduced network packet size on the broadcast if the number of tags sent is less then the number of local tags.
Can broadcast any Tag Variable, not just the Value.
Can broadcast tag values from other remote nodes within the DMZ.

Step 6

Select the Save button on the toolbar at the top.

Step 7

Save the file myUDPBroadcastServer.UDPBroadcast in the directory of your choice.

You can specify for this configuration to load automatically when the Service starts using Configure-Options to specify this default UDP Broadcast file.

Step 8

From the receiving service select Configure-UDP Receive.

Step 9

Select the Local OAS Service by selecting the Select button next to the Network Node drop down.

Step 10

Click the CheckBox to Enable UDP Receive and enter the desired watchdog rate. The watchdog rate is the amount of time it will wait before setting the receiving tags quality to bad without receiving a broadcast.

Click on Apply Changes.

Click the Add Button to add a Port Number to listen on and select OK. You can enter multiple receiving port numbers.

Step 11

Select the Save button on the toolbar at the top.

Step 12

Save the file myUDPBroadcastClient.UDPReceive in the directory of your choice.

You can specify for this configuration to load automatically when the Service starts using Configure-Options to specify this default UDP Receive file.

Step 13

In the receiving node select Configure-Tags. Add Tag’s with the Data Source of UDPClientTag and enter the Tag name of the broadcasting node you want to receive the value from.

Keep in mind you may not be able to browse for the tag name from the broadcast node, so you may have to manually enter it or use Tag CSV Import or programmatic tag setup using .NET or REST API to setup multiple tags.

The Tag defined must match the broadcast tag name defined in Step 5.

Examples:

Ramp.Value
Ramp.HighAlarmActive
\\192.168.0.1\Ramp.Value

Save the Tag Configuration file and specify it to load automatically under Configure-Options-Default Files.

July 21, 2016August 23, 2022

Remote OAS Service Access

The OAS Service must be started to be accessed by a local or remote OPC client component or application. Use the OAS Service Control application to Start the Service.

If you are using a Firewall make sure to open up TCP port 58727 for both inbound and outbound traffic. You can find what port number is used under Configure-Options-Networking in the service, 58727 is the current default port number.

You can check if the TCP port is open using the Windows Command Prompt with the following command on the same computer as the OAS Service.

netstat -an | find “58727”

If the service is not started or the port is not open then the command will just return without any results.

To check a remote computer port use PortQry from Microsoft.

Download PortQry from Microsoft.

Run PortQryV2.exe to extract to desired directory.

Use the Windows Command Prompt from the PortQryV2 directory with the following command. Replace 127.0.0.1 with the IP address of the remote system where the OAS Engine is running.

portqry -n 127.0.0.1 -e 58727

If this test fails check the network connection to the remote system and open the TCP port for incoming and outbound traffic in the firewall and antivirus software.

February 23, 2016January 16, 2018

FAQs – Networking

How can I define IP Addresses when browsing for network nodes?

Use the Configure-Options-Networking in the Configure OAS application to define a list of IP addresses in the Network Nodes field as shown in Networking OPC Data.

How can I change the default WCF Port Number to use in the OAS Service and Client applications?

Go to Configure-Options Networking and set the WCF Port Number. View the following video for adjusting the client applications and how to adjust WCF port number in the realtime service and all client applications:

How can I host my OAS Service on the Internet without a fixed IP Address or registered domain name?

Use the Live Data Cloud feature that is free to use. How to host data from any Windows PC with a standard Internet connection. No fixed IP Address or registered domain name required.

Do I need to make a web application in order to access data over the Internet?

No, all Open Automation Software client applications and services support Internet communications in Open Automation Software by default. You can deploy them as Smart Clients.

When trying to connect to a local or remote OAS Service an error occurs and access is denied.

View the Remove OAS Service Access section is this file.

When I select localhost I receive an error

Try 127.0.0.1. If it works you can correct your hosts file where is shows localhost.

Data packet size is limited on Windows XP and Windows Server 2003 for UDP Broadcasts

If you setup a large number of tags to be transferred via UDP Broadcast sent from or received on XP or Windows Server 2003 and the data is not transferred, but is with a small number of tags download and install the following Hotfix. https://support.microsoft.com/en-us/kb/824838

February 23, 2016August 25, 2021

Videos – Networking

Edge network platform for IIoT communications. Host data directly at the source.

Basic Networking

How to network all products to central service using a fixed IP Address or registered domain name for the Internet.

Unidirectional Gateway

How to transfer data through networks with one way communication data diodes.

Live Data Cloud

How to host data from any Windows PC with a standard Internet connection. No fixed IP Address or registered domain name required.

Adjustable WCF Port Number

How to adjust WCF port number in the realtime service and all client applications.
Modern OAS now uses TCP Port Number with default value of 58727 which is also adjustable with the same methods.

Excel with Live Data Cloud

How to use OPCExcel.NET with data service being hosted with free Live Data Cloud feature over the Internet.

Data Log with Live Data Cloud

How to use Data Logging with data service being hosted with free Live Data Cloud feature over the Internet.

OPC Client with Live Data Cloud

How to use OPCClient.NET with data service being hosted with free Live Data Cloud feature over the Internet.

February 23, 2016November 10, 2019

Getting Started – Networking

Networking with Open Automation Software is so fully integrated and easy to use its unique ability to move data in different ways can easily be overlooked. There are not a lot of instructions listed here as networking features are very intuitive simple to implement.

The Open Automation Software support remote client and service communications provided the license has networking enabled. Go to Configure-License of the OAS Configure application and verify you have Unlimited Client Applications listed there.

There are 4 types of basic networking the Open Automation Software supports. All networking features are included at no cost provide the data server has OAS Networking enabled in its license. Live Data Cloud servers and Network Forwarding nodes do not require a license of OAS, only at the data source server.

Basic Networking with Static IP Address
Live Data Cloud Networking with Dynamic IP Address at Data Source
Network Forwarding for redirect path through any number of servers
One Way Networking for transferring through communication diodes

Basic Networking is used when the data source services have fixed IP addresses and can be accessed directly from each client application.

Live Data Cloud Networking is used when the data source services do not have a fixed IP address. An example would be a laptop or server PC that has a standard Internet connection and you want to access its data over the Internet.

Network Forwarding is used in corporate networks where you need to redirect / bounce network communications through one or more servers to reach the data source from client applications. Most commonly to connect industrial networks together with business networks.

One Way Networking is used to transfer data through networks that have communication diodes that only allow one direction of communications. Most commonly used by our nuclear power customers.

Each networking feature can be used on its own or any combination of features to allow end to end access from any client to any service.

Each data server can host data up to 10,000 client applications at a time.

Each client application can access up to 10,000 data servers.

Tag Syntax

Visit each networking type page for syntax examples on how to define client access to remote data services. The following in an introduction to using Basic Networking as an example.

Tag access from .NET applications, Web applications, Microsoft Excel, and service to service communications is simply defined and is all the same. This includes HMI, Trending, Data Logging, Tag Calculations, etc.

Example of Basic Networking:

\\192.168.0.1\TagName.Value

The IP address can be replaced with a network node or registered domain name where the OAS Service is running like www.mydomainname.com.

Alarms

Remote alarm service from Alarm Logging, Alarm Notification, Alarm .NET, and Web Alarm are defined by the AlarmNetworkNodes property.

Trend History

Trend HistoryTags in both .NET and Web applications can be used to direct history to a different data server than the realtime trend Tags. The network node syntax would be the same as the Tag access but replacing the Tag name with Data Logging Group Name.Field Name.

Example:

\\192.168.0.1\Data Logging Group 1.Field01

Web Applications

The serverURL in the HTML code will determine the first base data service the web application will communicate with. If the Tags also reside on that same server the Tag names in the HTML code would all just be defined as local tags.

Basic Networking Example: Access to Ramp.Value on 192.168.0.1 when data server has a fixed IP address and directly accessible.

serverURL: 'http://192.168.0.1:58725'

"tag":"Ramp.Value"

The following would be an example of a network forwarding to redirect communications through the data service 192.168.0.2 for web client access to tags on a data server with IP address 192.168.0.2.

serverURL: 'http://192.168.0.1:58725'

"tag":"\\192.168.0.2\Ramp.Value"

Notice that data communications in this example from the web client is redirected through 192.168.0.1 to 192.168.0.2.

Hosting data from a laptop or server would use the Live Data Cloud Networking feature. View Live Data Cloud Networking for setup of hosting your own data on the Internet with a standard Internet connection without the need for a fixed IP address.

OPCSystems.NET OPC Server

The OPCSystems.NET OPC Server provides access to the live Tags to third party OPC Clients. It is best to install the OPCSystems.NET OPC Server on the same PCs that are running the OPC Clients. No additional license is required on the OPC Client PCs. OPCSystems.NET will utilize WCF communications to tunnel data of the .NET TCP port and eliminate the need for DCOM.

The OPC Item in each OPC Client will specify the remote data server to communicate with.

Network.192.168.0.1.TagName.Value

AddNetworkNodeAlias Method

WPF HMI .NET and WinForm HMI .NET controls have an AddNetworkNodeAlias method supported in the WPFDashbaord.WPFNetworkNodes component, .NET Data Connector component, and OPCControls.OPCNetworkNodes component. This makes it possible to redirect communications from a data service to another with just a simple call.

VB Example:

Dim m_OPCWPFNetworkNodes As New OPCWPFDashboard.OPCWPFNetworkNodes
m_OPCWPFNetworkNodes.AddNetworkNodeAlias("localhost", "192.168.0.1")

C# Example:

OPCWPFDashboard.OPCWPFNetworkNodes m_OPCWPFNetworkNodes = new OPCWPFDashboard.OPCWPFNetworkNodes();
m_OPCWPFNetworkNodes.AddNetworkNodeAlias("localhost", "192.168.0.1");

TCP Port Numbers

The default TCP port number for .NET applications, Microsoft Excel, OPCSystems.NET OPC Server, and service to service communications is 58727. For instructions on how change the TCP port number view Change Default Network Port Number.

The default TCP port number for Web HMI, Web Trend, Web Alarm, and PCL iOS and Android applications is 58725. To set the default port number use the registration step of the Service Control application and set the serverURL in the web app to the desired port.

To check if the TCP port is open from a client system perform the steps in Remote OAS Service Access.

Legacy OAS Services

Legacy versions prior to version 12 used a default TCP port of 58724. This is called the WCF Port number. This is not applicable on services deployed to Linux.

Legacy OPCSystems older than version 5 use default TCP port 58723. This legacy port number is not adjustable, but can be enabled in the data server under Configure-Options-Networking and enable the property .NET Remoting Classic Networking for older client applications or older services to communicate to a new service. To enable a new service to talk to an older service than version 5 go to Configure-Options-Remote Services and enable the property Client .NET Remoting Classic Networking. In the newer client application components there are provisions in each component to enable classic .NET Remoting to talk to older services. If you are new to using Open Automation Software and are not connecting to legacy systems do not enable Classic .NET Remoting in any service or client application.

February 15, 2016January 16, 2018

FAQs – UDP Broadcast

Do I need to use UDP Broadcast to send data across a network of the Internet?

No, you only need to use UDP Broadcast on networks that have a communication diode that only allow one way communications.

Can UDP Broadcast be used to send data to multiple remote services?

Yes.

Do I need to have all of the source tags defined in the remote receiving services?

No, set the Data Source in the receiving node to UDP Client. View the video in the Videos-UDP Broadcast section.

Category: Networking

One Way Networking

More:

Network Forwarding

Live Data Cloud Networking

Basic Networking

Getting Started – Unidirectional Network Gateway

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

Step 9

Step 10

Step 11

Step 12

Step 13

Remote OAS Service Access

FAQs – Networking

Videos – Networking

Networking

Basic Networking

Unidirectional Gateway

Live Data Cloud

Adjustable WCF Port Number

Excel with Live Data Cloud

Data Log with Live Data Cloud

OPC Client with Live Data Cloud

Getting Started – Networking

FAQs – UDP Broadcast