Main Features Controls Space Temperature in a Zone Optimum Start and Stop Control DIN-mounted with On-board Outputs to drive plant directly All standard driver options available Selectable as Master or Slave Zone

Summary Features

General

This product is based on the standard Slave Zone Controller code but is housed in a DIN rail mounted module and therefore has its own triac outputs to drive plant directly without requiring submodules. A version with two analogue outputs with isolated 0-10v signals is also available. The controller supports all the standard Slave Zone Controller features plus it has three triac outputs and therefore most of the standard driver options are available (see product codes later).

Note that there is no display so it is important the system is designed such that the Occupation time profiles can be set up and changed, this could be from a master Zone controller or from Doorway, InSite or the smartServer products.

The controller must have at least one temperature sensor fitted. Support is provided for network based Temperature or Temperature+RH sensors as well as the standard thermistor sensors wired directly to the controller.

As per the standard Zone and Slave Zone Controllers the DIN-mounted version supports the following features:-

2 Time Periods per Day; 7 Days per Week

Special settings for Today and Tomorrow

Holiday Period Feature

Independent Optimum Start function

Inputs for temperature sensors or Occupancy Override signals

Can use temperature values from other modules for control

Fabric Protection using temperature or Relative Humidity

Can be used to supervise the operation of other plant

Condensation control for Chilled Ceilings

Description of Features

Primary Control Functions

The controller is designed to control a space temperature to a heating setpoint (occupied setpoint) and optionally to a cooling setpoint if the setpoint deadband (SPDB) parameter is set. The heating and cooling demands are passed to the output drivers which can be setup to control heating and cooling valves. A pump or fan output can also be used.

The heating and cooling demands are also sent to the heat and cool source for the zone (set on HTSC and CLSC) to bring on the requisite upstream plant.

The controller provides optimum start and stop for both heating and cooling.

Temperature Control

Optimum Start

The Occupation Time periods define the times that the building or zone will be under temperature control and suitable for occupation.

The Controller will bring on the heating services or HVAC system for a boost period before the beginning of the occupation period to bring the building to the required temperature. The boost period is varied depending on both the zone temperature and the outside temperature in order to bring the zone just up to the required temperature by the beginning of the occupation period. This feature is known as optimum start. By changing the boost time, energy is saved as the plant does not run longer than actual conditions require, the Zone Controller adapts the parameters in its optimum start algorithm so it learns the characteristics of the building and of the services plant.

The Zone learns different characteristics for heating and cooling modes because the plant will have different characteristics in each mode.

Two Parameters can be adjusted to affect Optimum Start; MXOS is used to limit the length of the boost period. With undersized plant, it may not be possible to reach the Occupied Setpoint on very cold days without an excessively long boost period, so the length of the boost period may need to be limited.

The OPTE parameter may be used to allow the Optimum Start algorithm to aim for a setpoint lower than the Occupied Setpoint. This is useful where a step change in heat gain occurs at Occupancy Start, due to lots of people entering the space (e.g. schools) or equipment being turned on - the use of the OPTE parameter can prevent temperature overshoot under these conditions. It is also useful when using Fan Coils with a standby mode.

Optimum Stop

The services for a zone can often be turned off before the end of occupation without the temperature falling outside acceptable conditions. The optimum stop control algorithm calculates how long before the end of occupation the services can be switched off based on zone temperature, outside temperature and its learned characteristics of the building.

The maximum optimum off period is preset to 2 hours configurable by MXOF. Setting the parameter of 0 disables the optimum off function which is the preset. Note that the optimum off function turns off the heating or cooling only . Fresh air and ventilation plant would continue to run until the normal end of the occupation period. The target temperature for optimum off can be offset from the Required Temperature by setting the configuration parameter SBDB - preset to 0°C. When Optimum off is invoked the control deadband is increased to the standby deadband SBDB.

Required Temperature

Unlike the standard pattress-mounted Zone and Slave Zone Controllers which provide local display and adjustment of the required temperature (current occupied setpoint), the setpoint in the DIN-mounted Slave Zone can only be adjusted via a PC running InSite or Doorway; a smartServer; or by being setpoint-supervised by a standard Master Zone Controller.

Adjustment Range

The total Adjustment Range of the Required Temperature is limited to prevent it being set to unacceptable conditions. The Adjustment Range is preset to 5°C about the range midpoint temperature which is preset to 20°C. The Adjustment Range and Midpoint can be set by configuration parameters, SPRG & SPMD.

Required Temperature Reversion

At the beginning of each day the Required Temperature reverts to its Default value so that any changes made the previous day are lost and the control returns to an energy efficient default. The Default temperature can be configured to be anywhere within the Adjustment Range and is preset to 20°C (configuration parameter SPOC). The Required Temperature Reversion feature can be disabled by setting the configuration parameter SPDF to 1.

Heat - Cool Control

The Controller has the ability to control cooling as well as heating. It can drive plant directly using its on-board outputs or it can work through separate plant controllers and submodules for both heating and/or cooling.

It is normal to set a dead band between the heating and cooling functions to allow the temperature to float between the two modes which will improve energy efficiency. The dead band is configured by the SPDB parameter. It is preset to 0 which disables the cooling control loop. Setting between 1 to 10°C enables cooling control and sets the cooling dead band.

Standby deadband

Parameter SBDB defines an additional amount of deadband to be applied when the controller is in 'standby mode'. This is used for Optimum off (see previous) and also on some specialised applications involving the use of external occupancy devices (e.g. PIR sensors).

Fabric Protection - using Temperature

During the occupation period the controller controls to the Required Temperature. Outside the occupation period, the controller will become 'occupied' and bring on the services if the temperature falls to the Fabric Protection Temperature in order to avoid condensation forming.

The Fabric protection temperature is set on parameter SPNO and is preset to 10°C.

Once the Fabric Protection algorithm has been initiated it will bring the temperature up by the Fabric Rise Temperature in order to avoid the plant cycling ON and OFF. The Zone remains in this mode until the temperature has risen by the amount specified by the parameter FRSE at which point the Zone Controller reverts to non-occupied setpoint as before. If a stable temperature is required during non-Occupancy (e.g. night setback for a nursing home) then SPNO can be set to the appropriate value and FRSE can be left set to the factory default setting of zero.

During fabric protection AHU's and Fan Coils which are controlled using Occupancy can be prevented from starting with the use of Occupation Only OCCO config variable.

Fabric Protection - using Relative Humidity

If a Networked T+RH sensor is registered to the Zone Controller, the Humidity value may be used for Fabric Protection; the Zone Controller can be made to bring on the heating to prevent RH levels rising above a predetermined level. The Zone controller will accept any flavour of TRH sensor Supply, Return or Outside - the TRH code must be version 2a or later.

The desired maximum RH level is set on parameter SPRH (Rh setpoint); setting a non-zero value will enable RH Fabric Protection.

If the RH is below the RH setpoint, the Zone will control to its normal non-occupied setpoint (set on SPNO) as for temperature-based Fabric Protection. As the RH in the space rises, the Zone Controller will increase its current setpoint (which can be read on Monitoring Parameter REQD) at a maximum rate of 0.1 degC per minute according to an integrating control action. As this temperature setpoint exceeds the current temperature in the space, so the heating will be enabled, raising the temperature and thus reducing the Relative Humidity. The temperature setpoint is limited to the normal Occupied setpoint for the zone (set on SPOC) thus providing a high limit for space temperature.

The RH value can be monitored on InSite or Doorway as Sensor 6. The value can also be plotted by changing the controller's default plot routines. Also note that setting parameter SACT=5 the controller's temperature value is also replaced by the Networked sensor temperature value.

Do not register more than one networked sensor to the controller at any one time, the controller will use the last value received, a symptom of this is the displayed value jumping between two or more values.

Frost Protection

The controller is made aware of the Frost protection status of the Boiler Controller. If the Boiler is in Frost protect this is communicated to the controller which will drive its outputs to 50% open and start any optimum start/stop switched loads. The controller remains in non-occupied to distinguish this mode from Fabric Protection.

Master/Slave selection

These controllers will be extensively used to control direct fired unit heaters. In large bays multiple heaters will be used to heat the space, Master slave relationships between controllers needs to be setup to provide coordinated control.

This could have been done by producing a Master version of the Zone Slave DIN controller, but this would require complete definition of controlled areas and master / slave numbers before the project was installed.

Additional functionality has been added so that controllers can be selected as masters by setting a software switch MMDE (Master Mode). With this switch set the controller behaves like a Master Zone and Setpoint supervision and Time supervision links can be made to any number of other Slave Zone Controllers. When this switch is changed to Master Mode, the Master Zone number (C121MZON) used by InSite and the WebServer to construct the system structure is reset to zero, as is the group reference in the address table thus breaking any previously made slaving links.

External Interlock

The options available for the additional sensor input has been extended, SACT 7 now allows for a delay timer before the AND interlock becomes active, the timer is setup on config C27 IDLY, Interlock Delay is set in minutes.

External pushbutton for intelligent Override

An additional setting SACT 9, allows the external input to be wired to a normally open pushbutton. Closure of the pushbutton for at least 10 seconds, use a ‘slow release’ light switch, will toggle the occupancy state of the controller, equivalent to pressing the override button on a normal zone. This is provided to allow for exceptional working situations.

Heating Disable

An additional setting SACT 10, allows the heating output only to be disabled using the external input. The controller remains active but the heat demand is disabled if the interlock signal is open circuit. The Interlock delay C27 IDLY can also be used with this feature.

Heating Output Limit

An additional configuration parameter (C105 MXHT) allows the maximum output of the controller when in heating to be limited. This was introduced to enable the control of certain radient heaters which should not be run continuously.

Hours Run

This feature allows the integrated heating and cooling demand to be monitored. The data is presented on C123- C124, HRSH -HRSC and provides the %*hours/100 since last reset. The outputs are checked every ten seconds, the data is provided to the nearest tenth of an hour. The total can be reset or set to any other value by writing to the configuration variable

Fan or Pump Interlocks

A single parameter for each driver type is provided which sets up the on delay or run on time for the fan or pump.

HDLY :-

• if negative sets the on delay in minutes for the fan or pump

• if positive sets run on time in minutes for fan or pump to run after heating shut down

Typically negative values will be used for wet applications to provide start up protection against frost and positive (run on-) values would be used with electric heating applications.

The same features are available for cooling using CDLY.

Two Pipe Control

When used in conjunction with Heat Source HSCVT4d1 or later as its Heat Source the controller now allows for Two Pipe heating and cooling. The Heating Secondary Controller must have a temperature sensor connected to the Flow side of the two pipe system so that it can broardcast the medium temperature to all it's registered consumers. The 4d1 range of secondary controllers also allows for interlocks between heating and cooling versions so that the medium can be controlled (see issue notes).

A new configuration variable TPSL Two Pipe SeLect must be set to 1 to enable this feature. (The minimum output feature MNOP has been removed). Remember the SPDB SetPoint DeadBand also needs to be set to enable the cooling control.

The Heating demand to the actuator controller will carry the Cooling Demand if the temperature of the medium is at least 1 degree less than the controller mid point setpoint. Normal Heating is resumed if the Flow temperature of the medium is at least 1 degree above the controller mid point setpoint.

Occupancy Control

Time Schedules

The user can set the times that the Zone is to be used - called occupation periods - by setting the time schedule. This allows 2 occupation periods per day and different settings for each day of the week.

Preset times are

• One occupation period: 0830 to 1700 Mon - Fri

• No occupation: Saturday & Sunday

System Clock

All Zones share a common system clock function so on multi zone systems it is only necessary to set the clock and day on one zone - all the other zones will receive and use the updated time and day.

The Real Time Clock (RTC) is located in the System Housekeeping Module and this module broadcasts the time information over the network every minute and this is received and used by all modules that require this information. If the Zone Module fails to receive the time update - (for instance if the System Housekeeping Module is disconnected or is in configuration mode when it will not communicate) then the zone will automatically switch to use its internal software based clock until the time signals are restored.

Setting the System Clock

