Posted on

Installing SQL Server

Ensure that you have Administrative privileges on your computer

Download Microsoft® SQL Server® 2008 R2 SP1 – Express Edition with tools form here

64 bit version – SQLEXPRWT_x64_ENU.exe- 980.9 MB

32 Bit Version – SQLEXPRWT_x86_ENU.exe – 308.4 MB

After downloading reboot your computer and close all applications.

Installation

Run the downloaded SQLEXPRWT file

Select New Installation:

SQL System requirements 20

Accept the license terms and click Next:

SQL System requirements 21

Select All and Click Next:

SQL System requirements 22

Select Default Instance and select Next:

SQL System requirements 23

Select Next:

SQL System requirements 24

Select Next:

SQL System requirements 25

Select Next:

SQL System requirements 26

SQL Server installs…

Click Close:

SQL System requirements 27

Open SQL Server Management Studio

Accept the defaults and click Connect:

SQL System requirements 28

Posted on

Recommended Hardware

32 Bit and 64 Bit Operating Systems

For best performance choose a 64 bit operating system.

  • Open Automation Software version 4.0 or greater will take advantage of 64 bit operating systems to use up to 1 terabyte of memory.
  • Open Automation Software version 14.0 or greater can run on Linux 64 bit operating systems.
  • For any system that has more than 100,000 Tags a 64 bit operating system is required.
  • All versions of Open Automation Software targeting Windows will run on 32 bit operating systems up to 100,000 tags.

Number of Processors

Open Automation Software will take advantage of multiple processors and will evenly distribute processing of the service functions across all processors that are available.

  • It is recommended to allocate 2 processors for every 100,000 tags running in the service.
  • Allocate 1 additional processor for each set of 25,000 tags to be logged at a 1 second frequency.
  • Allocate 1 additional processor for every 50,000 tags to be trended at a 1 second rate for 1 hour of time frame.
  • Allocate an additional processor for each 25 clients or more connected to the service.

RAM

  • Allocate 4 Gigs of RAM for every 100,000 tags running in the service.
  • Allocate 4 Gigs of RAM for each set of 25,000 tags to be logged at a 1 second frequency.
  • Allocate 4 Gigs of RAM for every 50,000 tags to be trended at a 1 second rate for 1 hour of time frame.
  • Allocate 4 Gigs of RAM for each 25 Smart Clients connected to the service.

Minimum Requirements

Open Automation Software for Windows minimum hardware requirements would be a single Pentium II with 256 Megs of RAM and 100 Megabyte hard disk. This would be limited to a system that had 10,000 tags or less on the service, trending 1,000 tags, and logging 10,000 tags at a 1 second frequency. The number of clients would be limited to 10 clients for this minimum hardware configuration.

OAS Services

View the Operating Systems article for a list of all operating systems that the OAS Engine supports for both Windows and Linux.

Client Applications

For .NET applications for Windows deployment all components target .NET Framework 4.0 to run all all versions of Windows operating systems from Windows XP and newer.  View Operating Systems to see an entire list.

For client applications developed with OAS Cross-Platform HMI tools can be deployed to Windows 10, Linux, and Mac operating systems.

For .NET applications developed with the .NET Standard 2.0 assemblies including Universal Driver Interface, OASData, and OAS Config they can be deployed to Windows operating system with .NET Framework 4.6.2 or greater, and Linux operating systems listed in Operating Systems article.

For thin client applications hardware devices that have browsers that support JSON jQuery will work. This includes the following:

  • All Windows and Linux Operating Systems
  • All versions of the iPhone
  • All versions of the Android
  • Windows Smartphone 7 and 8
  • All versions of iPads
Posted on

Operating Systems

Open Automation Software has 3 target deployments: Linux, Windows, and Windows 10 IoT Core.

 

Linux

NOTE: For any Linux installation, general knowledge of Linux server configuration is required. This includes managing files, users, permissions, and configuring services (daemons in systemd).

OSVersionArchitecturesNotes
Red Hat Enterprise Linux6+x64Microsoft support policy
Red Hat Enterprise Linux
CentOS
Oracle Linux		7+x64Red Hat support policy
CentOS lifecycle
Oracle Linux lifecycle
Fedora31+x64Fedora lifecycle
Debian9+x64, ARM32, ARM64Debian lifecycle
Ubuntu16.04+x64, ARM32, ARM64Ubuntu lifecycle
Linux Mint18+x64Linux Mint end of life announcements
openSUSE15+x64OpenSUSE lifecycle
SUSE Enterprise Linux (SLES)12 SP2+x64SUSE lifecycle
NOTE: While running OAS on a RaspberryPi 4+ is fully supported, the default Raspbian OS is not. Please choose one of the supported Linux distributions above, making sure to install a server variant as opposed to a desktop variant. Extensive testing with Ubuntu Server has proven to be the most reliable and simplest to configure.
 
The OAS Platform utilizes the .NET Core Framework and is self contained, so there is no need to install .NET Core before installing OAS. For more information on supported Linux Distributions, see the following MS article on OS Support.

Windows 10 IoT Core

The Win 10 IoT Core deployment of OAS targets .NET 6 as self-contained.

Windows

The Windows target  has 6 different Framework installations for compatibility for older systems.  For server systems and client applications running on Windows the following frameworks are supported:

.NET 6

The latest version of the OAS Engine targets .NET 6 as self-contained.

To to installed on 64 bit Operating System only.

.NET Framework 4.6.1

For use with Visual Studio 2017, 2019, and 2022

The most up to date version is for .NET Framework 4.6.1 and will run on the following Windows Operating Systems for both 32 bit and 64 bit operating systems on all service packs.

  • Windows 11 – 64 bit
  • Windows Server 2022 – 64 bit
  • Windows 10 – 32 bit and 64 bit
  • Windows 10 IoT Enterprise 64 bit
  • Windows Server, version 2004 – 64 bit
  • Windows 8.1 – 32 bit and 64 bit
  • Windows 8 – 32 bit and 64 bit
  • Windows 7 SP1 – 32 bit and 64 bit
  • Windows Server 2019- 64 bit
  • Windows Server, version 2004 – 64 bit
  • Windows Server, version 1909 – 64 bit
  • Windows Server, version 1809 – 64 bit
  • Windows Server, version 1803 – 64 bit
  • Windows Server, version 1709 – 64 bit
  • Windows Server 2016 – 64 bit
  • Windows Server 2012 R2 – 64 bit
  • Windows Server 2012 – 64 bit
  • Windows Server 2008 R2 SP1 – 64 bit

.NET Framework 4.5.2 (Legacy versions)

For use with Visual Studio 2017 and 2019

  • Windows Vista SP2 – 32 bit and 64 bit
  • Windows Server 2008 SP2 – 32 bit and 64 bit

.NET Framework 4.0 (Legacy versions)

For use with Visual Studio 2010, 2012, 2013, 2015, and 2017

  • Windows XP – 32 bit and 64 bit
  • Server 2003 – 32 bit and 64 bit

.NET Framework 3.5 (Legacy versions)

For use with Visual Studio 2008

  • Version 9.0 of Open Automation Software is for .NET Framework 3.5 and will run on all Windows Operating Systems for both 32 bit and 64 bit operating systems.

.NET Framework 2.0 (Legacy versions)

For use with Visual Studio 2005

  • Version 4.0 of OPCSystems.NET is for .NET Framework 2.0
  • Will run on Windows 2000 Professional (with .NET Framework 2.0) and all 32 bit operating systems supporting .NET Framework 2.0

.NET Framework 1.1 (Legacy versions)

For use with Visual Studio 2003

  • Version 1.1 of OPCSystems.NET is for .NET Framework 1.1 and will run on the following Windows Operating Systems for 32 bit operating systems.
  • Will run on Windows 2000 Professional (with .NET Framework 2.0) and all 32 bit operating systems supporting .NET Framework 1.1

Client Applications

For client applications Smart Clients will run on all Windows operating systems. All components are compiled for Any CPU and are 100% managed.

For thin client applications all browsers that support JSON jQuery. This includes the following but not limited to:

  • Chrome
  • Internet Explorer 8.0 or greater
  • Safari
  • Firefox
  • Mozilla
Posted on

OAS System Requirements

Open Automation Software utilizes 3 Windows Services when running on Windows and 1 daemon service when running on Linux.  The main service is referred to as the OAS Engine.  All services are multi-threaded and are compiled to Any CPU for execution on both 32 bit and 64 bit Windows operating systems and Linux 64 for Linux.

The following service attributes affect what software and hardware requirements are to be selected:

Number of Tags

The number of tags running in the service will determine the minimum RAM and recommend number of processors required to run the OAS Services.  For any system that is above 100,000 tags a 64 bit operating system is required. For each 100,000 tags implemented 2 processors and 4 Gigs of RAM is recommended.

Data Logging

The data logging frequency and the number of data logging groups to be run on the service will determine how many processors are required and how much RAM will be needed to execute the data logging.

Allocate a processer and 4 Gigs of RAM for every 25,000 tags to be logged at a 1 second frequency. If the logging rate is much faster allocate more processers and more RAM.

Database Engine Requirements

If the database engine is to run on the same PC as Open Automation Software each database engine has its own system requirements that must be considered in addition to the Open Automation Software requirements. Most likely for data logging, historical replay to trends, and reports the database engine will be the most resource intensive execution above Open Automation Software.

For each 100,000 tags to be logged at a frequency of 1 second you should allocate 16 Gigs of RAM for the performance of the database engine.

Trending

The number of different time frames for real-time trending combined with the number of tags enabled for trending will impact the resources required to cache and perform trending.

Allocate a processer and 4 Gigs of RAM for every 50,000 tags to be trended at a 1 second frequency over 1 hour time frame. If there are multiple timeframe and sample rate combinations allocate more processers and more RAM.

Use Configure-Options-Trending to set the Maximum Allowed Time Frame to limit the realtime trend cache.

Client applications running on remote PCs will perform better for resource intensive trending if the graphics card is better.

Number of Clients for HMI, Trending, and Alarming

Allocate 1 processor and 4 Gigs of RAM for each set of 25 clients connected to the service. For example if 100 client systems will be communicating to the service an additional 4 processors with an additional 16 Gigs of RAM will be required.

Web Applications

Web applications are more server intensive that Smart Client applications. For Web applications that display a lot of data for more than 25 clients at a time load balancing across multiple servers may be required for web applications. For smaller web application allocate a server for each 100 clients.  For larger web applications allocate a server for each 25 concurrent clients.

Windows Presentation Foundation HMI

For client applications that are using Windows Presentation Foundation (WPF) components the best performance is on Windows 10, 8, 7, and Vista. Windows Server 2008, Server 2003, and Windows XP using OAS version 11 or older can also run WPF client applications, but there may be a higher CPU load for more graphic intensive animations.  Windows 2000 Professional cannot run WPF client applications.

Cross-Platform HMI

For client applications to run on both Windows 10 and Linux the OAS Cross-Platform HMI can be utilized to build one application that serves both Windows and Linux operating systems.

Posted on

Start Service

To run OAS as a service on Linux view how to Setup OAS Engine as a Linux Service or Daemon.

After you install the Windows version of OAS use the OAS Service Control application to start the OAS Service, OAS Data Service, and OAS Database Service if they are not already started.

These services will automatically start when you restart your computer unless you set the startup type to Manual for each of the services.

Service Control 1

You can optionally Start Runtime here also or later in the example. All modifications are allowed during Runtime except loading a Tag configuration file.

You can add, delete, and modify Tags, Data Logging Groups, Alarm Logging Groups, Alarm Notification Groups, Recipes, Reports, Security Groups, and Security Users during Runtime.

Posted on

Quick Start Example

Use this Quick Start Section to become familiar with the product features of Open Automation Software. Each section walks you through a very basic setup and use of the product features. Feel free to skip sections that do not pertain to your application needs.

Consider both your Data Sources and what you would like to perform with the data to determine which of the following steps in the Quick Start you would like to implement.

Use the Data Sources topic to select which data sources you will be using.

Use the Data Destinations topic to determine where the data will be shared.

