PARAMETRIZATION SYNCHRONISATION

[riccardo.crociani]

Hello,

we use WinCC OA 3.11 with a 2x2 architecture for the Disaster Recovery.
We have setted up a synchronization from PSS (Primery Server System) to SSS (Secondary Server System) every 20 minutes by the standard winccoa panel ( sync_panel.png).



If we activate (or deactivate) the alert of a datapoint by the function dpSetTimed(time t, string dp1, bool value) with t=0 we expected to not see any configuration exchange in the next synchronisation file from PSS to SSS, but we find it.
This beaviuor in some conditions generates a new alarm in the alarm page of the SSS that will be not automatically acknowledged when the alarm on the PSS is acknowledged.

Did we misunderstand the function dpSetTimed with t=0 :S ?

Is there any way to avoid that a specific dpSet goes into the export file for the synchronization ?

E.g.
the command dpSetTimed("0", "CT1:F001000XXXXX_X_X_XXX_XXXXXXX_MFXXX01.VALORE:_alert_hdl.._active", 1)
produces the export "paraSyncPSS_2015_05_20_14_40_00.dpl"

[leoknipp]

Hello,

the idea of the disaster recovery system is to have identical system in both redundant projects.
When using dpSetTimed(0,...); instead of a normal dpSet(); no entries in the configuration history are saved.

This function cannot be used to avoid that the configuration is synchronized.
It is not possible to make changes at the configuration without synchronizing them to the other system.

Best Regards
Leopold Knipp
Senior Support Specialist

[riccardo.crociani]

Thanks for the clarification.

Best Regards
Riccardo Crociani