Click here to Skip to main content
15,895,084 members
Articles / Desktop Programming / Windows Forms

Using .NET with Wonderware

Rate me:
Please Sign up or sign in to vote.
3.75/5 (9 votes)
24 Aug 2010GPL33 min read 221.1K   3.1K   22   113
This article will show how to read and write to Wonderware from VB

Introduction

This article is born out of several projects I have had extending Wonderware by calling VB.NET applications. Wonderware is an HMI/SCADA front end made by Wonderware. Wonderware is fairly easy to use, although I am not a huge fan of it, I don't have much against it either. It is just a common program in the SCADA industry. This will show you how to write applications that communicate with Wonderware. I usually have to do this to extend the functionality or to fill in the gaps between what Wonderware can do and what the customer requires.

Background

I write HMI/SCADA software mostly for the oil and gas industry. In this industry, many companies use a product called Wonderware. I have also come across it in waste water plants as well as food processing plants (Cheese Cake to be exact!!!). At most of these facilities, they need a function in the Wonderware application, but Wonderware can't do it. This will give you another option. I have seen other options using DDE. However, DDE is no longer supported so we will be using the Wonderware Toolkit. This code will contact the Wonderware running on the same computer.

Using the Code

Using the code will be pretty easy. We will create 2 VB files that are required to call the Wonderware toolkit (ptacc.dll and wwheap.dll). After that, all that will be left is your application to call the read/write functions of the Wonderare Toolkit. These files were created based on information from Wonderware West and my experience with using the 2 DLLs.

To do this, you need to copy the Intouch.vb and the Ptacc.vb into your project as well as reference the wwheap.dll and the ptacc.dll. Doing this will allow you to communicate with the Wonderware database.

The Ptacc.vb file will contain everything necessary to communicate with Wonderware. However it isn't very pretty, so that is why we use the Intouch.vb file. It is just the basic level.

The Intouch.vb file is going to contain our commands for reading and writing values with the Wonderware database. This will allow you to read/write Strings, Floats, Booleans(Discrete), and Integers.

So if you want to read the first 132 characters from the string variable with the tag SBuffer, then you call IntouchToolkit.ReadString("SBuffer", 132) or you can use ReadInteger, ReadDiscrete and ReadFloat for the respective types. Also, the similar is true but the functions is WriteString, WriteFloat, WriteInteger and WriteDiscrete. The Tag name is always a string.

Now that we got the basics out of the way, you need to call this from your application. This is pretty simple. In your main VB file, whether it is Windows Form or console application doesn't matter. I have not tried this with a web form, but I would like to hear your experience with it if you do try it.

VB.NET
Public Class Form1
    Dim accid As Integer
    Dim hPt As Integer
    Dim SB As String
    Dim IntouchToolkit As Intouch

    '------------------------------------------------
    'Form1_Load
    '------------------------------------------------
    Private Sub Form1_Load(ByVal sender As System.Object, _
		ByVal e As System.EventArgs) Handles MyBase.Load

        IntouchToolkit = New Intouch(0, 0)
        SB = IntouchToolkit.ReadString("SBuffer", 132)	'SBuffer is the Tag 
						'I want to read in Wonderware

    End Sub
    
    Private Sub btnOpen_Click(ByVal sender As System.Object, _
		ByVal e As System.EventArgs) Handles btnOpen.Click
        IntouchToolkit = New Intouch(0, 0)
        IntouchToolkit.WriteDiscrete("SomeTag", 1)
    End Sub
End Class

These are the write functions available to call:

  • VB.NET
    IntouchToolkit.WriteString("SomeTag", "FooBar")

    This is to write a string value.

  • VB.NET
    IntouchToolkit.WriteFloat("SomeTag", 3.1415)

    This is to write a float value.

  • VB.NET
    IntouchToolkit.WriteInteger("SomeTag", 10)

    This is to write an integer value.

  • VB.NET
    IntouchToolkit.WriteDiscrete("SomeTag", 1)

    This is to write a boolean value.

These are the read functions available to call:

  • VB.NET
    IntouchToolkit.ReadString("SomeTag")

    This is to read a string value.

  • VB.NET
    IntouchToolkit.ReadFloat("SomeTag")

    This is to read a float value.

  • VB.NET
    IntouchToolkit.ReadInteger("SomeTag")

    This is to read a integer value.

  • VB.NET
    IntouchToolkit.ReadDiscrete("SomeTag")

    This is to read a boolean value.

*NOTE: Replace "SomeTag" with the tagname you want to read or write from.

Points of Interest

As you can see, this is pretty simple. I have used this code several times on Wonderware 7.1 to 10.0. I usually put in some code that starts my application when an icon in Wonderware is clicked. This is the reason why I get the x and y values from Wonderware. It took me about a week with Wonderware support to find this information, and they do not support the Wonderware toolkit, but it has been reliable for me.

History

Well, this is the initial version.

License

This article, along with any associated source code and files, is licensed under The GNU General Public License (GPLv3)


Written By
Software Developer Chemex Modular
United States United States
I am a Developer and Electrical Engineer. I work mostly on HMI and SCADA systems in the Houston area. I have worked mostly around oil and gas industry. I have also spent time in Indiana working on automotive assembly plants.

Comments and Discussions

 
GeneralRe: [My vote of 2] I keep wondering Pin
earl the dead cat23-Aug-10 11:42
earl the dead cat23-Aug-10 11:42 
GeneralRe: [My vote of 2] I keep wondering Pin
Luc Pattyn23-Aug-10 11:45
sitebuilderLuc Pattyn23-Aug-10 11:45 
GeneralRe: [My vote of 2] I keep wondering Pin
knockNrod24-Aug-10 6:58
knockNrod24-Aug-10 6:58 
AnswerRe: [My vote of 2] I keep wondering Pin
Luc Pattyn24-Aug-10 7:12
sitebuilderLuc Pattyn24-Aug-10 7:12 
GeneralRe: [My vote of 2] I keep wondering Pin
knockNrod25-Aug-10 2:39
knockNrod25-Aug-10 2:39 
GeneralRe: [My vote of 2] I keep wondering Pin
earl the dead cat25-Aug-10 2:57
earl the dead cat25-Aug-10 2:57 
GeneralRe: [My vote of 2] I keep wondering Pin
earl the dead cat24-Aug-10 7:30
earl the dead cat24-Aug-10 7:30 
GeneralRe: [My vote of 2] I keep wondering Pin
knockNrod25-Aug-10 3:03
knockNrod25-Aug-10 3:03 
I thought so too, when I first started working with WinCC. Their documentation is certainly not helpful, but then I compare it to WW's, and, well, what documentation? I asked around the office thinking I was missing something, but they don't know of any, either!

I will admit that WinCC has a daunting learning curve. But when it comes to dropping in a custom .Net control, I LOVE WinCC over WW. Unfortunately, it's the nature of our business that we have to make our controls work in various consumer preferred HMI hosting environments, so I have to code to the lowest common denominator. So, even though I don't need all the interop crap for WinCC, I still have to code it because someone will need to drop it into WW sooner or later.

This peculiar working environment, where the next user will likely have a different PLC investment than the past six, is why we have a strong preference toward OPC. Write once, use many is much preferred to maintaining code for over a dozen drivers. It makes it especially nice when the hosting tools (WOnderware, WInCC for example) already include an OPC Server built in. But we're not the only vendor that works this way, so it will be a long, long time before OPC breaths its last breath.

Thanks for the offer of help. The biggest problem we're having is proving our code, since we can't get hands on a trial version of WW! But the thing is, I'm working in the other direction. Instead of writing programs to access WW stuff from Windows, I'm writing Windows programs to run inside of WW. If anyone reading this is intrigued by the idea of using .Net UserControls inside of WW or WinCC, let me save you man-weeks of effort by pointing you to Microsoft's InterOp Forms Toolkit. (Google or BING will give you the link.)
Without darkness, there are no dreams.
-Karla Kuban

GeneralRe: [My vote of 2] I keep wondering Pin
earl the dead cat25-Aug-10 3:26
earl the dead cat25-Aug-10 3:26 
GeneralRe: [My vote of 2] I keep wondering Pin
earl the dead cat24-Aug-10 7:33
earl the dead cat24-Aug-10 7:33 
GeneralRe: [My vote of 2] I keep wondering Pin
knockNrod25-Aug-10 3:04
knockNrod25-Aug-10 3:04 
GeneralJust a giant code dump... Pin
Dave Kreskowiak18-Aug-10 1:59
mveDave Kreskowiak18-Aug-10 1:59 
GeneralRe: Just a giant code dump... Pin
earl the dead cat18-Aug-10 4:34
earl the dead cat18-Aug-10 4:34 
GeneralRe: Just a giant code dump... Pin
Dave Kreskowiak18-Aug-10 12:28
mveDave Kreskowiak18-Aug-10 12:28 
GeneralRe: Just a giant code dump... Pin
earl the dead cat18-Aug-10 13:09
earl the dead cat18-Aug-10 13:09 
GeneralRe: Just a giant code dump... Pin
Dave Kreskowiak18-Aug-10 18:24
mveDave Kreskowiak18-Aug-10 18:24 
GeneralAs interesting as I'm sure this is... Pin
R. Giskard Reventlov17-Aug-10 21:44
R. Giskard Reventlov17-Aug-10 21:44 
GeneralRe: As interesting as I'm sure this is... Pin
Trollslayer17-Aug-10 23:00
mentorTrollslayer17-Aug-10 23:00 
GeneralAh I used to do all that Jazz, SCADA, PLC, HMI Pin
Sacha Barber17-Aug-10 21:40
Sacha Barber17-Aug-10 21:40 
GeneralRe: Ah I used to do all that Jazz, SCADA, PLC, HMI Pin
earl the dead cat18-Aug-10 4:33
earl the dead cat18-Aug-10 4:33 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.