DeltaV 12.3.1 PHV takes 20seconds to open

Am experiencing Sluggish response (20 seconds) when i try to open PHV on workstations other than PROPLUS, I have tried workstation configuration,loaded WS-015 hotfix,reduced even chronicle active dataset to 100mb. Is there anything else i can do?

  • You can try the following on one of the stations and see if PHV opens faster.
    1. Download station from PRO+.
    2. Disable unused and non-DeltaV network cards.
    3. Correct NIC binding order.
    4. Restart station.
    5. Rerun workstation configuration using a fresh DevData.cfg from PRO+.

    In my experience this issue is usually caused by security issue, network issue, workstation setting issue, slow Historian or Event Chronicle servers, or PHV is pointing to an incorrect or non-existing data source.

    Hope this helps.

    Regards,
    Neil Castro
  • In reply to Neil Castro:

    Make sure that you have reverse lookup zones configured under DNS for both the primary and secondary networks. There's a KBA for this (I don't know the number). This was the problem for us in the past.
  • In reply to TPatterson:

    This is not a domain environment , its a workgroup. I ahve tried all those above suggestions. I even created a new workstation with the spare machine and connected to the network and tried to open PHV from new machine, and found that it still taking 20 to 30 secs to open PHV.
  • Hi,

    Have you determined if it is the trending data portion of PHV or the Events portion of PHV? The way you figure this out is: Open PHV from the toolbar and select Trend only. Next, attempt to trend the same point that you would as if you opened a faceplate trend. If PHV responds in a normal fashion, then the issue is related to querying events. If not, then it is related to querying trend data.
  • I suggest you call the GSC if you want to resolve this more quickly. Each of us on this thread will offer suggestions that could waste your time. There may be information you are not sharing that a structured diagnostic approach will help uncover and reveal the source of the issue. That said, I always like mysteries....

    The first thing we should do is understand your installation, and what type of PHV files you are experiencing this on.

    I'm assuming the Event Chronicle is on the Pro Plus. (Confirm)
    What server is providing the Continuous Historian Data. (is it the pro plus, or an App Station, or just runtime data on each workstation)
    Are you seeing delay if you call up a CHART only file (no events)?
    Are you seeing delay if you call up an Event only file? (try a 5 minute file, 30 minute and 60 minutes. Do they all take 20 seconds?)

    This information will help us determine if the issue is only with the Event data, and therefore between the Pro Plus and the workstations. It will also tell us that the Historian App Station (if it exists) is working as expected. That too would be useful.

    If the issue is only with event data, I would suspect one of two things: NIC Binding order on workstations, Event Chronicle database has extremely high data density. (focus on one workstation and once that is solved, apply to the rest)

    For the NIC binding order, document the Pro Plus, a Workstation and the App Station, and compare. You can also simplify this problem by disabling extra NIC's , leaving only the Primary and Secondary DeltaV NICs enabled. If everything works fine with only the Secondary and Primary DeltaV NIC's enabled, we now where the issue is.

    Divide the problem to find the source, and simplify the problem by eliminating components. If you find things work with only two NICs on the enabled, that confirms the issue is network binding order well worth the test. Each action you take should be done with the goal of either confirming an issue or eliminating a possibility. If the result is not A or B, but something else, rethink the problem.

    Good luck.

    Andre Dicaire

  • Hi,

    Some months ago I had the same issue and the solution was to modify the "host" file, which is located at "C:\Windows\System32\drivers\etc"

    What you have to do is:

    1.- Edit the host file with the explicit IP Address and the Host Name of your App Station or OS Station from whcih you read the historical records.
    2.- In the Process History View you need to use the Host Name instead of the explicit IP Address.

    Host file Example:

    # localhost name resolution is handled within DNS itself.
    # 127.0.0.1 localhost
    # ::1 localhost
    #
    10.4.0.52 App_Stat
    10.4.0.76 OS_Station1

    I suggest to do this in all the computers that have to get connection to historical database.

    I hope this help with your issue.

    Regards,
    Marcos Moreno
  • In reply to Marcos Moreno:

    We modified the Host file as well to contain primary and secondary IP's (10.4... & 10.8...) of our Pro+ (events) and App Station (Historian). PHV worked fine after.

    Host file Example:

    # localhost name resolution is handled within DNS itself.
    # 127.0.0.1 localhost
    # ::1 localhost
    #
    10.4.0.## App_Stat
    10.8.0.## App Stat
    10.4.0.## Pro+
    10.8.0.## Pro+


    Good Luck
  • In reply to Leon Gonzales:

    For some reason hosts file is missing (in all the machines) from the directory and i have created one hosts file in one of the workstations and it seems to be working fine and also i found that every time i reboot the system the files gets deleted by itself, so after entering explicit IP of App station n Pro Plus i made the hosts file read only.Since then it is not deleting and the issue has been resolved.
    Now i have one question is it safe to create this file? hope it is not going to tamper DeltaV operations?

    Thank you ,Leon Gonzales
  • In reply to bobgally:

    Hi,

    It is perfectly safe to create the file, it only helps Windows in the task of "name resolution", in order to find the proper IP address route quickly.
    I have seen some computers wheres Host File was missing and I simply copied one from another computer, then customizing it and that's it.

    Now you can say: Consider it solved !!!