UCWEB – Web interface for room controllers Installation and

Transcription

UCWEB – Web interface
for room controllers
Installation and operation manual
V08/09
1
Contents
1
Contents .............................................................................................................2
2
2.1
2.2
Introduction .........................................................................................................3
Inputs ..............................................................................................................3
Outputs............................................................................................................3
3
Before you start ..................................................................................................4
4
Installation ..........................................................................................................4
5
5.1
5.2
5.3
5.4
5.5
5.6
5.7
5.8
5.9
Connection..........................................................................................................5
Communication terminals................................................................................5
Power ..............................................................................................................5
Valves .............................................................................................................5
Cables .............................................................................................................5
Connection of the controllers ..........................................................................6
Ethernet...........................................................................................................7
Relay ...............................................................................................................7
Inputs ..............................................................................................................8
Others .............................................................................................................8
6
Indicators ............................................................................................................8
7
7.1
7.2
7.3
7.4
7.5
7.6
Installation, commissioning.................................................................................9
Cabling and valves..........................................................................................9
Connecting the UCWEB .................................................................................9
Setting of IP address and other network parameters....................................11
Relay configuration .......................................................................................13
Input configuration ........................................................................................15
Central settings .............................................................................................17
8
8.1
8.2
Adding and removing controllers ......................................................................19
Adding controllers .........................................................................................19
Removing controllers ....................................................................................21
9
9.1
9.2
Controller settings.............................................................................................22
Controller mode and temperatures ...............................................................22
Time schedules .............................................................................................24
10
10.1
10.2
10.3
Access levels....................................................................................................25
View only ...................................................................................................26
Settings......................................................................................................26
Service.......................................................................................................26
11
11.1
11.2
11.3
11.4
Service menu items ..........................................................................................26
Reboot .......................................................................................................26
Firmware....................................................................................................27
System information....................................................................................27
Logout........................................................................................................28
12
Frequently asked questions..............................................................................28
Comments and hints for improvement of this manual are welcome. Forward them to
[email protected], please. Thank you.
www.domat-int.com
UCWEB
2
2
Introduction
UCWEB is the interface for remote access to UC... room controllers over intranet or
internet. Over UCWEB, users are able to read and set values, time schedules, and
other process data.
The UCWEB board incorporates two digital inputs and two relays with configurable
functions.
The device is mounted to a DIN rail, usually in a switchboard or installation box
togehther with a 230/24 V transformer for powering of the room controllers.
To install and address the controllers, no other software nor tools are necessary, all
settings follow over the web interface. The controllers are added one after another, the
interface searches for a new one and changes the controller’s address to avoid
conflicting addresses.
The RS485 interface is fully galvanically separated. Maximum port communication
speed is 115200 bps.
2.1
Inputs
The UCWEB provides two inputs (DI1 and DI2) for potential-free contacts with
configurable function:
Central Off: all controllers are set to a defined mode (e.g. with security system going to
On); mostly to Standby. Suitable for long-term unoccupancy.
Alarm: the alarm bell symbol is displayed at all controllers and optionally an e-mail with
predefined text is sent to a given address – used for critical alarm messages
Maintenance: the spanner symbol is displayed at all controllers and optionally an e-mail
with predefined text is sent to a given address – used for maintenance messages
Boiler operation: the boiler symbol is displayed at all controllers as indication of boiler
operation
Change-over: if a heat pump with change-over (reverse) option is installed, and the
heating / cooling distribution system is designed accordingly, this signal will change all
controllers into the cooling mode. The cooling symbol is displayed at all displays, and
the control sequence operates with cooling setpoints.
The change-over input is connected to the change-over signal from the heat pump, or to
a strap-on thermostat installed on the supply water piping to the rooms.
2.2
Outputs
The UCWEB also provides two 230 V / 5 A relays. If the relay has to be normally open,
use the COM1 and NO1 terminals. If the relay is active (ON), the COM1 and NO1
terminals are connected, NC1 is not connected. If the relay is inactive (OFF), terminals
COM1 and NO1 are disconnected, terminals COM1 and NC1 are connected.
Relay 1 switches (according to configuration):
•
with heating demand from the controllers (to enable the heat source, e.g. boiler,
with configurable off delay 0..60 min),
•
if set manually over the web interface; it is used as remote control for any device
•
if temperature in a selected room runs out of preset limits (e.g. for greenhouse
emergency heating).
Relay 2 switches (according to configuration):
•
with cooling demand from the controllers (to enable chiller, central air condition or
any source of coling energy, with configurable off delay 0..60 min),
•
if set manually over the web interface; it is used as remote control for any device
UCWEB
3
•
3
if temperature in a selected room runs out of preset limits (e.g. for greenhouse
emergency heating).
Before you start
UCWEB and UC100 room controllers may be installed under following prerequisites:
•
central heating with radiators equipped with control valves and thermic actuators
powered by 24 V AC, recommended actuator types are e.g. Siemens STA71, or
Danfoss TWA (24 V AC types). Please check if your valve is compatible with the
actuator.
•
heat source (boiler) with enable (start) terminals, boilers usually feature two
terminals to connect a room thermostat. If those terminals are short-circuited, the
boiler operates.
•
a suitable place to install the UCWEB - a conduit box dimensioned appr. 20 x 40
cm, containing 230 / 24 V transformer to power the UCWEB and room controllers.
The power of the transformer depends on the amount of controllers anf thermic
actuators installed. For installations up to 10 actuators, a 63 or 80 VA transformer
will do.
•
230 V power at the place UCWEB is installed.
•
cable path from UCWEB to the room controllers (line topology, i.e. UCWEB –
controller1 – controller2 - .... – controllerN).
•
cable path in the rooms from each controller to the thermic actuator.
To install and commission the system you will need:
•
cable (LAM 2x2x0.8, or JYTY 2x1), see below (Cables) to link the controllers to the
actuators and to UCWEB
•
other components (power socket for the power adapter, CYKY 3x1.5 cable to install
the socket, conduit boxes, installation terminals etc.)
•
tools for cable installation (uninsulating knife, pliers, screwdriver).
•
pocket meter to check voltage and actuator resistance before inserting the
controllers into sockets
•
PC with Ethernet interface and web browser
•
Ethernet cross cable.
Attention! Low voltage installations (230 V) may be carried out only by authorised
persons!
4
Installation
Install the communicator in a dry place with temperatures not exceeding 60°C. The most
suitable place is a conduit box or a switchboard. On the back of the UCWEB there is a
DIN rail snap-on holder. The UCWEB may be mounted in any position, its thermal load
can be omitted and there are no special demands for air circulation around the
enclosure. It is useful that the LEDs are visible for easy troubleshooting.
In case the UCWEB is installed on an installation plate, fix a 8-10 cm piece of DIN rail
first and snap the UCWEB on it.
Remember to allow some space around the device for connectors and cabling; 3 cm is a
reasonable minimum. If a RS232 connector is used, there must be at least 7 cm free
space above the CANNON connector.
UCWEB
4
5
Connection
Fig. 1: UCWEB switches and terminals
5.1
Communication terminals
The K1+ and K1- terminals connect the controller bus. Use any communication cable,
e.g. LAM 2x0.8. If there is communication and 24 V AC power in the cores of the same
cable (e.g. LAM 2x2x0.8) remeber to select conductors with sufficient cross-section, as
this power also supplies the thermic actuators - see below.
5.2
Power
Connect the power supply to G and G0. If there is 24 V AC available at the place
UCWEB is installed, e.g. a transformer powering the controllers, it is possible to use
this power source instead. With DC 10..35 V power, the UCWEB is not polaritysensitive.
persons!
5.3
Valves
The UC... controllers feature 24V AC PWM (pulse-width modulation) outputs for thermic
actuator of radiator valves. Recommended actuator types are e.g. Siemens STA71, or
Danfoss TWA (24V AC types). Check compatibility of the valves with your supplier.
Follow the installation instructions of the valve manufacturer.
One controller (output) can host maximum two thermic actuators. If there are 3 and
more actuators to be controlled by one controller, an external triac must be used, or 230
V AC actuators and the PWM signal must be processed in PWR011, the triac module.
persons!
To connect the actuator to the controller, use any 2-core cable with cross-section at
least 0.8 mm2. The cable must not be shielded, twisted, etc. JYTY is OK.
5.4
Cables
Suitable cable types are LAM DATAPAR 2x0.8 (cross-section in mm2), JYTY 2x1
(diameter in mm) etc. If communication and power are in the same cable, use 4-core
LAM DATAPAR 2x2x0.8, JYTY 4x1. Up to 100-120 meters, parallel lines of 24 V and
UCWEB
5
data bus are no problem. Regarding to EMC it is better if the pairs are twisted, such as
with the LAM DATAPAR or Belden 8205 cable.
Fig. 2: Connection of the controllers (without AC adaptor,
UCWEB powered together with the controllers)
A terminal is designed for maximum 3 wires of 0.8 mm2. With cable types as above,
maximum (starting) power of the controller and valve of ca. 7 VA and acceptable voltage
drop of max. 15 %, the maximum cable length for 10 controllers is about 50 m.
If the controllers and valves are at higher distance than 50 m from the transformer or
more valves are connected to the transformer (max. 2 valves per controller), it is more
suitable to supply the controllers locally (Fig. 3). The RS485 bus is galvanically
separated and connects all controllers, regardless of the way they are powered.
If there are higher voltage drops at the power cabling, the thermic actuators may not
fully open. The radiator bodies then provide less heat. However, the electronics in the
controllers works OK until the power drops below 12 V AC.
Fig. 3: Two transformers for distant controllers
5.5
Connection of the controllers
The controllers are powered either with a separate transformer(s), or with one common
source with the UCWEB interface (as on Fig. 2). It is possible to mix both ways
especially at longer cabling: use local power source for distant controllers to prevent
voltage drops, see previous part.
The last controller in the line must have the bus termination on: on the back of the circuit
board there are two BUS END switches. To terminate the bus switch both of them to the
ON position. A badly or not terminated bus may not work correctly and there may be
communication dropouts, or the communication may be totally spoiled and the
controllers may not be detected by the UCWEB interface. However, this will not affect
their control functionality.
UCWEB
6
Fig. 4: BUS END switches
Before inserting the controllers into the sockets, check if there is proper power voltage
at the 6 and 7 terminals, that the bus has correct polarity at all the sockets, and that
there is no voltage at any of the other terminals.
Incorrect polarity at one or more controllers will result in non-communication of the
affected controller or maybe some other controllers. However, this does not affect the
control functionality of the controllers.
Swapping of the power cores basically does not influence the system functionality at all,
however, it is recommended to keep the same polarity for all the controllers for the sake
of unified installation of the complete system.
5.6
Ethernet
The Ethernet RJ45 socket connects UCWEB to a 10/100 Mbps network. If the UCWEB
shall be available over the Internet, the network must be connected to the Internet and
the router must be configured basically so as to accept incoming connection on port 80
and forward them to the IP address of the UCWEB. It is also possible to use an
advanced technology (VPN etc.). To configure the router contact your network
administrator or Internet provider.
The UCWEB supports DHCP client functionality, however, it is more suitable if it
becomes a fixed IP address. Please contact your network administrator or Internet
provider.
Deafult network settings are:
IP address
network mask
default gateway
primary DNS
secondary DNS
192.168.1.99
255.255.255.0
192.168.1.1
192.168.1.1
192.168.1.1
If the IP address of the UCWEB is not known, reset it to factory settings, or use
Finder.exe (on the installation CD) to find the UCWEB in the network and read/change
its IP settings.
5.7
Relay
The DO1 output is usually used for boiler control. The communicator collects up heating
demands from the controllers (rooms), and enables the heat source (boiler or heat
pump). The off delay is configurable so as to avoid frequent starts of the boiler. The
relay provides both NO and NC contacts, however, usually the NO and COM terminals
are used (connected if there is heat demand).
Mind that the boiler may use 230 V AC as its enable signal. This means that on the
UCWEB terminals there may be 230 V voltage even if the UCWEB is not powered.
Disconnect the boiler prior to any installation works on the UCWEB.
The DO2 output provides similar functionality; for remote control it may be loaded up to
250 V AC / 5A. Keep safety rules when connecting to 3rd party electrical appliances.
UCWEB
7
persons!
5.8
Inputs
The binary inputs are used for connection of potential-free (dry) contacts. Do not apply
any voltage on their terminals! The input circuits are powered from the UCWEB by 12
V DC, load of the external contact is appr. 4 mA. If the inputs are activated by open
collectors rather than by metallic contacts, as it sometimes is with output cards of
security systems, keep the correct polarity (DI is positive, G0 common). The functionality
of the inputs is configurable, see below.
5.9
Others
The INIT switch brings the device into factory (default) settings.
6
Indicators
In the lower right corner, there are 2 communication LEDs:
TxD (green), and RxD (red).
Status
Function
TxD flashes, RxD flashes:
Normal function, communicating
TxD flashes, RxD off:
Bus disconnected or controllers do not answer
TxD flashes, RxD on:
Bus short-circuited
TxD, RxD off:
UCWEB error or no controller defined (no
requests are sent), this appears also appr. 2
mins after reset.
At the front panel, there are green LEDs:
POWER on: UCWEB powered and alive
RUN flashes: the UCWEB microprocessor works correctly
DO1: status relay 1 (on – relay active, off – relay inactive)
DO2: status relay 2 (on – relay active, off – relay inactive)
DI1: status input 1 (on – input active, off – input inactive)
DI2: status input 2 (on – input active, off – input inactive)
At the Ethernet connector, there are 2 LEDs:
yellow LED: on – physical link (to a switch or PC) is OK
green LED: flashes – data transfer
After power up, the LEDs should follow this pattern:
– green LED on
– yellow LED on
– after appr. 20 seconds, yellow LED off and on again
– green LED off and flashes as data is transferred.
UCWEB
8
7
7.1
Installation, commissioning
Cabling and valves
1.
Lay all the cabling, i.e. power cables, communication bus, and cables from the
controllers to the thermic valves. See details above.
Fig. 5: Numbers of cores in the cables
7.2
2.
Install the sockets (bottoms) of the controllers, and the UCWEB, and connect the
wires to the terminals.
3.
Switch the power on.
4.
Check if the correct voltage (24 V AC) appears on the terminals 6 and 7 of the
bottoms and not on any other terminals (see Fig. 2).
5.
Check if the bus cabling has the correct polarity.
6.
Check if the cabling to the thermic valves has the correct resistance at the terminals
3 and 6 – appr. 150 Ohm. If the resistance is zero, do not insert the controllers in
the sockets – the UC100 output would be damaged. Check the resistance of the
thermic actuator direct at the actuator cable. Either the actuator is damaged or there
is short circuit in the cabling from the controller to the actuator cable.
7.
As soon as everything is OK start with connecting and addressing of the controllers.
(If the controllers should operate as soon as possible, even autonomously, i.e.
without central functions and commanding over the UCWEB, insert them into the
sockets and disconnect the RS485- and RS485+ terminals at the UCWEB. When
addressing them later, all controllers must be removed from the sockets again and
inserted one after another for the UCWEB to find and readdress them correctly.)
Connecting the UCWEB
8.
Connect the Ethernet interface of the UCWEB either with a straight Ethernet cable
into an existing network, or with a cross Ethernet cable direct to the computer which
will be used for configuration (see Fig. 6).
9.
Check if the yellow LED is on at the Ethernet interface of the UCWEB. This means
that the interface is physically connected to the network. If the yellow LED is off,
check if the other end of the cable is connected to a switch, or – with the direct
connection to a PC – check if a cross cable is used. Some network cards may show
problems autodetecting the network speed. It is recommended then to use two
straight cables and a switch instead the cross cable.
UCWEB
9
Fig. 6: UCWEB in a network and connected directly to a PC
10. In the PC, set network IP address in the 192.168.1.x subnet, e.g.192.168.1.2, and
network mask 255.255.255.0.
11. Enter the default IP address of the UCWEB in the browser: 192.168.1.99. The login
page opens:
If the page can not be found check if UCWEB is connected to the network and if the
Ethernet interface responds at the default address (e.g. ping 192.168.1.99). If the
UCWEB does not respond, reset the device or use Finder.exe (on the installation
CD) to search for the UCWEB in the network.
12. The service (Name: Service) password is root. After the password is entered and
the Login button clicked, the main page with system information opens.
There is main menu with links to system functions in the left column.
UCWEB
10
At the Home page there are following items:
- IP address: current IP address of the interface. This address (as well as other network
settings) can be changed in the IP – Ethernet menu.
– MAC address: physical address of the network interface, can not be changed. It may
be useful for advanced settings, such as access control list at your provider. If your
Internet provider needs the MAC address of your device, this is it.
– Firmware version: Have this ready when consulting technical problems with support.
– Up Time: Time since the last power failure / reboot.
7.3
Setting of IP address and other network parameters
If the UCWEB is being attached to an existing network, it will most probably be
necessary to change its network settings so as to correspond with the numbering plan
of the network. In an internal home network it may be that the default IP address and
other parameters will be OK. Ask your network administrator or Internet provider for the
correct values to set.
The IP address and other parameters are set in the IP – Ethernet menu.
Changes must be confirmed by the Submit button and usually they become active only
after reboot (also called restart) of the UCWEB.
UCWEB
11
Connection settings:
Obtain IP from DHCP server automatically: This option is suitable for networks where
IP addresses are automatically assigned by a DHCP server. Usually, it is not used.
Use following IP address: This is where you enter the IP adress and other network
parameters. Ask your network admin for correct values. If the UCWEB is connected to a
PC via a cross cable the default settings should do the job.
HTTP server port: In case the UCWEB should answer on other than standard (80) TCP
port, enter the web server port number here. Usually, it is not necessary to change this
value, however, it may be useful when configuring NAT port forwarding. Consult your
network administrator.
Primary NTP, Secondary NTP: Servers providing accurate time over the NTP service.
This time is used for synchronization of all the controllers on the bus. For the
synchronisation to work correctly, the UCWEB must have access to the Internet.
There are more items below:
UCWEB
12
SMTP settings: A SMTP server is necessary for sending e-mails. The UCWEB must
know its address in order to send alarm e-mails. There also must be an e-mail account
through which the mails will be sent (this is the user the mail will be sent from). It is
recommended to subscribe for an account for example at some of the freemail services
and use this account to send mails.
Server: Enter the outgoing mail server address here. It is usually defined by your
Internet provider.
Recipient: Enter the e-mail address of the target e-mail address (where alarms will be
sent to).
Sender: Enter the e-mail address of the outgoing mail (which appears in the From: field
in the recipient’s incoming mail).
SMTP authentication: Most of the outgoing mail servers require username and
password as a protection against spam robots. This option thus will usually be selected.
Then fill in the other two items:
Login name: Enter the account (user) name for the outgoing mail.
Password: Password to autentify the user Login name at the SMTP server.
Realport settings:
Realport is a special communication mode where UCWEB acts as a terminal server,
which means that it tunnels a serial port over the network. Web access to the controllers
is not possible in this mode. The Realport mode is dedicated for remote access directly
to the bus: there is a virtual serial port on the remote computer and with the
configuration software domat.exe it is possible to read and set all the internal
parameters of the UC... controllers.
The correct functionality of the Realport access depends on configuration and quality of
the network connection. This manual will not deal with the Realport settings, the item
Realport enable: will be unchecked.
TCP port: This is the Realport TCP port used for data communication.
7.4
Relays configuration
This is where the output relays are configured.
Current status: ON or OFF – actual status of the relay.
UCWEB
13
To set the functionality of the relay, select one of the three options below:
Heating: the relay is on if at least one controller on the bus sends the heat demand
signal. The relay then enables boiler or another heat source. To prevent too frequent
switching of the boiler, the switch-off delay time can be set in the range of 1..60 mins
(Heat source switch-off delay) – recommended value is appr. 5 min.
The relay is connected to the „Room thermostat“ terminals of the boiler. Consult the
supplier of the boiler or its authorized installer.
Manual mode: It is possible to switch on and off the relay manually over the web
interface. You can enable and disable e.g. DHW preparation, garden watering, lights,
etc.
•
OFF: sets the relay to Off (inactive). Its status is indicated by the RELAY 1 LED at
the UCWEB front panel: the LED is off.
•
ON: sets the relay to On (active). Its status is indicated by the RELAY 1 LED at the
UCWEB front panel: the LED is on.
After the new state is selected, confirm it by clicking the Submit button.
Alarm: In the Alarm mode, the relay gets active if temperature in a selected room
exceeds the setpoints. The sequence operates with fixed hysteresis of 1 K.
Temperature min.: If the temperature decreases below this value the Relay 1 switches
to ON. If later the temperature increases over [this value + 1 K] the relay switches to
OFF again.
Temperature max.: If the temperature increases above this value the Relay 1 switches
to ON. If later the temperature decreases over [this value - 1 K] the relay switches to
OFF again.
Room controller: The controller to provide temperature for this function. Select the
room to be controlled here.
If only one threshold (low or high) should activate the relay, set the other value to some
extremely high (or low) value to disable the function.
Example: The normal greenhouse temperature setpoint in the UC100 controller is 18 °C.
If the heating fails and the actual temperature drops below 12 °C an emergency
electrical heating should be activated. The temperatures are then set as follows:
Temperature min: 12 °C, Temperature max: 100 °C.
The relay will then never be activated by high temperature, as the real temperature
never reaches 100 °C.
Send e-mail with subject: If this option is selected an e-mail is sent together with
activation of the relay because of temperature exceeding the preset limits. The e-mail
header (Subject: ) is defined in the next item right.
Similar settings apply for Relay 2, the only difference is that the Mode 1 is active with
cooling demand. This is used for the UC200 controllers which control radiators and
cooling panels. At most of the applications, however, there is only a heat source
installed, and Relay 2 is used for manual control of another technology (Mode 2) or as
an alarm relay for emergency heating (Mode 3).
UCWEB
14
7.5
Input configuration
The UCWEB provides two inputs for potential-free contacts. The functions of the inputs
is set in the Inputs configuration menu.
Each of the inputs is set into one of five modes:
Alarm: If the input is activated all controllers display the bell icon. If the Send e-mail...
option is selected an alarm e-mail is send immediately with subject entered in the field
at the right.
The Alarm function is used if it is useful to transmit an alarm message, e.g. flooding of
the boiler house, gas leakage etc. to all rooms where the controllers are, and optionally
by e-mail. The heating functionality is not affected.
Maintenance: If the input is activated all controllers display the spanner icon. If the
Send e-mail... option is selected an alarm e-mail is send immediately with subject
entered in the field at the right.
The Maintenance function is used if it is useful to transmit a maintenance message, e.g.
pump failure, fuel shortage etc. to all rooms where the controllers are, and optionally by
e-mail. The heating functionality is not affected.
UCWEB
15
Heat source activity (boiler operation): If the input is activated all controllers display
the boiler icon. It is indicating the operation of the boiler (not the heating demand of the
controller!), which means that it is possible to see at all controllers that the boiler or heat
pump is in operation. The heating functionality is not affected by this indicator.
Presence (Security system): In this mode, the input is used for centralised setting of all
controllers at the bus into a certain operation mode. It is used e.g. for longer building
unoccupancy periods: the input connects to the security system relay which gets active
as soon as the building is set to secure mode. After the building is left and coded (and
the input activated) all the controllers are automatically set to the mode which is defined
in the Presence mode settings below. Usually, it is Setback or Night.
This means that regardless of the fact how the controllers are set according to their time
schedules or manually (push button), after the contact is activated, they always go to the
predefined mode. After the contact is deactivated all the controllers are set to the modes
which have been defined in the Return from active Security system menu.
Change-over: If this input is active all controllers on the bus receive information that in
the piping there is cold water instead of hot water. This mode is used if the radiator or
panel in the room is used for heating in winter and for cooling in summer; this function is
supported by some heat pumps. Based on this signal coming from the heat pump, a
thermostat, or manual switch, the controllers suppose that in the change-over mode the
temperature will decrease after the valve is opened – and the valve control sequence is
modified accordingly.
Presence mode settings (Security system): Select the operation mode all controllers
shall be switched to when the Presence (Security system) input is active – see above.
If none of the inputs will be set to the Presence (Security system) mode, this setting is of
no importance.
As long as the Presence (Security system) input is active, it is still possible to change
the controller mode manually (by the push button or web interface) into another mode.
However, after the Presence (Security system) is deactivated, all controllers are set to
the modes defined in the Return from active Security system menu – see below.
E-mail body for alarm and fault: Here, some text may be defined, which is used when
composing the alarm and maintenance e-mails. Detailed information about the site,
phone number of the responsibles and service, short to-do information, etc. are usually
entered here. After this user part, the following text is automatically appended:
UCWEB
16
MAC address: 00:40:9D:26:FE:F9
Time: xx:xx:xx xx/xx/xxxx
Source: input x, status x
This text is used for unique identification of the UCWEB by its MAC address and
provides information on the time of event occurence, and which input and which status
originated it. This information is rather for service and diagnostic purposes.
Return from active Security system: When switching to Presence (Security system)
mode, all controllers are set to a common operation mode defined in the Presence
mode settings (Security system). As the input contact is open – leaving the Presence
(Security system) mode and changing to normal operation – all controllers are set to
modes which have been read from the controllers at the moment the Submit button had
been clicked.
To set the return modes proceed as follows:
7.6
1.
Set all the controllers either by the push button or over web into the modes which
should be active after leaving the Presence (Security system) mode. (Mostly it is the
Time schedule.)
2.
Click the Submit button in the Return from active Security system menu. The actual
modes of the controllers are now saved in the UCWEB configuration.
3.
Ready. Bring the controllers into current required operation modes now.
Central settings
At the Central settings page, all controllers can be set to a certain mode, and time zones
and synchronization configured.
Central setting mode: All controllers are set into the selected mode here with a group
command. This command is used
•
for remote setting from Setback to Time schedule mode, if the building shall be
pretempered several days before arrival
•
for remote setting from Time schedule to Setback mode, if the building will not be
occupied for a longer period.
How to proceed:
1.
Select the required mode which is to be set at all controllers.
UCWEB
17
2.
Click the Submit button.
3.
The controllers are set into the required mode.
Time zone: This must be entered if automatic time synchronization in the controllers
over a NTP server is used. The NTP servers provide world time (UTC), to which the
UCWEB adds the difference according to the time zone it is installed in. The default
setting is Central European Time, CET = UTC + 1 hour. If the UCWEB is installed in
another time zone, please change these setting accordingly.
Keep the correct format: +hh:mm, -hh:mm. Save the new value by clicking the Submit
button.
In the EU countries, it is not necessary to change the default settings.
Central time: If the time is not synchronized automatically over the Internet, all
controllers may be set actual correct time manually. The Date is relevant for the
UCWEB only and is evaluated to compute the weekday and daylight saving time
change dates.
Set the time:
1.
Enter actual values in the fields Current time and Date. Keep the correct format
(hh:mm, yyyy/mm/dd).
2.
Confirm with the Submit button.
There is current date and time of UCWEB at the next line. Refresh the values by
clicking the Central settings link in the menu at left).
Note the synchronization message:
•
if the UCWEB has access to the Internet and the NTP server addresses are
properly configured in the IP – Ethernet menu, you can see the „Synchronized with
SNTP“ message.
•
Otherwise, the UCWEB reads current time from the first controller which is found on
the bus. It is supposed that users have set the correct time in the push button menu.
Then the „Synchronized from controller at address X“ message is displayed.
Automatic change to Daylight saving time: Different countries have different summer
/ winter time change days. Enter the date after which the Sat-Sun night of change
follows.
It is not necessary to change the default settings in the EU countries.
Confirm the changes by clicking the Submit button.
UCWEB
18
Manual change to Daylight saving time: To change from and to DST manually. The
checkbox indicates the actual DST status. Select the correct option if necessary and
confirm the changes by clicking the Submit button.
Time synchronisation in the room controllers: To keep the time the same in all the
controllers, it is possible to enable automatic synchronization of the controller time. The
controllers are synchronized at 5 AM each day. The clock are backuped by a battery in
each controller. The accurate time is read from predefined NTP servers over the Internet
(as soon as the UCWEB has access to the Internet and the NTP server addresses are
defined correctly), or are read from the first controller on the bus and distributed to the
other controllers.
By selecting automatic synchronization the synchronization is enabled. Save the new
configuration by clicking the Submit button.
8
Adding and removing controllers
At the commissioning time, it is necessary to assign each controller a unique address on
the bus, and to configure the UCWEB. The functions are in the Bus configuration menu.
8.1
Adding controllers
The default controller address (factory settings) is 1. When adding controllers to the
UCWEB, connect always one controller addressed 1 at a time. The UCWEB finds it and
changes the address to the first free address on the bus, giving a prompt to set the
controller (or room) name at the same time. Proceed as follows:
1.
Remove all controllers from the sockets.
2.
Insert the first controller which should appear in the UCWEB list into its socket..
3.
Check if the controller has address 1 (default). After being inserted into the socket,
the controller displays in a sequence:
•
display test (all symbols on the LCD display)
•
firmware version: 0.11 means Version 11
•
controller address: 0.01 A means Address 1.
After this, the controller starts to operate and displays actual room temperature and
room status.
4.
If the controller address is different than 1, it is necessary to address it in the INIT
mode. Remove the controller from the socket and switch the INIT DIP switch to ON
(see Fig. 4 above). Then insert the controller back into the socket. The display is the
same as before, still showing another address than 1, but on the bus the controller
responds as address 1.
5.
In the Bus configuration menu
UCWEB
19
click the Search button.
6.
The page with the new controller appears:
7.
Enter the controller name, e.g. Living room, and click the Save button. Do not use
special and accented characters in the name. A blue line appears with the message
that the new controller has been added.
8.
Remove the controller from the socket again – it will be restarted and its new
address becomes active.
9.
If the INIT switch has been ON bring it back to the OFF position!
Insert the controller into the socket again. It should display its new address when
restarting.
10. Repeat steps 2 to 9 for all new controllers.
UCWEB
20
11. As soon as all controllers are added go to the Home page and refresh the browser
window (F5). In the Room controllers administration menu on the left all controllers
are displayed.
Now the UCWEB is configured and the controllers are available. Go to the Controller
settings part.
8.2
Removing controllers
In a similar way it is possible to remove the controlers from the bus. The removed
controller is readressed back to 1 and deleted from the list in the UCWEB interface.
When removing a controller, proceed as follows:
1.
Check if the controller is inserted in the socket and is in operation.
2.
In the Bus configuration – Remove room controller menu select the controller to be
removed.
3.
Click the Remove button.
4.
A message displays that the controller was removed successfully:
UCWEB
21
5.
After reboot (power cycle = removing from the socket and inserting back) the
controller responds on the default address 1. It is removed from the UCWEB table
at the same time. The change is updated in the Room controllers administration
menu after the browser window is refreshed by the F5 key:
If there is an attempt to remove a controller which has not been found on the bus (e.g.
because it had been removed from the socket or its power is down), only the
corresponding record in the UCWEB table is removed. However, the controller is not
readdressed to 1. In case the controller has to be added to the bus again use the INIT
switch (see Adding controllers, step 4).
9
Controller settings
To browse and change the temperatures and time schedules in the controllers, go to the
Room controllers administration menu and click the controller name.
The colour of the controller name indicates the communication status of the controller:
•
blue: controller is operating correctly
•
violet: controller not found on the bus
•
red: controller was found at the time of UCWEB start, but now it is not available
anymore.
In case of problems:
-
check if the controller displays actual temperature (power up)
-
check if the communication line is not broken / shortcircuited
-
check if the controller has the same address as in the Room controllers
administration menu – remove it from the socket, check if the INIT switch is set to
OFF, and insert it back. The actual address is displayed in the startup sequence
(see above).
Try also to refresh the web page by hitting the F5 key.
9.1
Controller mode and temperatures
The first tab in the Module menu displays current status and setpoints:
UCWEB
22
Current status:
Temperature: Measured room temperature.
Presence mode: Day, Night, or Setback – according to the time schedule, or manual
override by remote (web) or local pushbutton.
Setpoint: Relative setpoint correction. Can be changed by turning the knob in the range
of –3.5 to +3.5 K and adds to the basic setpoint. When changing the presence mode,
the setpoint correction is reset back to 0 and basic setpoints apply (Heating temps,
Cooling temps).
Time: Current real time of the controller clock. Set the correct time either directly in the
controller (superlong push) or over the UCWEB in the Central settings menu.
Heat/Cool mode: Heating, Cooling or No energy. Results in heat / cool demand for the
relays. The mode is also indicated by the heat / cool icon on the LCD display of the
controller.
Type: Controller type – for information only.
Room controller setting: Here, the basic setpoints for heating and cooling for all
operation modes are set. The values for heating and cooling of the same mode should
not overlap, i.e. the heating setpoint must be lower than the cooling setpoint of the same
mode. If this is not the case the heating setpoints can not be set to higher values!
If the actual temperature is above the heating setpoint (UC100, UC300), or between the
heating and cooling setpoints (UC200), the controller is in the No energy state, thus
sending no energy demand signal to the UCWEB.
In the Presence mode item select if the controller shall follow the time schedule, or
permanently keep the Day, Night or Setback mode. The function is the same as a short
push of the button at the controller. Confirm the settings by the Submit button.
Room controller name: this is where the controller name in the UCWEB table can be
changed. Save the new name by clicking the Submit button. Refresh the view in
browser by hitting the F5 key.
The last item is the weekly graph of heating setpoint temperature:
UCWEB
23
Move the mouse in the graph to see the actual setpoint of a certain weekday and time. It
gives a brief overview of night and weekend setbacks.
9.2
Time schedules
In the Monday to Sunday tabs there are settings of the time schedules separately for
each day of the week.
There may be defined up to 6 events – state changes – in one day. From midnight to the
first event of the day, the state from the last night applies, thus in the example above the
controller status from 00:00 to 06:00 keeps the last status set on Sunday night.
In the above screenshot the morning Day period is set from 06:00 to 08:00, then Night
(Standby) from 08:00 to 14:00, and from 14:00 to 22:00 the controller is in the Day mode
again. At 22:00 it switches to the Night mode which is kept until the first event of the
next day. This means that we only use 4 events out of 6. The unused events are marked
by a null state (“ – “) and their switching times are not relevant.
The program is changed by selecting the new mode and entering the switching time as
hh:mm. Confirm by the Submit button.
Move the mouse in the graph to see the actual setpoint of a certain time. It gives a brief
overview of night and weekend setbacks.
UCWEB
24
Similarly, the other weekdays’ schedules are set in the other tabs (Tuesday to Sunday).
The schedules are written directly into the controllers, so that even if the UCWEB is
disconnected or not powered the controllers switch according to the time schedules. If
the schedule is changed directly in the controller superlong push menu, refresh the web
view by clicking the tab with the particular weekday.
10
Access levels
The UCWEB provides 3 access levels: View only, Setting, and Service.
The default password for all three levels is root. It is recommended to change the
password immediately in the Access settings menu:
All three fields must be filled in: the old and new passwords, and new password to
confirm. After clicking the Submit button the new password is saved and active at the
next login.
UCWEB
25
10.1 View only
Users are allowed to browse all values inclusive system settings (because of
diagnostics). They are not allowed to change any value except for their own password.
10.2 Settings
Users are allowed to browse all values inclusive system settings (because of
diagnostics). They are allowed to change those settings:
•
switch on and off relays, if they are in manual mode
•
set the central mode for all controllers
•
set modes and setpoints in all controllers
•
set time schedules.
After longer inactivity time, the user is logged out automatically, and forwarded to the
login page to log in again.
10.3 Service
Users are allowed to browse and to change all values and parameters inclusive adding
and removing controllers and network settings. Users with the Service access rights are
the target audience of this handbook. All screenshots in this document have been taken
with Service user rights.
11
Service menu items
11.1 Reboot
Reboot the UCWEB after changing certain parameters (network settings) or firmware
upload (see below). The controller list and other settings such as inputs and relays are
not changed after reboot.
UCWEB
26
The UCWEB is restarted by clicking the Reboot button. After the login screen appears,
log in again.
11.2 Firmware
Here it is possible to replace the firmware by a more recent version or another language
version. Proceed as follows:
1.
Click the Browse button to select the image.bin file
2.
Click Upload
3.
Wait until a message appears that the firmware has been uploaded successfully.
Do not switch off the UCWEB!
4.
After „The file has been uploaded...“ message appears, reboot the UCWEB in the
Reboot menu.
Firmware upload does not delete any of the UCWEB settings (list of controllers with
addresses, input and relay configuration, network settings, etc.).
11.3 System information
UCWEB
27
The System information page is useful for diagnostics in case of trouble. Copy the
contents of this page to mail and send it to technical support.
11.4 Logout
Menu for user logout. Confirm your logging out in the dialog window. After logout, the
user is automatically forwarded to the login page.
12
Frequently asked questions
The Ethernet connection can not be established
•
Check if the yellow LED at the Ethernet connector is on. If not, the interface is not
physically connected to the network.
•
Check if you are using the proper cable type (straight x cross), see Connection,
Ethernet.
•
Some network card types may have difficulties autonegotiating the connection
speed: if you are using cross cable and direct connection UCWEB to PC, set in the
Network card properties fixed speed to 10M / Full duplex (switch off Auto
negotiation), or use switch instead of direct connection.
•
Run Finder.exe (on the installation CD) to find the UCWEB and in the IP settings
menu set the correct IP address. Remember to switch off the PC firewall for correct
detection.
•
Reset the UCWEB a and use the default IP address (192.168.1.99).
•
How to reset the UCWEB?
– switch off the power
– set the INIT switch (DIP switch No. 6) to ON
– apply power and wait appr. 1 min. for the relays to click 3 times fast
– set the INIT switch (DIP switch No. 6) back to OFF
Attention! Resetting the device deletes the complete configuration: controller
addresses, network settings, input and output functions etc.
UCWEB
28
Can not find the first controller on the bus
•
Check if the green TxD LED flashes with clicking the Search button. If not, reset the
UCWEB and check the status of the other LEDs – see Indicators.
•
Check if bus is connected properly – see terminals at Fig. 2
•
At longer bus routes (hundreds of meters) set the BUS END switches of the
controller to the ON position. For proper bus termination, the BUS END switches
should be ON only at the last controller on the bus. Therefore it is recommended to
activate them at the first controller to be commissioned only and proceed back to
the UCWEB.
•
Check if the controller address is 1 (the address is displayed shortly after power-up
in the startup sequence display test – firmware version – address – operation).
Can not find other controllers on the bus, the first one was OK
•
Check if bus is connected properly – see terminals at Fig. 2
•
At longer bus routes (hundreds of meters) set the BUS END switches of the
controller to the ON position. For proper bus termination, the BUS END switches
should be ON only at the last controller on the bus. Therefore it is recommended to
activate them at the first controller to be commissioned only and proceed back to
the UCWEB.
•
Check if the controller address is 1 (the address is displayed shortly after power-up
in the startup sequence display test – firmware version – address – operation).
After the controllers have been addressed, I can not see the list in the left column
•
Refresh the frame by hitting the F5 key
•
Restart UCWEB in the Reboot menu or by powering it off and on again.
I can see the controller list but can’t get into the controller menu
If the controller name displays in red or violet the controller does not communicate. If at
least one controller is communicating:
•
check if the controllers are powered
•
check if bus is not broken
•
check if the last controller on the bus has the BUS END switches in the ON
position.
If no controller is communicating and the green TxD LED flashes
•
check if the RS485 bus connector is plugged in properly
•
check if the bus is not short-circuited
If no controller is communicating and the green TxD LED does not flash
•
restart the UCWEB.
When changing temperature setpoints I can’t set the new value: the old or another
value is written
•
When changing the heating setpoint: Check that the cooling setpoint is higher than
the new heating setpoint. If not, increase the cooling setpoint first.
•
When changing the cooling setpoint: Check that the heating setpoint is lower than
the new cooling setpoint. If not, decrease the heating setpoint first.
UCWEB
29

UCWEB – Web interface for room controllers Installation and

Transcription

Similar documents

Dynapower Anodize Process Controller

MAXxess eAXxess Data Sheet

Motion Controller in Hydraulic Press

San Ysidro DMV Field Office

Simpletones: A System of Collaborative Physical Controllers for

portable usb dj mixer + scratch controll er + dj software

LT-1182 Installing TX3-BBCX

PeopleSoft Finance - Pain Points/Talking Points

Mega Plexxus Instruction

handheld controller