Re: [foxboro] Re-Usable Displays and Smurfed Values

It is also possible that you have consumed the stations capacity to
communicate to external stations.  I can't recall the exact limit, but it
includes all external connections and active display connections.  For
common plant areas this is often a problem.  SOM can be used to analyze
the list usage.  HH384 may help with this effort.





"Matic.Hank" <Hank.Matic@xxxxxxxxx>
Sent by: foxboro-bounce@xxxxxxxxxxxxx
10/30/01 07:15 AM
Please respond to foxboro

 
        To:     "'foxboro@xxxxxxxxxxxxx'" <foxboro@xxxxxxxxxxxxx>
        cc: 
        Subject:        Re: [foxboro] Re-Usable Displays and Smurfed Values



I've had a similar problem with displays on an  AB gateway , the graphics
were being displayed in various locations and would come up with  smurfed
values randomly , the main graphic that was primarily called was quite 
busy
, the problem ended up being a memory shortfall in the gateway. I had to 
do
some juggling of the data on the main graphic to reduce memory size , our
gateway is a COMM15 , so you'll probably have to call Foxboro to get an 
idea
of were your memory threshold for an integrator 30 is.

-----Original Message-----
From: Loupe, Rory (RJ) [mailto:RJLoupe@xxxxxxx]
Sent: Thursday, October 25, 2001 4:06 PM
To: 'Foxboro - Cassandra'
Subject: [foxboro] Re-Usable Displays and Smurfed Values



List,
I am using re-usable displays for identical tanks.  Each tank gets a
compound of it's own on one Integrator 30 (for Modbus).  Each compound and
MDSCAN for that compound have a period of 30 seconds.  The Integrator 30
connects to a Tank Gauging system that houses all the tanks.  There is a 
red
"I" (overstrike text) next to some values of a tank, gross volume for
instance, that is invisible when the value calculated is good and visible
when the value is bad.  A boolean output of a CALC block (on the same
Integrator 30) determines if the "I" is visible or invisible.  Sometimes
these "I"s appears smurfed on the graphic of the WP51D.  The "I" almost
always appears smurfed on a remote display via Exceed.  The boolean output
of the CALC block appears normal when using Select.  The actual values,
which are AIN or real outputs of a CALC, never appear smurfed.

Has anyone else experienced this problem?  Is there a way to fix it?


Thanks,
                 Rory Loupe
                                 The Dow Chemical Company
                                 LHC-3
                                 P.O. Box 150, Building 6801     21255 
highway 1,
Building 6801
                                 Plaquemine, LA 70765-0150 USA Plaquemine, 
LA  70764  USA
                                 Phone: 225.353-6409  Fax: 225.353.6968
                         E-mail: RJLoupe@xxxxxxx


 
 
___________________________________________________________________
This list is neither sponsored nor endorsed by The Foxboro Company.
Use the information obtained here at your own risk. For disclaimer,
see http://www.thecassandraproject.org/disclaimer.html#maillist

list info:   http://www.freelists.org/list/foxboro
subscribe:   mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave


 
 
___________________________________________________________________
This list is neither sponsored nor endorsed by The Foxboro Company.
Use the information obtained here at your own risk. For disclaimer,
see http://www.thecassandraproject.org/disclaimer.html#maillist

list info:   http://www.freelists.org/list/foxboro
subscribe:   mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave





 
 
___________________________________________________________________
This list is neither sponsored nor endorsed by The Foxboro Company.
Use the information obtained here at your own risk. For disclaimer,
see http://www.thecassandraproject.org/disclaimer.html#maillist

list info:   http://www.freelists.org/list/foxboro
subscribe:   mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: