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

Summary

This chapter has introduced concepts behind using structured data in the form of structs and UDTs. It has highlighted the benefits of using structures, and also some of the pitfalls and issues that can be faced in large projects by using them. Remember that a structured project is far easier to navigate through, standardize, and work with in the future.

After reading this chapter, the asset-oriented approach should make sense from a structural perspective: containerizing data so that data that is only relative to a particular asset lends itself to structures (structs or UDTs).

Identifying what is needed in structures is always the hardest part, as structures can be difficult to keep updating in a system that is already operational, so it's best to try and plan for common use cases first.

TIA Portal offers a robust and highly flexible solution to managing data using structures. With two different types of structured data (struct and UDT), programmers can simplify...