Here’s what more than 2,500 business decision-makers around the world say.Download the report
...with the Facility Hero app in hand! Discover how you can optimize your maintenance efforts today.Learn more
Access tailored services, 24/7 self-service and expert help. Anywhere, anytime, any project.Discover now
Everything you need to know about our IoT technology backbone.Learn more
Welcome to the Schneider Electric Global Website×
Goals and Symptoms
What cycle times are used for fields on application/alarm pages of XBT operator panels? Are these the same as for the dialogue table? What if you don't use the dialogue table?
Facts and Changes
Causes and Fixes
The communication is sampled at 400ms. The dialog table has priority. The requests to refresh variables are sent once the dialog table is over. In the case of the cycle time of the dialog table is under 400ms, only a few requests will have time to be sent between the dialog table. So, in case of a high number of variables to refresh, it is recommanded to set the cycle time of the dialog table > to 400ms to let time to send the requests.
The exchange principle also depends on the protocol chosen according to the type of PLC, and the category of variables to be displayed.
The XBT optimizes the refresh of variables by categories:
Types of variables: Word, doubleword, bit,...
Under types: Word bit, input bit, ...
EQUIPMENTs: Master, PLC, ...
Group: Init variables group (min, max), Cyclic variables group (Read or Read-Write refreshing fields)
Priority: Normal (variable in application page), Fast (Dialog table variable).
In order to optimize the refreshing of variables, when building a page, by category, the variables adresses should be consecutive.