User Manual

Programming and commissioning

Programming tool: SAPRO

24 | 38 A6V1127616_en--_a

● Strategy 3: ApplicationSave depends on the COV (change of value) of any

object member. The function block DB_ApSave_MbrChg pre-installed in the

basic template, can implement this strategy.

Note: Applying this strategy to counter-type objects may trigger too many write

cycles. We recommend a trigger with timer.

● Strategy 4: ApplicationSave can be scheduled by timer in the application using

block SysCtl_ApSave available in the xLibCAS\Universal\System\xAux (already

instanced in the basic template).

Notes:

After connecting the controller to Climatix IC for the first time, an ApplicationSave

must be performed, in order to permanently store the Climatix IC secret code in the

controller. The controller is otherwise unable to reconnect to Climatix IC after

power failure.

If the controller loses connection to Climatix IC after power failure, un-assign and

re-assign actions to be performed again. Ensure that the Climatix IC secret code is

stored in the controller.

Example of ApplicationSave: configuring IO type

Use ApplicationSave for persistent storage of the configured IO configuration. See

example below: