Getting Started – .NET Alarm
The following resources will provide you information to get your alarming application put together quickly.
If you do not have a copy of Visual Studio you can download a free version of Visual Basic Express 2010 or C# Express 2010 from www.microsoft.com/express. If you have no experience with either Visual Basic or C# choose Visual Basic. No programming is required to use OPC .NET WinForm HMI .NET.
The following steps can be used to add an alarm window to a C#, C++, or Visual Basic.NET application. All properties are programmatically accessible.
The following example demonstrates the alarm window with no code required. You can use Visual Studio 2005, 2008, 2010, 2012 or 2013. The alarm window can also be used with Visual Studio 2003 with the older .NET Framework 1.1 version of OPC Systems.NET.
The descriptions of each property of the alarm control can be viewed when selecting the property.
Start Visual Studio 2005, 2008, or 2010 and select File->New->Project to create a new C#, C++, or VB.
Select Windows Application or WPF Application as the project type.
If you are using WPF choose the OPCWPFDashboard assembly with the Target Framework set to the full 4.0 (not Client Profile) to then use the OPCWPFAlarm control.
Note: If using Visual Studio 2010 set the Target Framework to the full version not the Client Profile.
From the Toolbox if OPCAlarmControl is not available right click in the Toolbox and select Choose Items.
From the .NET Framework Components select OPCAlarmControl and then select OK.
For WPF applications from the Toolbox right click to select all OPCWPFDashboard assembly controls including the OPCWPFAlarm control.
Add the OPCAlarmControl or OPCWPFAlarm component onto the Form or Window.
Resize both the form and alarm window to the desired size.
Right click on the alarm window and select Properties.
Set the Anchor property to Top, Bottom, Left, Right.
Expand the AlarmFilter property and set the desired filter settings for the alarm window.
Select the AlarmNetworkNodes property and click on the small grey square with the 3 dots at the right.
Select all network nodes you wish to receive alarms from to this alarm window.
Note: If you want the application to be deployed across a network to remote PCs select the Network Node or enter an IP Address in the NetworkNode field and use the Select button to include the network node or IP Address of the OAS Service source. Refer to the VB.NET Example on how to programmatically assign the Alarm Network Nodes.
If you desire for the operator’s changes to the alarm window during runtime to remain set the ConfgiurationFile property to a valid file path. Make sure each system the application will run on that the directory path is valid.
Note: If you set this property to a file make sure you deploy the file with the application in the directory you specify.
Leave this property blank if you wish to have the default properties set during configuration remain on the application restarting.
Set the compile mode on the Visual Studio toolbar to Release.
Select Build from the VS menu and select to Build the application.
Use Windows Explorer to browse for the application located in the binRelease directory and run the application.
To deploy the application to remote nodes first make sure the AlarmNetworkNodes selection as described in Step 9 is set to a Network Node or IP Address. Then simply copy the files in the binRelease directory to the target systems or follow the Smart Client deployment section in this help file to deploy your application using Click Once Deployment.