Re: [foxboro] Cout

  • From: chris miller <gooooomaker@xxxxxxxxx>
  • To: foxboro@xxxxxxxxxxxxx
  • Date: Tue, 13 Apr 2010 13:29:46 -0400

Tom,  This is the same statement that I saw, and tried, with no success.  I
think that with the replies I have had that my experience is verified. That
is that it cannot be done. Thanks for all the replies and if there are any
other suggestions please respond.
Thanks again everybody.

Chris


On 4/13/10, Badura, Tom <tbadura@xxxxxxxxxx> wrote:
>
> Chris,
> I am not sure if I follow exactly what you are doing, but it sounds like
> you want to connect the IN parameter of a COUT block from OFL_1 of a PLB
> block and then have the COUT block drive CO_7 directly in a different
> FBM.  You need to set the COUT IOMOPT =1 and then enter the FBM's ECB
> name (not the PLB block) into IOM_ID and the physical output CO number
> into PNT_NO.
>
> COUT.IN = DCI_5.OFL_1
> COUT.IOMOPT = 1
> COUT.IOM_ID = <ecb_name> * See COUT description in B0193AX
> COUT.PNT_NO = 7
>
> However, I do not know if it is allowable to directly connect to an
> output of an FBM that is running ladder logic.  I gave this a quick try
> on our system. I created a COUT block as described above and tried
> connecting to an unused output in a FBM10/13 combo running ladder logic.
> I got the same W51- Invalid Hardware/software type error.  An FBM9 with
> ladder logic will have an ECB8 where as one without will have an ECB5.
> This may be your problem.  Perhaps one of the IPS (IOM) guys can verify
> if this is correct.
>
> Tom Badura
> Plastics Engineering Company
> tbadura@xxxxxxxxxx
>
>
>
> -----Original Message-----
>
> All,
> Working on Ver.8.3 Windoz with CP271.  I have FBM9/14 expansion set up
> for
> ladder logic.  Is there any way to access the COUT param through a COUT,
> MTR, GDEV, or other block with out having to use up IFL's in the ladder?
> I
> have logic in a different ladder with  DCI_5.OFL_1 mapped to
> DIO_3.IFL_29.
> CO_7 is the output I need. The ladder is
>
>
>     IFL_29                                                         CO_7
> 69 ---| |------------------------------------------------------------(
> )---
>     MPC-07-
> MPC-07-
>     115 INP                                                        115
> OUT
>
> I would like to set the DCI_5.OFL_1  to the .IN on a COUT block but I am
> unable to set the COUT block IOM_id. I am getting a W51- Invalid
> Hardware/software type.   According to what I have read, it looked like
> the
> COUT was the only way to make this work but I cannot get the .COUT of
> the
> COUT block mapped to a CO_X.
>
> Thanks in advance for your help.  I am looking forward to the responses.
>
> Chris
>
>
>
> _______________________________________________________________________
> 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: