Re: [foxboro] Timer Question
- From: "Gunter, Matt" <Matt.Gunter@xxxxxxx>
- To: <foxboro@xxxxxxxxxxxxx>
- Date: Tue, 16 Oct 2007 08:05:49 -0600
Thanks to all for their input. This issue was correctly identified as
overruns. Based upon the recommendations of this group, I sought and
found the CP60 loading workbook and did some modeling. Our system uses
1/A FIO and FBP12 integrator cards so there are no physical FBMs. Each
I/O card has its own ECB and it is treated like a "simple I/O" FBM. We
have several systems (most of which have this problem) and this
particular system services 110 I/O cards. I had to increase the period
on most of the ECBs then shift the phase for half of them in order to
more evenly distribute the load. When I last looked, there were no more
overruns and the timer blocks in this CP are working properly. Now to
tackle the other systems.
I am always impressed, and grateful, by the speed and level of
knowledge/understanding that comes out of this resource.
Thanks again to all.
Matt Gunter
ATK Launch Systems
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Johnson, Alex P (IPS)
Sent: Friday, October 12, 2007 9:18 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Timer Question
Re: If memory serves, Alex Johnson had some tips some time ago on this
list
for "tuning" the fieldbus by changing the order that segments were
scanned depending on the scan times for those segments.
The FCM/DCMs are scanned in the order shown in <cpLbug>_ECB.
In general, you want the FCM with the fewest FBMs to be listed first.
The CP issues all data requests in that order and then goes to the each
one in that order to pickup the requested data.
Each FCM processes in parallel so by putting them in increasing chain
length you maximize the probability that the FCM will have the data when
CP comes back to request it.
Make sense?
Regards,
Alex Johnson
Invensys Systems, Inc.
10900 Equity Drive
Houston, TX 77041
713.329.8472 (voice)
713.329.1700 (fax)
713.329.1600 (switchboard)
alex.johnson@xxxxxxxxxxxxxxxx
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
On Behalf Of Kevin Fitzgerrell
Sent: Thursday, October 11, 2007 6:48 PM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] Timer Question
Matt,
Just a couple more comments:
Station idle time includes idle time in overrun cycles, which means once
your CP starts overrunning, idle time is not a good indication of CP
load. In fact, it is a good indication of how inefficient the CP is
when overrunning. When the CP can't finish it's processing in a BPC, it
schedules an extra cycle to finish the processing in. That's the
overrun cycle. Your timer blocks should be processing fine, however the
extra overrun cycles aren't accounted for in the timer block algorithm
with would account for your inaccurate timing.
How many FBMs to these CPs have? Are they using 100 series FBMs? If
so, how many 100 series FBMs are on each pair of DCM10E modules? Do you
have any Intellegent Transmitter FBMs? Do you have any digital bus FBMs
(223 or 224)?
Most of my experience with high I/O scans has been with 100 series FBMs
where not enough DCM10Es had been specified. Once extra DCMs were added
to split the load better our I/O scans went way down.
Intellegent Transmitter FBMs seem to be an unusually high load on the
fieldbus - I ended up replacing a couple in one plant area (with
FBM01s) which made a huge difference in I/O scans.
If memory serves, Alex Johnson had some tips some time ago on this list
for "tuning" the fieldbus by changing the order that segments were
scanned depending on the scan times for those segments.
Regards,
Kevin FitzGerrell
On 10/12/07, Gunter, Matt <Matt.Gunter@xxxxxxx> wrote:
> MeeOuch! As Spencer Katt of eWeek would say!
>
> Thanks to everyone for their comments.
>
> We are running CP60s and I have suspected loading. Here's the skinny=20
> ...
>
> CP Field Bus Scan Cont Blks Seq Blks Total
> Station Idle
> Good Timer CP 61.4 13.4 3.2 78.0
> 62.9
> Bad Timer CP 1 121.2 15.8 7.6 144.6
> 77.6
> Bad Timer CP 2 114.8 13.0 6.0 133.8
> 80.4
>
> When I check the loading in our lab, the field bus scan is zero - of=20
> course since it is not hooked to any real hardware.
>
> Apparently the higher station idle time is not indicative of resources
> available to process timer blocks. It appears that I am going to have
> to figure out a way to reduce field bus scanning.
>
> Best Regards
>
> Matt Gunter
> ATK Launch Systems
=3D
=3D
_______________________________________________________________________
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
=3D
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe:
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Djoin
to unsubscribe:
mailto:foxboro-request@xxxxxxxxxxxxx?subject=3D3Dleave
=3D
Confidentiality Notice:
This e-mail and any associated files are intended solely for the
individual=3D or entity to whom they are addressed. Please do not copy =
it
or use it for =3D any purposes, or disclose its contents to any other
person. Further, this e=3D -mail and any associated files may be
confidential and further may be legal=3D ly privileged. This email is =
from
the Invensys Process Systems business uni=3D t of Invensys plc which is =
a
company registered in England and Wales with i=3D ts registered office =
at
Portland House, Bressenden Place, London, SW1E 5BF =3D (Registered =
number
166023). For a list of European legal entities within t=3D he Invensys
Process Systems business group, please click here http://www.in=3D
vensys.com/legal/default.asp?top_nav_id=3D3D77&nav_id=3D3D80&prev_id=3D3D=
77.
If you have received this e-mail in error, you are on notice of its
status.=3D Please notify us immediately by reply e-mail and then delete
this message =3D from your system. Thank you for your co-operation. You
may contact our Help=3D desk on +44 (0)20 7821 3859 / 2105 or email
inet.hqhelpdesk@xxxxxxxxxxxxx T=3D his e-mail and any attachments =
thereto
may be subject to the terms of any a=3D greements between Invensys =
(and/or
its subsidiaries and affiliates) and the=3D recipient (and/or its
subsidiaries and affiliates).
=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: //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: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