Please view the Getting Started with Open Automation Software Video to familiarize yourself with installation, setting up Tags, selecting Data Sources and Destinations, and implementing Networking and Security.

  • 00:00 – Introduction
  • 00:13 – Video Topics
  • 00:25 – Where to download OAS
  • 01:26 – Activate a new license
  • 01:52 – What’s a Tag in OPC Terminology?
  • 02:03 – How to Configure Tags
  • 02:16 – Ways to Add Tags in OAS
  • 02:22 – Add Tags Manually
  • 02:27 – Add tags using csv import export
  • 02:36 – Add tags one click import for AB, OPC UA or OPC DA
  • 02:56 – Add Tags Programmatically
  • 03:16 – Adding a tag manually
  • 07:07 – Saving Tag Configuration
  • 07:48 – OAS as a service-oriented architecture
  • 07:58 – Data Sources
  • 08:07 – Built In Drivers
  • 08:18 – OPC & OPC UA
  • 08:25 – One Click OPC
  • 08:34 – MQTT
  • 08:47 – AWS IoT Gateway
  • 09:02 – Recipe Product
  • 09:13 – .NET Data Connector
  • 09:29 – Universal Driver Interface
  • 09:53 – Data Destination
  • 10:02 – Data Historian
  • 10:39 – Web Alarm & Alarm.NET
  • 10:51 – Alarm Notification
  • 11:00 – Web HMI
  • 11:19 – Web Trend
  • 11:30 – Programmatic Interface
  • 12:02 – .NET WPF HMI
  • 12:17 – .NET Trend
  • 12:24 – .NET Alarm
  • 12:30 – Data route
  • 12:45 – Reports
  • 12:55 – Excel
  • 13:11 – Networking
  • 13:32 – Basic Networking
  • 13:53 – Security
  • 14:12 – More Information

The Basic Start Video is a good video that demonstrates some of the most commonly used features of Open Automation Software (previously called OPCSystems.NET).

  • System Configuration: How to setup Tags, Data Logging, Alarm Logging, Alarm Notification, Alarm and Events OPC Servers, Reports, Recipes, Security, Security Users, Options, Live Data Cloud networking, UDP Broadcast networking, and Licensing.
  • .NET WPF HMI: How to create a WPF HMI application.
  • .NET WinForm HMI: How to create a WinForm HMP application.
  • .NET Trend: How to add trending to a WPF or WinForm application.
  • .NET Alarm: How to add alarming to a WPF or WinForm application.
  • Web HMI: How to create a Web HMI application.
  • Web Trend: How to create a Web trending application.
  • Web Alarm: How to create a Web alarming application.
  • Excel: How to add realtime data access to Microsoft Excel.
  • Data Route: How to automatically transfer data from any Data Source to another Data Source.
  • 3rd Party OPC Client: How to access Open Automation Software tag values in an OPC Client.
  • Networking: Videos and syntax on how to best implement networking and the different ways that is possible.
  • Programmatic Interface: Examples on how to access Configurations and Real-time data via programmatic interface using .NET or JSON-jQuery.
  • Universal Driver Interface: How to create a communication driver for OAS.
  • Redundancy: Best practices for implementing redundant systems.
  • Frequently Asked Questions: Common topics to speed the understanding of all Open Automation Software features.
  • Videos: A complete list of all training videos.
  • Support: Contact information for obtaining sales or technical product assistance.
Posted on

Evaluation Guide

Steps to Evaluate Open Automation Software

Try Open Automation Software for free. Using the instructions below, you can download a fully-functional 30-day trial of the OAS Platform.

Step 1 – Download and Install

  • Install Open Automation Software.
    • Note: All products and communication drivers are included with this one setup.

Step 2 Install other required applications (optional)

  • Visual Studio – If you plan to develop .NET applications and you will need Microsoft Visual Studio. If you do not have a copy of Visual Studio visit Microsoft Visual Studio Community page (formerly known as Visual Studio Express) and select to download Visual Studio Community and install.  This is a free version of Visual Studio.
    • Note: If you install Visual Studio after Open Automation Software uninstall Open Automation Software and reinstall.
  • SQL Server Express:  If you plan to implement Data Logging or Alarm Logging and need a free database engine visit Microsoft’s SQL Server Express product page and select Download SQL Server Express and install. This is a free version of SQL Server.
    • Note: Open Automation Software also works with Oracle, mySQL, MongoDB, InfluxDB, SQLite, PostgreSQL, MariaDB, Amazon RDS, Aurora, Redshift, Google Firebase, and CSV files.  Also classic MS Access in the Windows version only.

