Dirk,
Have you looked at state blocks in combination with pattern blocks? While
not as flexible as HLBL programs, I have found them to be extremely
reliable, deterministic and well suited for many batch applications. They
are limited to 16 steps and 16 outputs, but can be easily daisy-chained
together to accommodate larger matrices.
mk
On Thu, Apr 25, 2019 at 5:27 AM Dirk Pauwels <dirk.pauwels@xxxxxxxxxx>
wrote:
Hi gents,
One of our older sequences handles an addition from 6 prod units to 6
storage tanks, any unit can go to any of the tanks, so 36 possibilities.
Also there are 48 valves involved for which we also check the status (64
states) and compare it to the desired status. (yes I know, ridiculous, but
we're a batch plant and someone tried to stuff as much units and tanks on a
small surface as possible using a "spaghetti" layout and a lot of tie in's
in the headers.... :))
I have a valve matrix for this addition and it's about 24" x24" wide and
long.... :)
This sequence uses a lot of external references and a lot of WAIT UNTIL
statements. It works, but uses a lot of lines and it takes some time to go
through the code because of the WAIT UNTIL statements.
Also it's not the preferred way off course.
For other sequences I often use MCOUT's containing valve states and PATT's
containing the selection masks, but that won't work in this case. Too much
valve states (64).
I'm looking for a clever way to clean up the sequence, shorten it, speed
it up without using tons of extra blocks.
It's a pity MCOUT and PATT only have 16 inputs.... :)
Thanks for sharing your ideas....
Rgds,
Dirk
________________________________
Lawter Notice: The information (including any attachments) contained in
this communication is confidential, private and proprietary, may be
privileged or otherwise protected by applicable law or legal rule, and is
intended only for the use of the addressee(s). Unauthorized use,
disclosure, distribution or copying is strictly prohibited and may be
unlawful. If you have received this communication in error, please notify
the sender immediately by reply e-mail, or by calling the sender, and then
delete it completely from your system.
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
