Re: [foxboro] On the fly trending config issues with V7 system?
- From: <tom.vandewater@xxxxxxxxxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Tue, 6 Sep 2005 09:32:57 -0400
Stan,
I assume your version 6 boxes are Sun and Version 7 boxes are
Microsoft. Is that correct? Are they both running Foxview or are
Version 6 boxes running DM? We went through similar pain and learning
when trying to build our "on the fly" generic overlays for all block
types. You are right in saying that $PICK1 is initialized to <-:.-> any
time you open a new graphic, (at least on Version 6 Sun platform using
DM), but without seeing the mechanism you use to push values and call
the generic trend I can't tell what might be happening. =20
On our generic block overlays we eliminated the use of $PICK1
and $PICK2 and created our own variables because it was impossible to
predict what Foxboro was doing, (or might do in the future), with
$PICK1/2 which are their dedicated variables. You have already created
$T1 - $T4 to retain the trend variables so why not use your own variable
to push values to them? I know, I know, it worked before but now it is
broken, maybe because Foxboro changed something from one release to
another.
If you pick and fill in all four trend variables, ($T1 - $T4),
does the generic trend call up in a timely manner? If so, the delay
might be associated with the display timeout of an undefined variable,
but it doesn't explain why that isn't an issue on the V6 system. A
workaround would be to make sure the operators pick four variables,
every time even if they have to pick the same value two our three times
to fill the $T variables.
Tom VandeWater
Control Systems Developer/Analyst
Dow Corning Corporation
Carrollton, KY USA
=09
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of stan
Sent: Sunday, September 04, 2005 10:43 PM
To: Foxboro List
Subject: [foxboro] On the fly trending config issues with V7 system?
WE use quite a bit of what I believe is called "pick, pick, pick
trending".
This allows operators to build on the fly trends from (up to 4) of any
values displayed on a given DM graphic page. This is done with a dmcmd=20
built into the graphic, that basicly pushes the value of $PICK1 onto
a stack ($T3, $T2, $T1). Once the trend overlay is up he/she can then
click in the grid area, and an on the fly overlay comes up allowing
the scaling etc to be changed.
This has worked well for years. However we are observing a problem
that we can reproduce only on V7 systems. So far it exists on all the V7
machines I've tried it on, and interestingly, not on V6 systems on the=20
same (mixed) node.
The issue is that the first time you do this after a first callup of
a graphic, if you do not pick 4 points, it takes about 10 seconds for
the on the fly config overlay to come up. We believe this is related to
the
fact that $PICK1 is initialized to -:.- which of course is not in the
trending database. We see this behavior both on legacy historian based
systems, and on a brand new AIM historian based system.
Has anyone else seen this behavior?
Anyone have any ideas how to work around it? The new system replaces
a Spectrum system, and I;m trying to educate the operators on just how
powerful the trending is, as a tool for them, but this is not helping.
--=20
U.S. Encouraged by Vietnam Vote - Officials Cite 83% Turnout Despite
Vietcong Terror=20
- New York Times 9/3/1967
=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:
