Re: [foxboro] Determining Forces in PLB

Hi Tom,

We have the same type of error: access error on bus A or B, but only on
FCM/FBM200 connected through coax. Combination of CP60 - coax - FBI10
-FBM100 does not produce this type of error. We hope to get rid of the
errors by changing coax to fibre.
All our digital connections are (M)CIN/(M)COUT/GDEV using FBM41/42 and
241 and they all have PLB's

A list of forced PLB connection would be nice to have.

Rgds,

Dirk

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of tom.vandewater@xxxxxxxxxxxxxx
Sent: woensdag 21 februari 2007 20:54
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Determining Forces in PLB


David,
        Yes!  That would be nice.  I hope someone else has the answer.
There has to be a bit or integer in the memory of the FBM that is set
because the PLB Monitor displays a differentiating color, red, when a
contact is actively forced on and a different color, blue, when forced
off.  I wonder if the force info is also stored somewhere in the host
filesystem?
        The only ICC ladder file I am aware of is on the CP host stored
in:
/opt/fox/ciocfg/PLBs_CMPD_Name/PLBs_Blockname.p  We are also interested
in accessing current timer or counter values that are running in the PLB
ladder if anyone knows how.
        As an aside, even though the ladder logic is continuously
executed in a 3-5 ms scan, we are migrating away from running it because
of the many issues such as this that have continually plagued us with
PLB's since we started using them in 1989.  The latest in a long line is
that FBM's running ladder logic on a loaded CP-60 fieldbus can
repetitively cause System Alarms such as the following:

02-21-07 10:43:33      0  SYSMON =3D3D SYS21A  21CP05  Equip =3D3D =
140304

  SYSMON -00069 Single PIO Bus Access Error on B

02-21-07 10:44:23      0  SYSMON =3D3D SYS21A  21CP05  Equip =3D3D =
140304

  SYSMON -00071 Single PIO Bus Access Recovery on B

        We have already reconfigured a lot of our ECB8/Software Type 8,
(Ladder Logic), FBM's to be ECB5/Software Type 5, (CIN/COUT), compatible
and use dedicated CIN and COUT blocks for each IO point instead of the
ladder embedded CIN/CO's.  More blocks, slower scan, but more reliable
and document able.

Cheers,
Tom V.

-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of David Johnson
Sent: Wednesday, February 21, 2007 2:03 PM
To: Foxboro@xxxxxxxxxxxxx
Subject: [foxboro] Determining Forces in PLB

Hi List,

Is there a way to get a force list for a PLB without having to look=3D20
at each line and visually determine if anything is forced?  We'd =
like=3D20
to be able to generate a report of PLB forces (the actual item that=3D20
is forced, and if it is forced high or low), but I have no idea how=3D20
you would do that.

Thanks,
David

=3D20
=3D20
_______________________________________________________________________
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
=3D20
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         =3D
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Djoin
to unsubscribe:      =3D
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Dleave
=3D20
=20
=20
_______________________________________________________________________
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
=20
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
to unsubscribe:      =
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
=20
 
 
_______________________________________________________________________
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:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: