Controlling Access to Logic_PIDE Faceplate

[Jim ManleyModeratorKarma: 262Rank: Jedi]

The control system uses the FactoryTalk View Logix_PIDE faceplate construct in several places.  In some situations, I need to be able to control who has access to the faceplate.  I can’t assign a Security Code to the Logix_PIDE faceplate in the Displays folder.

Is it possible to use the parameter file associated with each instance of the Logix_PIDE faceplate to control access to the faceplate?

Thanks,

Jim

[PLCGuruKeymaster]

Hey Jim, I’ve not seen security handled in parameter files – not to say that it’s not possible I’m just not sure. As a workaround is it possible to put your faceplate on a popup window(s)?

Then you can use Animations to display buttons that will launch the popup(s) depending on the user who logged in. Not sure if this is something you could consider.

[Jim ManleyModeratorKarma: 262Rank: Jedi]

I looked at animations initially but there doesn’t seem to be a way to apply animation control to the Logix_PIDE faceplate, which is why I was looking at the parameter file.

I did go back and look at the page again.  I noticed that each of the graphics that the operator clicks on had a “patch” around it.  This patch was the area the operator had to click on in order to get the faceplate to appear.

Turns out I could use animation to control who sees that patch based using the
Function->Security->CurrentUserHasCode().

Before applying the animation control, a user in the Operator group would see the orange patch around the control valve (shown in valve_with_patch.png).  By applying animation control shown in the expression_editor.png file, I was able to hide the orange patch around the control valve from the operator group (see valve_without_patch.png).

Attachments:

You must be logged in to view attached files.

[PLCGuruKeymaster]

Yes, that’s why I was suggesting using a popup(s) to hold your faceplate(s) and then use animations to control the screen navigation buttons to access those popup(s). Without fully understanding what it is you were trying to do this may or may not have worked for you???

Sounds like you have an animation work-around anyhow. Great!

[Sean TerrellModeratorKarma: 187Rank: Jedi]

Jim,

it sounds like you have your access control under wraps, however I did start a reply to this thread and never finished it, so I wanted to throw some thoughts in the mix.

1) I make it a habit to do all of the access controls and password comparisons on the PLC. This way if you ever have to change the OIT to a different vendor or anything, its all tag based and the passwords and controls are just as easily accessed and used. and it makes forgotten / changed passwords easier to deal with.

2) Use a visibility animation to make buttons for Setpoints or PID faceplates, or trending changes only available to users AFTER they have logged in, and multiple accounts can access the same buttons based on OR operators in the visibility expression.

3) this also allows me to log when setpoints were changed and by what account level. This wont pinpoint who made the change, but I can easily enough trace back to which Super was on at X date and X time, or which PLC tech was assigned a work order on X date to X site and have a “reasonable” accountability of who changed what. Its not perfect. but it mostly works

If you would like some examples of how to accomplish this with Logix 500 or Studio 5K I can send some examples as well as some examples of the FT studio expressions for visibility.

I hope this gives you some thoughts about working with security and animations in the future!!

– Scooter

 

[Jose CatalanParticipantKarma: 18Rank: Padawan]

Sean

woukd it be possible to have the examples you mention above?

 

[Sean TerrellModeratorKarma: 187Rank: Jedi]

Jose,

Most certainly! Give me a day or two, and I will put together some sanitized files I can upload!

– Scooter

[Sean TerrellModeratorKarma: 187Rank: Jedi]

Here you got Jose… Iill be sending you the Programming for the rest off it soon

[Author]

Posts