PHV Default Trends

Hello All,

We have one requirement in some of the operator workstations, the operator wants to see some default trends in PHV without opening one by one when there is an operator change/logged into a different account. For an example, when they press PHV, they want to see some group of default trends automatically without opening one by one. Have you ever implemented this type of settings/program in DeltaV system, if you have any information, suggestions, please let me know? Thanks in advance.

Regards,

Venkatesh G

  • Venkatesh,

    You can always create / add a button on the tool bar (or as a part of a graphic) that will call up a specific PHV. You could even setup to call up several PHVs and place in a certain arrangement on a specific monitor (just get the vb code correct). I commonly had a button on graphics for major vessels that called up a single PHV trend preconfigured for that process equipment.

    Another thing I've done in the past when operators wanted a certain set of trends up all the time and were not normally wanting to adjust time ranges or scales, was to embed ActiveX trends into a graphic. The ActiveX trend isn't as flexible as a PHV trend, but ensured the trend always defaulted to the correct pens, y-scale, and time range. It was easy to set the size and location of each trend on the graphic. It also allowed the operators to switch which monitor the view the trends on without having to move or resize windows.
  • If you are using v12, the EmbeddedTrendCntrl allows you to create a display with preset trends. This could be setup as a Pop Up display or a main display. You can also add these to existing displays to view history in context to a process graphic, as Michael indicates.

    If you have v13, the EmbeddedTrendCntrol was enhanced with commands that allow you to dynamically set the tags. This allows you to reprogram a Trend to show whatever tags you wish. The commands are documented in BOL. You can create a display with 6 or 8 embedded Trends, with preconfigured trends, or provide a means to configure these at run time. I replaced the CHART Builder with an AdHoc Trend display. I modified the right click event on my dynamos to call up this Embedded Trend picture and assign the PV, SP and OUT values (as appropriate) to the Trend. Using the Command Line Interface (CLI), I provide a button for the user to open the Adhoc tags in PHV with an ECHART, which gives them the Alarms and Events for the tags and time span of the Chart. In PHV, they can use the time management functions much more easily that the Embedded Trend fight click Menu. I'm working to add a Save Button that would save the tags into a list that would allow a user to recall a set of tags from a list. The user would then be able to scroll through various collections of tags in a single trend window. Another application would be to have a set of tags defined in every display, and when a display is called up in Main1 or Main2, those tags are updated in the Trend Display, allowing the Trend Display to update content based on the selected L2 or L3 display. Not sure about this, but it's possible.

    My current project is to replace the iFIX Chart object in the Trend Displays with the Embedded Trend. In fact, using the Embedded Trend can allow me to create one single Trend display that works for all modules. This is not possible in v12 because the tag substitution mechanism cannot reprogram the module wildcard. In v13, the trend display can check to module's IDISP parameter and set the trend tags dynamically. One display to manage.

    I am not aware of any mechanism in PHV that allows you to define a layout of trends that you can call up. The Embedded Trend object allows you to build a display that will always show the same trends in the same locations. You can build multiple displays as well. PHV adds the ability to view Alarm and Event Data with a trend, or work with an event view to investigate discrete events.

    Andre Dicaire

  • In reply to Michael Moody:

    Micheal,
    Thanks for the valuable Idea, yesterday I have implemented the script(Button) for the call up a sepcific PHV Trends as you said, It's absolutly working fine.

    But I have never implemented the ActiveX trends, so I'll try to impliment ActiveX trends this week and will leave the choice to operators between both(ActiveX and PHV)
  • In reply to Andre Dicaire:

    Andre,
    Thanks for your information, it's so useful for my learning purpose. We are using V11, already you said that those most of the features for V12 and V13, so i'm not going to involve so much in those changes but next year we are going to upgrade our system from V11 to V13 and will try to impliment most of the things mentioned by you, but I need to brushup my skills by that time. Thanks.

    Venkatesh G