• Not Answered

Opening multiple pages on process history view

We are having an issue opening multiple charts of different trends on PHV, we can open the first PHV with no issue via faceplate but if we want to open a trend for a different module, I get the following error message

 

• DeltaV #DCS
• faceplate
• processhistoryview
• DeltaVLive

Kowther Hussein

• 31 Mar 2026 12:21 AM
• Cancel

3 Replies

• Andre Dicaire

  

  • 31 Mar 2026 2:05 PM

  Your faceplate name is different and there must be a matching PHVE file created by the same name. For a faceplate that works, locate the file by the same name in the /LIB/ folder in PHV. Copy this file and rename it to match the name of the faceplate. The Faceplate PHV Button uses the IDISP name of the module to 'find' the correct PHVE file.

  Andre Dicaire

  • Cancel
• Andre Dicaire

  

  • 31 Mar 2026 2:18 PM

  In reply to Andre Dicaire:

  PHV has been structured this way for ever. If the file doesn't exist, it doesn't work. The reason for this, I suspect, is that to align the Pen colors to the standard HMI colors for PV, SP and OUT, a file is created and the pens are edited to match. The adhoc PHV CHART applies a different default pen color for each pen. The downside is you must create a PHVE file for each uniquely named faceplate.
  
  A different approach might be to create a PID.PHVE file in the library, along with an AI.PHVE, ALM.PHVE etc and alter the script in the PHV Button to use the main Function block to open the file matching the Block. The script would discern the primary block of the Faceplate and open PID.PHVE for all PID based Faceplates. Now you have one set of PHV files and when creating a new FB, simply setting a variable or context variable in the faceplate directs it to an existing file.
  
  I haven't tried this with PHV as I created my own Trend pop up contextual display using the Embedded Trend and table object in Live. But the premise is the same. I have a popup for PID, AI and ALM etc and I call the correct pop up based on the faceplates main FB. I added an Adhoc Trend button to move to PHV if the operator needs additional PHV features. In Live, the default PV, SP and OUT colors are now changed so all those existing PHVE files no longer follow the HMI color scheme for the trends. Decided not to care and bypass these files. They still exist and work with the default PHV button. Can't change too much at one time.
  
  My Trend pop up has limitations because the Live Trend object does not expose its start/end time or Cursor time, and one cannot fully define a new pen at runtime. Operate Trend object provided runtime methods. I submitted an enhancement request you could review and if you agree, vote it up. You never know what might happen.

  Andre Dicaire

  • Cancel
• Jason Jordan

  

  • 31 Mar 2026 6:55 PM

  In reply to Andre Dicaire:

  Thank you for your insight and help on this.

  • Cancel