The system clock can be set from any pattress-mounted Master Zone Controller; or from a PC running Doorway or InSite; of from a smartServer.

Setting the 7 Day Time Schedule

As there is no display it is important the system is designed such that the Occupation time profiles can be set up and changed, this could be from a Master Zone controller or from Doorway, InSite or the smartServer products.

To skip an Occupation Period

The controller will skip an occupation period if the start and stop times are set the same. The default times are to skip the second occupation Monday to Friday (preset to 24:00) and both periods Saturday & Sunday (preset to 00:10).

Today & Tomorrow

The time periods for today and tomorrow can be set to be different from the normal 7 day time periods but they are volatile and the system will revert to the normal 7 day time periods when they are over. This is useful for unusual events (e.g. late working, or early starts) which are not repeated every week. Once again this must be from a Master Zone controller or from Doorway, InSite or the smartServer.

Master Override

This feature is only available on Master Zone Controllers. When set any change in the Override settings initiated by pressing the Override button on the Master controller will be sent to all Slave Zones. The Slave Zones must be issue 4c or later for this to work.

If the Slave Zone is time slaved to a Master Zone Controller which has MOVR Master Override set, then changes to the Override state of the Master will be reflected in all the slaves controlled by that Master.

Occupancy Override

The Override button can be used to toggle between Occupied and non Occupied in the same way as on the Patrass version.

Holiday

The controller can be set to Holiday Mode which is the number of days holiday period starting from the following day. Occupation periods can be set for holiday (for cleaners etc.); the preset value is for no occupation period.

The number of days holiday becomes active tomorrow so looking at the number of days set does not specifically indicate whether the controller is in holiday mode, similarly on the last day of the holiday period the holiday setting will show zero but the controller will still be in holiday mode.

If the holiday setting is set to zero the holiday mode is cancelled. If the Holiday process is active then the standard occupation pattern is loaded for today otherwise the current today's times are retained.

If MHOL Master Holidays is set then any change to the holiday settings will result in these settings being sent to all Zone / Slave Zone Controllers and DHW controllers on the whole system. It is advisable to only activate this feature on one controller on the system. Similarly setting HDAY to zero when MHOL is set will cancel any Holiday setting throughout the system.

From issue 4c1 the number of days holiday is sent to all slave zones, or to all zones if MHOL is set. Changes to the holiday settings are sent after a 30 second delay, to give the user time to complete and check the change.

Extended Holiday features

The range of the Holiday features when changed from the network has been extended to 500 days. Also a special value for HDAY -1 allows the Zone to be put into Holiday (unoccupied) mode for ever.

Two addtional configuration variables have been added C168 RDAY RunDays and C169 SHOL StartHolidays. The operation of these parameters is quite complicated and it is intended that they are only changed by the smartServer. In essence Start Holidays provides a daily countdown to the start of a non occupied holiday period the length of which is defined by HDAY. RunDays provides for a number of days of normal occupation after which the Zone will become permanently not Occupied. Using these two values and HDAY the smartServer is able to set any length occupied or unoccupied period for any time in the next year.

If trying to recover from mis-set parameters set RDAY and SHOL to -1 (OFF) to disable the feature.

External Control of Holiday settings

If SACT=8 then the external contact input is used to set the Controller into and out of Holiday mode. This contact can be wired to a security system or other Home Automation Controller. The logic used allows subsequent setting of expected arival date using the normal Holiday setting.

When the contact changes from open circuit to closed circuit the Holidays setting is changed to -1 or OFF, providing permanent Holiday mode.

When the contact changes from short circuit to open circuit, if HDAY is still -1 then it is reset to 0 No Holidays, otherwise no action is taken. This allows for HDAY to be changed in the intervening period to represent the expected arrival date so that the building can be brought back up to temperature prior to arrival.

Registration

The controller can be used in several different ways, for controlling the zone temperature directly, for supervising other controllers in various ways, or for demanding services from other controllers. Some of these features are mutually exclusive, whilst some can co-exist at the same time.

The various forms of Logical Links between this controller and other controllers are made by the process of Registration; a brief description of the process is given below. For a full description, see our Design Guide publication.

Address Allocation

Before any Registration Links can be made, the controller must be allocated an address by the System Housekeeping Module. The Register button is pressed; the controller should indicate its address by flashing its status LED. The number of flashes indicates the zone address number.

Submodules

The controller may have up to 8 Submodules (e.g. Actuator Submodules or Pump Changeover Submodules) registered to it. The controller is put into Configuration Mode and the Submodule is registered to it. This sets up the Submodule’s address (which will be of the form Zn Am , where n is the zone’s address, and m is the Submodule’s address).

The registration process also makes Control Demand links between the zone and its Submodules, so that they will respond to Occupancy and Heating/Cooling demand signals from the controller as appropriate.

Networked Sensors

The controller may have a Networked Sensor registered to it; either a Condensation sensor, a Networked Temperature sensor, or a Networked Temperature + Relative Humidity sensor. Only one sensor may be registered to a zone. The zone is put into Configuration Mode and the Sensor is registered to it. To make the zone use the networked sensor in preference to a hard-wired sensor set SACT=5.

Demand Links

These links are Many-to-One links made from this zone (and perhaps many others) to a Module that is providing a service to the Zone (provision of Fresh Air, Energy or Domestic Hot Water services). They can each exist with any other links simultaneously.

Energy Demand

The controller can send its Energy Demands for Heating and Cooling to another Module (a Distributor Module, like a Secondary Circuit Controller or Provider Module like a Boiler Controller) if that Module is responsible for providing energy to the zone. The Distributor/Provider Module is put into Configuration Mode, and the Zone is registered to it. This sets up the HTSC or CLSC parameters in the Zone to “point” the Energy Demands at the appropriate Modules. Energy Demand linking can be used in conjunction with any other links at the same time.

Heating Demand - Constant Temperature

Parameter HTCT if set to a non zero value defines that the controller should send a CT setpoint instead of the normal percentage demand. The value set is the Constant temperature value which will be sent to the Heat Source.

Occupancy Demand
The Occupation state of the zone can be passed to an AHU or DHW Controller using Occupancy Demand linking; this is for plant which provides a service for many zones (e.g. Fresh Air plant). The Target Module is put into Configuration Mode, and the zone registered to it. This sets up the Occupancy Destination parameter OCDS to “point” the zone’s Occupancy Demand at the target, which will then run when the zone (or any other zone thus registered) is in Occupancy. Occupancy Demand linking can be used in conjunction with any other links at the same time.

Supervision Links

These links are One-to-Many links made from this zone to one or many other Modules. The controller will supervise the behaviour of these other modules in some way; either their Setpoint or Occupancy Status (i.e whether they are On or Off). The controller can only have one of the 3 types of link with any given Module, but it may have links of each type with several different Modules concurrently (e.g. it can supervise the Setpoint in an AHU Controller, and send Occupancy Status to a Fan Coil Controllers at the same time).

Setpoint Supervision

The controller can be used to transmit its Setpoint to another Module (e.g. an AHU Controller) or to many other Contollers (e.g. Fan Coils).

Parameters in the Supervised Modules will need to be set (typically their SPTY parameter -see appropriate Data Sheets for details).

The controller is put into Configuration Mode, and the target Controller(s) are registered to it.

AHU Controllers thus supervised would normally run to the zone’s setpoint during Occupancy, and will turn off during Non-Occupancy. If it is desired to run the AHU during Non-Occupancy (i.e for 24 hours) but at a different setpoint, the parameter NOSV may be used ; if set to a non-zero value, this will keep the AHU running at the desired setpoint.

• WARNING this same setpoint is sent to any other devices which are registered to the zone (FCU's etc) so a separate zone will probably be needed to supervise plant which needs to run continuously.

• WARNING this method only really works for heating only (or cooling only) AHU's because if the AHU has cooling it will cool to the new setpoint if the outside is warmer which is probably not what was intended.

• BONUS for sites which require 24 hour operation the NOSV can be set to the same value as the normal setpoint and the AHU's will not stop for 10 minutes at midnight.

Occupancy Supervision:

The controller can be used to transmit its Occupancy Status to many other Contollers (e.g. Fan Coils). This mode of linking can be used instead of Setpoint Supervision to drive Fan Coils on and off, but leave them controlling to their own setpoints. The controller will be responsible for Optimum Start and Fabric Protection.

Parameters in the Supervised Modules will need to be set (typically their SPTY parameter -see appropriate Data Sheets for details).

The controller is put into Configuration Mode, and the target Controller(s) are registered to it.

Multi Domain operation

This is only used on large systems where there are more than 100 zones. Most of the multi-domain features are hidden from the user and involve the controller differentiating between local communications and system wide communications. All communications between the Zone Controller and it's Actuators and Slave Zones or Fan Coils takes place on the local domain. Heat and cool demands other than to the Floor Controller for this domain are sent globally so that the Zone Controller can send demands to any Heat or Cool source on the system. The Controller is fully backward compatible and may be used on single domain systems.

There is one exception to this where Zones are registered to pre-issue 4 Floor controllers, in this case the method the Zone uses to determine whether to utilise dual domain fails, to provide backward compatibility on these systems a new config variable has been introduced ISS3, set this variable to 1 to force single domain operation.

However Controller issues should not be mixed on one system where many zones send demands to a single heat source and the advanced number occupied, or average demand features are being used. This is because the heat/ cool demand update rate has been reduced both to allow more controllers to fan in to one device and to reduce unnecessary network traffic. The actuator control signals are also not sent unless some actuators are registered to the node, this means after replacing a zone you must either rebuild the zone registration table with the re-build option or re-register it's actuators.

Where mixing controller issues is unavoidable, e.g. upgrading Zone Controllers on an old site this issue now allows the fast updating of heat/cool demands, to match pre-issue 4 Zones, to activate this function set ISS3 to 1.

Temperature, RH and Occupancy Inputs

Conventional Thermistor Sensors

The unit can be connected to one or two remote temperature sensors which are conventional, low cost thermistor types. The sensor action parameter SACT can be set so the controller uses the higher, lower or average value of the two sensors. If one sensor fails the control will continue on the other sensor alone.

Because they are standard 10K ohm thermistors, 4 can be wired in series/parallel configuration to provide electrical averaging of 4 sensors. Thus up to 8 sensors can be wired to the controller.

Intelligent Networked Sensors - Temperature

A SeaChange Intelligent Networked Temperature Sensor (which has its own Microprocessor and derives its power from the network) may be registered (as a Submodule) to the controller. This type of sensor has the advantage that it may be located anywhere on the network, and so may provide installation benefits because an additional cable may not need to be run between the zone and the sensor. The parameter SACT must be adjusted accordingly to make the controller use the Networked Sensor value as its Process Variable in place of its own thermistor. Control will revert to a hard-wired thermistor (if also fitted) if the Networked Sensor reading is invalid.

Intelligent Networked Sensors - Temperature + Relative Humidity

A SeaChange Intelligent Networked T + Rh sensor connected somewhere on the network may be registered (as a Submodule) to the controller. The parameter SACT must be adjusted accordingly to make the controller use the Networked Sensor Temperature value as its Process Variable in place of its own thermistor. Control will revert to a hard-wired thermistor (if also fitted) if the Networked Sensor reading is invalid.

The Relative Humidity may be used for Monitoring only, or it may be used for enhanced Fabric Protection using Rh control - see Fabric Protection.

Send own Temperature

When a controller is registered to an AHU controller which is set to SPTY=2 then the zone's temperature reading may be used as the Return temperature reading for the AHU. The AHU might have many zones registered and might also be using an intelligent TRH sensor for its Return temperature reading. To allow for these cases the Zone code has been changed so that sending the zone temperature needs to be enabled at the zone using configuration parameter SNDT. Do not set this if :- (a) the AHU is using TRH sensor for Return Temperature; or (b) if multiple zones are registered to the AHU in which case only set SNDT on one representative Zone. If you see the Return temperature cycling between one or more values then check SNDT on any registered zones. SNDT is 0 (OFF) by default.

Sensor Action

The parameter Sensor Action SACT allows considerable scope for combining hard-wired and networked sensor values. The min, max and average options will use all the sensor values which are valid so for example the minimum value would be the minimum of hard-wired sensors and a networked sensor if all were being used and were presenting valid readings.

It is sometime difficult to find a sensor position in a room which is not subjected to direct sunshine at soem time in the day. To overcome this two sensor can be fitted on opposite sides of the room and SACT set so the controller uses the minimum of the two sensors, i.e. the one that is not in the sun.

Sensor Calibration

The sensor calibration can be trimmed using the SCAL parameter. This provides a fixed offset to the temperature measurement and applies to the resultant temperature - after selection of remote, average, etc. functions using SACT parameter. Sensor calibration is preset to 0°C.

Switch Inputs

Remote Occupation Status Input

A Volt-Free Contact (VFC) may be wired to the external input connections to provide external control over the Occupation Status of the controller.

Occupancy/Non-Occupancy Switching

One of the input connections can be configured using SACT=4 to be a remote input to provide occupation override. This has been implemented as an OR function with the controller's own time schedules so this feature could be used as a secondary function say from a PIR sensor or sound sensor in addition to occupation periods set on its 'occupation times'. This uses a contact closure (volt free contact) to drive the zone into the occupancy state if it currently is not occupied, but will not alter the occupancy state if the time schedules etc have already put the zone into occupancy. This feature can be used to drive a zone into occupancy using an input from a simple switch, another item of plant, or a Presence Detector or Card Access Controller. Note that any timed on period should be part of the presence detector function. The controller will remain occupied as long as the input is maintained and will revert to Non-occupied directly the signal is removed.

If the external source is to be the only occupation signal then disable the inbuilt time schedule by setting all days to no occupation. The state of the external signal can be monitored on parameter XOCC.

If SACT=7 then zone Occupancy AND an external signal must be true for the zone to enter Occupation. This allows override OFF into non-occupied to be set with a switch or interlocked with other equipment in the panel.

Occupancy/Standby Mode Switching

The input connections can also be configured using SACT=6 to be a remote input to provide Occupation/ Standby Mode switching. This uses a contact closure (volt free contact) to drive the zone into the occupancy state if it is currently outside of its Occupation Times. If the Zone is in its normal Occupancy period, with the external contact open circuit, it will be running in Standby Mode (i.e with a wide deadband set on parameter SBDB).

When the external contact closes, the zone will be driven into its normal Occupation Mode (with a normal close deadband set on SPDB). This feature can be used to drive a zone into occupancy using an input from a simple switch, another item of plant, or a Presence Detector or Card Access Controller. Note that any timed on period should be part of the presence detector function, the Zone Controller will revert to Non-occupied directly the signal is removed.

When in Standby mode the REQD parameter will display the current setpoint. Adjusting the setpoint will change the Normal Occupied Midpoint as normal.

Condensation Control

The controller can control condensation in Static Cooling (Chilled Ceiling and Chilled Beam) installations, where condensation can form on the cold surfaces of the ceiling if the ceiling temperature is allowed to fall below the dewpoint of the surrounding air. This phenomenon is sometimes referred to as “Office Rain”.

A SeaChange Intelligent Networked Condensation Sensor must be registered to the controller (the sensor can be connected anywhere on the network).

If the Condensation Sensor reports a condensing condition, the controller will progressively ramp down its Cooling Control demand signal, and hence start to close down its outputs or any registered Actuator Submodules, which would be controlling the Cooling Valve on the Chilled Ceiling. An alarm can also be generated; see Alarm Handling and Display.

As the condensing condition clears, the controller will resume normal control; thus a simple form of local Dewpoint Control has been created. The Controller will allow the Chilled Ceiling to run as cold as possible whilst preventing condensation, which will ensure that the maximum possible cooling output is derived from the ceiling.

If the Condensation Sensor fails to respond or becomes disconnected during a condensing event, the controller will recover normal operation within 7 minutes, until the sensor is re-connected.

Alarm Handling and Display

The controller can generate alarms, and can also respond to alarms sent by other Controllers. If it receives an alarm, it can be set to take some control action.

Alarm Generation

The controller can generate 3 different alarms, which can be reported at Doorway or InSite.

Alarm Control Action

The controller can be set to react to alarms in different ways; the ALRM parameter can be set to ignore alarms, to report alarms but take no Control Action, or to shut down its control outputs (and also any registered Submodules’ outputs, e.g. Actuator Submodules) - either because of an internal alarm, or because a System STOP alarm has been received.

Alarm mode ALRM :-

Accessing Configuration and Monitoring Parameters

Configuration Parameters are used to adjust settings from their factory defaults; Monitoring Parameters are mostly used to monitor internal readings (such as temperature readings) during the Commissioning process.

This Module’s Parameters may be viewed, and in the case of some parameters, adjusted by one of two methods; Either by using a Master/Slave Zone Controller with display, or by using the Doorway or InSite.

Using a Zone Controller with Display

1. The controller must be connected to the network and registered (see Commissioning Guide for further details).

2. Put the Zone Controller with Display into Configuration Mode by depressing Select and Override buttons for 10 seconds, until the CNFG legend appears on the display.

3. To view Parameters in this controller (the target device), press and release the Select button.

4. Now hold down the Select button on the Zone Controller with Display, and rotate the rotary knob:
   clockwise to view Monitoring Parameters
   anticlock to view Configuration Parameters

5. When desired Configuration Parameter appears, release Select, hold down Override on Zone Controller with Display and turn knob to adjust the parameter (note; some Monitoring Parameters cannot be adjusted).

Using SeaChange Doorway:

Data Points may be added to a Doorway page to access/adjust any Configuration or Monitoring Parameter. Graphs of certain Parameters are also available. The code used to access this controller is Zn ,where n is the zone’s address number. The code for each parameter is shown in the Config Tables.

Further details of how to set up Doorway pages may be found in the SeaChange Doorway Manual, or in the online help facility supplied with SeaChange Doorway.

The PC running SeaChange Doorway can be connected locally via a Serial Adaptor Module, or remotely using standard High-Speed Modems; all Parameters can thus be monitored and adjusted remotely.

Manual Override

The controller has the universal manual control features introduced on other products, this allows manual operation from the override button and manual override from Doorway or InSite.

Manual Hand Control

When set, the controller output will be determined by the value set on the configuration parameter MANL. This may be changed between -100 full cooling output and +100 full heating output. This feature allows known demand levels to be setup to check that all the relevant demand links have been correctly made.

To activate, put a Zone Controller with Display into to configuration mode, press and release the select button on this controller then hold the select button down and rotate the knob clockwise on the Zone Controller with Display until the parameter HAND is displayed. Hold down the Override button on the Zone Controller with Display and set HAND equal to 1. Then display the MANL parameter which may also be set using the override button and the knob to set the required control output (positive for heating, negative for cooling). If it is important that a predetermined manual level MANL is used at the start of HAND mode, select and change the Configuration variable MANL before setting the switch HAND.

While in Manual Hand Mode the status led will fast flash. The value may be adjusted by holding down override and turning the knob. To exit Manual Hand Mode set HAND back to zero using the Zone Controller with Display.

Using Doorway add a point with the following syntax :-

[zn]W5(S)/hand/auto/12/10/C83(V) where n is the zone address number of the controller.

This will normally display as auto, then when clicked a dialog box will appear which will allow hand to be selected and the level adjusted, the point will change to hand when the controller is in Manual Hand mode.

Residential Defaults

When used on residential sites the default Occupation Times and the setpoint defaults can be changed by setting C122 RESD to 1.
The Times are set to 06:00 - 23:00 for Monday to Sunday, the following configuration defaults are also changed.

Options and Product Codes

Slave Zone Controller DIN Rail Mounting

ZSL / DIN / 3T / [driver option]

Driver Options

ZSL / DIN / AOP / [driver option]

Driver options

* using external Sontay relay module

SC Controls Ltd

PO Box313
Wadhurst
East Sussex
TN5 6JL

phone 08707 606040
fax 08707 606041
e-mail seachange@sccontrols.co.uk
http:// www.seachange.co.uk