• Not Answered

DeltaV Live V16 Stale graphics

Hi All,

I am experiencing an issue where it appears that Live occasionally opens with "stale" graphics. I have a display that has had some object removed (and their associated control modules deleted) which is published, but when I open Live it will show the old graphic with the objects showing magenta because the control module do not exist anymore. I have to do a manual refresh to bring the latest graphic up. 

Has anyone else experienced this?

Thanks  

3 Replies

  • Yes, I've been seeing this behavior since v15FP2. To confirm, you are seeing items in the initial displays that are highlighted in pink, as if a referenced standard is missing. It appears that Live is loading a previous version of the HTML display in which modified items are no longer complete (missing a standard or Function or subGem). On refresh, the current display is loaded and complete.

    The work around is to refresh the Live. At first I only saw this impact the initial displays. In v15FP3, I also see this on some Faceplate displays. A second refresh after opening an affected display clears that up. The affected FP displays were tied to GEMs on the initial display that were exhibiting this behavior. I'm not seeing any such issues on any non-initial displays.

    I've opened a call with the GSC on v15FP3. I advise you to do the same for v16.

    One test I am trying to complete is to see if the issue exists on a new workstation added to the system. Will it receive the "Previous version" with the issues or will it start with the new version and not show the issue. But I expect that subsequent modification would cause the issue to return on that station. This would indicate the issue is on the workstations if it initially does not occur. If it is there right away, the Server is publishing the issue.

    One thought I'm having as I write this is to change the Display set or Layout such that you call up a different Initial display and see if the issue occurs. Or create a copy of the initial displays, and then modify the Display set to use the new copy. Then delete the old display. I'm going to try this to see if this breaks the link to the old display.

    Please log a call to ensure this is on the radar for v16.

    Andre Dicaire

  • In reply to Andre Dicaire:

    So, I copied my Alarm Banner with the intent of changing my Layouts to use this copy. I opened this display, then closed it. Copied it. I changed two of my Layouts, but did not save or publish them. I opened Live and my "problems" were cleared. Hmmm. I proceeded with the change, saved my new display, updated my layouts, published and relaunched my VMs and started LIVE. My issues are no longer occurring.

    What that tells me, maybe, is the affected initial displays either need to be "tickled", or you can copy them, change your layout refences and force Live to launch with new displays. If you layout is linked via location in Hierarchy, then I would update the Hierarchy(s) to use the new copies. In this scenario, the workstations will have only ever received one copy of the new display which is a correct version, and would work. However, if you proceed to modify the display, this might cause the issue to return. Or not. Don't know as the underlying reason for this behavior is not known. But I don't see the behavior anymore.

    I was also seeing issues on some faceplates. This is no longer the case. Even though I did not touch the affected Contextual displays in Graphic Studio, they are now opening on all workstations without issue.

    If you decide to try this, check if the issue is resolved simply by changing the configuration but not publishing. This would be an interesting detail that might help Emerson identify the source of the issue. Then go ahead and publish your new displays and confirm all is working. Report this in your GSC call.

    Hope you see positive results.

    Andre Dicaire

  • You can check if there are any missing or invalid animations on your display when the red heart at the top left corner is red. Check those datalinks if those paths are valid.