Re: [foxboro] How to extract a Dep Block into Test File
- From: Kevin_Fitzgerrell@xxxxxxx
- To: foxboro@xxxxxxxxxxxxx
- Date: Mon, 14 May 2007 17:10:59 +0900
Not sure why you are seeing this... Are any of the 10 lines you can see
an "include" statement?
Regards,
Kevin
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Khudhair, Waleed K
Sent: Monday, May 14, 2007 4:55 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] How to extract a Dep Block into Test File
Thanks Kevin for your usual support. To tell the truth I tried this and
I was able to view the source of the INDs and TIMERs not the DEPs block.
When I more any DEP block I see only the head of the file "the first 10
lines only" while thru detailed display you can see the whole code.=3D20
Regards, =3D20
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Kevin Fitzgerrell
Sent: Monday, May 14, 2007 10:12 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] How to extract a Dep Block into Test File
Waleed,
On your AW that hosts the control station containing your sequence
block, go to:
/opt/fox/ciocfg/COMPOUND_NAME/
Look for the file BLOCKNAME.s - it is a text file of your sequence
logic.
Of course, substitute the above COMPOUND_NAME and BLOCKNAME for your
actual compound and block names.
Regards,
Kevin FitzGerrell
On 5/14/07, Khudhair, Waleed K <waleed.khudhair@xxxxxxxxxx> wrote:
> Hi list,
> This is the first time for me to work with Dep blocks. Thru the
Detailed
> Display I am able to see the code, however for easy reviewing I would
> like to extract the code into a text file, how to do this?
>
> Regards,
>
>
>
>
_______________________________________________________________________
> 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=3D3Djoin
> to unsubscribe:
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Dleave
>
>
=3D20
=3D20
_______________________________________________________________________
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
=3D20
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: =3D
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Djoin
to unsubscribe: =3D
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Dleave
=3D20
=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:
