Re: [foxboro] Cout

  • From: "Johnson, Alex P (IOM)" <Alex.Johnson@xxxxxxxxxxxx>
  • To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
  • Date: Tue, 13 Apr 2010 11:45:20 -0500

I'm pretty sure that the PLB block use prevents the COUT block use - we don't 
want two blocks writing to the same output.

Isn't the CO_7 an output parameter of the PLB block? Per the manual:

OUTPUTS
BAD                     bad I/O status          Boolean con/no-set 0 0 to 1
BLKSTA          block status            pack_l  con/no-set 0 bit map
CIN_1 to CIN_32 output point 1 to 32    boolean con/no-set 0 0 to 1
CO_1 to CO_16   contact output 1 to 16  boolean con/no-set 0 0 to 1


Regards,
 
Alex Johnson
Invensys Operations Management
10900 Equity Drive
Houston, TX 77041
+1 713 329 8472 (desk)
+1 713 329 1600 (operator)
+1 713 329 1944 (SSC Fax)
+1 713 329 1700 (Central Fax)
alex.johnson@xxxxxxxxxxxx (current)
alex.johnson@xxxxxxxxxxxxxxxx (good until September 2010)

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On 
Behalf Of chris miller
Sent: Tuesday, April 13, 2010 9:24 AM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Cout

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
 


*** 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 email comes from a division of the Invensys 
Group, owned by Invensys plc, which is a company registered in England and 
Wales with its registered office at Portland House, Bressenden Place, London, 
SW1E 5BF (Registered number 166023). For a list of European legal entities 
within the Invensys Group, please go to 
http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77. 
You may contact Invensys plc on +44 (0)20 7821 3848 or e-mail 
inet.hqhelpdesk@xxxxxxxxxxxxx This e-mail and any attachments thereto may be 
subject to the terms of any agreements between Invensys (and/or its 
subsidiaries and affiliates) and the recipient (and/or its subsidiaries and 
affiliates).


 
 
_______________________________________________________________________
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: