[foxboro] Good practice SBX, was: Trapping calls
- From: "Sieling, Marcel" <Marcel.Sieling@xxxxxxxxxxxxxxxx>
- To: "'foxboro@xxxxxxxxxxxxx'" <foxboro@xxxxxxxxxxxxx>
- Date: Tue, 24 May 2005 03:35:21 -0400
Hi Gang,
John wrote:
> Why not just secure the AUTDSR parameter and then wait to see=20
> which sequence block fails.
Perfect suggestion. Works even better, if in all used sequence blocks a
proper TO_SYS_ERROR SBX is configured which properly reports all OP_ERR
conditions on a printer. Then you just need to link AUTDSR to any =
parameter
to secure it and wait for the printout on the alarm printer. ;-)
The advantage is, that this approach works with all forms of =
addressing,
direkt FPN, claculated addresses, relative addressing and addresses in
SN00XX parameters. And you do not need to install any software or hack
cryptic grep scripts.
If you want a code example for a standard block exception just let me =
know
(off list please) and I'll send it to you (also off list, because not
everybody might be interested).
Best regards -
Marcel Sieling
Systems Technologies
Invensys Systems GmbH
Emanuel-Leutze-Str. 11
40547 Duesseldorf
Germany
Tel.: +49-211-5966-302
Fax: +49-163-99-5966302=20
Mobile: +49-163-5966302
Email: mailto:marcel.sieling@xxxxxxxxxxxxxxxx
Homepage: http://www.foxboro-deutschland.de
> -----Urspr=FCngliche Nachricht-----
> Von: foxboro-bounce@xxxxxxxxxxxxx=20
> [mailto:foxboro-bounce@xxxxxxxxxxxxx] Im Auftrag von Windle, John
> Gesendet: Freitag, 20. Mai 2005 22:13
> An: foxboro@xxxxxxxxxxxxx
> Betreff: Re: [foxboro] Trapping calls
>=20
>=20
> Why not just secure the AUTDSR parameter and then wait to see=20
> which sequence block fails.
>=20
> John Windle=20
> Invensys Process Systems
> Foxboro, MA=20
>=20
> > -----Original Message-----
> > From: foxboro-bounce@xxxxxxxxxxxxx=20
> > [mailto:foxboro-bounce@xxxxxxxxxxxxx]
> > On Behalf Of Ashley Davey
> > Sent: Friday, May 20, 2005 2:04 AM
> > To: foxboro@xxxxxxxxxxxxx
> > Subject: [foxboro] Trapping calls
> >=20
> > Hi List
> >=20
> > I have a GDEV configured to control a valve.
> > The AUTDSR parameter is not linked.
> > However, if I set AUTDSR to 1, (i.e. open the valve), something (a=20
> > sequence perhaps) sets the AUTDSR to 0. (closes valve)
> >=20
> > Is there a means of "trapping" this call so as to identify what is=20
> > closing this valve.
> >=20
> > Thank you for your assistance.
> >=20
> > Regards
> >=20
> > Ashley Davey
> > African Products (Pty) Ltd
> > South Africa
> >=20
> > Tel: +27 11 4585342.
> >=20
> >=20
> >=20
> >=20
> =
______________________________________________________________________
> > _
> > This mailing list is neither sponsored nor endorsed by=20
> Invensys Process
> > Systems (formerly The Foxboro Company). Use the info you=20
> obtain here at
> > your own risks. Read=20
> http://www.thecassandraproject.org/disclaimer.html
> >=20
> >=20
> foxboro mailing list: =20
//www.freelists.org/list/foxboro
> to subscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
> to unsubscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
>=20
=20
=20
_______________________________________________________________________
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
=20
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe: =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
_______________________________________________________________________
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:
- » [foxboro] Good practice SBX, was: Trapping calls
