Hello, I am grateful for the valuable insights provided here. Although I have extensive experience with Rockwell, my experience with Siemens is limited and from the past. I am currently facing challenges in obtaining "useful" S7 archive files for easy restoration in case of a catastrophic failure at my new job assignment. The issue I am encountering is with offline project archives for active PLCs. When I compare these archives with the PLC, I often find discrepancies where some blocks are newer in the archive and some in the PLC. To address this, I have been manually copying mismatched blocks from the PLC to my offline file. However, I am now facing errors when opening blocks with descriptors or labels in the "Name" column of DBs. It seems that when these DBs are loaded into the PLC, the names do not get transferred, only the data structure. This poses a challenge in maintaining alignment and preserving descriptors in the archive. I am hesitant to simply overwrite the archive with newer blocks as I am not fully aware of the implications on existing data and program references. What are the recommended practices for achieving a functional archive state? Is there a way to align the data from PLC blocks with the newer offline blocks? Furthermore, I am unsure if descriptors in DBs are copied to the PLC or if they only exist in the offline file. Any advice, suggestions, or resources on this matter would be greatly appreciated as I navigate through this learning process. Thank you for your help in advance. Regards, "Bob"
It has been a while since I worked with S7, but the issue may be related to the database information, such as differences in time stamps. This can occur if the offline project is saved again without downloading. Additionally, when uploading databases from the PLC, it may default to no structure. One way to address this is to open both online and offline projects and transfer the online databases to the offline project. This method was a common practice in older S5 models to prevent overwriting the structure when uploading blocks. For more updated solutions, someone with recent experience in this area can provide further guidance.
Managing project discrepancies between online and offline settings can be a complex task, but there are strategies to simplify the process. When faced with differences in values, consider rebuilding or recompiling the project to resolve the issues. Additionally, transferring symbols tables and using comparison tools can help identify and reconcile discrepancies effectively. When comparing projects, focus on identifying code matches and timestamp variations. By utilizing features such as hiding datablocks with different actual values, you can streamline the reconciliation process. If structural or hardware configuration variations are present, create a new project, upload station data, and compare blocks to ensure alignment. To address differing hardware configurations, follow a systematic approach by copying essential components from the old archive to the new project. Pay close attention to symbols, code blocks, and Hardware Configuration to ensure consistency. Additionally, include steps for transferring WinCC Flexible projects and Sinamics objects to maintain project integrity. In cases where global DB structures do not match, consider copying the online DB into the offline file and transferring the symbols table accordingly. By following a structured procedure and utilizing comparison tools, you can effectively manage project conflicts and maintain consistency across online and offline settings.
Hello Bob, it appears that the archived project does not contain the latest changes made to the PLC. It is crucial to establish a strict routine for immediately backing up any program changes. Before going online with a PLC, always conduct an offline/online comparison. Be sure to deselect any differences in actual values that are flagged in the program blocks. Only proceed if no differences are found. If variances are detected, rename the offline project with a new version number and work on synchronizing the offline and online programs. For single differing program blocks, use the comparison view to identify and resolve the issue. If multiple blocks differ, create a new project and perform a thorough block comparison. Once all differences have been addressed in the offline project, load it back to the PLC to synchronize timestamps. Consider not loading DBs if structures remain unchanged. Finally, remember to archive the project to the server. Additionally, ensure to select 'Hide data blocks with different actual values' in the comparison results to filter out unnecessary differences.
I would like to express my gratitude to everyone for their invaluable feedback – it is truly appreciated. I will carefully review each suggestion to determine the best course of action. At this moment, I feel confident that all aspects have been thoroughly addressed. Once again, thank you!
Thank you for the feedback. I have consolidated files into a new version of the original project to keep it separate. After running a file comparison, I have ensured that the project can be downloaded onto a clean PLC in case of emergencies. However, I am uncertain about the results of the block consistency check. Can you provide insights on what this message means and if it is a cause for concern? This check was done on the latest version with all matching blocks copied to the PLC. Any advice on this issue would be appreciated. Thank you. "Bob"
Hi Bob, Your issue is indeed a common one for those transitioning from Rockwell to Siemens systems. While Siemens doesn't provide a direct way of aligning the offline and PLC data seamlessly, the key to resolving your problem lies in meticulous management and regular updates of your offline archives. As for your concern about block descriptors (labels in the name column), they are indeed not transferred to the PLC and only exist in the project file. Thus, it’s critical to maintain an updated offline project file, particularly for troubleshooting and future modifications. When it comes to overwriting the archive with newer blocks, this can be done, but as you mentioned, there's a risk of losing existing data and program references. Therefore, I would advise making a copy of the current archive before overwriting anything. This way, you always have a backup you can revert to in case something goes wrong. One more suggestion, consider using the "Compare and Merge" tool in SIMATIC Manager. It let's you compare the offline and online blocks, and then you choose which version you want to keep. And, as always, keep learning and don't hesitate to ask for help. Siemens' automation community has a wealth of knowledge to offer and are more than willing to assist. All the best with your new assignment!
Hi Bob, Your issue is indeed a tricky one, but not uncommon. For the discrepancies you're finding in the blocks, it seems like the PLC and the archives are being updated separately, causing the mismatch. In terms of preserving the labels, unfortunately, when you upload a DB from a PLC, the symbolic information isn't included. What could be happening is that the symbols and comments are getting lost during the transfer. As for overwriting the archives, you're correct to err on the side of caution. I'd advise against it unless you're sure of what the newer blocks contain and how they'll affect the overall program. I would suggest to use an approach that Siemens calls the "offline/online comparison." This will help identify the differences between the PLC and your offline archive. This method will automatically highlight discrepancies and should help maintain the integrity of your archive. About the descriptors in DBs, they usually reside only in the offline file. I hope that helps a bit. You might also find it worthwhile to check out some of Siemens' own resources or run this by their technical support. Siemens has previously done webinars and tutorials on maintaining and restoring from their S7 archives which could be really worthwhile to you in this case. Best of luck navigating through this! -John
Hi Bob, There's a lot to unpack in your inquiry, isn't there? I've walked your path with Siemens S7 before, so I can relate to the challenges. Regarding the discrepancies in the PLC and archived files, my approach was always to ensure regular updating of the offline files. Remember to set a schedule for this to happen to keep them aligned as much as possible. The issue with missing names in the DBs is a known limitation of the Siemens platform. When downloading to a PLC, the name descriptors are not transferred, only the address structures. This means that if you want to keep the descriptor names in your backed up files, there's no other solution but to manually document and perhaps add comments to your archived blocks. Overwriting the archived blocks without knowing the implication isn't the best approach, as you've pointed out. Always ensure that you fully understand the impact and interaction of blocks with each other and the overall program. Lastly, don't worry, the descriptor names won't be copied to the PLC; they remain in the offline file. Familiarize yourself with Siemens Software like TIA Portal, this might help you with issues like this. Siemens also has a great technical support team who can provide your guidance on best practices. Good luck on your new assignment, and keep us posted on your progress. Best, [YourName]
Hi Bob, it sounds like you’re dealing with a pretty complex situation! One thing to consider when managing S7 archives is the use of version control for your PLC programs, similar to what's done in software development. This way, you can better track changes and ensure that your archives are up-to-date without having to manually copy blocks. Regarding your issue with descriptors in DBs, they should indeed be part of the program, but sometimes it can depend on how you export/import your files. If you can, try to keep the naming conventions consistent and document any changes you make. It might also help to create a reference guide for future modifications. Good luck, and I hope you find a solution that works for you!
✅ Work Order Management
✅ Asset Tracking
✅ Preventive Maintenance
✅ Inspection Report
We have received your information. We will share Schedule Demo details on your Mail Id.
Answer: Answer: Common challenges include discrepancies between archive and PLC blocks, issues with copying descriptors or labels, and concerns about overwriting newer blocks without understanding the implications.
Answer: Answer: One approach is to manually copy mismatched blocks from the PLC to the offline file, but this may not fully preserve descriptors and alignment.
Answer: Answer: It seems descriptors or labels in the "Name" column of DBs may not transfer to the PLC when loaded, causing challenges in maintaining alignment and preserving descriptors in the archive.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.