• Not Answered

Upgrading DeltaV Operate Graphics from v12.3.1 to v15.LTS

Hello everyone,

I’m looking for a clear procedure to upgrade the DeltaV Operate graphics from V12.3.1 to V15.LTS without having to send the files to Emerson for processing.

I attempted to transfer the PIC file (from the Graphics-iFix file) to the new system and used the Picture Upgrade Utility on the main pictures. However, I encountered several issues, including distorted images and some graphics that displayed unusually or didn’t fit the screen even after checking the resolution and enabling the auto-scale option.

Has anyone successfully completed this upgrade? Any guidance or suggestions would be greatly appreciated.

Thank you in advance!

8 Replies

  • Doesn't look like anyone wants to touch this topic.

    The default conversion tool for Live is not adequate, as you found out. When I first used this tool, I found it created some visually functioning displays, but not what I would call sustainable displays. The Tool replaces existing Dynamos with defined GEMs. The GEMS are created in Live natively, so they are 100%functional, providing they are "compatible" with the Dynamo properties that are gathered from the Operate display (ie Module Tag, Function Block etc. ) If a GEM requires some additional properties to be defined, you'd have to "touch" each of these GEMs to complete their configuration. With the GEMS working, the Operator can select a tag, get the faceplate and make changes.

    The rest of the graphic that is not based on Dynamos (lines, arrows, vessels and other static objects) are converted from the iFix format to the Live format. Animations created with standard Operate animation tools have a corresponding mechanism in Live, such as visibility or color etc. However, anything custom is not converted. The usability of the display after conversion will depend greatly on the adherence to supported features.

    The conversion tool does not have a mapping of global items to Standards and Functions, certainly for these global items created in Operate that are not in the default FXG file. What happens is the tool creates new standards for colors and other items rather than find the Live version of the item. An Error message structure identifies conversion issues in the Description field of items to help identify what actions are needed to resolve. Take a line color. If hardcoded in Operate, it is hard coded in Live, but if a global variable defined the color, a Standard would be created in Live. Even if you had a defined color standard for such a line, the conversion tool does not know to use that. You end up with many extra items in your library.

    My display was actually functional after migration, with minor alignment issues. A line created with multiple segments in Operator is converted to the same number of segments, even though Live can link those ends or has connector objects. The result is you have to manually touch up the objects. Live has end of line treatments like arrows. The conversion will create the separate arrow and line from Operate. Technically it could look the same, but it is not making use of Live features.

    Some Items, like embedded Trends must be recreated. The Live Embedded Trend has some new features but is lacking the ability to make changes at runtime to the configured pens. Note that v15.FP2 improved the Legend significantly, but it also broke a couple features on the EU scales.

    Since then, Emerson has been working on improving the conversion tools, and to create a migration service that can bring down the cost of conversion. We are working toward a modernization program to help our customers take their Operate Graphics and HMI environment to a higher level of effectiveness, rather than a like for like conversion. Part of that process involves understanding the current behaviors of the HMI and Operator workflows. ON some initial projects, we were able to significantly reduce the total number of displays and reduce the amount of display navigation for Operators by elevating their L1 and especially L2 level displays. They came out of the upgrade with a better HMI.

    Bottom line, we have to move from iFix and VBA to gain the benefits of a modern HMI running on today's OS. Cybersecurity is ever increasing in importance, and VBA cannot take us to where cyber threats will push us. If the only thing you accomplish in migrating to Live is identical displays and navigation, there will only be pain and no reward. If you look at this as an opportunity to improve your HMI, there will still be pain, but there will be gain.

    So, I would urge you to develop a plan that is broader than must conversion. v12 was released circa 2013. Lots has changed in our understanding of Human Centered Design and HMI best practices. I bet there is room for improvement. I also recommend you don't attempt conversion in a vacuum and to seek assistance from your local support organization as they will be involved in many projects converting, migrating, modernizing Operate to Live. Their lessons learned and experience has to be valuable in making this a success.

    Good luck.

    Andre Dicaire

  • Are you upgrading to Live or are these issues during an Operate-to-Operate upgrade?
  • In reply to Andre Dicaire:

    Thank you so much for your time and your reply, Andre.
    I totally understand your point about the importance of adapting to newer technologies, but in our case, we are aiming for an operate-to-operate upgrade.
    We will not be using Live.
    Could you please provide me with an overview of what to do in this situation?
  • In reply to István Orbán:

    I'm in an operate to operate scenario
  • In reply to Gustavo Frank:

    Hi, since I didn't recall needing to convert anything in DeltaV Operate graphics since DeltaV v11.3, I checked on the DeltaV Upgrade Picture Expert (to which is what I believe you're referring) in the DeltaV Operate Picture Help (In Operate configure -> Help -> DeltaV Operate Picture Help).
    Search for 'upgrade expert' then select the article titled "DeltaV Upgrade Picture Expert".
    In that help article is a section describing what is NOT converted, with statements referring to objects that must have parameter references to "FIX32.THISNODE" and "THISNODE" manually converted to "DVSYS". Those references were used in DeltaV v7.2 and earlier (as I recall) and needed the conversion to DeltaV v 7.3 and later.
    The upgrade expert also helped to handle parameter references involving zones.

    Did you have any issues in using the displays after copying the v12.3.1 pic directory to the v15.LTS directory without the use of the upgrade expert? Did the displays look and work as before?
    I have not checked for KBA's on the upgrade from v12.3.1 to v15.LTS yet, which may provide specific directions on what is needed for Operate displays.

    J.D. Wheelis
  • In reply to JDWheelis:

    Hi there,
    Yes, that’s correct. I was referring to the "DeltaV Upgrade Picture Expert." I used it on all my pictures and Dynamos, but it didn’t work with some user-defined Dynamos, and I’m unsure how to convert them.

    Regarding your question about the display status, the issue arose after I switched to a higher-resolution and larger screen (from 19 to 24 inches) and applied auto-scaling. Some of the pictures adjusted well and were stretched nicely across the entire screen, while others did not—even though they were all created from the same template.

    Thank you in advance for your help!
  • In reply to Gustavo Frank:

    Hi, Gustavo,

    The DeltaV Upgrade Picture Expert was developed to convert parameter references from DeltaV Operate v7.2 and earlier (using a version of FIX32) to the references required by DeltaV Operate v7.3 and higher (using a version of iFix).

    I would guess that the issues you experienced have more to do with the change to the larger monitor and higher resolution of the monitor. I am not aware of any tool or expert that helps with the conversion of the graphic elements on a display originally sized for one resolution and aspect ratio to a display sized for a higher resolution and possibly different aspect ratio.

    When changing screen resolution, I always created a new display in the new resolution, then copied graphic elements from the original display to the new display.

    DeltaV Operate does a reasonable but not perfect job in auto-scaling most graphic elements on a display created for one resolution to be shown on a monitor of a different resolution. As you described, though, some graphic elements do not scale well.

    Perhaps someone with project experience in upgrading DeltaV systems and particularly in working on the Operate displays will be able to provide additional assistance.

    J.D Wheelis
  • In reply to JDWheelis:

    Hi Mr. Wheelis,

    Thanks so much for your reply—it was such a big help! I really appreciate you taking the time to share your insights.