Frequently Asked Questions
Search Our FAQs
[ultimate-faq-search]
Or Browse FAQ Categories:
Getting Started
- The customer is not experienced in creating WPF applications but has strong knowledge in building Windows Forms applications and the application is not graphics intensive.
- The application is for mainly displaying values.
- The customer wants to use Open Automation Software Controls in an existing Windows Forms Application.
- The customer wants to write a service to read and write data to Open Automation Software.
- The customer application will be running on Windows 2000 Professional.
- The customer has no preference and he want to use graphics.
- The customer would like Lamps, Switches, Shapes, Gauges, Pie Charts, Bar Charts, PID Controls or story boards built into the control library.
- The customer wants to be using the latest technology.
- The customer’s application is graphic centered as opposed to mainly a data display.
- The customer wants to automatically scale his application to the monitor size.
- The customer wants the ability to Scale, Rotate or Skew object in the application.
- If you plan to run the application on a smart phone or non widows operating system.
Licencing
Windows Service
Tags
- Create a Tag called DateAndTime with the Date Type of String and the Data Source of DateTimeString.
- Modify the Calculation in both Reset tags to the following.
Import CSV
Select the OAS Service that you desire to import a CSV file to the Tag configuration and click the CSV Import button on the top menu to import a Comma Separated Variable file. Use the Export CSV feature to generate a CSV file. You can then use Microsoft Excel or other CSV compatible application to add or modify Tags. Only the Tag name is the required field. You can select to include or exclude all other fields. Only those fields that are found in the header will be used to update the properties of the Tags. If a Tag already exists it will be updated. If the Tag does not exist it will be created. Existing Tags that are not specified in the CSV file will not be updated or deleted. The same tag parameter structure can be used to programmatically define tags with the TagCSVImport method on the free to use OASConfig and OPCSystems components. This is demonstrated in .NET Server Configuration-CSV Import and Export example.Export CSV
Select the OAS Service that you desire to extract the Tag configuration from and select click the CSV Export button to generate a Comma Separated Variable file. You can then use Microsoft Excel or other CSV compatible application to add or modify Tags. Use the Import CSV feature to then import the modified CSV file.Data Logging
Download and install the Microsoft Data Access Components 2.8.
https://www.microsoft.com/en-au/download/details.aspx?id=21995
The following update will correct this issue.
For Office 2010, the following update will correct this issue.
https://www.microsoft.com/en-us/download/details.aspx?id=39664
For Office 365 (please note, by default Office365 installs the 32-bit version regardless of your system), use:
https://www.microsoft.com/en-us/download/details.aspx?id=54920
OAS version 12.00.0043 now uses OracleManagedDataAccess assembly. If you are using an older version of OAS we recommend to update to the latest version. If you have upgraded from a previous version and using TNSNAMES.ORA name in the Database file please see the FAQ on TNSNAMES.ORA.
- Please review the columns in each table with the SQL Server Management Studio. If they have been changed to not allow null values change them back to allow null values.
- Go to each logging group and enable the property Discard Null Rejects under the Database tab. Keep in mind that with this property enabled the records to be logged that contain null values will be discarded and not logged.
View the Data Logging Errors troubleshooting guide for a complete list of error causes and solutions.
View the source of the problem under Configure-System Errors.
The complete history of errors can be viewed under C:\Program Files\Open Automation Software\OAS\Log or the path that is set under Configure-Options-System Logging.
Enable Log Data Logging Transactions under Configure-Options-System Logging to see the details of each transaction and error returned from the database engine.
Alarm Logging
Download and install the Microsoft Data Access Components 2.8.
https://www.microsoft.com/en-au/download/details.aspx?id=21995
The following update will correct this issue.
For Office 2010, the following update will correct this issue.
https://www.microsoft.com/en-us/download/details.aspx?id=39664
For Office 365 (please note, by default Office365 installs the 32-bit version regardless of your system), use:
https://www.microsoft.com/en-us/download/details.aspx?id=54920
Alarm Notification
Create a new Boolean Tag with the tag name EscalateAlarm.
Enable the Digital Alarm limit in this new Tag with a Time Delay of ? Seconds.
Under the Tags tab of an existing or new Alarm Notification group the property “Set Tag When Alarm Active and Not Acknowledged” to a Boolean Tag with the Data Source of Value.
EscalateAlarm.AlarmStatusDigital can then be used to enable a second Alarm Notification monitoring the same alarms of the first Alarm Notification group with the Activate with Tag property in the second Alarm Notification Group.
Note: Under Configure-Options-Alarms uncheck “Update Alarm Status Immediately Without Alarm Time Delay”.
This will then enable the second alarm notification group when the alarms monitored in the first group.
Download and install the Microsoft Data Access Components 2.8.
https://www.microsoft.com/en-au/download/details.aspx?id=21995
The following update will correct this issue.
For Office 2010, the following update will correct this issue.
https://www.microsoft.com/en-us/download/details.aspx?id=39664
For Office 365 (please note, by default Office365 installs the 32-bit version regardless of your system), use:
https://www.microsoft.com/en-us/download/details.aspx?id=54920
- Configure OAS application: Use the LogIn from the menu.
- WPF application: Use the OPCWPFDashboard.OPCWPFLogIn component with the LogIn method. (Only need to do this once for the entire application)
- WinForm application: Use the OPCControls.OPCControlsLogIn component with the LogIn method. (Only need to do this once for the entire application)
- OPCTrend control in WPF or WinForm application: Use the LogIn method. (Need to do this for each trend control)
- OPCAlarm control in WPF or WinForm application: Use the LogIn method. (Need to do this for each trend control)
- Excel: Use the security login RTD formula generated with the OAS Excel Wizard application. (Only need to do this once for the entire Workbook)
- HTML5 Web application: Use the authentication token see the Authentication topic in the Web HMI Programming Reference-HTML5 section.
All default configuration files would be specified under Configure-Options.
Setup Security and select which Options you want users to be able to modify in the Default group and for each Security Group.
Data Source Quality
Use Configure-Tags to verify that the data quality of the source tags is "Good Quality".Security
The Default security group on either the local or remote OAS Engine may have Disable All Tags from Reading checked under the Read Tags Tab. See Restrict Tag Access of Security setup to see how read, write, and browse access can be restricted. View how to Implement User Credentials in Client Applications to provide log in method for each user in the .NET application.Network
.NET applications can be defined to communicate to remote OAS Engines. See Network Communications Troubleshooting to verify that port 58727 is allowing both incoming and outgoing traffic through your firewall.Tag Path
The full tag path would include the full tag name including its parent groups and the variable of the Tag.MyGroup.MyTag.ValueTag names are case sensitive and the current value of a tag would be .Value as the most common variable.
\\192.168.0.1\TagName.Value
License
Use Configure-License to verify that a product feature .NET Data Connector, WinForm HMI, or WPF HMI is enabled on the data source system where the tags are located.Target Framework for WPF and WinForm Applications
The project type for WinForm and WPF applications should be set to include (.NET Framework) and target .NET Framework 4.6.1 or greater. See the correct project type for WinForm above that is listed as Windows Forms App (.NET Framework) while Windows Forms App would not be the correct project type.Assembly References
Visual Studio on some operating systems will assign a legacy assembly to the project causing an incompatibility due to an older version of the reference assembly. A common assembly that can be incorrect is Newtonsoft.Json that has been registered in the GAC by another software product. Select Newtonsoft.Json under the Project References to verify the correct path and version as 13.0.0.0..NET Assembly is Blocked
If you have copied an application or project to another computer you may need to Unblock one or more the .dll files. Right click on the .dll file that you have downloaded. Check the Unblock checkbox for security as shown in the example below, then click Apply or OK.Legacy .NET Application with OAS Version 17
- .NET 6
- .NET 5
- .NET Core 2.0 or greater
- .NET Framework 4.61 or greater
- Xamarin.iOS 10.14 or greater
- Xamarin.Android 8.0 or greater
- UWP 1.0.0.16299 or greater
- C:\Program Files\Open Automation Software\OAS\Controls\NetFramework\OPCWPFDashboard\
- C:\Program Files\Open Automation Software\OAS\Controls\NetFramework\OPCControls\
- C:\Program Files\Open Automation Software\OAS\Controls\NetFramework\OPCAlarmControl\
- C:\Program Files\Open Automation Software\OAS\Controls\NetFramework\OPCAlarmDataOnly\
- C:\Program Files\Open Automation Software\OAS\Controls\NetStandard\OASAlarms\
- C:\Program Files\Open Automation Software\OAS\Controls\NetFramework\OPCTrendControl\
- C:\Program Files\Open Automation Software\OAS\Controls\NetFramework\OPCTrendDataOnly\
- C:\Program Files\Open Automation Software\OAS\Controls\NetStandard\OASTrends\
- C:\Program Files\Open Automation Software\OAS\Controls\NetFramework\OPCSystemsDataConnector\
- C:\Program Files\Open Automation Software\OAS\Controls\NetStandard\OASData\
- C:\Program Files\Open Automation Software\OAS\Controls\NetFramework\OPCSystems\
- C:\Program Files\Open Automation Software\OAS\Controls\NetStandard\OASConfig\
- OPCControls.dll
- OPCSystemsInterface.dll
Data Source Quality
Use Configure-Tags to verify that the data quality of the source tags is "Good Quality".Security
The Default security group on either the local or remote OAS Engine may have Disable All Tags from Reading checked under the Read Tags Tab. See Restrict Tag Access of Security setup to see how read, write, and browse access can be restricted. View how to Implement User Credentials in Client Applications to provide log in method for each user in the .NET application.Network
.NET applications can be defined to communicate to remote OAS Engines. See Network Communications Troubleshooting to verify that port 58727 is allowing both incoming and outgoing traffic through your firewall.Tag Path
The full tag path would include the full tag name including its parent groups and the variable of the Tag.MyGroup.MyTag.ValueTag names are case sensitive and the current value of a tag would be .Value as the most common variable.
\\192.168.0.1\TagName.Value
License
Use Configure-License to verify that a product feature .NET Data Connector, WinForm HMI, or WPF HMI is enabled on the data source system where the tags are located.Target Framework for WPF and WinForm Applications
The project type for WinForm and WPF applications should be set to include (.NET Framework) and target .NET Framework 4.6.1 or greater. See the correct project type for WinForm above that is listed as Windows Forms App (.NET Framework) while Windows Forms App would not be the correct project type.Assembly References
Visual Studio on some operating systems will assign a legacy assembly to the project causing an incompatibility due to an older version of the reference assembly. A common assembly that can be incorrect is Newtonsoft.Json that has been registered in the GAC by another software product. Select Newtonsoft.Json under the Project References to verify the correct path and version as 13.0.0.0..NET Assembly is Blocked
If you have copied an application or project to another computer you may need to Unblock one or more the .dll files. Right click on the .dll file that you have downloaded. Check the Unblock checkbox for security as shown in the example below, then click Apply or OK.Legacy .NET Application with OAS Version 17
- .NET 6
- .NET 5
- .NET Core 2.0 or greater
- .NET Framework 4.61 or greater
- Xamarin.iOS 10.14 or greater
- Xamarin.Android 8.0 or greater
- UWP 1.0.0.16299 or greater
- C:\Program Files\Open Automation Software\OAS\Controls\NetFramework\OPCWPFDashboard\
- C:\Program Files\Open Automation Software\OAS\Controls\NetFramework\OPCControls\
- C:\Program Files\Open Automation Software\OAS\Controls\NetFramework\OPCAlarmControl\
- C:\Program Files\Open Automation Software\OAS\Controls\NetFramework\OPCAlarmDataOnly\
- C:\Program Files\Open Automation Software\OAS\Controls\NetStandard\OASAlarms\
- C:\Program Files\Open Automation Software\OAS\Controls\NetFramework\OPCTrendControl\
- C:\Program Files\Open Automation Software\OAS\Controls\NetFramework\OPCTrendDataOnly\
- C:\Program Files\Open Automation Software\OAS\Controls\NetStandard\OASTrends\
- C:\Program Files\Open Automation Software\OAS\Controls\NetFramework\OPCSystemsDataConnector\
- C:\Program Files\Open Automation Software\OAS\Controls\NetStandard\OASData\
- C:\Program Files\Open Automation Software\OAS\Controls\NetFramework\OPCSystems\
- C:\Program Files\Open Automation Software\OAS\Controls\NetStandard\OASConfig\
DataTable myDataTable; myDataTable = opcTrendControl1.GetTrendDataTable();The following code can be used to programmatically get history data and return the data to a DataTable.
private void button1_Click(object sender, EventArgs e) { DateTime endTime = DateTime.Now; DateTime startTime = endTime.AddMinutes(-20); opcTrendControl1.HistorySelect(startTime, endTime); } private void opcTrendControl1_HistoryDataArrived() { DataTable myDataTable; myDataTable = opcTrendControl1.GetTrendDataTable(); dataGridView1.DataSource = myDataTable; }
- Nevron.Chart.dll
- Nevron.Chart.WinForm.dll
- Nevron.GraphicsGL.dll
- Nevron.Presentation.dll
- Nevron.System.dll
- OPCSystemsInterface.dll
- OPCTrendControl.dll
Data Source Quality
Use Configure-Tags to verify that the data quality of the source tags is "Good Quality".Security
The Default security group on either the local or remote OAS Engine may have Disable All Tags from Reading checked under the Read Tags Tab. See Restrict Tag Access of Security setup to see how read, write, and browse access can be restricted. View how to Implement User Credentials in Client Applications to provide log in method for each user in the .NET application.Network
.NET applications can be defined to communicate to remote OAS Engines. See Network Communications Troubleshooting to verify that port 58727 is allowing both incoming and outgoing traffic through your firewall.Tag Path
The full tag path would include the full tag name including its parent groups and the variable of the Tag.MyGroup.MyTag.ValueTag names are case sensitive and the current value of a tag would be .Value as the most common variable.
\\192.168.0.1\TagName.Value
License
Use Configure-License to verify that a product feature .NET Data Connector, WinForm HMI, or WPF HMI is enabled on the data source system where the tags are located.Target Framework for WPF and WinForm Applications
The project type for WinForm and WPF applications should be set to include (.NET Framework) and target .NET Framework 4.6.1 or greater. See the correct project type for WinForm above that is listed as Windows Forms App (.NET Framework) while Windows Forms App would not be the correct project type.Assembly References
Visual Studio on some operating systems will assign a legacy assembly to the project causing an incompatibility due to an older version of the reference assembly. A common assembly that can be incorrect is Newtonsoft.Json that has been registered in the GAC by another software product. Select Newtonsoft.Json under the Project References to verify the correct path and version as 13.0.0.0..NET Assembly is Blocked
If you have copied an application or project to another computer you may need to Unblock one or more the .dll files. Right click on the .dll file that you have downloaded. Check the Unblock checkbox for security as shown in the example below, then click Apply or OK.Legacy .NET Application with OAS Version 17
- .NET 6
- .NET 5
- .NET Core 2.0 or greater
- .NET Framework 4.61 or greater
- Xamarin.iOS 10.14 or greater
- Xamarin.Android 8.0 or greater
- UWP 1.0.0.16299 or greater
- C:\Program Files\Open Automation Software\OAS\Controls\NetFramework\OPCWPFDashboard\
- C:\Program Files\Open Automation Software\OAS\Controls\NetFramework\OPCControls\
- C:\Program Files\Open Automation Software\OAS\Controls\NetFramework\OPCAlarmControl\
- C:\Program Files\Open Automation Software\OAS\Controls\NetFramework\OPCAlarmDataOnly\
- C:\Program Files\Open Automation Software\OAS\Controls\NetStandard\OASAlarms\
- C:\Program Files\Open Automation Software\OAS\Controls\NetFramework\OPCTrendControl\
- C:\Program Files\Open Automation Software\OAS\Controls\NetFramework\OPCTrendDataOnly\
- C:\Program Files\Open Automation Software\OAS\Controls\NetStandard\OASTrends\
- C:\Program Files\Open Automation Software\OAS\Controls\NetFramework\OPCSystemsDataConnector\
- C:\Program Files\Open Automation Software\OAS\Controls\NetStandard\OASData\
- C:\Program Files\Open Automation Software\OAS\Controls\NetFramework\OPCSystems\
- C:\Program Files\Open Automation Software\OAS\Controls\NetStandard\OASConfig\
DataTable myDataTable; myDataTable = opcAlarmControl1.GetAlarmDataTable();
- C1.Win.C1FlexGrid2.dll
- OPCAlarmControl.dll
- OPCSystemsInterface.dll
Data Source Quality
Use Configure-Tags to verify that the data quality of the source tags is "Good Quality".Security
The Default security group on either the local or remote OAS Engine may have Disable All Tags from Reading checked under the Read Tags Tab. See Restrict Tag Access of Security setup to see how read, write, and browse access can be restricted. View how to Implement User Credentials in Client Applications to provide log in method for each user in the .NET application.Network
.NET applications can be defined to communicate to remote OAS Engines. See Network Communications Troubleshooting to verify that port 58727 is allowing both incoming and outgoing traffic through your firewall.Tag Path
The full tag path would include the full tag name including its parent groups and the variable of the Tag.MyGroup.MyTag.ValueTag names are case sensitive and the current value of a tag would be .Value as the most common variable.
\\192.168.0.1\TagName.Value
License
Use Configure-License to verify that a product feature .NET Data Connector, WinForm HMI, or WPF HMI is enabled on the data source system where the tags are located.Target Framework for WPF and WinForm Applications
The project type for WinForm and WPF applications should be set to include (.NET Framework) and target .NET Framework 4.6.1 or greater. See the correct project type for WinForm above that is listed as Windows Forms App (.NET Framework) while Windows Forms App would not be the correct project type.Assembly References
Visual Studio on some operating systems will assign a legacy assembly to the project causing an incompatibility due to an older version of the reference assembly. A common assembly that can be incorrect is Newtonsoft.Json that has been registered in the GAC by another software product. Select Newtonsoft.Json under the Project References to verify the correct path and version as 13.0.0.0..NET Assembly is Blocked
If you have copied an application or project to another computer you may need to Unblock one or more the .dll files. Right click on the .dll file that you have downloaded. Check the Unblock checkbox for security as shown in the example below, then click Apply or OK.Legacy .NET Application with OAS Version 17
- .NET 6
- .NET 5
- .NET Core 2.0 or greater
- .NET Framework 4.61 or greater
- Xamarin.iOS 10.14 or greater
- Xamarin.Android 8.0 or greater
- UWP 1.0.0.16299 or greater
- C:\Program Files\Open Automation Software\OAS\Controls\NetFramework\OPCWPFDashboard\
- C:\Program Files\Open Automation Software\OAS\Controls\NetFramework\OPCControls\
- C:\Program Files\Open Automation Software\OAS\Controls\NetFramework\OPCAlarmControl\
- C:\Program Files\Open Automation Software\OAS\Controls\NetFramework\OPCAlarmDataOnly\
- C:\Program Files\Open Automation Software\OAS\Controls\NetStandard\OASAlarms\
- C:\Program Files\Open Automation Software\OAS\Controls\NetFramework\OPCTrendControl\
- C:\Program Files\Open Automation Software\OAS\Controls\NetFramework\OPCTrendDataOnly\
- C:\Program Files\Open Automation Software\OAS\Controls\NetStandard\OASTrends\
- C:\Program Files\Open Automation Software\OAS\Controls\NetFramework\OPCSystemsDataConnector\
- C:\Program Files\Open Automation Software\OAS\Controls\NetStandard\OASData\
- C:\Program Files\Open Automation Software\OAS\Controls\NetFramework\OPCSystems\
- C:\Program Files\Open Automation Software\OAS\Controls\NetStandard\OASConfig\
Yes, refer to the OAS Example Service Code for working code examples if both C# and Visual Basic.
- .NET 5
- .NET Core 2.o or greater
- .NET Framework 4.61 or greater
- Xamarin.iOS 10.14 or greater
- Xamarin.Android 8.0 or greater
- UWP 1.0.0.16299 or greater
Using SSL with Web HMI is fully supported. You must first install an SSL Certificate on your server for the domain name(s) that you intend to use, for example “https://hmi.myserver.com:58726”. Once the certificate is installed properly on the server, check Use SSL and select the installed certificate from the dropdown menu. For detailed instructions, please see read: Configuring OAS Web Services. Purchasing and installing an SSL certificate is outside of the scope of the OAS product. For more information on Windows and Certificates, see the following article.
Please enable .NET Framework 3.5 in the operating system and then reinstall OAS.
https://docs.microsoft.com/en-us/dotnet/framework/install/dotnet-35-windows-10
Step 1 – Unregister server.
Using the Windows Command Prompt running As Administrator go to the directory C:\Program Files\Open Automation Software\OAS\ and type DANSrv.exe /Unregserver.
Step 2 – Register to run as a Windows Service
Using the Windows Command Prompt running As Administrator go to the directory C:\Program Files\Open Automation Software\OAS\ and type DANSrv.exe /Service /AutoStart.
Step 3 – Verify OPC Server is Registered
Using the Service Control Manager the Windows Service OPCSystems.NET DA Server should be listed to run in Automatic Startup Type. You can select to manually start the server or restart the operating system and the server will start automatically.
<add key=""ValueOnlyBrowsing"" value=""False""/>
<add key=""TCPPortNumber"" value=""58727""/> <add key=""WCFPortNumber"" value=""58724""/>View the following video on how to adjust WCF port number in the realtime service and all client applications:
Note: Remoting is a legacy format of communications and it is recommended to update to the latest version of OAS for the most secure transport.
For the OPCSystem.NET OPC Server modify the file DANSrv.exe.config in the directory C:\Program Files\Open Automation Software\OAS] with Notepad or a text editor.
Set the property EnableRemoting to True.
<add key=""EnableRemoting"" value=""True""/>
<add key=""UserName"" value=""""/> <add key=""Password"" value=""""/>
<< View All Troubleshooting Topics