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

Drawbacks of structs and UDTs

Despite Siemens' excellent approach toward UDTs and structs, there are some drawbacks to using them.

Most of the issues are small and are easily managed, however, a potentially confusing issue (especially to programmers that are new to using libraries and UDTs) occurs when a UDT and a block dependent upon the UDT both appear in a Project library.

Libraries

UDTs that are stored in a library and are utilized in many places can cause a large number of objects to upgrade to a newer version if modified.

Remember

A program block is dependent upon a UDT if its interface contains a declaration of the UDT.

When a project library has no objects in test, it would look something like the following:

Figure 3.20 – Project library containing UDTs and function blocks

If UDT_Sample_Pump_Raw_IO is modified and a new version is created, the project library indicates that the UDT is in test:

Figure...