Issues after succesfully installing a new Operator Station

Hello,

Recently we installed a new Operator Station (OS) and connected it to the DeltaV network. It was a physical replacement of another OS. We removed the old OS from the DeltaV network and deleted it in the hierarchy.

We got it up and running, however, similar alarms on another OS appear different in color on the new machine. The alarms on the newly installed OS is depicts a 'lower' priority color, e.g. vital alarms appear red instead of purple.

I tried to check out the manual and followed standard procedures. No avail.

Another issue is that on the new OS we read out absurd values for the PVs on numerous of control modules. Values consisting of alot of numbers which make no sense.

Did someone experienced a similar problem or am I missing out here during the config?

4 Replies

  • You stated that you deleted the old workstation. Does the new one have the same computer name or did you create a new name? The old computer may have had a User Settings file defined that provided modification of alarm colors and such. This file should still exist on the pro plus and you can simply rename it to apply to the new workstation.

    After changing the file name, redownload the workstation to force an update.

    Can you provide an example of what you call "absurd values"? Are these happening in display dynamos, faceplate displays? Do you see the correct value in control Studio on line? Do you have regional settings on this new computer that are different than those that work. Some country and language settings use different separators than the decimal point and this could affect how a value is being handled in scripts. You'll need to align these settings.

    Suggest you read an Absurd value with control Studio on line, Watchit, a "good" workstation and your new one. how does the value appear on all four. That would help us understand what you are seeing.

    Andre Dicaire

  • In reply to Andre Dicaire:

    Hi Andre.
    Thanks for your reply.

    I followed some of the things you suggested.
    Regarding the naming of the OS, I created a new name, 'OS3' instead of 'OS1' to prevent commissioning issues. I copied and renamed the User Settings file, restarted the OS and fired DeltaV Operate Run. Nothing is changed. Alarm colors are still different from the 'good' workstation.
    DeltaV Explorer did not gave an indicator to download the workstation, so I avoided re-downloading the OS because we are running live.

    The absurd values are displayed in the faceplates. It is not possible to enter Control Studio live on the OS because of the license. On the Pro+ the values are displayed correctly, both on the Faceplate and Control Studio live mode. The regional settings are aligned.

    Please check out the pictures I have uploaded:
    http://imgur.com/a/A6Ma2
    It seems that the decimals are 5 digits out of place.
    It indicated a temperature (R1220-TCV-002) of 824288.0 instead of 82.43, as shown in the background.

    What can I try to do next?

    Edit:It is worth to mention that the accounts in the Flexlock dropdown list is the similar with the other station. The only hassle is that the password do not work on the new station.

    Also, only one Windows account is configured. It is the default administrator account.

  • In reply to Jeison:

    Jeison

    Andre is quite correct in mentioning the yellow pages. I do not understand your comment about not downloading the workstation as it is live.

    1. Declare the workstation as Out of service to give yourself time to deal with the issue.
    2. OK so you have defined a new workstation in your database called OS3. Did you delete the old workstation and reallociate the licenses to the new workstation within DeltaV exploroer.
    3. Avoid opening any graphic until yellow pages have sucessfully replicated to the new (it is new as the old workstation has been removed)
    4. Rename the workstation OS7 and keep it off the network until you are ready for it to rejoin the domain.
    5. When all activities have been completed create the new placeholder (OS7) in the deltav database including liciences then proceed.
    6. Download the proplus setup data.
    7. Remove any stale AD records in the domain controller.
    8. Assuming you have done this export the network configuration and rerun the workstation config on the target op station. This will rejoin it to the domain. This is assuming you are using a domain and not a workgroup.
    9. Check yellow pages status and avoid opening the graphics until this process is complete.

    I would recommend getting Emerson GSC involved in this as they can walk you though the entire process.
  • In reply to Steve Linehan:

    Alright, this seems like a bigger issue than previously expected.
    Thanks for the reply. Iwill try to fix this in a upcoming maintenance stop for our DCS.