Re: [foxboro] Block resource usage listing
- From: "Corey R Clingo" <clingoc@xxxxxxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Tue, 20 Apr 2004 09:17:25 -0500
OK, thanks for hanging with me on this. To summarize what I understand:
Devices involved Message
----------------------------------------
CP->all FCMs Multicast to initate
FBM polling
(CP waits a bit)
CP->FCM1 Request for data
FCM1->CP Data returned
CP->FCM2 Request for data
FCM2->CP FCM busy/not ready
(CP waits a bit)
CP->FCM2 Re-request for data
FCM2->CP Data Returned
CP->FCM3
....and so on. Next BPC starts all over again.
I presume this is different from the older CPs, since as you mentioned,
the FBIs are not intelligent like the FCMs. I'm still not clear how this
impacts the CP60's idle time unless this waiting on the FCMs is counted
against it.
Also, does this imply that maybe one shouldn't have the full 4-baseplate
complement of 200-series FBMs per FCM?
Thanks,
Corey Clingo
BASF Corp.
"Johnson, Alex (Foxboro)" <ajohnson@xxxxxxxxxxx>
Sent by: foxboro-bounce@xxxxxxxxxxxxx
04/19/2004 05:55 PM
Please respond to foxboro
To: foxboro
cc:
Subject: Re: [foxboro] Block resource usage listing
One message to all FCMs in a BPC to initiate request of data from FBMs.
Generally, one request per FCM to retrieve data, but that could be off
esp.
on the first FCM. Since all FCMs are working in parallel, the other ones
should be ready by the time the first is complete.
Regards,
Alex Johnson
Invensys Systems, Inc.
10707 Haddington
Houston, TX 77043
713.722.2859 (voice)
713.722.2700 (operator)
713.932.0222 (fax)
ajohnson@xxxxxxxxxxx
For the latest information on ArchestrA, go to
http://www.invensys.com/Archestra.html.
_______________________________________________________________________
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: