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

Alarm tags

In the PLC, dedicated tags or data block addresses are required to be used in order to tell the HMI that an alarm has been raised. These exist in the HMI as the trigger tag and acknowledgment status tag.

Logic is developed against these tags in order to react to operator acknowledgment of alarms and to raise the instance of the alarm. Figure 12.19 shows a basic example of ladder logic controlling a latching interlock:

Figure 12.20 – An example of a basic alarm interface

When Scaled_Value for Instrument_1 is above High_Alarm_Trigger, both the trigger tag ("Alarms".Alarm_Group_1.Active[0].%X0) and High_Interlock are set to True. When this occurs, the HMI writes to the acknowledgment status tag ("Alarms".Alarm_Group_1.Accepted[0].%X0) and sets it to False, which then holds on to the trigger tag:

Figure 12.21 – A latched alarm in the HMI

If the trigger tag returns to a False value, the acknowledgment...