Join our "Ask Me About" community webinar on May 20th at 9 AM CET and 5 PM CET to explore cybersecurity and monitoring for Data Center and edge IT. Learn about market trends, cutting-edge technologies, and best practices from industry experts. Register and secure your Critical IT infrastructure
Broken io Variables Vijeo Designer
Modicon PAC Forum
A forum for topics related to the scope of Modicon PAC offers and ecosystem along the whole lifecycle: Modicon M580 and 340, EcoStruxure Control Expert, EcoStruxure Process Expert (Unity Pro) and more.
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send InviteCancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Link copied. Please paste this link to share this article on your social media post.
Posted: 2022-09-2705:28 AM. Last Modified: 2022-09-2705:31 AM
Broken io Variables Vijeo Designer
Hi, I am currently working with a Modicon m221 PLC (machine expert v.1.2 SP1 software) and a HMIGTO6310/6315 HMI (Vijeo Designer v.6.2 Software) The old programs were written in prior versions of Vijeo Designer and worked like a charm, after opening an old program in v6.2 it prompted an update to the file and this update seemed to break the communication with the PLC direct IO's.
All variable addresses that are memory allocated, %m, %mw, etc... all work fine. The HMI can read all these variables still but any direct address to IO cards %i, %Q, etc.. All show as a faded value. If I create redundant memory addresses for each io and store the values in memory the HMI can acknowledge the values.
This fix would be sufficient but the program has over 80+ Variables that would need to be rewritten and any old code that needs updated would all need new variables.
I have attempted to import the variables back into the HMI program but that did not solve the Issue. The variables don't show a non connection error, they are just dotted and faded out.