Not necessarily better, as there are many ways to accomplish things, but another alternate: I have had to deal with a varying array of valves and one with multiple COUTs with multiple valves which could not be handled with single GDEVs by using a script and the setb call to manipulate COUT blocks for x amount of time (with sleep) before closing them and opening others. E.g.: setb COMPOUND:BLOCK.COUT 1 sleep 10 setb COMPOUND:BLOCK.COUT 0. This script was executed from a graphic and I echoe'd feedback to the top line of the screen so we could tell what was happening. Just keep in mind the security of doing this on the WP or AW vs. on the CP itself. This has worked well for years without a hitch though. Sincerely, Diane B. Harris Harris Automation Services, Inc. http://www.HarrisAS.com ----Original Message Follows---- From: "Stear, Bo" <stear@xxxxxxx> Reply-To: foxboro@xxxxxxxxxxxxx To: "'foxboro@xxxxxxxxxxxxx'" <foxboro@xxxxxxxxxxxxx> Subject: Re: [foxboro] a simple challenge Date: Wed, 21 Nov 2001 16:44:34 -0500 MIME-Version: 1.0 Received: from [168.215.193.75] by hotmail.com (3.2) with ESMTP id MHotMailBDC56B8E002E400438E5A8D7C14B0C400; Wed, 21 Nov 2001 13:45:51 -0800 Received: from turing.(none) (localhost [127.0.0.1])by turing.freelists.org (FreeLists Mail Multiplex) with ESMTPid F1DA684276; Wed, 21 Nov 2001 16:45:43 -0500 (EST) Received: with LISTAR (v1.0.0; list foxboro); Wed, 21 Nov 2001 16:44:42 -0500 (EST) Received: from sgofims02.ccs.ppg.com (mail2.ppg.com [63.76.98.14])by turing.freelists.org (FreeLists Mail Multiplex) with ESMTP id 8D63984224for <foxboro@xxxxxxxxxxxxx>; Wed, 21 Nov 2001 16:44:38 -0500 (EST) Received: by sgofims02.ccs.ppg.com with Internet Mail Service (5.5.2653.19)id <XLKQDK69>; Wed, 21 Nov 2001 16:43:23 -0500 From foxboro-bounce@xxxxxxxxxxxxx Wed, 21 Nov 2001 13:47:08 -0800 Delivered-To: foxboro@xxxxxxxxxxxxx Message-ID: <6DF8B2761802D311906D0090273F76C001C28504@xxxxxxxxxxxxxxxxxxxxxxxxxxx> X-Mailer: Internet Mail Service (5.5.2653.19) X-archive-position: 299 X-listar-version: Listar v1.0.0 Sender: foxboro-bounce@xxxxxxxxxxxxx Errors-To: foxboro-bounce@xxxxxxxxxxxxx X-original-sender: stear@xxxxxxx Precedence: normal X-list: foxboro Better yet, have a look at the capabilities of the STATE block. Sequencing of outputs for valves as you describe can be done easily here. -----Original Message----- From: kevin.fitzgerrell@xxxxxxxxxxxx [mailto:kevin.fitzgerrell@xxxxxxxxxxxx] Sent: Wednesday, November 21, 2001 3:36 PM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] a simple challenge Michael, If I understand correctly you want to trigger a series of solenoid valves in sequence every X seconds. Each solenoid valve to stay open for Y seconds, with the next solenoid valve in sequence to open as the prior one closes. I'd probably do the logic in a CALCA or CALC block. Something like this ought to work. BO01 - 4 are outputs to drive solenoids. I'd just use COUT blocks or an MCOUT connected to BO01-4 to drive simple solenoids. type = CALCA period = 2 (execute each second) ii01 = seconds between cycle repeats ii02 = seconds for each solenoid timini = 1 (so OSPs don't trigger on initialize) 1 in ii02 2 stm m01 ; store SV on time in mem for osp 3 inc io01 4 in io01 ; 5 in ii01 ; 6 sub 7 bip 11 ; on new cycle go to init 8 clr bo05 ; otherwise clear cycle flag 9 gto 13 ; and skip initialize 10 clr io01 ; initialize second counter 11 set bo05 ; set in cycle flag 12 13 in bo05 ; on bo01 to 1 14 osp m01 ; generate signal for SV 1 15 out bo01 16 in ~bo01 ; on SV1 finish 17 osp m01 ; generate signal for SV 2 18 out bo02 ; 19 in ~bo02 ; on SV2 finish 20 osp m01 ; generate signal for SV 3 21 out bo03 ; 22 in ~bo03 ; on SV3 finish 23 osp m01 ; generate signal for SV 4 24 out bo04 25 end 27 Regards, Kevin FitzGerrell Systems Engineer Foxboro New Zealand ------------------------------------ Tel: +64 (9) 573 7690 Fax: +64 (9) 573 7691 mvandenberg@xxxxxx Sent by: To: foxboro@xxxxxxxxxxxxx foxboro-bounce@fre cc: elists.org Subject: [foxboro] a simple challenge 11/21/01 08:24 PM Please respond to foxboro Hi list, We are going to replace a local relay / timer driven filter cleaning sequence by "something" in I/A. We therefore need to separately activate 4 solenoids, one after the oth= er, for a variable number of seconds (most likely 2). The interval between activating the solenoids should also be variable. I have already made something with a Calc block that generates seconds = ( 0 to 62) connected to a AIN block. On the four boolean alarm limits I connected the solenoids using a GDEV with the pulse option on. But ther= e must be something more brilliant than this, without the use of a DEP bl= ock. The solenoids will be connected (2?wire) to FBM41C/42C, therefore a PLB= solution is an option. All suggestions are more than welcome. thanks, Michel Michel van den Berg PFW Aroma Chemicals B.V. PO Box 415 3770 AK Barneveld the Netherlands Phone : (31)342 - 407 791 Fax : (31)342 - 407 789 email : mvandenberg@xxxxxx FedEx : Nijverheidsweg 60 3771 ME Barneveld the Netherlands ___________________________________________________________________ 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: //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: //www.freelists.org/list/foxboro subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp ___________________________________________________________________ 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: //www.freelists.org/list/foxboro subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave