Re: [foxboro] Trapping calls
- From: "Johnson, Alex (Foxboro)" <ajohnson@xxxxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Fri, 20 May 2005 02:26:12 -0400
There should be, but there really isn't.
However, I thought of something else. There are freeware tools on the
FeedForward site or creates a cross-references.
http://www.feedforward.com/downloads.htm
Regards,
Alex Johnson
Invensys Process Systems
Invensys Systems, Inc.
10707 Haddington
Houston, TX 77043
713.722.2859 (voice)
713.722.2700 (switchboard)
713.932.0222 (fax)
ajohnson@xxxxxxxxxxx
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Ashley Davey
Sent: Thursday, May 19, 2005 11:19 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Trapping calls
Thanks Alex,
I thought there was an easier way.
Ashley
>>> ajohnson@xxxxxxxxxxx 08:12:08 20/05/05 >>>
No, but you could scan your sequence code for the reference
cd /opt/fox/ciocfg
grep AUTDSR */*.s
Repeat on each host.
There is an obscure case where the parameter to be changed is stored in
a
SN00xx parameter. This approach won't work in that case.
However, you could use getpars to examine the SN00xx parameters.
Hope this helps.
Regards,
Alex Johnson
Invensys Process Systems
Invensys Systems, Inc.
10707 Haddington
Houston, TX 77043
713.722.2859 (voice)
713.722.2700 (switchboard)
713.932.0222 (fax)
ajohnson@xxxxxxxxxxx
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [
mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Ashley Davey
Sent: Thursday, May 19, 2005 11:04 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Trapping calls
Hi List
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 sequence perhaps) sets the AUTDSR to 0. (closes valve)
Is there a means of "trapping" this call so as to identify what is
closing this valve.
Thank you for your assistance.
Regards
Ashley Davey
African Products (Pty) Ltd
South Africa
Tel: +27 11 4585342.
_______________________________________________________________________
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:
