Feature
Notes

Configuration Tables

Wiring

 

 

Datasheet

 

Floor Controller
with 6 x Relay Outputs

 

FLR / DIN / STD / ...

 

Main Features

Registration unit for up to 200 Zones / Fan Coils

Collates Demand signals from all Zones / Fan Coils

Provides 6 staged relay outputs - 3 for heating and 3 for cooling demands

Heat Pump and Fan control.

Summary Features

General

The Floor Controller is used in larger systems (particularly those with many Terminal Units e.g. Fan Coils) because it contains System Housekeeping and can support Registration for up to 200 Zones.
The Floor Controller also provides a means of collating demand signals from the Zones; it will collate Energy Demands from the Consumer Modules (e.g. Zone, Fan Coil Controllers) and send them to other Modules (e.g. Boiler Controller, Chiller Controller or Secondary Circuit Controller). Alternatively the Floor Controller can use the highest demand to set either a heating or cooling setpoint and can thus be used to control dual duct air systems or hot and cold water distribution if the relevant sensors are connected. If no sensors are connected the Demands are used to drive the Relay Outputs directly, which may be wired to a non-SeaChange legacy system to demand-drive the main plant.
In very large systems (several hundred zones) multiple Floor Controllers may be used on the same system. In this case, the system needs to be divided into multiple Domains ; these are separated from each other by Routers. Each Floor Controller will perform Housekeeping Registration Functions for its local Domain; one of the Floor Controllers (the one with the lowest Domain number) will perform the other Housekeeping Functions (Real Time Clock, Outside Temperature) for the whole system.
The controller monitors and broadcasts Outside Temperature, either hardwired to 'input F' (terminals 15-16) or registered as an intelligent sensor. If an intelligent Temperature or Temp+Humidity sensor is used the Humidity value can also be monitored (on parameter S7 in the monitoring parameters).

Description of Features

System Housekeeping

A SeaChange system needs certain system-wide functions to be provided by a single Controller to ensure synchronisation, and to avoid conflicts. These functions are known as System Housekeeping Functions and can be provided by the Floor Controller.
Firstly, it contains the real-time clock, which broadcasts time-of-day and day-of-week information to any modules that may need it. The clock may be set from any Zone Controller, and the time information is backed up by a Capacitor, which means that the correct time is retained for a minimum of 8 hours in the event of power failure (providing that power has been applied for at least 1 hour).
Secondly, it performs an important role in the unique SeaChange registration process; it is responsible for the automatic allocation of system addresses during registration.
Thirdly, it broadcasts Outside Temperature to any other modules that may need it; it acquires the temperature either from a sensor directly connected to its input terminals 15-16, or from a Networked Outside Temperature Sensor.
Alternatively, System Housekeeping Functions may be provided by another SeaChange Controller (e.g. Boiler Controller, AHU Controller).
It is important that only one SeaChange Controller in a System provides the System Housekeeping Functions, unless the system is a Multi-Domain system where a Registration (Housekeeping) device is provided on each Domain (separated by Routers) but only the Housekeeper with the lowest Domain number provides the Real-Time and Outside air temp functions.

Demand Collation

Heating and Cooling demand, for all Modules sending to the Floor Controller are collated by the Floor Controller. These demand signals may be used to drive main plant which is not controlled by SeaChange via the Floor Controller’s output relays. There are 3 relays each provided for Heating and Cooling demand, indicating low/medium/high demand for each medium.
These sequenced outputs may be driven in one of two ways:
1) Maximum demand: the relays will be driven according to the maximum demand received for heating and/or cooling from the Zones.
2) Average demand: the relays will be driven according to the average demand received for heating and/or cooling from the Zones.
In addition, the relays can be inhibited from energising until a certain number of Zones are demanding heating or cooling. This prevents main plant being called to run for just one Fan Coil, for instance. The minimum number of Zones may be set to Zero, if this feature is not required.

Modes of operation

Driver Only, SPTY=1

Set parameter SPTY to 1. In this mode the highest heating demand received is passed to the Heating driver and the highest Cooling demand is passed to the cooling driver. The driver is configurable so a wide range of output options are available including Heat Pump control and Fan control.

Temperature control, SPTY=2

