OPC Studio User's Guide and Reference
Live Mapping Model
Client and Subscriber Development > Development Models > Live Mapping Model

 

Live Mapping works with OPC Data Access ("Classic"), OPC XML-DA and OPC Unified Architecture servers (for data access). Its features include:

The features discussed here, or some of them, may not be available in all editions of the product. Check the Product Editions page for differences between the editions. The trial license has all features enabled (and is limited in period for which it provides valid data), but licenses for specific commercial editions may have functionality limitations.
This functionality is not yet available for OPC UA PubSub.

 

The live mapping development model allows you to write objects that correspond logically to a functionality provided by whatever is “behind” the OPC data. For example, if part of your application works with a boiler, it is natural for you to create a boiler object in the code. You then describe how your objects and their members correspond to OPC data – this is done using attributes to annotate your objects. Using Live Mapping methods, you then map your objects to OPC data, and perform OPC operations on them.

For example, when you subscribe to OPC items, incoming OPC item changes can directly set corresponding properties in your objects, without any further coding. You can then focus on writing the code that handles these property changes, abstracting away the fact how they come in.

To give a concrete example, here is a piece of code of a .NET object annotated for live mapping with OPC Data Access, in C#:

Live Mapping Annotations
Copy Code
    [DAType]
    class BoilerInputPipe
    {
        [DANode]
        public FlowTransmitter FlowTransmitter1 = new FlowTransmitter();

        [DANode]
        public Valve Valve = new Valve();
       
        [DANode, DAItem]
        public bool InAlarm { get; set; };
    }

You can use the Liver Mapping model with OPC Data Access, or with OPC Unified Architecture data.

 

See Also