Farina,
The ramping options on the PIDA block only apply to the local setpoint SPT.
Looks like you have a CALC block with a connection to PID remote setpoint RSP.
As suggested you could use a IND block to set the SPTARG and rate. Connect the
CALC to the IND and start the ramp function from the IND block.
The preferred method would be to insert a RAMP block between the CALC and the
RSP. What is the issue with the RAMP block?
David Johnson
Principal Application Engineer
Process Automation
Industry Business
Foxboro by Schneider Electric
D 15085493801
F 15085496788
E david.johnson@xxxxxxxxxxxxxxxxxxxxxx
70 Mechanic St.
Foxboro, MA 02035
United States
*Please consider the environment before printing this e-mail
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Luciano André Farina
Sent: Wednesday, April 12, 2017 8:58 AM
To: foxboro
Subject: Re: [foxboro] Ramp in a cascade loop
My mistake...
PID1.SPT -> CALC -> PID2.*RSP*
instead of
PID1.SPT -> CALC -> PID2.SPT
If I understood the manual, the native PID ramp can be used only in LOCAL mode,
right? I need to use it in REMOTE.
Thanks
__________________________________________________________
2017-04-11 15:14 GMT-03:00 Gunter, Matt <matt.gunter@xxxxxxxxxxxxxx>:
We ramp the set point of a PID from within the PID itself. The
process is controlled by an IND block. There are something like five
parameters that need to be set in a given sequence and then once the
SPRAMP parameter (the last to be set) is cleared, the L/R needs to be
set to Remote. As I recall, you have to set the PID block itself to
ramp either over time or based upon BPC.
I don't think you can set this up with a CALC block because you set
the SPRAMP point and then watch it change back.
That is what we do.
Matt
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Luciano André Farina
Sent: Tuesday, April 11, 2017 11:41 AM
To: foxboro
Subject: [foxboro] Ramp in a cascade loop
Hi folks.
I am configuring a kind of ratio control loop, with an architecture
like
this:
PID1.SPT -> CALC -> PID2.SPT
I would like to implement a ramp between CALC and PID2, but the block
RAMP does not appear to be the best approach. LLAG can be used, but
the answer will not be linear.
Any ideas?
Thanks in advance,
Farina
__________________________________________________________
______________________________________________________________________
___ This mailing list is neither sponsored nor endorsed by Schneider
Electric (formerly The Foxboro Company). Use the info you obtain here
at your own risks. See the disclaimer at
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
------------------------------------------------------------
------------------
Notice: This e-mail is intended solely for use of the individual or
entity to which it is addressed and may contain information that is
proprietary, privileged and/or exempt from disclosure under applicable
law. If the reader is not the intended recipient or agent responsible
for delivering the message to the intended recipient, you are hereby
notified that any dissemination, distribution or copying of this
communication is strictly prohibited. This communication may also
contain data subject to U.S. export laws. If so, data subject to the
International Traffic in Arms Regulation cannot be disseminated,
distributed, transferred, or copied, whether incorporated or in its
original form, to foreign nationals residing in the U.S. or abroad,
absent the express prior approval of the U.S. Department of State.
Data subject to the Export Administration Act may not be disseminated,
distributed, transferred or copied contrary to U. S.
Department of Commerce regulations. If you have received thi s
communication in error, please notify the sender by reply e-mail and
destroy the e-mail message and any physical copies made of the
communication.
Thank you.
*********************
______________________________________________________________________
___ This mailing list is neither sponsored nor endorsed by Schneider
Electric (formerly The Foxboro Company). Use the info you obtain here
at your own risks. See the disclaimer at
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
