Re: [foxboro] "protect name .PARM" DM/FV command
- From: "Landry, Dwayne" <rdlandry@xxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Wed, 23 May 2007 08:33:26 -0500
Although not highly polished, ( push a button and walk away ) I created a VB
app that sets the protection classes for all of our FV detail displays. The
basic steps that it does is a convert the files to a .g, reads each line in the
file looking for a specific string match. Part of the string will contain the
variable you want to protect and alevel=0. The variables found in the string
are compared to a protection class definition file that we created which
contains all the settable parameters and our desired protection level. The app
modifies the .g file then converts them back to an FDF file. The whole process
from getting an entirely new set of DD files takes a couple of hours to
complete. You can then propagate these new DD files. I'm sure the same
application could be used on Faceplates.
Dwayne Landry
PPG Industries Inc.
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Corey R Clingo
Sent: Wednesday, May 23, 2007 8:14 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] "protect name .PARM" DM/FV command
True. This mechanism is not foolproof, even if it had worked as I
envisioned/desired. But it would eliminate 90-95% of the issues, and
prevent all that typing of loopback connections in situations where
changes were not desired, but it wouldn't be the end of the world if they
happened. I was just salivating for a moment or two at the prospect of
several lines of "protect name .DONTTOUCHTHIS" lines in an environment
script to protect a desired list of parameters, rather than a combination
of locking them, having some enforcer application set them back when they
changed (for all those settable/non-connectable ones), or d_edit'ing all
the faceplates and details to control access via protection classes - on
every system upgrade (but then again I'm toying with the idea of making my
own, as I find the system-supplied ones lacking in several areas, so maybe
that last one is not such a big deal).
Corey Clingo
BASF Corporation
"Wilson, Brad" <brad.wilson@xxxxxxxxxxxxxxxx>
Sent by: foxboro-bounce@xxxxxxxxxxxxx
05/23/2007 07:47 AM
Please respond to
foxboro@xxxxxxxxxxxxx
To
<foxboro@xxxxxxxxxxxxx>
cc
Subject
Re: [foxboro] "protect name .PARM" DM/FV command
-----Original Message-----
From: Johnson, Alex P (IPS)
Sent: Wednesday, May 23, 2007 12:19 AM
The relative picks in some of the faceplates have been configured with
action names. For example, the OUT relative pick on the PID faceplates
have the name .OUT. If you call in a PID detail display and issue the
command
pref dmcmd "protect name .OUT"
the relative pick for the .OUT parameter is no longer pickable.
-----Original Message-----
If a protected element is not "pickable", it would still be "changeable"
by other means, correct? For example, if a display has user-defined
up/down buttons that change the .OUT parameter without a pick, then the
above protection method would not work. Some considerable thought needs
to be invested when designing and building a display if selected (not
global) protection is (or may) be desired.
Brad Wilson
brad.wilson@xxxxxxxxxxxxxxxx
Invensys Systems, Inc
1090 King Georges Post Rd, Suite 204
Edison, NJ 08837
732-874-0087
Confidentiality Notice:
The information contained in this electronic message and any attachment(s)
=
to this message are intended for the exclusive use of the recipient(s) and
=
may contain confidential, privileged or proprietary information. If you
are=
not the intended recipient, please notify the sender immediately, delete
a=
ll copies of this message and any attachment(s). Any other use of the
E-Mai=
l by you is prohibited.
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: http://www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
-- No attachments (even text) are allowed --
-- Type: image/gif
-- File: PPGProtClass.gif
-- Desc: PPGProtClass.gif
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: http://www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
- References:
- Re: [foxboro] "protect name .PARM" DM/FV command
- From: Corey R Clingo
Other related posts:
- » Re: [foxboro] "protect name .PARM" DM/FV command
- » Re: [foxboro] "protect name .PARM" DM/FV command
- » Re: [foxboro] "protect name .PARM" DM/FV command
- » Re: [foxboro] "protect name .PARM" DM/FV command
- » Re: [foxboro] "protect name .PARM" DM/FV command
- » Re: [foxboro] "protect name .PARM" DM/FV command
- » Re: [foxboro] "protect name .PARM" DM/FV command
- » Re: [foxboro] "protect name .PARM" DM/FV command
- Re: [foxboro] "protect name .PARM" DM/FV command
- From: Corey R Clingo