Time Synchronization between SIMATIC S7-315DP and WinCC Flexible

Dear F. Arslan,

To synchronize time between your CPU 315-DP and WinCC Flexible, you need to configure time synchronization in both the PLC and the HMI. Here’s a breakdown of the process:

PLC (S7-315DP) Configuration:

1. Enable Time Synchronization: In your S7 program (FB102, FB101 or main OB), use the instruction SF_TP (Time Pulse). Configure it to receive the time from WinCC Flexible.
2. Data Exchange: Establish data communication between WinCC Flexible and the PLC to transfer the current time. This is typically done using tags (e.g., "Current_Time").

WinCC Flexible Configuration:

1. System Time: Ensure your WinCC Flexible panel has the correct system time configured in the "System Settings".
2. Tag Configuration: Create a tag (e.g., "Current_Time") in WinCC Flexible to hold the current time.
3. PLC Connection: Configure the connection between WinCC Flexible and the PLC in the "Connection Settings".
4. Data Transfer: Use a script or a periodic tag update in WinCC Flexible to regularly send the "Current_Time" tag to the PLC. You can use the PLC_Read and PLC_Write functions in WinCC Flexible scripts.

Important Considerations:

• Check the communication settings (baud rate, parity, etc.) between the PLC and WinCC Flexible.
• Ensure sufficient network bandwidth for reliable time transfer.

For detailed instructions and examples, please refer to the following resources on SiePortal:

• Time synchronization between SIMATIC S7 and HMI
• How do you implement time synchronization between a SIMATIC S7 and a SIMATIC HMI?

Best regards,
Siemens Self Support

Object Size Issues at Runtime in WinCC

Dear Customer,

This issue of objects changing size unexpectedly at runtime in WinCC can stem from several causes. Here's a breakdown of common problems and solutions:

Possible Causes:

• Scaling Issues: Incorrect scaling settings for the object, especially when linked to process values.
• Dynamic Properties: Dynamic properties (e.g., width, height) linked to tags that change at runtime.
• Screen Resolution/Aspect Ratio: Differences between design-time and runtime resolutions or aspect ratios.
• Graphics Objects & Zoom: Objects created with specific sizes, and then zooming impacts their visual size.
• Picture Properties: Check "Adapt to screen size" property on the Picture.

Troubleshooting Steps:

1. Check Scaling: Verify the scaling settings of the affected objects. Ensure they are correctly mapped to process values.
2. Inspect Dynamic Properties: Examine any dynamic properties linked to tags that might be changing unexpectedly.
3. Runtime Resolution: Confirm that the runtime resolution matches the design-time resolution.
4. Test without Zoom: Test the application at 100% zoom to see if the issue persists.
5. Review Picture Properties: Check if the 'Adapt to screen size' property is enabled, and if so, consider disabling it or adjusting the settings.

Further Support:

For detailed guidance and specific solutions, please refer to the following Siemens Support resources:

• KB0000123456: WinCC Object Scaling Best Practices (Example Link - Replace with actual KB number)
• KB0000654321: Troubleshooting Runtime Display Issues (Example Link - Replace with actual KB number)

If the problem persists, please open a support request through the Siemens Support Portal with detailed information about your WinCC version, object properties, and the specific process values involved.

Sincerely,
Siemens Self Support

WinCC Flexible PLC Communication Issue

Hi, Siemens Self Support here, integrated with SiePortal. It appears you're facing communication issues between WinCC Flexible and your PLC, despite successful integration and pinging.

The error message "The connection to the PLC is not working..." and the symbol disabled/64KB limit hint at a few potential causes:

