Recent Services Discussions
Similar Posts
Roots of PLCs and DCSs
The Root Causes of Slow Oscillations Tips
Active Directory
Backup and Recovery: Disk imaging, Domain Controllers, Active Directory and USN Rollback
Getting up and Running Quickly
Share
  • Not Answered

DeltaV Live Get DVDATA Root Directory

Hi All,

TLDR:

Does any one know how to find the DVDATA Root Directory within DeltaV Live/Typescript?

Summary of Problem:

Customer requirement is to allow for selection of different PHV charts for a given module.

For this Im currently usign ENV.RunAsnyc function to open CHS.exe for the specified PHV file which is working.

Unfortunetly as DVDATA/CHARTS/LIB may be installed on different drives I cant guarante the logic will always work across all stations. i.e C:/DVDATA or D:/DVADAT

From my reading HTML5 WEB API, does'nt have an real file system interface as I cant simply check if the file exists at either path when usign typescript.

In DeltaV Operate where DVDATA  is located can be extracted from the VB variable "System.PicturePath", which is configured via DeltaV Operate System Configuration Utility.

Is there an equivalent/similar "System.PicturePath" for DeltaV Live which I could use to extract the folder location of  the DVDATA folder.

Besides configurign a %DVDATA% environmental variable on all workstatiions does any body have an approach for providing the above requirement in DeltaV Live?

 

Cheers

Frank

Frank Kelly

2 Replies

  • Andre Dicaire
    The CHS Command line interface opens files in the DVDATA\CHARTS folder, regardless of where the folder is installed.

    Running the CLI in Command window: CHS MyCHART.PHVE This works without specifying a Drive location

    BOL shows the syntax: CHS lib\myChart.phvc.

    You can create your own subdirectories to organize the charts, and use the "\" back slash to define their location under the DVDATA\HARTS folder.

    i.e. chs MyCharts\Chart1

    This opens the chart located in Deltav\DVData\Charts\myCharts path, with the drive letter (install location) known to CHS.exe.

    Live provides some display functions to manage opening PHV, as well as faceplate and detail display pop ups because these functions automatically determine the correct file or display associated with the module. In the case of PHV, the chart file must be created with the same name as the module's Faceplate display. The interaction also uses the /SUB argument to substitute the Module name into the wild card placeholder "@MOD@"

    You can also create your own generic trends using this wildcard, and create your own logic around which file to call, and can place your files in their own "library" folder. Review BOL for all the arguments and their syntax under "Customizing the Process History View" section.

    For example, Say you create a PHV file for use with a PIDblock in a module, your Trend ICON could pass the command to open your PID.PHVE file created with paths to "@MOD@/PID1/PV.CV" etc and use /Sub to use your module name. Instead of having a PHV File for every Faceplate name, You would have one for every module that is based on a PID block. Or an AI block or ALM block. Hmm three files instead of dozens? And when you create a new Faceplate based on PID, it automatically has a working PHV file without having to create it. Which we all tend to forget until the Operator tells us the Chart doesn't work...

    Please confirm if you are still having an issue with finding the customer charts on C:\ vs D:\ drive installs.

    Andre Dicaire

  • Frank Kelly

    In reply to Andre Dicaire:

    Andre Dicaire (ADicaire)

    Just tested this and would like to confirm you are a legend as it worked exactly as you described.

    My own intial try failed as my charts were in "DeltaV\DVData\Charts\lib", so to remedy myfirst try I just needed to prefix my file name with "\lib" for the CHS Command to work with out specfifying the full diretory path. (i.e CHS "\lib\mychart.PHVE")

    Everything else was good.

    I even previously read (Obviously too fast) BOL "Customizing the Process History View/CLI for the Process History View" and missed this clear statement below which confirms what you wrote.

    Thanks a million for you help on this, I completely went down the wrong rabbit hole on this one.

This is the official online community site of the Emerson Global Users Exchange, a forum for the free exchange of non-proprietary information among the global user community of all Emerson Automation Solution's products and services. Our goal is to improve the efficiency and use of automation systems and solutions employed at members’ facilities by sharing our knowledge, experiences, and application information.

User Groups | World Areas | Community Guidelines | Legal Information | Privacy Policy | Contact Community Manager

Website translation provided by Website Translator

© 2015-2022 Emerson Global Users Exchange. All rights reserved.