Re: [foxboro] CP40 Insufficient Memory

Hey Rick,

We see this problem often.  This problem occurs when your CP memory gets
fragmented, often caused by large sequence blocks that are edited
frequently.

----------------------------------------------------------------------
The only way to defragment is (that I know of):
1. Do a Save-All on the CP
2. Initialize the CP (from ICC)
3. Reboot the CP
4. Load-All

Yup, requires a CP reboot!

----------------------------------------------------------------------
To stop this problem from happening again:
To minimize memory fragmentation with large sequence blocks in the future,
you should look into using the CSPACE parameter with IND or DEP blocks.
This parameter pre-allocates a fixed amount of memory for the sequence
block, so that the block doesn't have to move (in CP memory) if you make a
small change to the block that increases its required memory size.

Foxboro documentation recommends that you set this CSPACE parameter as
follows:
1. Take your current size of the sequence block.  This is the value of the
CSIZE parameter.  You can do an omget on this parameter to get the current
value.
2. Add 1000 bytes to the CSIZE value.
3. Set CSPACE to this value.
4. The sequence block must be recompiled in order for the CSPACE to be
allocated.

----------------------------------------------------------------------
Hope this helps.

Mark Dumond
Sr App Engineer
FeedForward, Inc
Marietta, GA



-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of Rick Mol
Sent: Wednesday, November 20, 2002 3:21 PM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] CP40 Insufficient Memory


Hey Bunch,


I have a CP40 that has 530K free memory, 15K largest segment, per the
station block.  There is a fairly large sequence that gives an
"E35-INSUFFICIENT MEMORY FOR BLOCK" when I try to compile.

Any ideas, or am I looking at the dreaded CP reboot?


Regards,



Rick Mol
ESCO Company
IT/Automation Admin.
231.727.6409
rdmol@xxxxxxxxxxxxxxx



_______________________________________________________________________
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: