Re: [foxboro] Cout
- From: Neil Martin <neil_martin@xxxxxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Tue, 13 Apr 2010 11:37:46 -0500
I am not sure what the real question is, but if the FBM is configured for
PLB, then the PLB.CO_X is the only thing that can write to the FBM output.
You can connect the PLB.CO_X to other block boolean inputs like the .IN
parameter of a COUT block, but the COUT block can not be configured with
the letterbug of a FBM that is configured as PLB. The .COUT parameter of
a COUT block that is configured with IOMOPT of 0 can be connected to the
PLB.IFL_X parameter and then passed through PLB logic to the CO_X.
As s a further note, CIN (and similar blocks) can be connected directly to
inputs of a FBM that is configured with PLB by entering the FBM letterbug
and FBM point in the CIN block.
Neil Martin
Huntsman Performance Chemicals
Conroe & Dayton , TX.
Conroe ph) 936-760-6205
Dayton ph) 936-257-4212
pager) 936-522-0052
chris miller <gooooomaker@xxxxxxxxx>
Sent by: foxboro-bounce@xxxxxxxxxxxxx
04/13/2010 09:24 AM
Please respond to
foxboro@xxxxxxxxxxxxx
To
"foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
cc
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
_______________________________________________________________________
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:
