Emerson Exchange 365

• Not Answered

Named Set Configuratio

Hi All,

I am trying figure out what "User Selectable" means in a named set properties. In BOL, it is written that "In addition, named set states have to be configured as user selectable for the state name to be available for use within the controller. Does controller here mean Phase/Em/CM?

For example, if a phase running, the current action is setting the an EM (A_COMMAND) to a named state that has user selectable set to NO, will the phase stall or will it show the next named set that has User Selectable set to Yes?

Reason for asking is that I have observed this happening while running a phase. The Phase was setting an EM to Run, however, the faceplate EM SP  was displaying another named stated that has the User Selectable set to Yes (note: this name state is the next higher value state). 

Thank you.

WSoon

• 7 Mar 2019 7:21 PM
• Cancel

3 Replies

• Sal Salamone

  

  • 7 Mar 2019 9:40 PM

  Tricky question. When it says controller it means physical controller in BOL. But that User Selectable is also seen by the workstations and I believe they are responsible for not accept a person's command for that value. You'll notice that a default nameset for an EM can be 255 and the EM can go to 255 even though its not "User Selectable". If you had two different namesets, the "Name"should follow the value regardless of the nameset.
  So, it does not matter if the value is User Selectable or not unless you are an operator user. Try it sometime, go online and change a parameter to a value that is not user selectable and then try to do it as an operator.
  There is one case where I've seen a difference in namesets, but that's when it is cached in a workstations memory. If you need to know that one I can explain further.

  Sal Salamone

  • Cancel
• WSoon

  

  • 7 Mar 2019 10:06 PM

  In reply to Sal Salamone:

  Hi Sal, thank you for your reply. Then what about Visible? Is this property meant to hide the named state in a drop down menu?

  • Cancel
• Sal Salamone

  

  • 8 Mar 2019 5:38 PM

  In reply to WSoon:

  Visible is just that, can the operator see that name. But, what does the operator see when in that non-visible state?
  One thing nice about answering questions in this forum is that you learn something, and that I have.
  Lets separate values (integers) from nameset names. I'll use value if I am discussing the integer and name if the nameset.
  If I have a non-selectable name I cannot select it by name yet I can by value. When you use A_COMMAND in an EM you can go to a non-selectable name if you use a value.
  If a name is non-visible you just cannot see its name, but you still can go to that value. Your display (once you've downloaded "change set up data" ) will show a blank. When I was testing this I did see where an online EMs A_COMMAND still showed "Undefined" even after I made that name non-visible, but when I closed the module and reopened it, it was blank. Other times it changed as soon as I downloaded. The graphic always seemed to update. However I have experienced situations in the field where I have to restart a workstation to resynchronize nameset changes.
  Good question!

  Sal Salamone

  • Cancel