Siemens TIA Portal: Asset Oriented Programming In PLC & HMIs

What exactly is an “Asset”? By understanding how the term is being used, it will help in the creation of data sets later on

Small article that explains the basics behind what a UDT is

Let's take a more in-depth view at UDTs by walking through the “UDT_Quarter_Turn_Valve” example and the how it was created

Learn how to create different instances of the Asset's Data

Bespoke data "structs" provide a way to add additional data to individual Asset instances, without affecting UDTs

Walkthrough of the "Library Management Console" and how it is used

Learn about Library Types and why we need to use them

Learn how to version types in the Project Library, this is important for standardization later on

Learn how to add hardware from the catalogue in TIA Portal

Take a look through CPU Configurations and IO modules used in this project

Learn how to attach PLC tags to physical IO hardware and a naming convention that will help understand the locality of the signal

Learn how to create an Input Mapping later for your raw signals. The provides a place to modify and simulate signals for use in your main project code

Learn how to expand a basic Input Mapping Block into one that provides complete, and automated, simulation. Perfect for testing full system behaviour

First look at Asset Management as how these are put together. Later lessons will build on this concept

Explore the functions of the Analog Asset Manager. The lesson explains how non-specific sub-functions are used to provide functionality for the Asset Manager

The correct structuring of Asset Managers' instance data is crucial. This article helps highlight the overall usage of the Asset Manager

A walkthrough of the Quarter Turn Valve Manager. This looks at the differences between instruments and devices when it comes to management of assets

Interfaces are key to the AOP design approach. Using InOut interfaces is also important and is required to make this design work most efficiently

You cannot access global data from inside a function block when using standard approaches, this lesson explains why!

Learn why constants are used to index the alarm array

This lesson looks at the Alarm Data structure, and how we're using two UDTs to make up that data. We'll also look at comments and why they need to appear in two places in this case

The "Global Alarm Manager" is the logic that sets, accepts and resets the alarm. It also provides a status for us to control SCADA / HMI indications with

This lesson takes a look at ProDiag an how PLC controlled alarms can be configured and made a part of the AOP design

A look at how interlocks can be managed with a single DB and UDT. And a small example of raising system interlocks based on data from multiple places

First look at "Extension" and creating interlocks using bespoke data in the asset management layers

Learn how we're going to interface with the devices in this project, via a "Control Layer". This allows us to easily access the interface of our managers from our sequences and request handlers