PHV embedded chart in DV Live

I configured a sparkline and chart on a Live graphic, but if you change the screen and go back, you lose the history. It seems to only show history as long as the page has been opened. Is there a way to show all data?

• DeltaV

rhamlin

• 3 Jun 2025 3:13 PM
• Cancel

6 Replies

• Duane Harnish

  

  • 3 Jun 2025 3:54 PM

  Perhaps your sparkline & charts in DeltaV Live are only showing trends built from realtime data (after the display with the sparkline / chart is opened) and not showing any historical data (shown on the sparkline / chart to the left of "now" when the display is opened)?
  
  If you click on the PHV button in the chart, does the PHV Chart show historical data?

  • Cancel
• rhamlin

  

  • 3 Jun 2025 5:22 PM

  In reply to Duane Harnish:

  Yes, it works fine if I press the PHV button on the chart and pulls it up, but within the chart on the live graphic, it doesn't show historical data. I set the history server preference to be an app station that has the module in it's continuous historian, and the PHV chart that shows up is using the same history server.

  • Cancel
• Andre Dicaire

  

  • 3 Jun 2025 6:34 PM

  In reply to rhamlin:

  DeltaV Live uses an OPCHDA connection back to the DeltaV Continuous Historian.  Workstation Hardening and Microsoft OS changes to DCOMM were preventing the workstation from successfully connecting via DCOMM/OPCHDA to the historian.  Fix was to get the latest WS hotfix and Microsoft Patches installed so that all workstations and servers had the right OS level security and DeltaV WS had the correct settings for the Live OPCHDA connection.

  Since doing that, the Trends have been working, except from time to time, I find a workstation not refreshing history.  Again I find the DCOM errors in windows logs indicate an issue with the client connection.  This one I have not figured out, but I have observed that my VM's seem to change their Time and get out of sync with the host server.  I've apparently not set up my Time Server settings for HyperV VM's correctly and have seen nodes go out of sync.  If the client and server are too out of sync, there may be some authentication issues with DCOM, I'm not sure.  

  note that PHV still works for History as it does not use DCOM OPCHDA.  It uses an API call to the DVCH, as does DeltaV Reporter.  

  This is all related to the DCOMM OPCHDA for sure.  If not your level of OS patches, I suggest you log a call with GSC for any other reasons.  Check your Windows Log  System for a Error message with Event ID 10036 source DistributedCOM similar to:

  The server-side authentication level policy does not allow the user DV_DOMAIN\UserName SID (S-1-5-21-3xxxxxxxx8-4044618060-1168) from address 10.8.0.xx to activate DCOM server.

  Please raise the activation authentication level at least to RPC_C_AUTHN_LEVEL_PKT_INTEGRITY in client application.

  Today, I'm seeing a different DCOM Warning message today  Event ID 10016:

  The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
  {0DC1AB8B-A52D-4BA8-BD76-E2819386FB2F}
  and APPID
  {BDBED08B-7FB7-4EEA-AFD0-53DE534CB638}
  to the user NT SERVICE\ADDB Config Service SID (S-1-5-80-2656899328-802847255-2710573529-2758963984-2796279114) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

  Anyway, the issue is likely DCOM OPCHDA security settings.  The GSC should be able to set this right and identify the root cause.

  Andre Dicaire

  • Cancel
• Andre Dicaire

  

  • 3 Jun 2025 7:03 PM

  Embedded Trends, PHV and Sparklines start to collect runtime data once they are open and will retrieve History for the tags that have history in the referenced Historian, This allows the charts to show trends for both historized and non-historized tags. The non-historized trends build over time but disappear once the chart is refreshed or closed. What you are seeing is normal behavior for tags that do not have available History.
  
  There is no configuration option to force a trend to be only runtime or only history. If your history is not showing up, it is either an issue connecting the historian, or the data is not historized in the specified historian.
  
  Live Embedded Trends and Spark lines use a String Standard called S_HistoryServerPreference, which directs a trend to that server for history. If this standard is not correctly defined or points to the wrong server, History data will not be found. What happens if you have two history servers in your system? With PHV, you can point some consoles to use the server for their plant areas, setting the Default server list in PHV. For Live, you can leave the History Server undefined and let the Embedded trend find the history for the given tags. This is especially true for the Faceplate Trend object as it is a generic trend used for any tag. If targeted to the S_HistoryServerPreference standard, some tags would find their history there.
  
  You can define multiple HistoryServer standards and use them in Embedded Trends that are hard coded. These trends always need to use the specified server so it is slightly more efficient in making the connection. I'm not seeing any perceivable difference though.
  
  So it is possible that your loss of History in Embedded Trends is due to having used the S_HistoryServerPreference Standard and that it now is not properly defined. Or its DCOM and you'll see the DCOM errors in the Security Event log on the server.

  Andre Dicaire

  • Cancel
• rhamlin

  

  • 3 Jun 2025 7:03 PM

  In reply to Andre Dicaire:

  I looked at the event logger and didn't see any error message for Event ID 10036, but did see for 10016, although the message is from 5/21, not seeing anything today since configuring the chart.

  • Cancel
• rhamlin

  

  • 3 Jun 2025 7:11 PM

  In reply to Andre Dicaire:

  I didn't use a standard in history server preference. I just manually typed the name of the app station.

  • Cancel