Greetings all, I have developed a Recipe View that I intend to utilize across various presets, allowing me to modify, rename, delete, and add new recipes as needed. Initially, everything seems to be functioning properly as I input and save variables within the view. However, upon closing and reopening the simulation, all my changes are instantly erased, leaving me with a blank Recipe View screen. I attempted to use a data record to store my values, but unfortunately, the data record did not update with the changes I made. How can I ensure that my values are saved and retained, similar to the way retentive values are stored in my data blocks?
I am unable to locate the storage location of my recipes. When I attempt to add a new recipe, it does not appear in the data records. Additionally, modifying the values of existing recipes does not reflect in the data records.
If you're facing a similar issue, exporting and importing values to and from a csv file seems to be the only solution. Without a memory card to save these values, they may be lost during a re-initialization or factory reset.
If you're facing the same issue, exporting and importing values to and from a CSV file is the only solution. If you don't have a memory card to store these values, they will be lost during re-initialization or a factory reset. You may also consider exporting to a network drive as an alternative. However, keep in mind that re-imaging the panel will result in the deletion of all data stored in the internal flash memory. It is crucial to have a backup storage option such as a memory card or USB drive to prevent data loss in such scenarios.
The user mk42 mentioned that you can save data to a memory card, USB, or possibly a network drive. However, if the panel gets reimaged, all internal flash data is erased. Is this a common issue? How do engineers typically address this vulnerability? Perhaps creating an export-import button could help save recipes to a PC or external storage for added security and convenience.
When it comes to handling recipe data in HMIs, engineers may opt to leave them vulnerable like that. However, it is common practice to have a memory card in an HMI, especially a Comfort Panel from Siemens, for automatic backup. By using the Siemens memory card in the automatic backup slot, both the program and recipe data can be backed up. Alternatively, using a data slot allows easy access to the data. This data slot doesn't require a Siemens memory card, so cost concerns can be minimized. Therefore, the issue isn't about leaving data vulnerable in the panel, but rather choosing not to store them in non-volatile memory for added security.
Hey there, it sounds like you're dealing with a persistent storage problem. You mentioned attempting to use a data record, which was on the right track. Now, you might want to confirm that your simulation environment supports persistent data storage, as the limitations could be there. If it does, you would need to find where the application settings are being stored and ensure they are correctly updating. If not, you might want to consider using an alternative storage method like a database or flat file which can survive application termination. Hope this helps and good luck solving your issue!
Hey there! It sounds like you've done some solid work already but are running into data persistence issues. One thing that springs to mind is that this could be an issue with how your simulation software is set up - some simulation tools automatically reset everything upon reopening, as part of their default settings. This feature helps in some scenarios but is not ideal for your case. Unfortunately, it's difficult to offer a specific solution without knowing the exact software you're using. However, I'd look for a 'saving state' or 'keep persistent data' option in your software settings/preferences. Also, are you sure your data records are correctly tied to your variables? That could also be a potential problem area. Full-proof method, I suggest you consider using a local or cloud database to store your recipes. That way, even if your simulation restarts, the data saves independently.
Sounds like a frustrating issue! From what you've described, it looks like you're missing a persistence layer that can store your data across sessions. If you're using a database, make sure your changes are being committed correctly - potentially your variables are being held in a temporary cache and not actually saved. If you're using a data record, double check the configuration settings to ensure it's set to update. Alternatively, you might want to consider structuring your program to automatically save changes upon exit. I hope this helps, and you're able to get your Recipe View functioning as desired soon!
✅ 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: 1. How can I save and retain recipe data in TIA Portal Recipe View? - To save and retain recipe data in TIA Portal Recipe View, you can utilize retentive memory areas in your program to store the values. This will ensure that the data is not lost when the simulation is closed and reopened.
Answer: - The changes in the Recipe View are getting erased because the data is not being saved in a retentive memory area. Make sure to store the values in a way that they are retained even after the simulation is restarted.
Answer: - If the data record is not updating with the changes made in the Recipe View, check if the data record is correctly linked to the Recipe View and if it is configured to update and store values properly. Ensure that the data record is set up to work with the Recipe View functionalities.
Join hundreds of satisfied customers who have transformed their maintenance processes.
Sign up today and start optimizing your workflow.