Emerson Exchange 365

Process History View, Set Y Scale grayed out

In process history view, I have no ability to change the y scale as follows... Right click on Parameter Reference and Set Y Scale... All the options there for  EU Limits, Auto Scale and Manual are grayed out. This is only happening on one user however, i have compared to other plants we have and those users are setup with the same privileges in User Manager as this one with the problem is, so i'm not sure if there is a different place that is giving me problems. 

Thanks

TreyB

• 9 Jul 2024 2:02 PM
• Cancel

7 Replies

• Andre Dicaire

  

  • 9 Jul 2024 2:39 PM

  There are lots of things going on in charts depending on whether its a custom chart or a Faceplate CHART. and whether user has windows save privileges to the CHART directory and DeltaV Privileges. Also, pens 6, 7 and 8 share the same EU range settings. (Not sure if pens 7 and 8 are editable and you have to edit pen 6).
  
  What type of CHART are you trying to modify? The Faceplate linked CHARTs may not allow instance modification since they are expected to dynamically call up the module scaling data, and remain flexible to use what ever range in the module at call up.
  
  What else are you not able to do with the user and workstation that you can with other users?

  Andre Dicaire

  • Cancel
• jgrunschel

  

  • 9 Jul 2024 3:11 PM

  I don't know what causes it, but it sometimes happens after windows updates. Anyway, the "Control Level" gets set to "Standard", causing a lot of things to become "grayed out". Opening Process History View and selecting the menu item at "View" -> "Control Level" -> "Advanced" will reenable everything. In my experience, doing this once on each offending machine will resolve it until it "randomly" happens again later.

  • Cancel
• TreyB

  

  • 9 Jul 2024 3:40 PM

  In reply to Andre Dicaire:

  The chart is a faceplate chart, it is fully editable with the other user and with the same user privileges at other plants. Something at this site is the issue. I don't have any other unexpected issues. The following is what keys i have given to this user..
  Alarms
  Can Calibrate
  Can Configure
  Can Download
  Control
  Diagnostic
  Restricted Control
  System Records
  Tuning.
  
  It's the same as the other site, so i don't think that is an issue.
  
  The difference between sites:
  Working user is a workgroup user and non-working is a domain user.
  
  I am logging on remotely with a terminal session using the same user for windows login and deltav login.
  All areas are assigned for the terminal session for alarms and events. Setup data certainly has been downloaded.
  
  The non working user is logging in with Operator Station, Full Span of Control. The working user is logging in with Professional Station, Full Span of Control.
  I've switched to using Operator and it still works.
  
  I'm switching to different Windows login.. This seems to be the issue.
  
  Domain site: Works using domain user with local windows administrator role. However, it is not a local machine account.
  Does not work with domain user that does not have local admin role. Also not a local machine account.
  Workgroup site: Works with either account regardless of keys. Both are local machine accounts.
  
  So, i'm not sure how i can go about resolving this. I don't want to enable local windows admin for all users.. but that is the only difference i see. It's hard to compare since it's not apples to apples with the domain vs workgroup. Can I add the domain account as a local user account outside of User Manager? Otherwise, I feel i'd have to change in User manager so the account is local, but it's supposed to be a domain account.. don't like that option.

  • Cancel
• TreyB

  

  • 9 Jul 2024 3:45 PM

  In reply to jgrunschel:

  That is it!! Thanks. I swear i went through every menu item. I guess not.

  • Cancel
• Andre Dicaire

  

  • 9 Jul 2024 4:43 PM

  In reply to TreyB:

  That is interesting. I always forget about the "Advanced" settings in PHV. DeltaV does treat local admin accounts with special privileges that can override things that normally require explicit settings. Looks like this is the case here. It explains why it worked with local users. Or the setting was enabled previously for the local user and needed to be enabled for the domain user. I'll have to look on my system if this is repeatable, i.e. can be granted and taken way with domain users who are not Admin and whether local admin gets this by default.
  
  This seems to be a user related setting that is preserved by PHV, related to the windows user account and therefore not part of DeltaV privileges. The ability to run certain DeltaV Applications and to save things like PHV files is set by the Windows user security, i.e. assigned groups and such. Thanks jgrunschel.

  Andre Dicaire

  • Cancel
• jgrunschel

  

  • 9 Jul 2024 7:31 PM

  In reply to Andre Dicaire:

  I'm sorry that I don't know the root cause. I've never put forth effort to figure out the issue, because fixing it is easy, and it only happens every now and then (once or twice per year) and not on every workstation.

  • Cancel
• chip.burge

  

  • 13 Aug 2024 6:02 PM

  In reply to jgrunschel:

  This same issue recently came up for a workstation I'm supporting and am happy to have found this thread.
  
  I think the setting for the control level: standard/advanced is stored in a registry key. I found HKEY_CURRENT_USER/SOFTWARE/FRSI/DeltaV/CurrentVersion/PHV/Options/AdvancedModeSet which seems to makes sense to me. There also seems to be individual keys for each user within the same folder. If anyone has any ideas on how this is being changed or removed I'm sure everyone would like to know.

  • Cancel