SPTY must be set to 2. This mode is used to control a common media, e.g. a single water supply for 2 pipe fan coils, based off the demands received from the consumer modules registered to the Floor Controller.
A temperature sensor must be fitted to input c and/or input d (terminals 9-10 and/or 11-12). These inputs are combined as max, min or average using SACT similar to other SeaChange products.
The controller becomes occupied if either the heating demand or cooling demand is greater than minimum demand as set on MIND.
The setpoint for the control is calculated from the MAXH, MINH config limits for heating demands and from the MAXC, MINC limits for cooling demands. Only one setpoint is calculated if both heating and cooling demands exist - the highest will be used. If the demands are equal or zero then a heating setpoint will be used.

Operation with Remote User Switch/Trim Pot or Interlock

A switch can be connected to input c (terminals 9-10), which when made will force the Controller to Occupied.
This is achieved by adding an extra config variable input mode INMD. The following values are supported.
INMD = 0
Feature disabled
INMD = 1
Occupied is External AND normal occupation (window contact)
INMD = 2
Occupied is External OR normal occupation (outside normal hours)
INMD = 3
Occupation controlled by external signal only
INMD = 4
Input used as an external alarm, alarm state defined by ALST
INMD = 5
(RiverMill Project Heat Pump fan speed switch)
If the switch is wired in series with a 1K resistor and a 10K potentiometer Occupied/ Non occupied plus a 5 degree trim (operational only whilst occupied) is possible. The trim is slightly non linear (the applied resistance is affected by the parallel resistance on the board which helps linearise the thermistor when fitted, mechanical centre position of the pot gives -0.7C). The zero point can be adjusted to give the correct (0 degree trim) by backing off any error using the software trim SPTR parameter. Suggest pot is marked Hotter/Colder or +/- .
A resistance between 0 and 20K ohm will be considered to be Occupied, non Occupied is guaranteed for resistance values above 100K. The voltage generated by the pot will be converted to a setpoint Trim only for control modes SPTY 0 or 1

Fan Speed Control

The controller will automatically control fan speed, if the multi-speed fan driver is used. If either the heating or cooling demand is greater than 90% for a period longer than FPRD (seconds/10 to match other periods) then the fan speed will be incremented up to the next speed. If both the heating and cooling demand is less than 10% then the Fan Speed is reduced after the same delay time. While occupied the controller will maintain a minimum of Fan Speed 1.
Provision is made for the fan speed to be controlled from a network variable (nviFanSpeed), from a (hotel style) zone controller for example, if this network variable is non zero then this will override the automatic fan speed control.

Interlocks

Setting HDLY negative sets the on delay in minutes for the fan or pump; and setting HDLY 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 batteries to provide start up protection against frost and positive (run on-) values would be used with electric heating batteries.
The same features are available for cooling using CDLY.

Occupation Only

The selection of OCC or OSS is now made by setting OCCO to 1 on controllers where the control is only required when the building is in occupation. The default (OCCO=0) is for control during OSS and OCC.

Frost Protection

This is defined with a config parameter FRPT and it defines the controllers action when it receives a 'frost alarm' from the boiler controller.
FRPT = 0
No action (default)
FRPT = 1
Heating output to 50%
FRPT = 2
Heating output to 50% and pump/fan enabled

Demand Signals

Heat/Cool Demand

Heat and Cool demands can now be sent to Heat and Cool sources within the Floor Controllers domain and also to controllers on other domains. These links need to be setup manually for the time being, until other controllers can be changed to recognise that the Floor controller now has this feature. Either change configuration parameters HTSC and CLSC to point to the required Target module using the values in the following table, or use the drag and drop engineering features of InSite.
Target Module
HTSC setting
CLSC setting
HSC
Heat Source number
 
CSC
 
Cool Source number
AHU
AHU number +50
AHU number +50

Occupancy Demand - Occupation Destination OCDS

The controller can send it's Occupancy state to any other module which supports receiving OCDS, at present that is AHU, DHW, HSC and CSC controllers. This enables the demand fan-in to be done in the Floor Controller which then sets say a Fresh Air AHU to run. To avoid the inevitable confusion regarding whether a heat/cool demand link or an OCDS link is being made this feature is restricted to manual setting of OCDS in the sending controller, the table sets out the rules for OCDS numbering. InSite can be used to easily setup these links using the drag and drop Occupation Demand Structure view.
Target Module
OCDS setting
HSC
Heat Source number
CSC
Cool Source number +25
AHU
AHU number +50
DHW
DHW zone number (maximum 100) +100

Alarms

The Floor Controller supports sensor fail SENF alarm, this is raised if the sensor(s) fail and the controller is in a mode which requires the sensor connections. The Input Mode INMD can also be set up to generate an alarm for either a short or open circuit.
Alarm mode and Alarm State config variables have been added to the config variable list.
ALRM = 0
Alarms ignored
ALRM = 1
Alarms reported no other action
ALRM = 2
Control output set to zero on alarm
ALRM = 3
STOP alarm recognised, control set to zero
Alarm State ALST determines which input state 0 or 1 is considered to be the alarm condition when using an external VFC input for the alarm as set by INMD.

Submodule Registration

Will support registration of up to ? Actuator or Pump Changeover Submodules.

Doorway codes

Floor Controllers are addressed with [H1].
Submodules are addressed as follows:
Actuators [H1Am] where m= submodule number 1 to 8.
Item codes follow the normal conventions.

Options and Product Codes

Floor Controller

FLR / DIN / STD / [option]

Options

Option

 
/ 001
Standard version

 

 

Input Configuration
Input 5-6 ‘input a’
tba
Input 7-8 ‘input b’
tba
Input 9-10 ‘input c’
tba
Input 11-12‘input d’
tba
Input 13-14‘input e’
tba
Input 15-16 'input f'
tba

 

Multiple Domain Systems

On Larger installations where several hundred modules are used, the system can be divided into separate subsystems to extend the capacity of the modules on the network.  Routers are used to partition the system into smaller sub-systems called Domains.  Up to 8 Domains can be used extending the capacity of the system to 1500 Zones .

Each domain has its own registration device (e.g. a floor controller, boiler controller or an AHU controller).  The registration devices are responsible for allocating addresses to the modules in their own domain.  The system housekeeping function will automatically be performed by the registration device with the lowest domain number; the lowest domain is responsible for passing the outside temperature and real time clock to other domains on the system. 

  Floor Controller Boiler AHU
Zones/Fan Coils 200 100 80
AHU 10 50 40
Sec Heat sources 10 20 5
Sec Cool sources 10 20 5
Monitor nodes 10 25 5
SLT 4 8 4
Router 4 0 5

Subsystems

Each Subsystem has it's own local System Master (SSM) which must be located on the sub system side of the router. The routers block local SubSystem traffic from propagating on to the back bone. The local traffic consists of all Zone to Actuator, Zone to Fan Coil messages, thus Fan Coils can only be supervised within their local Subsystem.

Domain Numbers

The SubSystems are given domain numbers, which must be setup on the registration device (configuration parameter DOMN). This must be done before any modules are registered to the SSM. The domain number can be set between 0 and  8. The Controller defaults to Domain one. Selecting Domain zero forces the controller to work as a single domain.

Demand messages

Heat source (HTSC), cool source (CLSC) and occupation destinations (OCDS) settings have a domain associated with them. These messages remain local if the destination controller is registered to the same SubSystem, otherwise the message is sent on the global domain and the destination can be on any of the SubSystems. The links can be set up by registering the Zone to the Heat source as for a single domain system, the domain addresses will be set automatically, alternatively they may be setup using configuration parameters, the domain is represented as the thousand digit on the parameter (e.g. 1001 is heat source 1 on domain 1)

Registration

Each SubSystem can be regisistered independently.  If it is helpful to register SubSystems in parallel then the easiest method is to temporarily disconnect the router from the backbone. The SubSystem nodes can then be registered and all local links setup. The service pin on the router should be pressed at this time and the SSM will allocate adresses to the router and set it's mode correctly. Multiple routers can be used within a sub system, local network traffic will be constrained within each segment, this might be useful when there are a large number of relatively small floors.

When making changes to the system or setting registration links between SubSystems then it is necessary to have the whole system on line, in this situation it is important that only one registration master is active at any time, this is acheived by a new registration mode. Select the SSM you wish to use in the normal way by setting it into config mode, if you do not wish to set HTSC, CLSC links to the system master, press the 'select' button. This will prevent these registration links being set up and will also broadcast to all other SSM's that they should ignore registration messages until they are put into config mode. This registration master mode is indicated by the status led flashing amber/red. Config mode or Registration Master mode will automatically time out 30 minutes after the last Registration message is received. Putting any System Master into configuration will clear all other System Masters out of config mode and Registration Master mode. Putting any other node into config mode will automatically change the System Master which is in Config Mode to Registration Master mode.

Time Synchronisation

Systems with multiple System Masters have multiple Real Time clocks, the network is organised such that the clock updates are broadcast globally, so that all System Masters receive time updates and time broadcasts from other System Masters. This function is carried out by the System Master in the lowest numbered domain.  Please note if this controller is disconnected from the network or fails to operate, the next highest numbered system master will take over broadcasting of the time signals.

 

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