Re: [foxboro] Memory Register in Calc type blocks
- From: Brian Bates <batesb@xxxxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Mon, 15 Nov 2004 13:50:16 -0500
Jeremy
If you have enough unused outputs and steps in your CALC blocks, you could
use the outputs, and add the outputs to a historian.
...Since there are 24 memory registers, and only a few outputs, this may
not be possible for your application.
I recommend using "fault-tolerant" CP's, and an adequate UPS.
We have FT CP30/40/60 pairs at our site, and the only time these CP's
reboot is for an upgrade.
-Brian Bates.
Jeremy Milum
<jmilum@xxxxxxxxx To: foxboro@xxxxxxxxxxxxx
> cc:
Sent by: Subject: [foxboro] Memory
Register in Calc type blocks
foxboro-bounce@fr
eelists.org
11/15/2004 12:35
PM
Please respond to
foxboro
I have a problem (well I have lots, but let's focus on just one right
now). We have
a lot of CALC blocks that generate data for daily reports and stuff.
These blocks
store some of their data in memory registers to be used again for the
next calculation
which usually occurs the next day(example: month-to-date totals and
averages).
The problem is that memory registers are not saved during an upload so if a
CP
reboots I lose it all. The only way I can see to save the data is to
use getpars,
and then use setpars to put it back in. This will work if I know the
CP is going down,
but what if I don't? getpars puts a load on the CP so this is not
ideal, but I could
run it once a day to save the data, and only be off a bit if we had an
unexpected
reboot.
Perhaps I shouldn't have used memory registers to store important data, but
it's
too late know. Any thoughts?
--
Patron saints in general are broadband connections to the Almighty
- Michelle Delio, Wired News
_______________________________________________________________________
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
_______________________________________________________________________
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: