Kkula
Browse Questions » SIMATIC WinCC flexible: Template working Including the Process control loop

About User

Questions Asked: 37.9K

Answers Given: 32

0
  • Open

SIMATIC WinCC flexible: Template working Including the Process control loop

Hi there,
I'm also trying to get the faceplate working with the PID, but having the following issue:
I'm having abt. 10 temperature control loops running on FB58 (TCONT_CP). Of course they all have there own DB for the data.
With a faceplate I want to make all the necessary data visible and able to change some data. Also a trend for monitoring must be available.
As the DB's are all the same, I don’t want to add all the data from these DB's in my WinCC flex. So I thought about using the WinCC flex STRUCTURE to help me out. I have some experience with but when I want to create the structure, it doesn't give me the possibility to change the offset . I want to do this because I want the HMI toread/ writein different parts of the DB.. I don't want to open all...
(think about it.. everything in the face plate and just tell WinCC which DB it has to look at...)
Does anybody have an idea to do this (or to work around, rather not )\
Thanks in advance!

0 Likes 0 Favourites 0 Followers 0 Comments
Answers(1)

Understanding Your WinCC Flex Faceplate Challenge with PID Loops

You're facing a common challenge when scaling PID control loops in WinCC Flex – efficiently managing multiple instances with identical data structures (FB58/TCONT_CP DBs) and avoiding redundant configuration.

You're correct to consider WinCC Flex STRUCTURES, but the limitation regarding offset adjustment is known. Unfortunately, directly modifying the offset within a STRUCTURE for dynamic DB addressing isn't supported.

Here's a recommended approach to achieve your goal, balancing functionality and maintainability:

  1. Indirect Addressing with Tags: Create a central tag (e.g., "Current_Loop_DB") that dynamically points to the desired DB number.
  2. STRUCTURE with Relative Addressing: Define your STRUCTURE based on the first byte of the DB (offset 0).
  3. Dynamic Tag Creation: Within the faceplate, build your tags using the "Current_Loop_DB" tag and relative addressing. For example: "%Current_Loop_DB%.DBX0.0" for the first bit of the selected DB.
  4. Trend View: Configure trend views using these dynamically addressed tags.

Important Considerations:

  • Carefully validate data types and lengths when using indirect addressing.
  • Error handling is crucial to manage scenarios where "Current_Loop_DB" is invalid.

For detailed guidance and examples, refer to these SiePortal resources:

This approach provides a flexible solution without requiring extensive duplication in your WinCC Flex project.

0