Converting TDOP (Protool) to a Protool Project

Good morning!

Yes, you can convert a TDOP folder containing PRO.FUD and PRO.RDF files to a Protool project. These files are part of a Protool project.

Here’s how:

1. Open Protool: Launch Siemens Protool (Protool CS or Protool DX).
2. New Project: Create a new Protool project.
3. Import: Use the "Import" function (typically under File or Project) and select the TDOP folder. Protool should recognize the PRO.FUD and PRO.RDF files.

Important Note: Ensure you have the correct Protool version compatible with the TDOP files. Older TDOP files may require an older version of Protool.

For detailed instructions and troubleshooting, please refer to the SiePortal knowledge base:

Data Import to Multiple Recipes in WinCC Unified

Hello! It sounds like you're facing an issue with importing CSV data into specific recipes within WinCC Unified. The system appears to be defaulting to the first recipe.

Unfortunately, WinCC Unified currently lacks a direct mechanism to specify the target recipe during the CSV import process itself. The import functionality generally applies to the currently active recipe.

Here's a workaround:

1. Activate the target recipe: Before importing each CSV file, ensure you've activated the recipe you want the data to be imported into.
2. Import Data: Then, proceed with the CSV import. The data will be loaded into the currently active recipe.

For detailed guidance on recipe management and data import, please refer to the Siemens documentation:

If the problem persists, consider submitting a support request through SiePortal for further assistance, providing your project details and screenshots.

Syncro Error with OP when opening OP30B/Com Graph Backup

Dear Muneeb,

The "Syncro.. error with OP" typically indicates a version mismatch between the backup file (created from OP30B) and the Com Graph version you are using to open it.

Here's how you can troubleshoot and potentially resolve this:

1. Version Compatibility: Ensure your Com Graph version is compatible with the OP30B project version the backup was created from. Older Com Graph versions may not correctly interpret newer OP30B backup structures.
2. Restore to Correct Version: Ideally, restore the backup to a system running the exact same version of Com Graph as the original OP30B project.
3. Check SiePortal: Search SiePortal for "Com Graph OP synchronization error" or similar keywords for known issues and solutions.
4. Data Conversion: If a direct open isn't possible, you might need to explore intermediate conversion steps (if available) depending on the Com Graph and OP30B versions involved.

If you continue to experience issues, please provide the specific versions of both OP30B and Com Graph you are using, and details on the error message, to assist with further investigation.

Sincerely,
Siemens Self Support

Communicating TP177A to Omron CQM1H CPU51

Dear rheyaninz,

You successfully communicated with the Omron CPU via WinCC Flexible runtime on a PC using a USB to serial cable. Now you want to achieve the same communication using a TP177A HMI.

Here's how you can approach this:

1. Communication Protocol: The TP177A needs to be configured to communicate using the appropriate protocol for the CQM1H. Typically, this is either Serial (RS-232) or a proprietary Omron protocol. Verify the communication settings (baud rate, parity, data bits, stop bits) used in your PC-based WinCC Flexible configuration.
2. Cable: You will likely need a serial cable (RS-232) to connect the TP177A to the CQM1H. The TP177A has a serial port; ensure you have the correct cable with appropriate connectors for both devices. You may need a null modem cable depending on the CQM1H's serial port configuration.
3. TP177A Configuration: Configure a new communication connection within the TP177A project using WinCC Flexible. Specify the serial port, baud rate, and other communication parameters to match the CQM1H settings.
4. Data Exchange: Define the data exchange between the TP177A and the CQM1H. This involves mapping tags in WinCC Flexible to the corresponding memory addresses in the CQM1H.

Resources:

• Siemens Support Article: WinCC Flexible Communication with Omron PLCs (This provides a general overview and may contain helpful details.)
• Omron Documentation: Refer to the Omron CQM1H CPU51 manual for specific serial communication settings and protocol information.
• WinCC Flexible Documentation: Consult the WinCC Flexible documentation for detailed instructions on configuring serial communication.

If you encounter issues, providing specific details about your current WinCC Flexible configuration (tags, communication parameters) and the CQM1H serial port settings will help in troubleshooting.

