AVEVA Plant SCADA Forum
A support forum for AVEVA Plant SCADA (formerly Citect SCADA). Share new and exciting product information, connect, learn, and collaborate with the ecosystem of Plant SCADA Users. AVEVA Plant SCADA a reliable, flexible and high-performance Supervisory Control and Data Acquisition software solution for industrial process customers. This forum is to connect, share, learn and collaborate new and exciting product information. Feel free to join and share to your Ecosystem of Plant SCADA Users.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2024-07-23 12:07 PM
Description:
Hello Support Team,
I am encountering an issue with our DCS system where we are losing tags in our SCADA system after making changes and uploading them to one of our PLCs. Here are the details of our setup and the issue:
System Configuration:
Issue Description:
Whenever I make changes to one of the PLCs (e.g., PLC1), and upload these changes to the PLC three times, we observe that some tags in the SCADA system corresponding to this PLC are lost. This issue is consistent and happens every time we follow this procedure.
Steps to Reproduce:
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2024-07-29 05:47 AM
It has been quite some time since I used Unity Pro to program the PLC, but I believe there should be an option to create the data dictionary on build of the PLC program, which also gets stored in the PLC memory. Here is the Schneider FAQ which outlines the steps:
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2024-07-24 09:27 PM
Hi @oualid,
Wow, you have some vintage product versions in production! Any reason why you haven't updated them to take advantage of latest bug fixes and enhancements?
What I can say is that this is a known issue. Basically OFS and the PLC are out of sync when you make changes to the PLC tag database. This was resolved in OFS by allowing it to pre-load the updated Data Dictionary from the PLC before starting the new scan and implementating the PLC changes.
See this forum post for the problem and recommended solution:
Basically upgrade to the latest OFS version 3.63 SP3, tick the options in OFS for "Using Data Dictionary" and "No Communications Break" to ensure there is no comms break between SCADA, OFS and the PLC. Of course if you modify a tag name in the PLC, you would also need to make the corresponding change to the Variable Tag Address to match.
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2024-07-26 03:10 PM
Hi @olivier_vallee,
I am no responsable for the updated the product versions and no one here to do that, I would like to do that.
about the OFS options "Using Data Dictionary" and "No Communications Break" are ticked.
I followed the forum post provided from you, I find only the preload on build changes in the PLC project settings \ embedded data settings is not ticked, is that what you meant, about allowing the OFS to pre-load the updated Data Dictionary from the PLC before starting the new scan?
Thank you about your quick response.
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2024-07-29 05:47 AM
It has been quite some time since I used Unity Pro to program the PLC, but I believe there should be an option to create the data dictionary on build of the PLC program, which also gets stored in the PLC memory. Here is the Schneider FAQ which outlines the steps:
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2024-12-13 01:42 PM
Hi @olivier_vallee, thank you for your time and advice. I resolved the issue by generating a new XVM symbol table file after adding the new tags to the PLC program and replacing the old file with. This allowed the OFS to reconnect with the PLC successfully.
Link copied. Please paste this link to share this article on your social media post.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2024-12-17 03:07 PM
Thanks for the feedback. Please know that newer versions of OFS are capable of reading the Data Dictionary stored in the PLC (after it is updated) and provide a seamless solution with no interruption to communications or manual exporting files. But I'm glad to hear you are happy with the solution you found.
Link copied. Please paste this link to share this article on your social media post.
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.