HMI Factory Reset/OS Update Issue - TIA Portal V16

Dear User,

Based on the screenshots, the issue appears to be related to communication problems preventing the factory reset or OS update of your HMI. Here are potential solutions:

• Check Network Settings: Verify the IP address of your PC and HMI are in the same subnet.
• Firewall: Temporarily disable Windows Firewall to rule out interference.
• TIA Portal Options: In TIA Portal, go to Options > Communications and check the 'Access Control' settings. Ensure your PC has access.
• HMI Firmware: Ensure the HMI is in boot mode (refer to the HMI manual for the specific key combination).
• SiePortal Knowledge Base: Search SiePortal using keywords like "HMI factory reset failed" or "HMI OS update issue" for similar cases and solutions.

If the problem persists, please provide the exact HMI model number and the specific error message displayed during the reset/update attempt. You can also open a support request via SiePortal for dedicated assistance.

Sincerely,

Siemens Self Support

Mapping Digital Alarms to Desktop Speaker Annunciation in WinCC V11

Dear Iyyappan,

Migrating alarm annunciation from WinCC 7 to WinCC V11 requires careful consideration. Here's a suggested approach:

1. Alarm Configuration: Ensure your digital alarms are correctly configured in WinCC V11 with appropriate priority levels.
2. Annunciation Scripting: Utilize WinCC V11 scripting (VBScript) to trigger audio playback via the desktop speaker based on alarm events. You'll need to identify the system sound playback function.
3. Sound Files: Prepare appropriate WAV sound files for different alarm priorities.
4. Tag Linking: Link alarm occurrences to the script that plays the relevant sound file. Use alarm triggers (e.g., 'Alarm Acknowledged', 'Alarm Active') to control playback.
5. Testing: Thoroughly test all alarms and priority levels to confirm correct annunciation.

Resources:

• Siemens Support - WinCC Alarm Configuration
• Siemens Documentation - WinCC Scripting

For specific implementation details and troubleshooting, consult the WinCC V11 documentation and Siemens support forums. Please provide specific details of your existing WinCC 7 implementation if further assistance is required.

Sincerely,
Siemens Self Support

TIA Portal V16 - WinCC Advanced HMI SSL Handshake Failure

Based on the provided information, the SSL handshake failure with Sm@rtClient specifically from a VM on the 'public' network, while local and IPC access works, points to a client-side certificate issue. Here's a breakdown and potential solutions:

Possible Causes:

• Outdated Root Certificates on the Client VM: The VM may be missing the root certificate authority (CA) used to sign the HMI's certificate.
• Certificate Mismatch: While the router allows port 5900, the SSL certificate presented by the HMI might not be trusted by the Sm@rtClient on the VM.
• SSL/TLS Protocol Version Mismatch: The VM's Sm@rtClient might be attempting to use an SSL/TLS version not supported by the HMI's OpenSSL 1.0.2l (which is quite old).

Troubleshooting Steps:

1. Update Root Certificates on VM: Update the trusted root certificates on the VM where Sm@rtClient is installed. This is generally done through the operating system's update mechanism.
2. Certificate Export and Import: Export the HMI's certificate from the HMI itself (if possible) and import it into the trusted root certification authorities store on the VM.
3. Check SSL/TLS Settings: Review the SSL/TLS settings within Sm@rtClient and the HMI configuration to ensure compatibility. Consider enabling older TLS versions within Sm@rtClient for testing (though this is not a long-term security solution).
4. Temporary Certificate Override (For Testing ONLY): Sm@rtClient might have an option to disable certificate verification for testing purposes. Warning: This significantly reduces security and should only be used temporarily for diagnostic purposes. Consult the Sm@rtClient documentation for this option.
5. Review HMI Certificate: Check the HMI certificate's validity period and ensure it hasn't expired.

File Considerations:

The issue is unlikely to be resolved by deleting or refreshing a single file. Focus on the certificate trust chain and SSL/TLS configuration.

Further Support:

For detailed instructions on updating certificates and configuring Sm@rtClient, please refer to these resources on SiePortal:

• FAQ: How do I update the root certificates on a SIMATIC HMI?
• How do you configure SSL communication in WinCC (TIA Portal)?

If the problem persists, consider opening a support request with Siemens Support, providing the HMI's certificate and detailed logs from both the HMI and Sm@rtClient.

Recipe Data Persistence in WinCC TIA Portal (Offline Mode)

You're experiencing a common issue: runtime recipe modifications are lost when the HMI stops. WinCC TIA Portal recipes, by default, don't automatically persist changes made during runtime unless configured to do so.

Here's how to achieve data persistence for offline use:

1. Recipe Storage: Ensure your recipe is configured to be stored in a traceable recipe and saved to a persistent storage like the HMI's memory or a connected database. Navigate to Recipe configuration properties and check the storage settings.
2. Traceability: Enable traceability for the recipe. This is *essential* for saving runtime changes.
3. Recipe Save Trigger: Utilize scripts or events (e.g., HMI shutdown event) to explicitly save the recipe data to the persistent storage before runtime ends. The 'RecipeSave' function can be used within scripts.
4. Consider Database Integration: For larger datasets or multi-user access, integrate with a database (SQL Server, etc.). This offers more robust data management.

Important SiePortal Resources:

• How do you save changes in a recipe during runtime in WinCC (TIA Portal)?
• How do you implement recipe management in WinCC TIA Portal?

Review Siemens documentation and the provided links for detailed configuration steps specific to your WinCC TIA Portal version (13.0 SP1).

Visualization Error with Gauges in TIA Portal V15.1

Hello, thank you for reaching out to Siemens Self Support. We understand you're experiencing a visualization error when adding gauges to your HMI/PC station project in TIA Portal V15.1.

This issue is often related to missing or corrupted graphic libraries. Here's a potential solution:

1. Check Graphic Library Versions: Ensure your graphic libraries are compatible with TIA Portal V15.1. Older versions can cause display issues.
2. Rebuild Graphic Libraries: Try rebuilding the used graphic libraries within TIA Portal. This can resolve corruption issues.
3. Update TIA Portal: While you're on V15.1, confirm you have the latest Update packages installed via SiePortal. Check for Updates
4. Test with a Simple Gauge: Create a new project and add a simple gauge to isolate the problem. If it works, the issue likely lies within your existing project's configuration.

For further assistance and to review similar cases, please refer to this FAQ on the Siemens Support website: TIA Portal V15.1 Visualization Errors

If the problem persists, please open a support request through SiePortal, including the project (or a representative sample) and the error message details.

Efficient Tag Reading from Siemens PLCs (1500/1200) via Industrial Ethernet

For reading a large number of tags (especially Booleans) from Siemens PLCs (1500/1200) over Industrial Ethernet (IE) with minimal communication load, avoid reading tags individually. Packing data is significantly more efficient.

Here's a breakdown of recommended approaches:

1. Data Blocks & Unpacking in WinCC: This is the most efficient method. Pack your Boolean values into a Data Block within the PLC. Read the entire Data Block as a single communication request. In WinCC (TIA Portal), unpack the Data Block into individual Boolean tags. This minimizes the number of PLC cycles used for communication.
2. Arrays within the PLC: Similar to Data Blocks, arrays reduce communication overhead. Read the entire array at once.
3. Optimized Data Types: Use appropriate data types. For example, packing multiple Booleans into a single integer (using bit manipulation) and reading that integer is very efficient.

Why this matters: Each tag read creates a separate communication request (PDU). More PDUs = higher network load & increased PLC cycle time. Reducing the number of PDUs is crucial for performance, particularly with a large number of tags and multiple PLCs.

Further Information: Refer to the SiePortal for detailed guidance on optimizing communication with Siemens PLCs. Siemens Support Article and Optimize Communication

WinCC Professional V15.1 Update 4 - Screen Adaptation Issues

Hello masmith1553,

You've encountered a common challenge with screen adaptation in WinCC Professional V15.1. The 'Adapt screen' feature is designed to scale *down* to smaller resolutions, but reliably scaling *up* to larger resolutions, especially with aspect ratio changes like 4:3 to 16:9, can be problematic.

Here's a breakdown of the issue and potential solutions:

1. Design for the Highest Resolution: The most reliable method is to design your HMI primarily for the 1920x1080 resolution (16:9). Then, use the 'Adapt screen' feature to scale down to 1280x1024 (4:3).
2. Screen Properties: Double-check your screen properties. Ensure 'Adapt screen' is enabled in the Runtime Settings. Also, verify that the 'Scaling' settings are set to 'Proportional'.
3. Graphics Alignment: Ensure all graphics are aligned to the screen edges and are not fixed to specific pixel coordinates. Using relative positioning helps with scaling.
4. Consider Multiple Screens: For optimal appearance on both resolutions, you might consider creating two separate screens – one for 4:3 and one for 16:9. This provides the best visual quality but requires more development effort.

Important Note: WinCC's screen adaptation isn't a perfect solution for significant aspect ratio changes. Some manual adjustments to graphic sizes and positions may still be necessary.

For further detailed information, please refer to the Siemens Support article: Screen adaptation in WinCC (TIA Portal) does not work as expected

If you continue to experience issues, please provide screenshots of your screen properties and a sample project (if possible) through the Siemens Support Portal for further assistance.

Regards,
Siemens Self Support

UpdateTag Function in WinCC RT Advanced

You are correct that the UpdateTag function is documented for WinCC RT Advanced. The "Variable 'UpdateTag' is not defined" error typically occurs due to a namespace issue.

The UpdateTag function resides within the CIMRuntime namespace. To resolve the compilation error, you must explicitly qualify the function call with this namespace.

Correct Usage: CIMRuntime.UpdateTag(TagHandle, Value)

Please refer to the following SiePortal knowledge article for more details and examples:

This article provides a comprehensive explanation and troubleshooting steps. Updating tags on demand using UpdateTag is a valid approach to avoid unnecessary cyclic updates.

WinCC Upgrade to V16 & Web Navigator

You are correct regarding the Runtime license: 6AV2105-3HH06-0AE0 (SIMATIC WinCC RT Professional, 4096 PowerTags V16, upgrade V11..V15 -> V16) is required for the core upgrade.

Regarding Web Navigator, the licensing is included within the WinCC RT Professional license. The upgrade license you've identified includes the necessary Web Navigator rights for up to 5 clients. No separate license is needed for the Web Navigator itself when upgrading within the same number of clients.

For detailed information on WinCC V16 licensing and compatibility, please refer to the official Siemens documentation on SiePortal.

Siemens Self Support

Connecting Additional OPC Servers to WinCC TIA Portal

Hello! To connect another OPC server to WinCC TIA Portal, you'll primarily use OPC UA or OPC Classic connectivity. Here's a breakdown:

OPC UA (Recommended)

TIA Portal V17 and higher have native OPC UA support.

1. Add Connection: In the TIA Portal project, navigate to 'HMI > Connections > OPC UA'.
2. Configure: Enter the OPC UA server endpoint URL and configure security settings.
3. Browse: Browse the OPC UA server's namespace to select tags.

Refer to Siemens Support article for detailed instructions.

OPC Classic (Legacy)

For older OPC servers, you might need the OPC Classic interface. This often requires a redistributable and configuration within WinCC Runtime.

1. Install Redistributable: Install the Siemens OPC Classic Redistributable.
2. Configure in Runtime: Configure the OPC connection within the WinCC Runtime configuration editor.

See this Siemens FAQ for more information on OPC Classic.

Important: Ensure the OPC server is running and accessible from the TIA Portal engineering PC.

WINCC Runtime Advanced V13 Limitations

Here's a breakdown of limitations for WINCC Runtime Advanced V13, along with links to relevant documentation:

1. Screen Limitations

The maximum number of screens is largely dependent on the hardware and system configuration. However, a practical limit generally falls around 500-1000 screens for optimal performance. Excessive screens can impact loading times and runtime responsiveness.

2. Objects per Screen

The number of objects (buttons, fields, pictures, etc.) per screen is also system-dependent. A good practice is to keep the object count below 200-300 for complex screens to maintain performance. Simple screens can handle more.

3. Tags per Screen

The number of tags directly bound to a screen impacts performance. Aim for 50-100 actively updating tags per screen. Excessive tag connections can lead to slower update rates.

4. General Limitations & Further Information

• Maximum Data Points: WINCC Runtime Advanced V13 supports a significant number of data points, but this is tied to licensing and hardware capabilities.
• Alarm History: The size of the alarm history is configurable, but large histories consume significant resources.

For detailed limitations and best practices, please refer to the official Siemens documentation:

These links provide comprehensive details on system requirements, limitations, and configuration guidelines.

Recipe Selection and Job Mailbox - Initial Setup Assistance

Hello! As Siemens Self Support, integrated with SiePortal, I understand you're facing challenges selecting recipes and data records from the PLC using the job mailbox. It's common to encounter initial hurdles when setting up recipe handling.

Jobs 69 & 70 are typically used for recipe transfer, but updating the HMI dropdown requires additional steps. The data record changes you observed indicate successful mailbox processing, but a separate mechanism triggers the HMI update.

Here's what you might be missing:

• HMI Configuration: Ensure your HMI recipe display is correctly configured to reflect changes made via the mailbox. This often involves linking the HMI dropdown to a specific PLC data block that's updated by the recipe transfer.
• Trigger Mechanism: You likely need a trigger (e.g., a PLC tag change, HMI button press, or scheduled event) to force the HMI to re-read the recipe list after the mailbox updates the data block.
• Recipe Trigger Job: Consider using Job 71 (Recipe Trigger) to explicitly signal the HMI to refresh its recipe list after a transfer.

Resources:

• Siemens Industry Online Support - Recipe Management
• SiePortal (Search for "Recipe Handling", "Job Mailbox", and "HMI Recipe Display")

For detailed configuration guidance tailored to your specific HMI and PLC, please provide the following information: HMI type (e.g., WinCC, TP series), PLC type (e.g., S7-1200, S7-1500), and the method you're using to link the recipe data to the HMI display.

Accessing Miniweb & Alarm Log Files Remotely - TP700 Comfort

Hello,

You are correct that Miniweb login credentials are typically configured directly on the HMI via WinCC Internet Settings. Unfortunately, TIA Portal v15.1 does not allow creating these credentials remotely.

Here are your options to access the alarm log file and Miniweb:

1. Configure Credentials on HMI: The most direct solution is to request someone on-site to access the HMI's 'WinCC Internet Settings' and create a user with a password. See Siemens documentation for detailed instructions.
2. Access Log File via FTP: If FTP server is configured on HMI, you can access the log file directly from your PC using an FTP client.
3. TIA Portal Archive/Retrieval: You could potentially archive the HMI configuration with the log file included and then retrieve it on your PC. However, this isn’t the intended use and may not be reliable for large log files.

Important Note: For security reasons, avoid using default or easily guessable passwords.

For further assistance, please refer to the Siemens Industry Online Support and search for "TP700 Miniweb password" or "TP700 Alarm Log Access".

Best regards,
Siemens Self Support

TIA Portal V16 Update 5 - WinCC Professional V16, SIMATIC Logon: "TriggerOperatorEvent" Errors in WebNavigator

The errors you are encountering ("undefined identifier 'TriggerOperatorEvent'" and "'TriggerOperatorEvent' is not a function") in WebNavigator after creating Operator Event logging scripts with a Release button event are a known issue in TIA Portal V16 Update 5 when using faceplates.

Cause: The TriggerOperatorEvent function is not fully supported or correctly interpreted in the WebNavigator environment despite functioning correctly in the client runtime.

Solution/Workaround:

• Suppression: As you've found, suppressing the errors allows WebNavigator to function correctly. This is a temporary solution.
• Alternative approach: Avoid using the TriggerOperatorEvent function specifically within scripts that are executed by WebNavigator. Consider alternative methods for triggering events or updating the HMI based on your requirements. For example, you might use indirect triggering through PLC variables.
• Update TIA Portal: Check for newer updates of TIA Portal V16. Siemens often releases updates that address known issues.

Further Information: You can find related discussions and potential solutions on the Siemens Support forum: Siemens Support Forum. Searching for "TriggerOperatorEvent WebNavigator" will likely yield relevant results.

Disclaimer: As Siemens Self Support, I am an AI assistant. For critical applications, always consult official Siemens documentation and support channels.

Password Protection for View Navigation in WinCC Professional V13

Hello! You can implement password protection for navigating between views in WinCC Professional V13 using User Management and appropriate scripting.

Here's a general approach:

1. User Management Configuration: Define user groups with specific access rights within WinCC.
2. View Properties: Assign specific user groups to each view, restricting access.
3. Scripting (VBScript): Use VBScript in the 'OnTouch' event of buttons/objects used for view navigation. The script should check the currently logged-in user's group membership before allowing navigation.

Refer to the following resources for detailed guidance:

• WinCC Professional V13 SP1 – Simple Sample: Users – access restriction
• How to use user management in WinCC Professional

For TP900 panels, ensure the user management configuration is correctly deployed to the HMI device.

Error: No Configuration File Specified

This error message, "No configuration file was specified on the command line or in the “HmiRTm.ini” file," typically occurs during runtime of a WinCC Runtime Advanced project.

Possible Causes & Solutions:

• Missing Configuration File: Ensure the correct HMI configuration file (.pcd or .apc) is being referenced.
• Incorrect Path: Verify the path to the configuration file in the command line or HmiRTm.ini is accurate.
• HmiRTm.ini Configuration: Check the HmiRTm.ini file (located in the WinCC Runtime Advanced installation directory) to ensure the 'ConfigurationFile' parameter is correctly set with the full path to your project.
• Command Line Parameters: If starting Runtime via the command line, make sure you are including the configuration file path as a parameter.

Further Support:

Please refer to SiePortal for detailed information and troubleshooting steps:

Also check FAQ: How to start WinCC Runtime Advanced in command line mode.

Reading and Writing Data Block Variables from KTP1000 Basic PN

Yes, it is absolutely possible to read and write Data Block (DB) variables from your KTP1000 Basic PN HMI with a S7-1200 CPU and TIA Portal V10.5.

How to achieve this:

1. Establish Communication: Ensure a properly configured HMI connection in TIA Portal to your S7-1200 PLC.
2. Create Tags: In the HMI project, create HMI tags that are linked to the DB variables in the PLC. Use the correct data type matching the PLC DB variable.
3. Access DB Variables: When creating the HMI tags, you’ll specify the PLC address using the DB number and offset (e.g., "DB1.DBX0.0" for a bit, or "DB1.REAL0" for a Real value).
4. HMI Screen Design: Drag and drop I/O fields onto your HMI screen. Link these I/O fields to the HMI tags you created.
5. Input Fields for Writing: For writing to the DB, use Input fields. When a value is entered and accepted in the input field, the HMI will write the value to the associated DB variable.

Important Considerations:

• Data Types: Ensure the data types of the HMI tags match the PLC DB variables to prevent errors.
• Access Rights: Verify that the HMI has the necessary access rights to read and write to the specific DB variables.
• Optimization: For large DBs, consider optimizing communication by only transferring necessary variables.

Further Resources:

For detailed step-by-step instructions and examples, please refer to these resources:

• Siemens Support - Accessing PLC Data Blocks from HMI
• Siemens Forum - HMI and Data Blocks

Siemens Self Support - Your partner for efficient solutions.

Object Disappearance in WinCC - TIA Portal

This issue, where objects vanish after closing a pop-up screen and reappear when another pop-up is closed, is often related to screen updates and object visibility management within WinCC (TIA Portal). The linked topic highlights this behavior.

Solution: You need to adjust the "Redraw" settings for the main screen. Specifically, ensure the screen is configured to redraw completely when regaining focus.

1. In TIA Portal, open your HMI project.
2. Navigate to the main screen experiencing the issue in the project tree.
3. Go to Properties of the screen.
4. Select the Screen transitions tab.
5. Under Events -> On losing focus, check/enable the option Redraw screen completely.
6. Also under Events -> On gaining focus, check/enable the option Redraw screen completely.

Explanation: When a pop-up closes, the main screen doesn't always update correctly without being explicitly redrawn. This can lead to objects becoming invisible. Forcing a complete redraw ensures all elements are refreshed and displayed properly.

For more detailed information and examples, please refer to the following Siemens Support article:

Stopping Objects in WinCC Basic (TIA Portal)

Hello! I understand you're following the YouTube tutorial (https://www.youtube.com/watch?v=AJYzyGMSg7w) and having trouble stopping the moving object, even with a PLC timer.

Directly stopping a moving object via a PLC timer isn't the typical approach in WinCC Basic. The animation path needs to be controlled. Here's what commonly works:

• Disable/Enable the Animation: The most reliable method is to control the 'Enabled' property of the animation object from the PLC. When disabled, the object stops.
• Modify the 'Run' Property: Set a PLC tag to control the 'Run' property of the animated object. A '0' stops the animation, and a '1' starts it.
• Check Timer Logic: Ensure your PLC timer is correctly configured to toggle the control tag (Enabled/Run) and that the tag is properly linked to the WinCC Basic object. Verify data type compatibility between PLC and HMI tag.

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

• Animation control in WinCC Basic
• How to stop an animated object?

If you continue to experience issues, please provide details about your PLC code (timer configuration and tag used), and the WinCC Basic animation settings (specifically, which property you are trying to control).

WinCC V11 Structure Tags & WebNavigator Licensing

You're asking about similarities to WinCC V7 features in WinCC V11.

Structure Tags

Yes, WinCC V11 supports structure tags similar to WinCC V7. You can define structures for both internal and external tags, allowing for organized data handling. The functionality is maintained and enhanced in V11.

WebNavigator Licensing

The licensing for WebNavigator in WinCC V11 largely follows the V7 model. You'll require:

• WinCC Server License: A base WinCC Server license is essential.
• WebNavigator Client Licenses: You need a separate license for each concurrent WebNavigator client accessing the system.

For detailed licensing information, please refer to the official Siemens documentation on SiePortal: SiePortal. Search for "WinCC V11 licensing" or "WebNavigator licensing".