Best Regards,
Siemens Self Support

TP177B Automatic Connection Switching & Communication Conflict

Hello,

Regarding your redundant S7-400H PLCs with CP443 and TP177B HMI, automatic connection switching to the Master PLC isn't directly supported via IP address configuration on the TP177B alone. You'll need a more sophisticated solution leveraging redundancy protocols.

Suggestions:

• RedMate: Consider using Siemens' RedMate redundancy module. It handles automatic switchover and communicates this status to the HMI. More info on RedMate
• Custom Logic & Diagnostics: Implement logic within the PLCs to detect the Master PLC and signal this status to the TP177B via a dedicated variable. The TP177B can then use this variable to switch connections.

Addressing the Communication Conflict:

You're experiencing a conflict because the TP177B uses TCP/IP, while your WinCC SCADA uses Industrial Ethernet (likely PROFINEt). They are competing for resources.

Solutions:

• Separate Networks: The best solution is to use separate physical networks – one for the TP177B (TCP/IP) and one for WinCC (PROFINEt).
• CP443 Configuration: If separate networks aren't possible, configure the CP443 cards to support both protocols, carefully managing IP addresses and routing. This is complex and may impact performance.
• WinCC Communication via CP443: Configure WinCC to communicate *through* the CP443 cards using TCP/IP, mirroring the TP177B’s communication method.

For detailed configuration guidance, please consult the Siemens documentation for your specific hardware and software versions. You can find relevant documentation via SiePortal: SiePortal

Best regards,
Siemens Self Support

TP177A Panel Blank Screen & ProSave Issue

Based on your description and the referenced Siemens support document (ID: 19701610), you're facing difficulties resetting your TP177A panel due to a missing OS image in ProSave and a mismatch error when attempting a manual update.

Here's a breakdown of potential issues and troubleshooting steps:

• Connection Type: Double-check you've selected "Serial (via RS232/PPI Multi-Master Cable)" in ProSave's "General" settings, as recommended in the document. Ensure the correct COM port is selected.
• Adapter Compatibility: The 6ES7 972-0CB20-0XA0 adapter should work, but verify the cable is correctly connected to both the panel and your PC. A faulty cable can mimic adapter issues.
• OS Image Availability: The document states an image should appear by default. Since it doesn't, and manual selection yields a mismatch, this is a key issue.
• Image Selection: Given you state there’s only one image for TP177A, and it reports a mismatch, it’s likely the image isn’t *specifically* for your panel’s revision.

Recommendation:

Download the correct OS update image for your exact TP177A panel version (6AV6 642-0AA11-0AX0) from the Siemens Industry Support. Manually selecting the appropriate image is crucial. If the mismatch persists after verifying the image version, consider contacting Siemens Support directly for further assistance, as it could indicate a hardware problem with the panel or adapter.

Understanding Job Operation Changes in Siemens Software

Yes, you can typically upload a modified operation (like changing OP20 to OP20 - essentially a no-change upload) in Siemens software, but the process depends on your specific software (e.g., NX CAM, Teamcenter, etc.) and configuration.

Here's a general approach and key considerations:

• Software Specifics: The upload process differs significantly between NX CAM, Teamcenter Manufacturing, and other Siemens solutions.
• Version Control: Ensure your system is configured to handle version control effectively. Uploading the same operation might create a new revision.
• Impact Analysis: Before uploading, consider if this change affects downstream processes or other dependent operations.

For detailed instructions, please refer to the SiePortal knowledge base:

• Siemens Support
• NX CAM Documentation (If applicable)
• Teamcenter Documentation (If applicable)

If you can specify which Siemens software you're using, I can provide more tailored guidance.

PDF Record Creation & Transfer from TP1200 to Server

You're looking to create PDF records from PLC data on your TP1200 HMI and transfer them to a remote server, avoiding direct server configuration or virtual printer setup.

Here's a breakdown of how to achieve this, focusing on using Option+ Manager (since direct server config isn't possible):

Solution Outline:

1. PDF Creation on TP1200: Utilize the TP1200's PDF generation capabilities. You can read data from your S7-300 PLC DBs and create a PDF report stored on the HMI's SD card with a button press.
2. Option+ Manager Configuration: This is the key to server transfer. You'll need to configure Option+ Manager on the TP1200 to establish a connection to the remote server.
   • Configuration Location: Configuration is primarily done on the TP1200 through Option+ Manager. Minimal (if any) server-side changes are needed.
   • Protocol: Option+ Manager supports protocols like FTP, SFTP, or Email. FTP is often the simplest for file transfer.
3. Transfer Trigger: Implement a second button on the TP1200. When pressed, this button uses Option+ Manager to transfer the PDF file from the SD card to the remote server.

Important Considerations:

• Option+ License: Ensure you have the appropriate Option+ license for the desired communication protocol (e.g., FTP, SFTP).
• Network Connectivity: Verify network connectivity between the TP1200 and the remote server.
• Security: If using FTP, consider using SFTP for more secure file transfer.
• CSV vs PDF: You'll need to modify your HMI program to generate the PDF instead of a CSV file.

Resources:

• TP1200 - How to create PDF reports on the HMI
• Option+ Manager - Overview

This approach allows you to achieve your goal without modifying the remote server or setting up a virtual printer. Focus your configuration efforts on the TP1200 and Option+ Manager.

TP1200 Comfort Slow Navigation - Main Screen Issue

Dear Customer,

Thank you for providing the detailed information and the video link. Based on your description and the fact that the issue occurs even when disconnected from the network, and simulation works fine, it strongly suggests a performance bottleneck within the HMI project itself, specifically related to the main screen.

Here are potential causes and troubleshooting steps:

• Excessive Tag Updates: Even if not visually apparent, a large number of tags being updated on the main screen (even if not displayed) can cause significant lag. Review the tag list associated with the main screen and minimize unnecessary updates. Use cyclic updates sparingly.
• Complex Graphics/Animations: Complex graphical elements or animations on the main screen can strain the HMI's processing power. Simplify graphics where possible.
• Scripting: Extensive or inefficient scripts running on the main screen's events (e.g., screen activation) can cause delays. Optimize any scripts for performance.
• Global Objects/Templates: Overuse of global objects or templates, especially if they are complex, can contribute to performance issues.
• HMI Firmware: Ensure you are running the latest firmware version for the TP1200 Comfort. Updates often include performance improvements. Check Siemens Industry Online Support for updates.

Recommendation: Start by temporarily removing a significant portion of the tags and graphical elements from the main screen to see if the performance improves. If it does, gradually add elements back in to identify the specific culprit.

For further assistance, please provide your HMI project (or a representative sample) to Siemens Support via Siemens Support Request Form.

Sincerely,
Siemens Self Support

KTP1000 Internal Tag Limit - WinCC V13 SP2

Hello,

Yes, the 500 tag limit documented for the KTP1000 HMI when using WinCC V13 SP2 includes both internal and external tags combined. This means the total number of tags (internal variables, process tags connected to the PLC, etc.) cannot exceed 500.

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

KTP1000: What is the maximum number of tags?

You can also find additional information within the WinCC V13 documentation library via SiePortal.

Sincerely,

Siemens Self Support

Downloading Files from Comfort Panels via PowerShell

This outlines a method to download files (e.g., AuditTrail.csv) from Siemens Comfort Panels with the Mini Web Server enabled, using a PowerShell script. This is particularly useful when a WINS server or Windows file sharing isn't available.

Script Overview

The provided script utilizes Invoke-WebRequest to:

1. Authenticate to the Comfort Panel's Mini Web Server using POST request to the login URL.
2. Download the specified file using a GET request, storing it locally.

Key Script Variables:

• $loginUrl: URL for the Comfort Panel's Mini Web Server login page (e.g., 'http://192.168.1.83/FormLogin').
• $downloadUrl: URL of the file to download (e.g., 'http://192.168.1.83/StorageCardSD/AuditTrail0.csv').
• $outputFilePath: Local path to save the downloaded file (e.g., 'C:\\file.csv').
• $loginData: Contains the username and password for the Mini Web Server (e.g., "Login=Administrator&Password=1234").

Appending to File

The script currently overwrites the output file. Modifying the Invoke-WebRequest command for the download to append might be possible, but requires testing. Consider using the `-Append` parameter (if supported and compatible with the Mini Web Server's response).

Important Considerations

• Security: Hardcoding credentials in the script is not recommended for production environments. Explore secure methods for storing and retrieving credentials.
• Error Handling: Implement robust error handling to manage potential issues like network connectivity problems, authentication failures, or file write errors.
• Mini Web Server Limitations: The Mini Web Server has limitations. Large files or frequent requests may impact panel performance.

For further assistance with Siemens products and support resources, please visit the Siemens Support Portal.

Accessing TP1200 Data via USB without Interruption

Here's how to retrieve data (alarms, errors, etc.) from your TP1200 HMI via USB, and troubleshooting the RJ45 connection:

USB Data Transfer

1. Create a Project: Open TIA Portal and create a new project (or open an existing one).
2. Add HMI Device: Add your TP1200 HMI to the project.
3. Go Online & Download: Go online with the HMI. Choose "Download to Device" and select "Entire project with parameterization." This will not disrupt operation if you only download the configuration.
4. Access Data in TIA Portal: After downloading, you can access alarms, error logs, and other data within the TIA Portal project.
5. Save Archive: Save the TIA Portal project as an archive (.zip) to retain a copy of the HMI configuration and data.

RJ45 Connection Troubleshooting

Difficulty logging in via RJ45 often relates to network settings. Here are a few checks:

• IP Address Conflict: Ensure your PC and HMI have unique IP addresses on the same subnet.
• Firewall: Temporarily disable your PC's firewall to rule out connection interference.
• TIA Portal Connection Settings: In TIA Portal, verify the HMI's IP address is correctly configured in the "Device View".
• PROFINET Settings: Check PROFINET communication settings on both the HMI and your PC's network adapter.

Further Support

For detailed instructions and troubleshooting guides, please refer to these resources on the Siemens Support website:

• How do you create a backup of a TP1200 Comfort HMI?
• Communication between PC and HMI via PROFINET

If you continue to experience issues, please provide the exact error message you receive when trying to connect via RJ45 for more specific assistance.

Screensaver Deactivation with Scheduled Script on MP277

The scheduled script on your MP277 is likely preventing the screensaver activation due to continuous panel activity, even with seemingly passive operations. The file operations (kill, copy) and log handling, though quick, register as user interaction, resetting the screensaver timer.

Why this happens: The HMI interprets any script execution as activity, overriding the screensaver timeout.

Workarounds:

1. Optimize Script Execution: Reduce the script's execution frequency if possible. Can the task be done less often than every minute?
2. Use a Timer (Indirectly): Instead of a scheduled script, consider using a global script block triggered by a timer that only performs the necessary actions when certain conditions are met. This introduces idle time for the screensaver.
3. HMI API Calls (Advanced): Investigate using HMI API functions to directly manage screen activity without constant script execution. Refer to the Siemens documentation for available functions.

For detailed information on HMI scripting and API functions, please refer to the SiePortal knowledge base: Siemens Industry Support Portal. Searching for "MP277 screensaver script" may yield relevant articles.

Please note that Siemens Self Support can provide additional assistance if the above suggestions do not resolve the issue.

Modbus Communication with TP 277/177B and 3rd Party PLCs (Selectron)

You're facing a common issue when configuring Siemens TP panels (TP 277 & TP 177B) with 3rd party Modbus devices like the Selectron 831. The WinCC Flexible configuration specifically restricts CPU type selection to certain brands.

Solution: The "Modicon Modbus" driver in WinCC Flexible is designed for Schneider PLCs. For 3rd party Modbus devices, you must use the "Generic Modbus" driver. This allows you to define the communication parameters without being limited by predefined CPU types. You will need to manually configure the Modbus address mapping.

Address Table/Mapping: There isn't a pre-defined Siemens address table for all PLCs. You'll need to refer to the Selectron 831 Modbus communication manual to create the correct mapping between TP tags and Selectron registers.

Communication Confirmation: Yes, Siemens panels can communicate with Modbus devices. However, successful communication relies on correct driver selection (Generic Modbus), accurate Modbus address mapping, and proper physical layer configuration (RS485/RS422 settings, baud rate, parity, etc.).

Troubleshooting (Navnag's issue with TP 177B): If no Tx/Rx is happening despite correct configuration, double-check:

• Physical Connection: Ensure correct wiring and termination resistors for RS485/RS422.
• DIP Switches: Verify correct DIP switch settings on the TP 177B for RS485/RS422 mode.
• Baud Rate & Parity: Confirm the baud rate, parity, and data bits match *exactly* between the TP and Selectron PLC.
• Modbus Addressing: Check the slave address configured in both devices.

For further assistance and detailed configuration steps, please refer to the WinCC Flexible documentation and Siemens Support articles on SiePortal: Siemens Industry Online Support

Historical Data Backup for Basic 7" HMI

Hello Arek,

Unfortunately, the Basic 7" HMI does not natively support direct saving of historical trend data to external memory like a USB stick.

The historical data is stored in the HMI's internal memory, which has a limited capacity. Options for managing this data include:

• Reducing the data logging frequency: This extends the storage duration.
• Clearing historical data regularly: Manually delete older data through the HMI's interface.
• Utilizing WinCC (TIA Portal): For more advanced data handling, consider migrating to a WinCC HMI (using TIA Portal) which offers features like recipe management and data archiving to external sources.

For detailed information on managing historical data within the Basic HMI, please refer to the Siemens documentation:

Best Regards,
Siemens Self Support

Migrating OP277 Backup to a Comfort Panel

Yes, it is possible to migrate a backup file from an OP277 to a new Comfort Panel, even without the original project file. However, it requires a specific process using Siemens software.

Here's how:

1. Use WinCC Flexible 2008 SP3 or higher: This software version is capable of opening OP277 backups (.backup files).
2. Open the Backup: In WinCC Flexible, go to 'File > Open' and select the .backup file.
3. Convert to a Project: WinCC Flexible will convert the backup into a project. Be aware this process might show warnings or errors due to differences between the OP277 and the Comfort Panel.
4. Hardware Configuration: You *must* configure the hardware settings in the WinCC Flexible project to match your new Comfort Panel. This includes specifying the correct panel type, communication settings (PROFINET, MPI/PPI, etc.), and memory size.
5. Download to Comfort Panel: Once the hardware is configured, download the project to the Comfort Panel.

Important Considerations:

• Screen Resolution and Objects: The Comfort Panel has a different screen resolution than the OP277. You may need to adjust screen layouts and object sizes for optimal display.
• Global Scripts & Data Types: Review and potentially update global scripts and data types for compatibility.
• TIA Portal: While WinCC Flexible is used for the initial migration, you can open the WinCC Flexible project in TIA Portal (V13 SP1 or higher) for further editing and maintenance, if needed.

SiePortal Resources:

• FAQ: Migration of Operator Panels from WinCC Flexible to TIA Portal
• How to migrate a WinCC flexible project to TIA Portal

If you encounter issues during the migration, please provide details about any error messages or unexpected behavior for further assistance.

Missing Graphics and Text on Restored MP 277 HMI

This issue typically arises from a version mismatch between the HMI firmware and the WinCC Runtime version used to create the project. Restoring a project to a panel with a different firmware version can lead to display errors like missing graphics and text.

Here's a troubleshooting approach:

1. Check Firmware Versions: Verify the firmware version on both the original (defective screen) and the target MP 277 panels.
2. WinCC Runtime Version: Determine the WinCC Runtime version used to develop the project.
3. Update/Downgrade: Update the target MP 277's firmware to match the WinCC Runtime version, or adjust the WinCC Runtime version used to open and re-compile the project. See Siemens Support article for firmware updates.
4. Recompile & Download: After adjusting versions, recompile the project in WinCC and download it to the target MP 277.

Important: Factory resetting the panel doesn't resolve version incompatibility issues. A direct firmware/runtime version match or adjustment is required.

If the problem persists, please provide the firmware versions of both panels and the WinCC Runtime version. You can also check SiePortal for known issues and FAQs.