Commissioning > Synchronization

It is possible to synchronize calendars and scenarios between polar bears. For example, to keep both projects in master / slave operation on the same status for switching times and scenarios.

For the synchronization to work, the calendars or scenarios must have identical channels. Since IDs are used internally in the program, we recommend copying the project after creating the calendars or scenarios. It is also possible to export and import the components as ScadaComp. In addition, there are export and import functions for the calendar to exchange the channel settings in the channel editor. For the scenarios, export and import is possible in the scenario editor.

If "export on change" is activated, the changes are sent to the other server every time the calendar or the scene is changed and imported into the calendar and the scene there.

Thesynchronization is realizedvia the data points XML text at the calendar and scenario components.

Name	Standard	Function
XML text output	Output	Output of the appointment data in xml format. This data can be sent to another calendar/scene(XML text import).
XML-Text Output Trigger	Input	Trigger input to output the appointments at the output"XML-Text Output" in xml format.
XML-Text Import	Input	Input to import the calendar entries/scenes as xml text. The data can come from another calendar/scene(XML text output).

The transfer between the EisBaer servers is done via text exchange. Synchronization is possible in both directions.

In the following example, an MQTT connection is established between 2 servers.