Re: [foxboro] Lock Setpoint Value in Controller

> You might try
> 
> SPT  CName:BName.SPT.Value.0

No, this is not possible. As Chuck Jones wrote:

> In any event, I don't think it is possible to connect the SPT parameter to
> anything.  You can connect to it and read it, but you can't connect
anything
> to it and write to it.  That's why I go with the remote setpoint.

A quick test in the CIOCFG will tell you that this is the case.

I know this as I happen to have to work through this just yesterday. We used
Chuck's solution of locking the block in remote (REMSW  :Blockname.REMSW.1)
and expanded on it by securing the remote setpoint value using a similar
link back to itself with a value (RSP    :Blockname.RSP.40.0).

Duc

-- 
Duc M. Do
Dow Corning Corp.
Carrollton Plant
Carrollton, KY, US


-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of Nasif, Mohamed
Sent: Wednesday, December 15, 2004 10:10 AM
To: 'foxboro@xxxxxxxxxxxxx'
Subject: Re: [foxboro] Lock Setpoint Value in Controller


Dan,
You might try

SPT  CName:BName.SPT.Value.0

I wish this helps.  Thanks.

Regards,

Moh Nasif


-----Original Message-----
From: Karppi, Dan (SudburySmelter)
[mailto:DKarppi@xxxxxxxxxxxxxxxxxxxxxxxx]
Sent: Wednesday, December 15, 2004 7:44 AM
To: 'foxboro@xxxxxxxxxxxxx'
Subject: [foxboro] Lock Setpoint Value in Controller


Hello List Members,
I want to lock the value of the setpoint in a PIDA controller so that it
cannot be changed from the faceplate.  I recall that in an earlier post it
was suggested that a configured parameter can be linked to itself in the
block configuration to lock its value.  I've searched the archives but
cannot find this post.  Does anyone remember how to do this?

Thanks in advance,

Dan Karppi CCST
Instrument Technologist
Falconbridge Limited
Falconbridge, ON
Canada

 
 
_______________________________________________________________________
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
 

Other related posts: