Re: [foxboro] Detect transition

  • From: Kevin FitzGerrell <fitzgerrell@xxxxxxxxxxxxxxx>
  • To: foxboro@xxxxxxxxxxxxx
  • Date: Fri, 01 Sep 2006 20:17:42 +1200

On closer reading, I see you want to set on a 1 to 0 transition, so:
BI01 = REALM.HAIND.~

or

IN BI01
NOT

Regards,

Kevin FitzGerrell

Kevin FitzGerrell wrote:
> A little hard to tell what you are asking, thanks to the =20s.  If I've 
> understood you correctly, you should be able to do this in a logic 
> block, no need for seqence block.
> 
> BI01 = REALM block HAIND
> BI02 = from operator screen request (can be momentary contact or toggle 
> depending on desired result)
> 
> IN BI01  ; read HAIND
> IN BI02  ; read operator request
> FF       ; set on HAIND clear on reset
> OUT BO01
> 
> The FF could be MRS if the reset should have priority over the HAIND.
> 
> Regards,
> 
> Kevin FitzGerrell
> 
> 
> 
> Ghodhbani, Hafedh wrote:
> 
>>=20
>>Hi,
>>I=20want=20to=20set=20a=20boleean=20prameter=20"B"=20to=20"true"=20ONLY=20=
>>when=20the=20(REALM
>>block)=20=20
>>HAIND=20parameter=20changes=20=20from=20"1"=20to=20"0".=20"B"=20need=20to=20=
>>be=20reset=20to
>>"false"=20manually=20by=20screen=20click.
>>I=20am=20doing=20a=20sequence=20block=20to=20do=20the=20above.=20Is=20ther=
>>e=20an=20easier=20way=20?
>>Regards
>>Hafedh=20G
>>Sr=20C&I=20Eng
>>BG=20Group
>>Tel:+21674259250=20=20
>>
>>______________________________________________________________________
>>BG=20Energy=20Holdings=20Limited
>>Registered=20in=20England=20&=20Wales=20No:=203763515
>>Registered=20address:
>>100=20Thames=20Valley=20Park=20Drive
>>Reading,=20Berkshire=20RG6=201PT=20=20UK
>>Telephone:=20+44=20(0)118=20935=203222
>>Website:=20http://www.BG-Group.com
>>
>>This=20e-mail=20is=20intended=20only=20for=20the=20addressee=20named=20abo=
>>ve.=20=20As=20this=20
>>e-mail=20may=20contain=20confidential=20or=20privileged=20information,=20p=
>>lease=20
>>advise=20us=20immediately=20if=20you=20are=20not=20the=20named=20addressee=
>>=20or=20the=20person=20
>>responsible=20for=20delivering=20the=20message=20to=20the=20named=20addres=
>>see.=20=20The=20
>>contents=20should=20not=20be=20disclosed=20to=20any=20other=20person=20nor=
>>=20copies=20taken.
>> 
>> 
>>_______________________________________________________________________
>>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: