Re: [foxboro] Sequencecode and block behaviour

Andreas,

In addition to what Brian and Doug have suggested (SBX logic and connections
rather than one-shot gets/sets), I would add that you need to find out why
the CP's are dropping the messages.

There are a lot of possible reasons, but the most likely culprit is a
program or script making lots of getval/setval broadcast messages and/or a
program/script/sequence block hitting a CP too often and filling its message
queue.

If the CP you are trying to address from the Sequence Block consistently has
problems, I would really start there. 

Broadcast messages are easily seen using a variety of tools and most of our
FS people can help you identify the station that is generating them.
Likewise, messages directed to the same CP as your sequence code can be
monitored and their source machines identified.

One you know the stations that are generating the bulk of the broadcasts
and/or directed messages, you can take steps to reduce or slow them.

Hope this helps.

Regards,

Alex Johnson
Invensys Systems, Inc.
10707 Haddington
Houston, TX 77043
713.722.2859 (office)
713.722.2700 (switchboard)
713.932.0222 (fax)
ajohnson@xxxxxxxxxxx
For the latest information on ArchestrA, go to
www.invensys.com/Archestra.html.

 -----Original Message-----
From:   Weiss, Andreas [mailto:Andreas.Weiss@xxxxxxxxx] 
Sent:   Wednesday, May 14, 2003 9:39 AM
To:     foxboro@xxxxxxxxxxxxx
Subject:        [foxboro] Sequencecode and block behaviour


Hi List,

sometimes do I run into problems with my sequencecode.

The Independent-Block goes into manuell mode due to the fact that =
another C:B.P isn't reachable (OM-overruns).

What is the "best" solution?

The best would be, to buy a faster Control Processor but what can I do =
up to that time.

a) Build an observer-Block who checks the ::IND.MA state and puts the =
IND-Block regularly into automatic mode

b) Link the ::IND.MA to the ::IND.ACTIVE parameter


Solution a) is realized at this time but I think that it costs =
unnecessarily Control Processor power.


Regards,

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