Re: [foxboro] Cyan displays...

Jaime,

I'm not an expert on the subject by any means.  But, the connection lists
required in the CPs for feeding information to displays are dynamic.  You
need to retain a certain amount of free memory to allow space for these
lists.  If there's not enough memory, the last display called up with
information required from that CP will show up with cyan fields.

There are two ways that I'm aware of to improve the memory allocation in a
CP.  If you simply reboot the CP, the "largest segment" of free memory
expands (assuming that it was previously less than the "total free memory").
If the CP OM lists need to be in contiguous memory locations (I'm not
sure?), this might help with the cyan display field issue.  Rebooting the CP
also might clear up old "defunct" lists and free up memory that way.  Since
the display OM lists are dynamic, you'll also most likely shuffle around
which display stations get shortchanged on list space if there's still not
enough to drive all of them.

Short of deleting logic, the most effective way to increase the "total free
memory" in the CP is to perform a saveall/initialize/reboot/reload.  This
seems to more efficiently repack memory and give you additional "total free
memory".  Reboot the CP again to maximize the available memory in the
"largest segment".

You can monitor the effect of these changes through the station display for
the target CP.

Regards,

Doug Lloyd
DGL Controls

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]On
Behalf Of Jaime Claramunt R. (Inforsa)
Sent: Wednesday, November 26, 2003 9:22 AM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Cyan displays...

Hi list,

Say, I remember you've been discussing about some cyan values on screen
displays...but I don't recall the actual issue...
I had something similar: some of the values on some of the displays appear
in cyan with no values, but all the conections and overlays and commands
were working fine (in all WPs). After some operations, openning, closing,
changing displays, the problem was "solved".
We saw that te CP free memory is quite low (CP40A FT), and when openning
some of these displays the amount was reduced.
Control charge is not so high (70-75), phasing seems Ok, maybe CP damaged ?
too much drawings on display ?

Any suggestion ?

Thanks
B.R.

Jaime Claramunt
Automation Engineer
INFORSA Paper Mill
CHILE


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