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

Creating control data

By creating control data, programmers create a specific set of criteria or variables that all standard controls should follow. This is a dataset that should follow a requirement or process, such as the following:

  • All asset controlling function blocks should return one of the following status types:
    • Healthy status
    • Running status
    • Not available status
    • Inhibit status

The preceding status types can be added to a Struct data type called Control_Data, as illustrated in the following screenshot:

Figure 6.14 – Example of a Control_Data output

Figure 6.14 demonstrates a function with an output for the Control_Data elements. The output is a struct containing elements that go on to be used in a program for control and interlocks with other equipment.

The contents of this Control_Data struct are shown here:

Figure 6.15 – Control data output

The Control_Data_Example asset control function block is...