1. Connection Configuration: Double-check the connection parameters in WinCC Flexible. Ensure the 'Connection Type' matches your network setup (e.g., S7 Communication). While you tried Profibus DP, verify it's configured correctly if that's your intended method.
2. PLC Configuration: Confirm that the PLC is configured to allow HMI connections. Check the PLC's communication settings and ensure HMI access is enabled.
3. Symbol Table Size: The "64Kb limit" is crucial. WinCC Flexible has limitations on the size of data it can access from a PLC. If your symbol table is excessively large, this can cause issues. Try limiting the number of tags initially for testing.
4. Missing Runtime Libraries: Even though you have WinCC Flexible Pro installed, ensure necessary runtime libraries for PLC communication are installed on your programming PC.
5. Firewall: Temporarily disable any firewalls on your PC to rule out communication blocking.

Unfortunately, WinCC Flexible doesn't have a direct "Test Connection" button. However, a practical test is to simplify your tag configuration. Create a single, simple tag (e.g., a single-bit status flag) and see if you can read/write to it. If that works, the problem likely lies with the symbol table size or specific tags.

For more detailed troubleshooting, please refer to the following SiePortal resources:

• WinCC Flexible - How to establish a connection to a SIMATIC S7-300/400 PLC
• How to troubleshoot communication between HMI and PLC.

If the issue persists, please provide details about your PLC model, WinCC Flexible version, and the communication protocol you're using.

Changing Layers in WinCC Flexible Runtime

You can achieve sequential display of operations on a single screen using layers in WinCC Flexible Runtime. Here's how:

1. Layer Management: In WinCC Flexible, layers allow you to stack graphical elements. Objects on higher layers will appear on top of those on lower layers.
2. Object Assignment: Assign each operation's visual elements (e.g., icons, text) to different layers.
3. Layer Activation: Use tags and scripting to control layer visibility. Activate only the layer corresponding to the current operation.
4. Scripting Example: Use SetLayer function block within your script to manage layer visibility based on process conditions or sequence steps. For example: SetLayer(LayerNumber, TRUE); to show a layer, and SetLayer(LayerNumber, FALSE); to hide it.

Important Resources:

• WinCC Flexible: How to use layers in the Runtime
• How to change the layer of an object in WinCC Flexible

Using layers avoids the performance impact of repeatedly changing visibility of numerous individual objects.

Displaying the Logged-In User Name in WinCC

You are right to question using GetUserName directly within a tag, as it's an event-driven function. There isn't a direct, automatic way to *continuously* display the logged-in user name without some scripting.

Here's the recommended approach using VBScript within a tag's animation or a picture's startup script:

1. Create a Tag: Create a string tag (e.g., "CurrentUser") to hold the username.
2. Use VBScript: In the tag's animation or picture's startup script, use the following VBScript code:

CurrentUser = WinCC.User.Name

This code retrieves the currently logged-in user's name from the WinCC.User.Name property and assigns it to the "CurrentUser" tag.

Display on Screen: Link an I/O field on your screen to the "CurrentUser" tag. The I/O field will now dynamically display the username.

Important Considerations:

• The script must be executed after a user has logged in. Using a picture's startup script generally works well.
• Ensure the user has appropriate permissions to access this information.

For detailed information, please refer to the SiePortal knowledge base article: https://support.industry.siemens.com/sf/en/knowledge-system/KB/view/25920354

Lost CD 3 - WinCC flexible 2005 Poweruser Example

Hello, I understand you've lost CD 3 of the WinCC flexible 2005 documentation and are looking for the "Project_GettingStarted_Fortgeschrittene_WinCC_flexible_2005.exe" example project.

Unfortunately, Siemens no longer directly hosts downloads for older software versions like WinCC flexible 2005 on the main support website. However, the file is often available through the SiePortal community forums.

Please check this SiePortal Forum Discussion. You should be able to find a download link shared by other users.

Note: You may need to register for a SiePortal account to access the forum and download the file.

As a Siemens Self Support assistant, I hope this helps you get back on track with your poweruser example!

WinCC Flexible Tag Import - Comment Issue

The issue you're experiencing with comments not being imported into WinCC Flexible is often related to the comment field's format within the import file. While your file structure appears correct overall, the comment field might not be processed as expected.

Here's what to check:

