TIMETABLES

REG System manages up to 8 weekly programs, called Timetables for simplicity’s sake.

Each Timetable determines, for any given moment of the week, the Working Mode, which can be:

• COMFORT

• ECONOMY

• OFF

The working mode determined by the day/hour of the current week is then communicated to the connected subsystems (which can only be Zones, DHW, CMV).

Warning

The timetables are only shown on the display of the REG or RegConfig if they are associated to a zone, DHW, or CMV, it is not possible to enable a timetable that is not associated with one of the listed subsystems!

If no timetable is associated, the Timetable page will be empty! 

For each Timetable, up to 6 transitions can be programmed for each of the 7 days of the week, therefore for a maximum of 42 variations in the week.

The programming of a timetable looks like this: (the data shown are examples only):

It is not necessary that all of the transitions of the day are set: the transition that are not required can be set to the special value “n/u” (not used): in this way, this range will be ignored.

Warning

It is necessary that the ranges of a certain day of the week are sorted according to time and that all the not used ranges are at the end of the day. If the timetables are set via REG-TFT or REG-DOT-B display, these automatically reorder the ranges conveniently; if, on the other hands, the set is made via LCD display of the Master or via PC, the user must ensure that the set timetables observe the given indications.

Each Timetables can also be forced to work in a certain working mode:

• Forced Comfort, all associated subsystems are in Comfort mode

• Forced Economy, all associated subsystems are in Economy mode

• Force Antifreeze (OFF), all associated subsystems are in Antifreeze/OFF mode

This operation suspends the application of the timetable program and determines the current working mode; the timetable program remains stored and is restored by putting the timetable back into automatic mode.

Note

The Zones, CMV, and DHW subsystems have their own forcing parameters; these are prioritized over the timetable itself and its forcing; for this reason, if the Zone (or the DHW subsystem) is force into a certain mode, the associated working mode given from the associated timetable will be ignored. The forcing function allows to use a timetable to set the working mode of several zones at the same time; imagine you have several zone that must be manually activated or deactivated, for example to host events or exhibitions; all the engaged zones can be associated to the same timetable; this timetable can be programmed to always be in OFF mode; when the air-conditioning activation is required, it is possible to operate on the forcing control on this timetable (for example by setting it to COMFORT) to activate all the engaged timetables at the same time.

The Associated Description allows you to specify a text identifying the timetable (see DESCRIPTIONS). The set text is shown on the displays and on all the system interfaces (app, web site www.s5a.eu) in order to help user identify the timetable they want to operate on. If no text is associated, the timetable will not be displayed on any interface.

Warning

The system does not prevent from associating the same description with several Timetables, but this is not recommended as it creates confusion during use; associate a unique and clear description to each timetable.

It is possible, by ticking one of the two white squares next to Hide on TFT/DOT, to hide the timetable on display 1 or display 2 (for example if the display 1 is on the day zone and the display 2 on the night zone, the timetable of the day zone can be hidden from the display 2 and the night zone timetable from display 1).

If both squares are ticked while having an associated description, the timetable will not be displayed on any interface (display, app, web), but only from RegConfig or directly from REG-DIN-8.

This is the case, for example, of the timetable used to manage DHW circulation pump, which you don’t want the user to edit (see DHW CIRCULATION MANAGEMENT).

OPTIMIZED TIMETABLES

If Optimized is ticked:

the timetable will follow the settings on Configuration 2:

so, depending on the season and the detected outdoor temperature (if no outdoor temperature sensor is installed, there is no point in using this function), it is possible to advance or postpone the set time ranges.

The minutes to be entered consider the sign, so if you enter –10 the timetable will be advanced, if you enter 10, the timetable will be postponed! If the measured outdoor temperature is between 0 and 10°C, for example, the delay or advance entered will be interpolated.