Re: . How many SVs would be available to us for use in getting these
averages displayed?
The number of SVs is configurable. By default, the AW has 1250. The limit
can be expanded using the instructions in
* System Administration Guide for 50 Series Systems (Solaris 2.X)
[B0193ND/Rev H]
* 50 Series Configurable Operating System [B0193MJ/Rev A]
The documented limit is 4000 SVs in a station. This limit can be raised
using a different procedure to around 50,000. That limit can be raised by
taking one more step.
The ultimate limit is unknown, but I've taken it as high as 80,000.
Re: How to get the data into the SVs
The obvious mechanism is generate a text file with the data, use grep and
awk to isolate the values and names and create a script using omset to stuff
the SVs.
(Yes, omset is okay to use in this case because the data will be local. Use
omsetimp if the SVs are in a different station.)
Regards,
Alex Johnson
10707 Haddington
Houston, TX 77043
713.722.2859 (office)
713.722.2700 (switchboard)
713.932.0222 (fax)
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
-----Original Message-----
From: Stan Ruth [SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, April 10, 2001 7:34 AM
To: Foxboro DCS Mail List
Cc: [EMAIL PROTECTED]
Subject: RE: AIM historian and display of reduced data
Alex,
In our case, we have more averages than we care to perform in a CP
due to
loading issues. That function we were hoping to perform by the AIM
historian, since we could configure it to provide the reduction for
hourly,
daily, monthly, etc. as needed. How many SVs would be available to
us for
use in getting these averages displayed? And where might there be
documentation on how this could be accomplished?
Stan
____________________________________________________________________________
_______________________________
FV/DM get their data from an OM variable (CPB, AOA, or SV) by name.
AIM* reduces data and stores it internally. For that matter, so does
the
old/legacy/data historian.
So far as I am aware the only ways to get these calculations onto a
FV/DM
display are:
* Use a trend
* Write a program/script to extract the data from AIM* and
put it
in a
SV periodically which probably more trouble than doing the averages
in the
CP.
Regarding averages in a CP, you have a number of options, the DTIME
block
can be used to generate a rolling average.
The 8 of the 10 buckets in the DTIME can be connected to one of the
inputs
of a SIGSEL block and the SIGSEL can do the average of those 8
values.
Setting the DTIME delay and the SIGSEL and DTIME periods will give
you the
average you want (if 8 samples is sufficient).
There are others, but these are not obvious.
Regards,
Alex Johnson
-----------------------------------------------------------------------
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]