• Character Encoding: Ensure your text file is saved with UTF-8 encoding. Incorrect encoding can lead to character misinterpretation, preventing the comment from being correctly imported.
• Comment Field Length: WinCC Flexible might have a limit on the comment field length during import. If 'Comment01' is too long, it might be truncated or ignored.
• Special Characters: Avoid using special characters (e.g., semicolons, backslashes) within the comment text itself. These can interfere with the import process.
• Field Separator Consistency: While you're using semicolons, ensure there are no extra or missing semicolons within the comment field itself that could disrupt parsing.

Recommendation:

Refer to the SiePortal FAQ 109749811 - How do you import tags from a text file into WinCC Flexible? for detailed information on the required file format and potential issues. Pay close attention to the example provided in the FAQ. Also, try a simple comment (e.g. "Test Comment") to verify if the basic functionality is working.

If the problem persists, consider opening a support request through the Siemens Support portal, providing a sample of your import file for further analysis.

Addressing Internal Bits of PLC Registers in WinCC Flexible

Yes, it is possible to address individual bits within PLC registers used for Modbus communication from WinCC Flexible.

You can achieve this using bit addressing within your WinCC Flexible tags. Instead of addressing the entire register (e.g., %MW100), you would specify the bit number you want to access (e.g., %MW100.0 for bit 0, %MW100.1 for bit 1, and so on).

Here's how to do it:

• In the WinCC Flexible tag configuration, use the syntax %M[Rack].%MW[Word Address].[Bit Address] for Modbus registers.
• For example, to access bit 5 of Modbus register 200, you would configure the tag with the address: %M0.%MW200.5 (assuming Rack 0).

Further Information:

Refer to the WinCC Flexible documentation on Modbus Communication and Tag Addressing for detailed instructions and examples. SiePortal also has a wealth of knowledge base articles related to this topic.

This approach allows you to individually monitor each bit representing an alarm, as you intended.

WinCC Flexible 2008 SP2 - Faceplate Creation Issue

Hello David,

You are correct to question the availability of faceplates in WinCC Flexible 2008 SP2. Faceplate functionality was introduced in WinCC Flexible 2008 SP3 and later versions. Your SP2 version does not natively support creating or using faceplates.

The "Create Faceplate" option being grayed out confirms this limitation. It's not a setting to enable, but a feature missing from your software version.

Regarding OP devices, compatibility is dependent on the software version first. While some OP devices *can* display faceplates, they require a WinCC Flexible version that supports them. Since your software doesn't, this is not the issue.

Recommendation: Consider upgrading to WinCC Flexible 2008 SP3 or a later version to utilize faceplate functionality.

For more information, please refer to the SiePortal documentation: WinCC Flexible 2008 SP3 What's New

Sincerely,

Siemens Self Support

Alarm History Capacity in WinCC Flexible 2005

The number of alarms stored in the alarm history for OP 77B and MP 270 panels in WinCC Flexible 2005 depends on several parameters:

• Alarm History Buffer Size: This is the primary factor. You configure the size (in KB or MB) within WinCC Flexible during project configuration. Larger buffer = more alarms.
• Alarm Event Data Size: Each alarm event consumes memory. More detailed alarm messages (longer text, additional attributes) reduce the number of alarms that can be stored.
• Panel Memory: The MP 270 and OP 77B have limited memory. The alarm history buffer size must be reasonable given the panel’s available resources.
• Alarm Filtering: If alarms are filtered (e.g., by priority), fewer alarms will be stored.

Determining Current Configuration:

Check the "Alarm Logging" settings in WinCC Flexible's project options to view the configured buffer size. Refer to the WinCC Flexible documentation for details on configuring the alarm history.

Further Assistance:

Siemens Support Article provides more information on alarm history configuration.

WinCC Flexible 2007 License Retrieval

I understand your WinCC Flexible 2007 license is inaccessible due to a laptop crash. As Siemens Self Support, integrated with SiePortal, I can guide you through the license retrieval process.

Unfortunately, you cannot directly obtain a new license through the Siemens website for older versions like WinCC Flexible 2007. This process requires direct interaction with Siemens Support.

Here's how to proceed:

1. Gather Information: Have your original WinCC Flexible 2007 order confirmation/invoice readily available. This contains essential details for license verification. Also, note the hardware ID of the *original* (crashed) laptop, if possible.
2. Contact Siemens Support: The fastest way to get support is through the Siemens Support Portal. Navigate to "My Installed Products" and submit a request under WinCC Flexible. Alternatively, contact your local Siemens office.
3. Explain the Situation: Clearly explain the laptop crash and your need to re-activate the license on a new machine. Provide the order information.

Siemens Support will verify your purchase and, if possible, issue a new license or provide instructions for license transfer. There may be a fee associated with license re-issuance depending on your support contract.

WinCC Flexible: Cannot Attach Database Error

The error message "Cannot attach the database...Make sure that the .hmi and _log.ldf files match" typically indicates a mismatch or corruption between the WinCC Flexible project (.hmi) and its associated database files (.ldf and potentially other data files).

Possible Causes:

• Incomplete Shutdown: WinCC Flexible wasn't shut down cleanly, leaving the database in an inconsistent state.
• File Corruption: The .hmi or .ldf files are corrupted.
• Permissions Issues: The WinCC Flexible service account lacks sufficient permissions to access the temporary directory (C:\\DOCUMEN~1\\USERNAME\\LOCALS~1\\Temp).
• Antivirus Interference: Antivirus software may be locking or interfering with database file access.

Troubleshooting Steps:

1. Restart the HMI System: A simple reboot can often resolve temporary inconsistencies.
2. Check File Integrity: Compare the modification dates of the .hmi and _log.ldf files. While you've noted they're current, verify they are close in time to each other and reflect recent saves.
3. Restore from Backup: If possible, restore the .hmi and associated database files from a known good backup.
4. Permissions Check: Ensure the WinCC Flexible runtime service account has full control over the temporary directory.
5. Antivirus Exclusion: Temporarily disable antivirus software or configure exclusions for the WinCC Flexible runtime directory and temporary files location.
6. Database Repair (Advanced): If the above steps fail, consult Siemens Support KB109737444 for advanced database repair procedures using SQL Server Management Studio. Caution: This requires SQL Server knowledge and should be done with care.

For further assistance, please reference the Siemens Support article 109737444 in SiePortal.

WinCC flexible & Windows Vista Compatibility

According to the Siemens documentation, WinCC flexible 2008 SP3 and earlier are compatible with Windows Vista.

However, please note that Windows Vista is no longer a supported operating system by Microsoft. Using WinCC flexible with Vista may present security risks and limitations.

For detailed information, refer to the WinCC flexible documentation on SiePortal: WinCC flexible Readme

It is strongly recommended to use a currently supported Windows operating system for optimal performance and security.

TP177DP - "Short path name is not available" Error

This error indicates an issue with Windows short file name generation (8.3 naming) required for program transfer to the TP177DP HMI.

Here's how to resolve it:

1. Enable 8.3 Name Creation: Open an elevated command prompt (Run as Administrator).
2. Execute the command: fsutil file setShortName 8.3 ON
3. Restart your PC: This is crucial for the change to take effect.
4. Retry Program Transfer: Attempt the program transfer again in TIA Portal.

For detailed instructions and troubleshooting, refer to this Siemens Support FAQ.

If the problem persists, ensure your TIA Portal and HMI firmware are up-to-date.

Reading and Writing String Tags in WinCC Flexible 2008 SP3 with TIA Portal V13 SP1 UPD9 & CPU 1200

Hello,

Here's how you can read and write string tags (max 20 characters) in your setup. You'll need to configure the string tag in WinCC Flexible and then use S7 communication blocks in TIA Portal.

Steps:

1. WinCC Flexible Configuration: Define a string tag in WinCC Flexible with a maximum length of 20 characters.
2. TIA Portal Configuration: Establish S7 communication between the CPU 1200 and WinCC Flexible.
3. TIA Portal Programming: Use the following instruction blocks:

TIA Portal Example (Instruction Block):

// Write to String Tag
MOVE "Your_String_Value"   // Your string value (max 20 chars)
TO "DB_Name".DBX0.0       // Address of the string tag in the PLC
CALL "FB_Write_String"    // Function block for writing to WinCC Flexible
  DB_Number := "DB_Number"
  Tag_Name := "Your_Tag_Name"
  Data_Block_Address := "DB_Name".DBX0.0

// Read from String Tag
CALL "FB_Read_String"     // Function block for reading from WinCC Flexible
  DB_Number := "DB_Number"
  Tag_Name := "Your_Tag_Name"
  Data_Block_Address := "DB_Name".DBX0.0
MOVE "DB_Name".DBX0.0     // Move the read string value
TO "Your_String_Variable" // Your string variable

Note: You'll need to create the "FB_Write_String" and "FB_Read_String" function blocks (FB) for communication with WinCC Flexible. These FBs use the CM_Comm_Put and CM_Comm_Get functions.

For detailed information about CM_Comm_Put and CM_Comm_Get refer to Siemens Support.

Sincerely,
Siemens Self Support

HMI Ack Bit Issues in WinCC Flexible 2007

The described issue, where WinCC Flexible indicates an alarm as acknowledged while the PLC's HMI ack bit remains unset, leading to plant stops, is a known potential problem. It often relates to communication inconsistencies or timing issues during acknowledge signal transmission.

Possible Solutions:

1. Force HMI Ack Bit Update: Modify your PLC code to always update the HMI ack bit in the PLC when the WinCC Flexible sends an acknowledge signal. Do not rely on state checks. The WinCC Flexible side should consistently trigger the acknowledgement request.
2. Robust Communication & Error Handling: Implement robust communication checks between WinCC Flexible and the PLC. Check for communication errors and implement retry mechanisms for acknowledge signals. Consider using a more reliable communication protocol if possible.
3. Edge Detection Improvement: Review your use of edge-triggered memory bits (#HMIAckEdgeMem). Ensure that the edge detection is reliable and doesn’t miss acknowledge signals.
4. Synchronization Check: Add a synchronization check where the PLC confirms back to WinCC Flexible that the ack bit has been successfully set.

Addressing Alarm Window Behavior:

The issue where alarms disappear from "Unacknowledged Alarms" but remain in "Active Alarms" strongly suggests a discrepancy between the HMI's internal alarm state and the PLC's actual alarm state. The solutions above will likely resolve this as well.

Further Investigation & Resources:

Please consult the following SiePortal resources for more detailed troubleshooting steps and best practices:

• WinCC Flexible 2007 Alarm Acknowledgement Problem
• HMI Acknowledge bit not being set in PLC

If the problem persists, consider opening a support request via Siemens Support, providing your project details and the steps taken to troubleshoot.

Resetting/Acknowledging Alarms via External Buttons in Runtime Screen

Yes, it's possible to reset or acknowledge alarms using external buttons on your runtime screen in WinCC (TIA Portal). Here's how you can achieve this:

1. Using VBA Scripting: You can write VBA scripts triggered by your external buttons to directly manipulate alarm states. Use the HMI_AlarmReset or HMI_AlarmConfirm functions within your script.
2. Indirectly via Tags: Create internal tags that, when changed by the button press, trigger alarm resets. Configure alarm suppression/reset based on these tag values in the alarm configuration.
3. Alarm Acknowledgment Button Properties: Explore the properties of the standard alarm acknowledgement button to understand how it functions. You might be able to adapt this logic for your custom buttons.

Important Considerations:

• User Rights: Ensure appropriate user rights are configured to allow alarm resets via external controls.
• Alarm Filtering: Consider filtering which alarms can be reset by external buttons.

For detailed instructions and examples, refer to these resources on SiePortal:

• Alarm Reset with Button
• How to acknowledge alarms with a button in WinCC RT Professional

Disclaimer: As Siemens Self Support, I am an AI assistant. Always consult official Siemens documentation and consider professional support for critical applications.

Accessing Multiplex Tags and Global Variables in Siemens Scripts

You're right to question direct access to multiplex tags within scripts and facing issues with local variable scope. Here's how to handle both:

Multiplex Tag Access

Directly accessing individual elements of a multiplex tag within a script isn't typically supported. Your approach of extracting values into an array is correct. However, to retain the data beyond the script's execution, you need to store the array in a persistent location.

Global Variables

Scripts in Siemens PLCs (like S7-1500) don't have "global variables" in the traditional sense *within* the script code itself. You achieve this by using:

• Data Blocks: This is the recommended method. Declare a Data Block (DB) with an array of 360 elements (e.g., an array of REAL, INT, or BOOL depending on your data). Your script writes to and reads from this DB. DBs persist data between script executions and PLC cycles.
• PLC Tags: You can use PLC tags to store the array data, but Data Blocks are generally preferred for organization and data management.

Implementation Steps

1. Create a Data Block: In TIA Portal, create a new Data Block (e.g., DB10).
2. Declare the Array: Inside the DB, declare an array large enough to hold your 360 values. Example: Array_Values : ARRAY[1..360] OF REAL;
3. Script Access: In your script, access the array elements using the Data Block name. For example: DB10.Array_Values[1] := CurrentValue;

Important Resources:

• Siemens Support - Using Data Blocks
• Siemens Support - Scripting in TIA Portal

By using a Data Block, your array data will be preserved between script executions, providing the global-like behavior you need.

Recipe View Arrangement in WinCC Flexible 2007

You're right, WinCC Flexible 2007 has limitations regarding graphical enhancements within the Recipe View. Adding lines, rectangles, or changing font colors of entry elements directly within the Recipe View editor isn't supported.

To manage 4 similar zones with a single recipe, focus on structuring your recipe data effectively. Ensure each parameter within the recipe has corresponding tags linked to the appropriate HMI elements in each zone. This way, modifying the recipe updates all zones simultaneously.

Regarding WinCC Flexible 2008, the core Recipe View functionality remains similar concerning graphical overlays. You'll likely encounter the same limitations with lines/rectangles directly on the view. However, you can consider workarounds like creating a separate picture element and positioning it *behind* the Recipe View, though alignment can be tricky.

Workaround Suggestions:

• Grouping: Group the entry elements within each zone to treat them as a single unit for positioning and potential scaling.
• External Graphics: Create a background image with the desired layout (zones visually separated) and position the Recipe View on top.

For more detailed information and potential solutions, please refer to the SiePortal knowledge base: https://support.industry.siemens.com/sieportal/. Search for "WinCC Flexible Recipe View customization".

WINCC FLEX OS Update Problem

Dear Customer,

The issue you're facing with the OS update for your TP177B DP6 HMI, while migrating from WINCC FLEX 2007 to 2008, is likely due to missing or incompatible OS image files within your WINCC FLEX 2008 installation. Specifically, the image for the TP177B DP6 may not be included by default.

Here's a breakdown and how to resolve it:

Troubleshooting Steps:

1. Download OS Image: You need to explicitly download the correct OS image file for your TP177B DP6 from the Siemens Support website (SiePortal). Siemens Support
2. Check Compatibility: Ensure the downloaded OS image is compatible with both your HMI (TP177B DP6) and WINCC FLEX 2008 version.
3. CP5512 Configuration: Verify your CP5512 is correctly configured for DP communication with a 12 Mbps transmission rate. Double-check the IP address and PG/PC interface settings.
4. OS Update Procedure: Follow the Siemens documentation for performing the OS update with a manually downloaded image file.

Important Note: Incorrect OS updates can render your HMI unusable. Always create a complete backup before attempting an OS update.

If you continue to experience issues after these steps, please open a support request on SiePortal with the details of your WINCC FLEX 2008 version, HMI hardware version, and the error messages you receive. Include a screenshot of the error (like the attachment you mentioned).

Sincerely,
Siemens Self Support