User Manual

Working with Projects
2.4.3 Performancein theoperatorpanel
It is important to understand that due to the complex nature of a r unning system,
there are several things that affects the overall performance. The following list
gives some examples of things to consider, when it is necessary to optimize the
performance of the operator panel:
Number of tags
Number of sampled tags in trend viewers and data logger
Number of alarms
Driver performance
Multiple drivers
Type of panel
Alarm list size
Size of pictures
Scripts
RecommendedLimits
In order to optimize performance, it is recommended to limit the number of items
in the project. The recommended limits depend on the type of panel, and are
listed in the table below.
iXTxA/X2base
iXTxB/ iXTxBR
X2pro/X2
marine/X2
control/ X2
motion
iXTxC
PC
Tags 1000 2000 4000
ActiveControllers 3 10 Unlimited
Dataloggers 102550
DatabaseItems 50 700 2000
AlarmItems 150 500 4000
AlarmViewerRows 100 200 400
AlarmDatabaseMax. Rows 500 1000 4000
Screens 100 500 1000
ObjectsonScreen 150 400 500
Tags
Tr y t o a
void keeping the tag constantly active. If scripts are used, then hooking up
event
handlers on value change event will also set the tag to be always active. Use
the pa
ssive value change event when possible. The passive event will only trigger
when
the tag is active, and the tag can be deactivated when it is not in use. When
the
tag is deactivated the passive event will remain idle until the tag is activated.
The default setting in iX Developer updates all tags every 500 ms. If some tags
may be updated less often, it is possible to assign them to a poll group with a lower
update interval. Poll groups are configured in the Ta gs configuration page.
BeijerElectronics, MAEN831P
31