Book Image

PLC and HMI Development with Siemens TIA Portal

By : Liam Bee
Book Image

PLC and HMI Development with Siemens TIA Portal

By: Liam Bee

Overview of this book

With automation requirements on the rise, Siemens’ TIA Portal development environment is almost a necessity for any automation engineer. The Totally Integrated Automation (TIA) environment helps seamlessly integrate all things automation, from PLC hardware and software design to HMI development. This book helps you understand the tools available in the TIA toolbox and shows you how to write code effectively. The book begins by introducing you to the TIA environment, covering the layout and tools available. Once you’ve got to grips with the environment, you’ll find out how to create hardware to write programs against, including adding IO modules and assigning memory for input and output. Next, you'll develop logic in all of the languages that TIA Portal offers, such as Ladder, Function Block Diagram, and Structured Text (SCL) (note that Statement List is not covered as a deprecated language), as well as the newest language, Cause and Effect (CEM). You’ll also discover how to store standard code in libraries, creating a version control system that is easy to manage and aids standard design. Finally, following the PLC design chapters, you’ll learn how to develop HMI applications in TIA Portal’s latest unified hardware. By the end of the book, you'll be well equipped to use all of the features that TIA Portal V17 offers.
Table of Contents (21 chapters)
1
Section 1 – The TIA Portal – Project Environment
5
Section 2 – TIA Portal – Languages, Structures, and Configurations
11
Section 3 – TIA Portal – HMI Development
16
Section 4 – TIA Portal – Deployment and Best Practices

Extending standard data

Similar to program blocks, standard data blocks that use UDTs or structs can also be easily extended without breaking standardization. For this to work, a data block needs to be structured in a particular way.

Have a look at the following screenshot:

Figure 8.4 – Example of a data block structured with UDT and bespoke data

Figure 8.4 is an example of a data block that consists of the following two areas:

  • Asset UDT Data—This is the data that standard objects will access.
  • Asset Bespoke Data—This is an extension of the standard data.

Now, have a look at the following screenshot:

Figure 8.5 – Example in TIA Portal data blocks

Figure 8.5 demonstrates this pattern in data blocks. Asset_1 has the UDT defined as a variable named Typed, and that is the only variable that appears in the data block. This means that any standard object that requires data from Asset_1 can...