Hi,
I'm programming a Magelis HMISTO screen for the first time with Vijeo Designer and I've come across a rather unusual text display issue.
I have two text resources defined in Vijeo Designer: one for indicating ON/OFF and the other indicating FAULT/HEALTHY. I recently did a download to the HMI while preserving runtime data and it's caused some (not all) of my message displays to switch text resources. In other words, some message displays which were correctly displaying ON/OFF are now displaying FAULT/HEALTHY for some reason. Everything else works correctly.
This issue does not happen this on the HMI simulator in Vijeo Designer, only on the actual HMI hardware that I am using to test my program. I did a full download with runtime data cleared and it hasn't fixed this issue. Just wondering if this has happened to anyone else before...
EDIT: So I downloaded a new Service Pack for Vijeo Designer and updated the entire runtime environment on the HMI and it seems to have solved the issue. I'm still curious as to what could've caused it in the first place...
I'm programming a Magelis HMISTO screen for the first time with Vijeo Designer and I've come across a rather unusual text display issue.
I have two text resources defined in Vijeo Designer: one for indicating ON/OFF and the other indicating FAULT/HEALTHY. I recently did a download to the HMI while preserving runtime data and it's caused some (not all) of my message displays to switch text resources. In other words, some message displays which were correctly displaying ON/OFF are now displaying FAULT/HEALTHY for some reason. Everything else works correctly.
This issue does not happen this on the HMI simulator in Vijeo Designer, only on the actual HMI hardware that I am using to test my program. I did a full download with runtime data cleared and it hasn't fixed this issue. Just wondering if this has happened to anyone else before...
EDIT: So I downloaded a new Service Pack for Vijeo Designer and updated the entire runtime environment on the HMI and it seems to have solved the issue. I'm still curious as to what could've caused it in the first place...
Last edited: