Tim,
I have made such a thing (based on dumping all CPs with iccdrvr.tsk and
producing subslists for filling out generic enclosure displays) for the
Leuna Refinery, Germany. They have displays graphically showing the FBM
allocation in an enclosure (nest/slot) using different colors for different
module types along with an indication if there are still points available on
the card. For each FBM there is an overlay (also generic and filled out by
subslists) showing the I/O points allocated along with their current status
(digital input or raw counts) at the card. FBM and CP failures are alarmed.
You have to take care about everything that smells like I/O such as
intelligent transmitters, PLBs (for which it is rather complicated to find
all the I/Os they use because a PLB can but doesn't have to use all I/Os
which are available to it), GDEV blocks and the like (along with the
standard CIN, COUT, AIN and AOUT blocks). The awk script I run over the CP
dumps is rather long.
If you want to show which FBM is in which nest/slot you have to have an FBM
numbering scheme which reflects this information.
Regards,
Sascha Wildner
erpicon Software Development GmbH
----- Original Message -----
From: "Lowell, Tim:" <[EMAIL PROTECTED]>
To: "'Foxboro DCS Mail List'" <[EMAIL PROTECTED]>
Sent: Wednesday, November 22, 2000 7:57 PM
Subject: What Honeywell hath wrought
> I just got back from my first ever Honeywell course (we also use
Honeywell,
> and my boss finally asked me to learn it), and I really like some of their
> system status displays, so I attempted to duplicate one of them on the
I/A.
> After a few days development, I have come up with this:
>
> A graphical display of all the FBM's in a given CP, area, unit, whatever.
> Each FBM on the display is represented by its letterbug. Clicking on the
> letterbug runs a script file which creates a substitution list and then
> calls up a re-useable display that gets filled in by the script with all
the
> configured I/O blocks on that FBM. On the re-useable display you get the
> block name, description and current value of each block on that FBM, with
> the current value in background text so you can see if it is BADIO or not.
> You can click on each block name to call up a standard detail display for
> each block.
>
> It's not completely real-time like Honeywell, because I couldn't figure a
> way to extract blocks in real-time given the FBM letterbug. What I did
was
> write another script that creates the "master list" of all I/O blocks in
the
> system with their IOM_ID's and PNT_NO's which takes about 30 minutes to
run
> using "getpars" and "omgetimp" calls. You could use FoxAPI unbuffered
reads
> too, I suppose. The substitution list script then greps out the FBM
> letterbug from the "master I/O list". The idea is that you run the
"master
> I/O list" script once a day or once a week using crontab, since you don't
> normally add I/O points very often anyway. You could run it on demand
also.
>
>
> The whole scheme is kind of kludgy, but it works and I think will be very
> useful around here. You could use it to see if a given FBM has any spare
> points or to see what's on an FBM if it goes bad. It's also nice just to
> monitor an FBM to see how the points on it are doing.
>
> If anyone wants to see the scripts and displays, I would be happy to
provide
> them. The current version supports AIN, AINR, AOUT, AOUTR, CIN, COUT,
GDEV,
> and DPIDA, because that is all we have here. You could add other I/O
blocks
> easily enough. I also would love to hear any better ways to accomplish
what
> I tried to do, especially ways to make it more real-time, and any other
> system status displays that people have come up with.
>
> Tim
>
> -----------------------------------------------------------------------
> This list is neither sponsored nor endorsed by the Foxboro Company. All
> postings from this list are the work of list subscribers and no warranty
> is made or implied as to the accuracy of any information disseminated
> through this medium. By subscribing to this list you agree to hold the
> list sponsor(s) blameless for any and all mishaps which might occur due to
> your application of information received from this mailing list.
>
> To be removed from this list, send mail to
> [EMAIL PROTECTED]
> with "unsubscribe foxboro" in the Subject. Or, send any mail to
> [EMAIL PROTECTED]
>
-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All
postings from this list are the work of list subscribers and no warranty
is made or implied as to the accuracy of any information disseminated
through this medium. By subscribing to this list you agree to hold the
list sponsor(s) blameless for any and all mishaps which might occur due to
your application of information received from this mailing list.
To be removed from this list, send mail to
[EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]
