beautypg.com

Rockwell Automation 1757-SWKIT4000 ProcessLogix R400.0 Installation and Upgrade Guide User Manual

Page 276

background image

Publication 1757-IN040B-EN-P - March 2002

11-24 Performance and Capacity Specifications

† These numbers may be further limited by other restrictions noted in
this document.

Table 11.P 1757-FIM Performance Limits

FIM Performance Limits

Per FIM

Per Link

Per Device

Burst

Sustained

Burst

Sustained

Burst

Sustained

H1 Link Publication Rate (parameters/second, pps)

Assumes

50% of link schedule is usable for client-server messaging.

---

32‡

---

16‡

---

16‡

Client-Server Store Rate‡ (pps) [excludes publications from
ProcessLogix function blocks]

Assumes

50% of link schedule is usable for client-server messaging.

* This assumes that the FF device supports AlterEventConditionMonitoring, the ability
to suppress Update Events. Otherwise reduce by factor of 2.

40

10*

20

5*

4

1*

Max number of slow history points. ‡

All parameters must be in one view list per device or published.

‡ Assumes

50% of link schedule is usable for client-server messaging.

---

40

---

20†

---

20†

Max number of read-activities per second. ‡ (A read-activity
includes any or all of a block view list parameters or a single
non-viewed parameter.) [Includes all users such as slow history, SCM
connections to non-published parameters, Excel or OPC reads of
non-published parameters, etc.]

Assumes

50% of link schedule is usable for client-server messaging.

10

10

5

5

2

2

Maximum number of parameters read per second. ‡ [Includes all
users such as CM connections to non-output parameters (e.g. tuning
constants or limits), SCM connections to non-published parameters,
Excel or OPC reads of non-published parameters, etc.)

Assumes all parameters read are in view lists and the average number of parameters

read and used per view is 8; Also assumes

50% of link schedule is usable for

client-server messaging.

80

80

40

40

16

16

Maximum Alert Rate per second. (Alarm and Return-to-Normal
reports) ‡

Assumes

50% of link schedule is usable for client-server messaging and bursts are

up to one minute apart.

50

2

50

2

2

1

Maximum Number of Devices

32†

16†

---