PM-QUALITY Database Connection Error - 627E IPC

This error indicates a problem with the connection between PM-QUALITY and its databases. Here's a breakdown of potential solutions, leveraging Siemens support resources:

Troubleshooting Steps:

1. Database Initialization: As the error message suggests, re-initialize the PM-QUALITY databases. This is often the quickest resolution.
2. Check SQL Server/Database Status: Ensure the SQL Server instance (or other database system PM-QUALITY uses) is running and accessible. Verify services are started.
3. User Permissions: Confirm the user account PM-QUALITY uses to connect to the database has the necessary permissions (read/write).
4. Network Connectivity: Though unlikely if it worked yesterday, double-check network connectivity between the IPC and the database server.
5. PM-QUALITY Configuration: Review the PM-QUALITY configuration within WinCC to ensure the database connection details (server name, database name, user ID, password) are correct.

Further Support & Resources:

• SiePortal Knowledge Base: Search SiePortal using keywords like "PM-QUALITY database connection error", "PM-QUALITY database initialization", and "PM-QUALITY reports not showing". Siemens Support
• PM-QUALITY Documentation: Refer to the official PM-QUALITY documentation for detailed configuration and troubleshooting instructions.
• Siemens Support Forum: Post your issue on the Siemens Support Forum to get assistance from other users and Siemens experts.

Given that the problem started suddenly without changes, a database service interruption or permission issue is most likely. Re-initializing the databases is the recommended first step. If the issue persists, investigate the database server itself.

Configuring Alarms for ET200SP Connection Failures

To monitor connection status between your ET200SP, PLC, and HMIs, leverage diagnostics and alarm generation within TIA Portal. Here's a breakdown:

Steps to Configure Alarms:

1. Diagnostics Configuration: In TIA Portal, configure diagnostics for the PROFINET interface on the ET200SP. Enable "Diagnostics active" and select relevant diagnostics events (e.g., Connection establishment failures, message errors).
2. Alarm Generation: Create alarms in TIA Portal linked to the diagnostic objects of the ET200SP’s PROFINET interface.
3. HMI Integration: In your HMIs, create tags linked to the ET200SP's diagnostic output bits. Configure alarm displays based on these tag values. Since you have 5 HMIs, ensure consistent alarm configuration across all.
4. Connection Monitoring: Utilize PLC functions (e.g., `PGN_CheckConnection`) to actively monitor connections to each HMI and the ET200SP. Raise alarms in the PLC if connections are lost.

Resources:

• Siemens Industry Online Support: https://support.industry.siemens.com/ - Search for "ET200SP PROFINET diagnostics" and "TIA Portal alarm configuration".
• TIA Portal Documentation: Refer to the TIA Portal documentation for detailed instructions on configuring diagnostics and alarms.
• Example: Example for diagnostics configuration

By combining ET200SP diagnostics, TIA Portal alarm generation, and PLC-based connection monitoring, you can effectively detect and signal connection issues to your HMIs.

Unlimited Booking Lines in Resource Scheduling

Regarding your request for unlimited booking lines in Siemens Resource Scheduling, this is generally achievable through configuration adjustments within SiePortal.

Specifically, you'll need to review the settings related to "Maximum number of bookings per resource" and potentially "Booking horizon". These are typically found within the resource/crew profile configuration.

Please note: Completely removing limits on booking lines can impact system performance. Carefully consider the potential consequences before making changes.

For detailed instructions and guidance, please refer to the following resources within SiePortal:

• Configuring Resource/Crew Profiles
• Booking Horizon Settings

If you require further assistance, please open a support request through Siemens Support, referencing the above SiePortal documentation.

Disclaimer: As Siemens Self Support, I provide guidance based on available documentation. Complex configurations may require expert assistance.

WinCC OA S7+ Alarming Troubleshooting

Hello! I understand you're facing challenges setting up WinCC OA alarming with a Siemens S7-1511 PLC. Based on your detailed description, here's a breakdown of potential issues and troubleshooting steps, leveraging SiePortal resources:

Key Areas to Review:

1. TIA Portal Alarm Configuration: Double-check the 'Alarm Class' assignment within the 'Program_Alarm' FB properties. Ensure it correctly points to 'My_Alarm_Class'. Confirm the alarm is correctly appearing in the TIA Portal's alarm list (PLC Supervisons & Alarms).
2. WinCC OA Driver Configuration: Your driverAckClassPrefix = "S7" setting is correct. Verify the S7+ driver's connectivity and that alarming is enabled within the driver configuration in WinCC OA.
3. Alarm Class Mapping: Ensure 'My_Alarm_Class' from TIA Portal is accurately mapped to a corresponding alarm class in WinCC OA (System Management -> S7+ Alarm Class Mapping).
4. DPE Configuration - Critical Check: The 'Type of transformation = Int' and 'Direction = Input, Receive mode = Alarm' are correct. However, crucially, verify the 'Periphery Address Config' points to the *correct memory location* in the PLC where 'Alarm_Input' resides. This is often the root cause of such issues. Make sure the address is valid and accessible by the WinCC OA driver.
5. Trigger Signal: Verify the trigger memory bit is actually toggling in the PLC when you expect an alarm. Use the TIA Portal's online monitoring to confirm.

Resources:

• S7Plus PLC Alarms Guide: https://support.industry.siemens.com/cs/ww/en/view/109778031 (Review this guide again, paying close attention to the DPE configuration details.)
• WinCC OA Documentation: Consult the official WinCC OA documentation on S7+ driver configuration and alarming.
• SiePortal Forum: https://support.industry.siemens.com/cs/forums/us/en/discussion/ Search for similar issues and solutions from other WinCC OA users.

If the problem persists, please provide the following for further analysis:

• A screenshot of your DPE configuration (Periphery Address Config).
• The exact address in the PLC that corresponds to 'Alarm_Input'.

WinCC Flexible vs. WinCC (TIA Portal) for PC-Based Supervision

Dear Ignacio,

You're right to explore WinCC options for your production line supervision application. Here's a breakdown of the key differences and answers to your questions:

WinCC Flexible (MP377 Focused)

WinCC Flexible is primarily designed for Human Machine Interfaces (HMIs) like the MP377. While it *can* run on a PC as a Runtime (RT), it's not its strength. The limitation you experienced with sequential script execution is a core characteristic. It's single-threaded in its scripting engine when running as RT on a PC.

WinCC (TIA Portal)

WinCC within TIA Portal is a more modern and scalable SCADA system. It's built for PC-based applications and offers significantly more features, including better performance, scalability, and integration with other Siemens systems.

Key Differences:

• Scalability: WinCC (TIA Portal) is far more scalable for larger applications.
• Scripting: WinCC (TIA Portal) supports multiple concurrent scripts/tasks utilizing multi-threading. This addresses the limitation you faced with WinCC Flexible.
• Features: WinCC (TIA Portal) offers advanced features like alarm archiving, historical data collection, reporting, and web visualization that are either limited or unavailable in WinCC Flexible.
• Development Environment: TIA Portal provides a unified engineering environment for PLC, HMI, and drive programming.

Can WinCC applications run multiple scripts simultaneously?

Yes, WinCC (TIA Portal) applications can run multiple scripts concurrently. The multi-threading capability allows for parallel processing of tasks, improving application responsiveness.

Does WinCC Flexible running as RT allow it?

No, WinCC Flexible running as a Runtime on a PC does not allow concurrent script execution. It remains single-threaded in that configuration, as you’ve already experienced.

Recommendation: For a PC-based supervision application with additional functionalities, WinCC (TIA Portal) is the better choice. It provides the necessary scalability, performance, and features to build a robust and responsive system.

For more detailed information, please refer to the following resources:

• WinCC (TIA Portal) Overview
• WinCC Flexible Overview

Regards,
Siemens Self Support

Siemens S5 Visualization & HMI Compatibility with 928B CPU

Hello! Siemens Self Support here, integrated with SiePortal. You're looking for a list of HMIs/Operator Panels directly compatible with your Siemens 928B CPU for visualization. Here's a breakdown:

• OP17 DP12: As you mentioned, this is a confirmed compatible option.
• OP27: Supports communication with the 928B CPU.
• OP37: Compatible; offers larger display and more functionality.
• OP47: Can connect directly, providing advanced features.
• TP series (TP270, TP370): Touch Panels that are also compatible.

Important Considerations: Compatibility depends on the 928B CPU's firmware version and the communication protocol used (likely MPI/PROFIBUS). Check Siemens Industry Online Support for detailed compatibility lists and manuals related to your specific CPU model.

To determine the *most* appropriate panel, consider factors like display size, required functionality, and budget. You can find detailed specifications and pricing on the Siemens website or through a Siemens distributor.

Coloring Tank Level in WinCC OA using CTRL

You're on the right track with setValue, but the way you're calling the color variable isn't quite correct. The issue is likely how you're referencing the dynamic variable name within the object.

Instead of directly embedding the variable name in the string, you need to use string concatenation to build the correct expression. Here's how you can do it:

setValue("Tank4", "backCol", eval("$s_Col"));

Explanation:

• setValue("Tank4", "backCol", ...);: This targets the "backCol" property of the "Tank4" object.
• eval("$s_Col"): This is the key. eval() evaluates the string "$s_Col", resolving it to the actual color value stored in the '$s_Col' variable of the "Tank4" object.

Important Considerations:

• Ensure that '$s_Col' is correctly defined and has a valid color string (e.g., "red", "#FF0000") assigned to it within your tank object.
• Using eval() requires caution as it evaluates arbitrary code. In this scenario, it's safe as long as '$s_Col' is controlled within your system.

For more details on setValue and dynamic variables, please refer to the WinCC OA documentation on setValue and Dynamic Data Access in SiePortal.

Adding Tags to WinCC HMI Recipes without Data Loss

Yes, you can add new tags to recipes in a WinCC HMI and download the modified recipes without losing existing operation data values. Here's how:

1. Modify Recipes in the Engineering Software: Add the new tags to the existing recipes within your WinCC HMI project in the engineering software.
2. Download Recipe Data Separately: Instead of a full download, specifically download *only* the recipe structure (including the new tags). This is typically an option within the download settings.
3. Keep Existing Data: Ensure the download settings are configured to preserve existing process values during the recipe structure download.

Important Considerations:

• Always create a backup of your HMI project and the current recipe data before making any changes.
• Refer to the WinCC HMI documentation (available on SiePortal) for detailed instructions specific to your WinCC HMI version. Search for "Recipe Download Options" or "Preserving Process Values".

If you encounter issues, consult the SiePortal for FAQs, manuals, and support requests: Siemens Support