Step 3

Make use of the support resources:

  • This online help -View the Contents section of this file for a list of easy to follow guides in setting up the most common features of Open Automation Software.
  • View the Videos section of this file for a list of online video training. You can follow along while watching the video while you learn quickly and also see other important aspects.
  • The Basic Start Video is a good video that demonstrates some of the most commonly used features of Open Automation Software with a .NET application.
  • Review the FAQ – In each section there is a Frequently Asked Questions section which is all listed in the common Frequently Asked Questions.

Step 4

Contact Support if you have questions about any of the products or steps to implement Open Automation Software.

1-303-679-0898

support@oasiot.com

Posted on

Windows Installation

Install

On Windows run the downloaded Setup.exe file to install one or more of the Open Automation Software features. Select the default Typical installation if you are not sure what features to use or the Custom installation if you want to save disk space on the target system.

When prompted agree to the End User License Agreement to continue the installation.

Start Services

When the installation is finished the OAS Service Control application will appear if the OAS Service was installed. Use this application to start the 3 Services. If this is the first time installing the software it will automatically enter Runtime with an example Tag Configuration.

If you restart the computer the OAS Service will automatically start. You can change the start mode of the OAS Service using the Service Control Manger built into the operating system.

Other Platforms

For installation in Linux or Docker, see the following:

Posted on

Download

New System

Download the Windows or Linux OAS installation here.

Once downloaded, proceed with the Installation section in Getting Started.

Existing System

Automatic Update

To upgrade an existing system go to Configure-Options-License and select Update Version.

Manual Update

First download the OAS Platform.

For Windows next uninstall Open Automation Software using Add / Remove Programs from the Control Panel.  Run the new setup and start the 3 OAS Services.

For Linux simply copy in the extracted files to the OAS Engine directory.

Do not delete the installation directory, options, or license files and all configuration data will remain.

Posted on

Frequently Asked Questions – License

How can I see how many tags are currently in use for my license?
Select Configure-System Status using the Configure application and view the Totals section of the information provided.
Why do I get a warning my tag count license is exceeded?
There is a default demo Tag configuration file that is set to load under Configure-Options.  If you are not using these tags remove this default file or create your own only with your own tags and restarted the 3 OAS Services using the OAS Service Control.
How do I license the software?
Use Configure-License with the Configure application with one of the methods listed in the System Configuration – License section of this help file.
What happens when I exceed the tag limit?
  • A warning appears when you use the Configure application.
  • Also the Runtime will not start if you have too many Open Automation Software Tags loaded.
  • If you are using DirectOPC once you reach the tag limit no other DirectOPC Items will be added.
  • You can see how many tags you are using under Configure-System Status in the Totals section.
Do I need to reinstall the software after I purchase a license?
No, the one common download of Open Automation Software contains all of the products, drivers, and is activated with a Serial Number with an Internet connection, or with a License Key without an Internet connection.
I just purchased a 100 tag license and now I get a message that the tag limit is exceeded?
There are more than 100 tags in the demo tag configuration. Delete the demo tags and set the default tag configuration file under Configure Option Default Files.
Do I need to Kill a license if I am upgrading the version of Open Automation Software?
No, the license will remain active while you uninstall and reinstall Open Automation Software.
How do I move a license from one computer to another?
If you software license is up to date with a current maintenance use the steps in Moving a Software License.
Do I need to kill or backup the license when I uninstall and reinstall the software?
No the license will remain, but do not delete any files from C:\Program Files\Open Automation\OAS\ or C:\ProgramData\OpenAutomationSoftware\ after you uninstall Open Automation Software.
What will make my license stop working?
  • If you upgrade your software to the latest version without an active maintenance plan that covers that version.
  • If you change the CPU mother board. This includes cloning the image of the drive and restoring to a new PC.
  • If you remove all of the hard disks from the system that were present when the software was licensed.
  • With older OAS version 9 or less if you remove all of the Ethernet cards from the system that were present when the software was licensed.