The way the include statement works is that it duplicates in your block whatever was in the included file at the time the block was compiled. The best way I can think of to compare is to run the "strings" command on the .r file and compare that to the .s file + the included file. There will be some differences - ie as I recall, comments are not shown in the .r file. Regards, Kevin FitzGerrell -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Khudhair, Waleed K Sent: Monday, May 14, 2007 5:32 PM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] How to extract a Dep Block into Test File Yes Kevin. At the end there is an include statement.. I believe it refers to another file under the directory /opt/fox/ciocfg/sequeninclude When I more the file I get code listing however I am not sure is it the same code the I get in the detailed display or not? how to double check? -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Kevin_Fitzgerrell@xxxxxxx Sent: Monday, May 14, 2007 11:11 AM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] How to extract a Dep Block into Test File 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 =3D code.=3D3D3D20 Regards, =3D3D3D20 -----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=3D3D3D3Djoin > to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3D3D3Dleave > > =3D3D3D20 =3D3D3D20 _______________________________________________________________________ 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 =3D3D3D20 foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: =3D3D3D mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3D3D3Djoin to unsubscribe: =3D3D3D mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3D3D3Dleave =3D3D3D20 =3D3D20 =3D3D20 _______________________________________________________________________ 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 =3D3D20 foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: =3D3D mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3D3Djoin to unsubscribe: =3D3D mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3D3Dleave =3D3D20 =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