Yes, Terry is right. You could use Brian's code and then
AND BO01 BI01
OUT BO02
To generate a pulse when BI01 is true.
The PTC block is an elegant solution. However we sometimes forget that we can
use block period as a default timing function.
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Terry Doucet
Sent: Friday, January 29, 2016 1:48 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] info on ladder logic
I was reading his logic to be:
As long as IN1 is TRUE, the OUT1 must pulse at some configured rate. When
IN1 is FALSE, the OUT1 is OFF.
Terry
From: blong@xxxxxxx
Date: Fri, 29 Jan 2016 12:43:17 -0600
Subject: Re: [foxboro] info on ladder logic
To: foxboro@xxxxxxxxxxxxx
Really only need 3 steps..........
IN BO01
NOT
OUT BO01
Brian
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Johnson, David A.
Sent: Friday, January 29, 2016 11:34 AM
To: 'foxboro@xxxxxxxxxxxxx'
Subject: Re: [foxboro] info on ladder logic
Much easier way to accomplish this. Build a logic block with code
IN BI01 SUSTAINED INPUT
BIT 5
CLR BO01
EXIT
IN BO01
NOT
OUT BO01
END
The block period (0.5 sec, 1 sec, 2 sec, etc) will determine the flash
frequency. Connect BO01 to your COUT/MCOUT to drive your blink output.
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of gheyIl .
Sent: Friday, January 29, 2016 11:46 AM
To: Foxboro mailing list
Subject: Re: [foxboro] info on ladder logic
I don't have access to an FBM to try it, but I think this should work
in
ladder:
--|/|-------(TOF)-- t1
--|/|-------(TOF)-- t2
Where the 1st contact is tied to the 2nd TOF, the 2nd contact is tied
to the 1st TOF.
When the FBM initializes, the first contact is closed and TOF is on
for for
t1 secs; this forces the second contact to open, thereby stopping its TOF.
When the 1st TOF times out, the second contact closes, starting its
TOF timer for t2 secs, thereby stopping the TON timer.
I believe this will result in a t1 on /t2 off blink, which could be
tied to a CO.
Since there are 16 timers available in ladder logic, you could drive 8
outputs.
The document you want is B0193AW Integrated Control Software Concepts.
On Fri, Jan 29, 2016 at 11:07 AM, gheyIl . <breandan789@xxxxxxxxx> wrote:
Rather than being limited to 8 Boolean outputs, consider using LO01"AND"
(long integer output) which has 32 bits, each of which can be
written with OUT Oxx. This LO01 can then be connected to a MCOUT to
drive all your FBM outputs.
On Fri, Jan 29, 2016 at 10:45 AM, Jones, Charles R. (Chuck) <
Chuck.Jones@xxxxxxxxxxxxxxx> wrote:
You could use a bit of code to generate the "blink" signal and then
panel.that signal individually with each of your lights.
Example:
STEP 01 ;Blink Code
STEP 02 LAC M01
STEP 03 NOT
STEP 04 OSP 1
STEP 05 STM M01
STEP 06 NOT
STEP 07 OSP 1
STEP 08 STM M01
STEP 09
STEP 10 ;AND the inputs with the blink
STEP 11 IN BI01 ;request for 1st light
STEP 12 AND M01 ;blink signal
STEP 13 OUT BO01 ;flash the light
STEP 14
STEP 15 IN BI02 ;request for 2nd light
STEP 16 AND M01 ;blink signal
STEP 17 OUT BO02 ;flash the light
Et cetera
The CALCA block only has 8 Boolean outputs, so I considered
exporting the blink on one of the outputs. But, since it was going
to require a second CALCA anyway, I thought that putting 5 lights
in the first CALCA block and then cloning it would be easier.
By the way, on my machine the blink generates an unexpected pattern.
It blinks on and off at about the expected rate. But, the pattern
is flash-flash-skip ; flash-flash-skip; etc. But, for blinking
lights it may not be critical.
Chuck Jones
Automation Technologist
Tate & Lyle
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
[mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Dirk Pauwels
Sent: Friday, January 29, 2016 7:52 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] info on ladder logic
Hi Tom,
Thanks for the info and the logic code..
I already experimented a bit with LOGIC and DON and DOFF and came
up with something that works, but I need to "drive" 10 lights, so
logic seemed so "overcomplicated". I was surprised I/A doesn't seem
to have a block I can use to generate a repeating pulse contact.
Never needed it before, we tend to use foxview screens ,PLC's,
Schneider displays etc..., this is the first time I use a "non
programmable" control
//www.freelists.org/list/foxboro
Thanks & rgds,
Dirk
___________________________________________________________________
__ ____ 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:
mailto:foxboro-request@xxxxxxxxxxxxx?subject=jointo subscribe:
mailto:foxboro-request@xxxxxxxxxxxxx?subject=leaveto unsubscribe:
______________________________________________________________________
___ 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
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
______________________________________________________________________
*** Confidentiality Notice: This e-mail, including any associated or
attached files, is intended solely for the individual or entity to
which it is addressed. This e-mail is confidential and may well also
be legally privileged. If you have received it in error, you are on
notice of its status. Please notify the sender immediately by reply
e-mail and then delete this message from your system. Please do not
copy it or use it for any purposes, or disclose its contents to any other
person.
______________________________________________________________________
___ 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
______________________________________________________________________
___ 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