Re: [foxboro] Any experiences with FBM224

  • From: "Johnson, Alex (Foxboro)" <ajohnson@xxxxxxxxxxx>
  • To: 'Ken Heywood ' <kheywood@xxxxxxxxx>, "'foxboro-bounce@xxxxxxxxxxxxx '" <foxboro-bounce@xxxxxxxxxxxxx>, "'foxboro@xxxxxxxxxxxxx '" <foxboro@xxxxxxxxxxxxx>
  • Date: Thu, 2 Sep 2004 23:06:35 -0400

You can take the output of an AOUT block and connect it to a DCI real output
block. You could fan it out to two such.

Is that what you are asking?

AJ

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx
To: foxboro@xxxxxxxxxxxxx
Sent: 9/2/04 9:46 PM
Subject: Re: [foxboro] Any experiences with FBM224

Alex,
 
Will the AOUTR block work with the DCI?
 
Ken

        -----Original Message----- 
        From: Johnson, Alex (Foxboro) [mailto:ajohnson@xxxxxxxxxxx] 
        Sent: Thu 9/2/2004 8:11 PM 
        To: 'foxboro@xxxxxxxxxxxxx' 
        Cc: 
        Subject: Re: [foxboro] Any experiences with FBM224
        
        

        The implementation under the CP270 will be much more complete,
but even so
        you can build an redundant Modicon interface with CP60 and a
pair of
        FBM224s.
        
        While this interface is not transparently redundant, it will be
fully
        redudant assuming the remote device has two ports.
        
        Buy two FBM224s, configure each to scan the PLC. Take the data
from each and
        connect the DCI blocks to a SSEL. Configure the SSEL to handle
two inputs, a
        selection (H or L), and to drop the signal that is bad.
        
        Voila!
        
        The output of the SSEL can feed an AIN or CIN if you wish to
alarm it.
        
        
        You can do something similar with outputs.
        
        You can also control the scanning to turn off the "extra"
interface until
        there is a failure.
        
        
        
        
        
_______________________________________________________________________
        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:
//www.freelists.org/list/foxboro
        to subscribe:
mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
        to unsubscribe:
mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
        
        

-- No attachments (even text) are allowed --
-- Type: application/ms-tnef
-- File: winmail.dat


 
 
_______________________________________________________________________
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:             //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:             //www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
 

Other related posts: