Can I configure DeltaV Operate Toolbar ?

I am trying to add a new button in DeltaV Operate toolbar for the toolbar. Is there a way to know which toolbar is the operate utilizing when we open a picture. 

Has anyone configured this before?

20 Replies

  • You can customize the toolbar or can create your own. To get the name of current toolbar i would suggest you can right click on the toolbar and use 'Quick Edit'. Once you are in config mode of the DeltaV Operate you can get the toolbar name from explorer objects.
  • In reply to girishbm1:

    Thank you so much that did help!
    quick question - Can I add a button to open a webpage from the toolbar? Also, how to write this in VB?
  • In reply to Summer:

    I don't know it will be safe, for testing you can try this 

    The Operator user must have Windows Administrator Access (go to User Manager to enable the access) for this coding.then only he can access this browser path.

    here the VBScript code
    frsRunTask ("C:\Program Files (x86)\Google\Chrome\Application\chrome https://www.google.com)

    if you want to use microsoft egde brower , select the path of microsoft esge browser in your directory and replace with
    frsRunTask ("path of microsoft esge browser https://www.google.com)

  • In reply to THENNARASU R:

    Thank you.
    I am trying to add a Syncade (MES) button on the DeltaV toolbar. When the user clicks on the MES icon from the toolbar, user is directed to open MES application through internet explorer. Do you think is this possible or the operator will need windows admin rights for this?
  • In reply to Summer:

    I have assisted a client to perform this exact feature. I would like to advise that because browsers open up the deltav workstation to a host of security risks, not to mention user interface challenges, that you employ a series of group policy settings to ensure this implementation is smooth and secure for the end user. The code to launch IE to the Syncade URL is easy. The other stuff is the real challenge. The details are to much to describe here.
  • In reply to Youssef.El-Bahtimy:

    The default toolbar has a button for Logbooks that does this. it is hidden until you define the URL in a predefined global variable. Logbooks Is a Syncade application.

    the button VBA code sets Explorer featuers so that the window and browser is locked to the URL and the user cannot change the path or modify the settings.

    in Operate Configure navigate in the toolbar picture until you see the various buttons in the button groups and find Logbooks button/bitmap and edit script. you could simply set the Logbook GS variable to you syncade URL and it will appear in the toolbar ready for use. then decide how you want to use this to create your new button.

    Andre Dicaire

  • In reply to Youssef.El-Bahtimy:

    Thank you.
  • In reply to Summer:

    My toolbar is set to read only is there a way to update the toolbar or create a new one and use it as a default toolbar that shows up on the operator screen?
  • In reply to Summer:

    The Out of Box toolbars are set to Read Only, as these are replaced and updated when you upgrade. To avoid having your work replaced with defaults, you simply make a copy of the OOB version to create your own.

    The actual toolbar used is determined by the User Settings File, or the Layout file if you have defined one. The Layout overrides the User Settings File. BOL discusses this. The User settings file can be saved to a Workstation name so you can customize the behavior of each workstation. Similarly, a Layout File can be defined for each workstation, based on the number of screens and the toolbar and alarm banner you want to use on each workstation.

    In the user settings file, there is existing code commented out and you simply remove the comment prefix and change the name of the Toolbar picture to be your new custom toolbar. If you have a layout file, change the name of the Toolbar picture to use your custom toolbar.

    There is a default User Settings file that is used if a workstation does not see a specific file for it. Make sure this file is updated so those stations without specific settings file or layout will use your toolbar.

    Andre Dicaire

  • In reply to Summer:

    The Out of Box toolbars are set to Read Only, as these are replaced and updated when you upgrade. To avoid having your work replaced with defaults, you simply make a copy of the OOB version to create your own.

    The actual toolbar used is determined by the User Settings File, or the Layout file if you have defined one. The Layout overrides the User Settings File. BOL discusses this. The User settings file can be saved to a Workstation name so you can customize the behavior of each workstation. Similarly, a Layout File can be defined for each workstation, based on the number of screens and the toolbar and alarm banner you want to use on each workstation.

    In the user settings file, there is existing code commented out and you simply remove the comment prefix and change the name of the Toolbar picture to be your new custom toolbar. If you have a layout file, change the name of the Toolbar picture to use your custom toolbar.

    There is a default User Settings file that is used if a workstation does not see a specific file for it. Make sure this file is updated so those stations without specific settings file or layout will use your toolbar.

    Andre Dicaire

  • In reply to Summer:

    The Out of Box toolbars are set to Read Only, as these are replaced and updated when you upgrade. To avoid having your work replaced with defaults, you simply make a copy of the OOB version to create your own.

    The actual toolbar used is determined by the User Settings File, or the Layout file if you have defined one. The Layout overrides the User Settings File. BOL discusses this. The User settings file can be saved to a Workstation name so you can customize the behavior of each workstation. Similarly, a Layout File can be defined for each workstation, based on the number of screens and the toolbar and alarm banner you want to use on each workstation.

    In the user settings file, there is existing code commented out and you simply remove the comment prefix and change the name of the Toolbar picture to be your new custom toolbar. If you have a layout file, change the name of the Toolbar picture to use your custom toolbar.

    There is a default User Settings file that is used if a workstation does not see a specific file for it. Make sure this file is updated so those stations without specific settings file or layout will use your toolbar.

    Andre Dicaire

  • In reply to THENNARASU R:

    I added the path something like this :

    frsRunTask ("C:\Program Files (x86)\Internet Explorer\iexplore.exe https://svr-mes-nlb")

    But it does nothing. I also tried defining it as a parameter

    Private Sub MES_Click()
    Dim dummy As Variant
    dummy = frsRunTask("C:\Progra~1\Intern~1\iexplore.exe", "http://svr-mes-nlb")
    End Sub


    Do you think is this correct or I am missing something?
  • In reply to Summer:

    This is simple but works for us....

    Private Sub CommandButton3_Click()
    ' open URL
    Dim lSuccess As Long
    lSuccess = ShellExecute(0, "Open", "http://mywebpage.html")
    End Sub
  • In reply to Summer:

    The code below is what we used.  Notice that invoking windows explorer then uses the user profile setting for which application opens URLs, so that if the browser changes, the code doesn't have to.  The default is Internet Explorer.

    Your observation of the unprivileged OS/DeltaV user not being able to open applications via script on the DeltaV Desktop is something I have also seen in recent versions of DeltaV, though I am looking at a 14.3.1 system now and my OS/DeltaV does not have administrator access and can launch the browser using this code.  Please note, they are also NOT configured as a 'Basic Operator' which is a significantly more restricted role than 'not an administrator'.

    Here are a few of the things you also need to consider with this HMI strategy, some are pre-requisite, some are things to think about. :

    1. Is you MES server SSL? Have you created, installed a certificate so that the DeltaV system trusts the secure site?

    2. Have you added the MES site as a trusted site for all OS users to the DeltaV HMIs?  You'll need to.

    3. Internet explorer will ask users whether they want to save their password when logging into MES, especially Syncade Workflow 4.9?  You won't want them to click yes on this prompt

    4. Browsers have tons of ways to access the file system and tons of nagging warning prompts  that DeltaV applications have either never had or have worked in some cases to reduce or eliminate over time.  These conveniences built into 'consumer software' like IE don't account for an operating and file system that should not be accessed by users.  You don't want users being able to open Developer Mode on IE, or to open new tabs that default to MSN.com regardless of the fact that they can't reach this site.  It just looks ugly and raises questions.

    Here is the code.

    Private Sub YOURBUTTON_Click()

    On Error GoTo ErrorHandler

    Dim strPath As String

    strPath = "YourURL"

    frsruntask "explorer", strPath

    Exit Sub

    ErrorHandler:

       frsHandleError

    End Sub

  • In reply to THENNARASU R:

    Thanks for your answer! would you like to explain what does the “frs”that from DeltaV VB script means? Thanks a lot !