Re: [foxboro] setpars utility
- From: "Hyde, James" <James.Hyde@xxxxxxxxxxxxxx>
- To: "'foxboro@xxxxxxxxxxxxx'" <foxboro@xxxxxxxxxxxxx>
- Date: Wed, 10 Apr 2002 12:59:24 -0400
I'm on top of it. Thanks to Lisa K.
I'm trying to understand a Windows Command Script that our Developers wrote.
OPEN CP4L11 READ ZIMMER
GET *:* SUBSET PIDA
NAME
LIMOPT
END
CLOSE CP4L11
EXIT
Can someone tell me how this works and where the output goes?
-----Original Message-----
From: Johnson, Alex (Foxboro) [mailto:ajohnson@xxxxxxxxxxx]
Sent: Wednesday, April 10, 2002 11:54 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] setpars utility
B0193NE - Integrated Control Configurator Application Programming Interface
Checkout the CSC web site (http://ips.csc.invensys.com/
<http://ips.csc.invensys.com/> ) or FoxDoc.
Regards,
Alex Johnson
System Products - Invensys Systems, Inc.
10707 Haddington
Houston, TX 77043
713.722.2859 (office)
713.722.2700 (switchboard)
713.932.0222 (fax)
ajohnson@xxxxxxxxxxx <mailto:ajohnson@xxxxxxxxxxx>
Come to the Invensys Showcase: http://www.invensysshowcase.com/
<http://www.invensysshowcase.com/>
-----Original Message-----
From: Hyde, James [SMTP:James.Hyde@xxxxxxxxxxxxxx]
Sent: Wednesday, April 10, 2002 9:36 AM
To: 'foxboro@xxxxxxxxxxxxx'
Subject: Re: [foxboro] setpars utility
Thanks Kevin, I did not know this.
Do you have a reference to iccdrvr.tsk on how to use?
-----Original Message-----
From: Fitzgerrell Kevin [mailto:fitzgerrell@xxxxxxxxx]
Sent: Wednesday, April 10, 2002 12:23 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] setpars utility
James,
Take a look at the MODOPT setting in the PIDA blocks that stayed at
LIMOPT=3. I think you'll find that they don't have an integral
term,
ie P or PD. In the P only blocks (MODOPT=1) the controller will
show
LIMOPT=3 regardless of it's state in the ICC (I didn't check the PD
option), ie. in a PIDA block with MODOPT=1 and LIMOPT=1 showing in
ICC,
SELECT will show LIMOPT=3. If you change MODOPT to 5, and make no
change to LIMOPT, SELECT will show MODOPT=5 and LIMOPT=1.
You may want to reconsider your use of setpars to make these
changes.
Because LIMOPT is not a settable parameter, changes made by setpars
to
it will not be updated to the station workfiles with an upload.
This
results in a permanent mismatch between station and workfile.
Savealls
are generated based on the station workfiles, so if you ever load
from
a saveall diskette these changes would be lost. Additionally,
setpars
doesn't checkpoint, so until the stations are checkpointed after the
changes are made, a CP reboot would cause these changes to be lost.
Finally, consider the scenario where a P only block is changed to a
PI.
If LIMOPT had originally been set to 2 in the ICC (or via
iccdrvr.tsk), when the later change to PI mode is made, LIMOPT will
still be 2 (and will now show 2 instead of 3 in SELECT). If LIMOPT
was
set with setpars, a subsequent change in MODOPT would cause LIMOPT
to
revert to the value in the station workfile, probably 1.
The iccdrvr.tsk is fairly easy to use for bulk editing, makes
changes
in both CP and station workfile and does checkpoints. Additionally,
small typos are significantly less likely to cause major damage to
the
control database (-c vs -C for instance).
Regards,
Kevin FitzGerrell
Systems Engineer
Foxboro New Zealand
+64 9 573 7690
kevin.fitzgerrell@xxxxxxxxxxxx
fitzgerrell@xxxxxxxxx
--- "Hyde, James" <James.Hyde@xxxxxxxxxxxxxx> wrote: >
> Hi,
>
>
> With the recommendation from Foxboro in the :
> Customer Advisory
> PIDA Block Behavior with V6.3 CS Release
> April 1, 2002
>
> We use a lot of PIDA's and, we did have most of the LIMOPT's set
to
> 1. I
> used the setpars utility to change the LIMOPTS to 2.
>
> /opt/fox/bin/tools/setpars -Ucp**** -tpida -mlimopt=2
-gIknowwhatido
>
> This only change the parameters that were set as 1 to a 2. It did
> not
> change the parameters that were set as 3 to a 2.
> Does anyone know why?
>
>
> James W. Hyde III
> Controls Technician
> Wellman Inc.
> Office: 228-533-4528
> Pager: 888-634-1690
>
>
> If the reader of this e-mail is not an intended recipient, you
have
> received
> this e-mail in error and any review, dissemination, distribution
or
> copying
> is strictly prohibited. If you have received this e-mail in error,
> please
> notify the sender immediately by return e-mail and permanently
delete
> the
> copy you received.
>
>
>
>
http://www.sold.com.au - SOLD.com.au Auctions
- 1,000s of Bargains!
_______________________________________________________________________
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:
//www.freelists.org/list/foxboro
to subscribe:
mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:
mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
_______________________________________________________________________
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:
//www.freelists.org/list/foxboro
to subscribe:
mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:
mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
_______________________________________________________________________
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: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
_______________________________________________________________________
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: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
