Re: [foxboro] foxboro Digest V9 #177

We usually use "find tag", and  "where used", "references" etc functions 
and you can do an advanced query on all HLBL code, inluding sequeninclude 
(ie "select * from seqcode where code like '%RETRY%'") which would give 
you all the blocks containing a "RETRY" string...Basically I haven't yet 
seen a case in which I couldn't find the data I needed....
Works great and I honestly don't know how we managed before we had FoxRay 
(we have it for 6 months now). It's easy, there's no 300p manual you need 
to read or training required. 

I mostly use it to track operator changes, (also FOXSELECT changes), 
configurator changes and to find references to blocks/parameter/code I 
want to change without finding out 2 days later the change I made caused 
problems in related blocks/code I didn't know of..... (including display 
references)

It's also great for back documentation of block diagrams, logic/calc and 
even sequence code flowcharts are created automatically, no more drawing 
visio stuff. (Allthough the flowcharts document everything in the seq so 
you might need to clean it up or narrow it down a little bit in ie VISIO)
There's an FBM manager which helps you find free I/O, you can show/print 
PLB layout etc....

another nice feature is that it tracks and stores all the alarms, both 
process and system alarms. You can also get nice trends regarding alarms 
out of the system very easily, great help when you're evaluating the 
alarms config 

Also nice is that you can export to excell every list you pull up and you 
can print out directly without exporting

 It also reports integrity errors in blocks etc....

Another nice add on is that it has an operator log in feature, so that all 
changes made by the operator are logged at his name. (I know you can have 
this in the I/A, but I never bothered to inplement it)

And we can match our DCS tags against the PI tags

It's worth checking it out on the website and ask for a demo.

Rgds,


Dirk Pauwels - DCS/MOC coordinator 
Engineering dept.
Hexion Specialty Chemicals
E mail: dirk.pauwels@xxxxxxxxxx
T.  +32.(0)3.570.95.97
F.  +32.(0)3.570.16.09
Mob. +32.(0)497.428.300


wrote:

On Thu, May 14, 2009 at 2:45 PM, Doucet, Terrence
<tdoucet@xxxxxxxxxxxxxxxxxx> wrote:
> Can the tools check through your code and advise you which blocks need
> to be modified so that you do not try to send a display to a
> non-existing letterbug?

Are the letterbugs hard-coded or generated algorithmically? If they
are hard-coded, then yes, Foxray's "Find Tag" dialog box includes an
option to search all HLBL code for text strings, so you could search
all of your 1000 IND blox at once for the letterbugs to determine
which INDs need to be edited.

OTOH, if they are generated algorithmically, then I doubt there is any
generic tool out their that would do what you need.




 
 
_______________________________________________________________________
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:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: