Overview Controller Standard



This description describes the web interface of the controller. The complete documentation can be found in the hardware documentation. See also the data sheet as PDF.

Important: Work on mains voltage only by qualified personnel. Please note the Safety notes and the Legal Notice.

Table of contents


Connection diagram

The terminals are arranged in one row on the top, the connectors for network, USB and KNX are on the bottom:

24V – 24V – 0V – 0V Supply 24 V DC. The two pairs of terminals are connected internally and serve to loop the supply through.
− – + – C1 RS485. The data lines are on − and +, the shield on C1. The terminating resistor R sits between C1 and C2: if the controller is operated at the end of the line, the two terminals are bridged.
C2 – RX – TR RS232 with receive and transmit line; C2 is the common ground.
ETHERNET (RJ45) Network socket. For the two LEDs on the socket see LEDs on the network socket.
USB A For USB sticks and serial USB adapters, see the note below.
Micro SD card slot Only for the firmware update of the IO modules. During operation the slot has to stay empty, see the note below.
KNX + / − Connection to the KNX bus line, + is red, − is black.

The exact position of the terminals and the dimensions are given in the data sheet.


Important: The micro SD card slot is only used to update the firmware of the IO modules. No SD card may be inserted during operation, otherwise the IO board will not boot; as a consequential error the serial number cannot be read and the error "license invalid" appears. How to recognise this situation on the MODE LED is described under MODE LED: SD card in the slot.

The controller has a USB port to which serial USB adapters or USB sticks can be connected. Important: When using serial USB adapters, you should not use them for critical components. The operating system of the controller does not support all USB adapters and USB sticks, therefore products from brand manufacturers are recommended. In general, USB components are used at your own risk.

Commissioning

The controller is delivered with the network setting DHCP by default. If a DHCP server is available in the network, the controller automatically receives an IP address and is found automatically by the programming software.

Alternatively, the controller has a second static IP address through which the controller can also be reached if no DHCP server is available in the network. The IP address is "172.31.1.100"; to connect to the controller you must give the PC an IP address from the same range, for example 172.31.1.200. Please note that if the controller is set to DHCP, a DHCP server must also be available in the network. The second static IP address is only used for configuration and not for permanent operation; if no DHCP server is available, DHCP must therefore always be switched off.

Tip: The controller can be reset to factory settings with the reset button on the controller. To do this, the reset button must be pressed for 30 seconds until the LED stops flashing. Then release the reset button, the controller will then restart automatically.


LED

The controller consists of two assemblies: the IO board, which handles the inputs and outputs, and the CPU board, on which the runtime runs. The MODE LED belongs to the IO board, the RUN LED is driven by the runtime on the CPU board. The two LEDs therefore indicate different things - which is exactly what makes them the most important tool for troubleshooting on site.

MODE LED

The MODE LED consists of a red and a green LED. The following sequence takes place when switching on:

1x short red (0.2 seconds)
The bootloader of the IO board starts.
2x red, then 1x green
Normal start of the system: flashing red twice (different duration) and green once. The IO board is now ready for operation.
MODE LED stays dark
The CPU board is booting. This step takes considerably longer than the start of the IO board, depending on the image a few minutes. During this time the RUN LED does not flash yet either.
green lights up briefly, RUN LED starts to flash
The runtime has started and reads the information from the IO board. Both LEDs react at the same time - this confirms that the CPU board and the IO board are working together.
green during operation
Indicates the communication with the IO board, see the following section.
red during operation
Communication error with the IO modules.

The green MODE LED indicates the communication with the IO board. It flashes because the runtime reads information from the IO board. What matters here is what has been configured in the project:

Target state during operation: The red MODE LED must not light up. The green MODE LED can be off, lit or flashing, depending on the program.

MODE LED: SD card in the slot

If a card is inserted in the externally accessible micro SD slot next to the Ethernet socket when switching on, the bootloader starts instead of the application and looks for the file R02_FW.bin on the card. The application of the IO board then does not start, so the controller does not boot completely. This situation can be recognised on the MODE LED:

1x long red (3 seconds)
A card is inserted but the file R02_FW.bin is not on it. The device remains in the bootloader.
red flashing fast / continuously
A firmware update has been completed successfully, the device is waiting for the card to be removed. If the card is not removed, a new update starts every time the device is switched on.
2x short red (0.2 seconds)
The bootloader restarts due to a problem, for example wrong file size, verification error or an error while writing to the memory.

As a consequential error the serial number of the IO board cannot be read, and the Studio reports "license invalid". If you see this message, the first thing to check is the SD card slot.

Remedy: Disconnect the controller from the power supply, remove the card and switch it on again. The externally accessible slot is intended exclusively for the firmware update of the IO board; the complete list of flash codes can be found under Firmware update IO board. Not to be confused with the SD card on the CPU board, which holds the operating system and the license, see Re-flashing the SD card.

RUN LED

The RUN LED is driven by the runtime on the CPU board. If the RUN LED is flashing, the controller and thus the runtime is running. This is the most important sign of life of the controller.

After switching on, the LED remains quiet until the CPU board has booted, which can take a few minutes depending on the image. With the first flash the green MODE LED also lights up briefly.

The flashing rate additionally indicates the state of the VPN connection:

fast rate (changing about every 0.5 seconds)
The runtime is running and the VPN connection is established.
slow rate (changing about every 1.5 seconds)
The runtime is running, but there is no VPN connection. If VPN is not switched on, this is the normal case.
LED permanently on or off
The runtime is not running. First wait a few minutes, then check the power supply and restart the controller.

This makes it possible to narrow down a remote access problem on site without having to connect a PC.

Note: When resetting to factory settings, the LED stops flashing after 30 seconds, see Commissioning. In this case the LED stopping is not an error but the acknowledgement of the reset button.

LEDs on the network socket

There are two LEDs on the network socket. One of them indicates the established connection to the switch or router and lights up permanently, the other indicates the data traffic and flickers irregularly. These LEDs are driven by the hardware and also light up when the runtime is not running.

Troubleshooting

If the controller cannot be reached or does not work as expected, it is best to work from the outside in:

  1. Is the RUN LED flashing? If it is not flashing, the runtime is not running - check the power supply and restart the controller.
  2. Is the red MODE LED lit or flashing in one of the bootloader patterns? Then the problem is on the IO board, usually because of an inserted SD card.
  3. Is the connection LED on the network socket lit? If it is not, the cause is the cable, the switch or the remote station.
  4. If all LEDs are in order and the controller still cannot be reached, open the web interface via the static IP address 172.31.1.100 (see Commissioning) and continue searching there under Status and Connection test.

The following table summarises the most common symptoms:

No LED is lit
There is no supply voltage. Check the 24V DC supply and the terminals.
RUN LED does not flash, is permanently on or off
The runtime is not running or the CPU board has not booted. After switching on, wait a few minutes, then disconnect the controller from the power supply and restart it. If this does not help, the operating system on the SD card of the CPU board has to be checked, see Re-flashing the SD card.
RUN LED flashes slowly, remote access does not work
There is no VPN connection. Check whether VPN is switched on in the web interface (see Services - VPN) and whether the controller reaches the Internet under Connection test. Further information under VPN.
RUN LED flashes, the Studio does not find the controller
The runtime is running, the problem is in the network. The most common cause is DHCP without a DHCP server in the network. Connect via the static IP address 172.31.1.100 and switch DHCP off, see Network.
Red MODE LED is lit during operation
Communication error with the IO modules. Check that the modules are properly seated on the DIN rail and compare the configuration in the Studio with the modules that are actually fitted.
Green MODE LED stays off
Normal if no IO modules are configured in the project or if only output modules without any change are present. If modules with inputs are configured, the green LED must light up continuously. If it stays off in that case, check the configuration in the Studio and the seating of the modules.
MODE LED flashes 1x long red (3 seconds) at start
There is an SD card in the externally accessible slot on which the file R02_FW.bin is missing. Disconnect the controller from the power supply and remove the card.
MODE LED flashes red quickly after an update
The firmware update is complete and the SD card has to be removed. Otherwise a new update starts every time the device is switched on.
The Studio reports "license invalid"
The serial number of the IO board cannot be read, usually because an SD card is inserted in the slot and the IO board has therefore not booted. Remove the card and restart the controller. If the error persists, please contact our support.
No LED is lit on the network socket
There is no connection at cable level. Check the network cable, the port on the switch and the remote station.

Web interface

The controller has a web interface in which various settings can be made without having to use the programming software. For example, the IP address can be set via the web interface with the browser, so that technicians who are not familiar with the controller can also make changes when the network changes.

Enter the IP address of the controller in the browser; if you use the static IP address, enter 172.31.1.100. You will then be asked for the user name and password; the user name is "admin" and the password is "z-server", each without quotation marks. After entering the access data, the Info page is displayed.

The language can be switched between German and English with the DE / EN switch at the top right. On the first visit it follows the language of the browser. The menu is divided into three groups:

Controller
Info, Status
Settings
Network, System time, Services, Password
Maintenance
Project, Software update, USB backup, Portal backup, Files, Connection test, Reboot

Note: Controllers with an older system image still show the previous web interface. Its layout and labels differ from this description.


Info

The Info page shows the serial number, license and versions of the controller.

Serial number
The serial number is used to uniquely identify the controller. This is not the same serial number that is printed on the controller. This number is a so-called GUID; since this number is also used for service access, it is generated separately for each controller and cannot be guessed by counting up.
License
If the controller is licensed, "valid" is displayed here in green, otherwise "not valid" in red.
License type
Type of the license.
Project
Name of the project running on the controller.
Runtime version
Version of the runtime.
System image
Version of the system image. Some functions require a minimum version, which is stated in this help where applicable.
VPN
The VPN server the controller is assigned to, and the IP address of the controller in the VPN.
Device name
Name of the controller in the network.

Status

The Status page shows load, memory and network of the controller. The values refresh every 5 seconds.

System

System time
Current time of the controller.
Uptime
Time since the last start of the controller.
Runtime
"running" in green or "stopped" in red.
Processor
Current clock frequency in MHz and temperature of the processor.
Load 1 / 5 / 15 min
Average load over the last 1, 5 and 15 minutes. Below it the number of processor cores is shown: values above the number of cores mean overload.
Memory
Used and total memory, also shown as a bar.
Memory card
Used and free space on the memory card, also shown as a bar.

Network

For each network interface, the IP addresses, the MAC address and the amount of data received (RX) and sent (TX) are shown.


Network

The IP address of the controller is set on this page.

Local IP address

DHCP
Obtain the address automatically from the router. If DHCP is switched on, address, gateway and DNS are provided by the DHCP server of the network, and the fields for the fixed address are hidden.
IP address
Static IP address
Network mask
Network mask
Gateway
Default gateway
DNS 1 / DNS 2
DNS server. Two DNS servers can be specified, DNS 2 is optional.

Virtual IP address

In addition to the standard network settings, a virtual static IP address can be specified. This fixed second address always keeps the controller reachable, for example if no DHCP server is available. The default is "172.31.1.100". Please note that if the controller is set to DHCP, a DHCP server must also be available in the network; if no DHCP is available in the network, DHCP must therefore always be switched off and a fixed IP address assigned. The IP address "172.31.1.100" must also not collide with the network; if the network in which the controller is operated also uses "172.31.1.", the virtual IP address should be changed.

IP address Static IP address. It must differ from the local IP address.
Network mask Network mask
Gateway (optional) Default gateway. If no gateway is available for the virtual IP (for example if no VLAN is used), the field must be left empty; this is also the default setting.
Route (optional)
Optionally, a route can be entered here if the virtual IP address is used as a backbone. The route is executed as a command when the controller starts and must be a single line. E.g.: route add -net 172.31.2.0 netmask 255.255.255.0 dev eth0:1 gw 172.31.1.1

Click on "Save" to save the settings of both sections. The new settings apply only after a reboot of the controller. After saving, the button "Go to reboot" appears, which leads to the Reboot page.


System time

The clock of the controller, the automatic synchronisation and the time servers are set on this page.

Current time of the controller
Running clock with date and time zone of the controller. Below it, it says whether the time is "synchronised with time server", "not synchronised yet" or "set manually".
Synchronise automatically via the internet
With this switch, the system time is automatically synchronised via the configured time servers (recommended). The button "Synchronise now" starts the synchronisation right away.
Set manually
Enter date and time and click on "Set time". The time is also written to the real-time clock of the controller. If automatic synchronisation is switched on, it overwrites the time again as soon as a time server is reachable.
Time server 1 / Time server 2
Alternative time servers (NTP) can be set here. They are used for the automatic synchronisation and for the synchronisation when the controller starts.

Services

Additional services of the controller are switched on and off on this page. Each service has its own switch; below it, it says whether the service is "running" or "stopped". If a service is not present on the controller, it shows "not installed" and the switch is disabled.

VPN

The switch VPN connection activates or deactivates the service VPN. With this VPN service, the controller automatically connects to the manufacturer's server via a secured VPN connection. The support can access the controller via this connection. This connection can also be used to connect to the controller via the APP without DNS. Registration with email and password is required for this.

In order to use this function, the controller must be able to access the Internet and VPN connections must not be blocked by a firewall.

Important: Please note the disclaimer when using the VPN service. The link to it is also shown on the Services page.

VPN connection
Switch VPN on. Establishing the connection may take a few minutes. Whether the connection is up is shown on the Connection test page under "VPN connected".
Tips:
  • If you allow external access to the controller, the default password should be changed, see Password.
  • If you do not use the service VPN and want to connect from outside, the use of your own VPN is recommended instead of port forwarding.
  • In general, there can always be security gaps with connections via the Internet, so the VPN should only be activated when required, for example for support.
  • The VPN internally uses a network address with 10.10x.0.0/16; this must not collide with the local network.

See also Remote access.

MQTT broker

MQTT broker
This switch activates the local MQTT broker (Mosquitto) on the controller. It is used to connect devices that support MQTT to the controller, for example Shelly devices.

The internal MQTT broker is available from image version 3.034. The image version is shown on the Info page as "System image".

Depending on how heavily the MQTT broker loads the controller, the SD card is subject to greater wear. An industrial memory card is therefore recommended. It is optionally available.

This broker is used by all Shelly blocks as well as MQTT input, MQTT output and MQTT Addresses I/O with server type "Internal". If it is switched off, the error messages of the diagnostics show "MQTT BROKER OF CONTROLLER NOT REACHABLE" with the affected blocks, see MQTT devices - general.

Node-RED

Node-RED
This switch activates the Node-RED software (from image version 3). The Node-RED platform contains many additional interfaces that can be used with uniPRO.

The link "Open the Node-RED editor (port 1880)" opens the Node-RED user interface.

See https://nodered.org/
Important:

  • Depending on the nodes used, the Node-RED software can require considerable resources. For large projects, the use of an industrial memory card is recommended.
  • Node-RED and Matter should not be enabled on the controller at the same time. Running both services together causes very high memory usage, which may reduce the service life of the SD card.
  • Communication between Node-RED and uniPRO can take place via the function block MQTT addresses IO. The broker on the controller can be used as the MQTT broker for this.
  • This software is third-party software. We have no influence on its development. For software support, please contact the corresponding support forums and documentation of the respective projects.

KNX IP gateway

Internal KNX IP gateway
The web interface no longer has a switch for the internal KNX IP gateway. The runtime starts and monitors the gateway itself, depending on the KNX interface block in the project: with the type “KNX-IP gateway onboard” it runs, with any other type and without a KNX block in the project it is stopped.

Via the internal gateway, KNX devices can also be programmed with the ETS. The ETS finds the gateway via the automatic interface search.
Important:

  • For programming KNX devices with ETS 6.1 or newer, the image version of the controller must be at least 4.011. The image version is displayed on the Info page as "System image".
  • The internal KNX IP gateway only works if the controller is connected to the KNX bus and the bus has voltage. Without a bus it shuts itself down after a few seconds and is restarted by the controller at growing intervals (up to 30 seconds); the ETS then cannot keep a connection. A test without a KNX bus, e.g. in the office, is not possible.
  • The internal KNX IP gateway is third-party software. We have no influence on its development, therefore functionality with future versions of the ETS cannot be guaranteed.

Password

The password for logging in to the web interface is changed on this page. Enter the new password under "New password" and "Repeat password" and click on "Save".

Important: Only the password for the web interface (user admin) is changed, the password for the project remains unchanged. After saving, the browser asks for the login again.


Project

On this page, the project and the persistent data of the controller are downloaded or loaded onto the controller. The Studio is not needed for this.

On the controller

Project
Name of the project on the controller.
Project file (.upro) / Project file (.zpro)
Size and date of the project file. If one of the two files is missing, it shows "not available".
Persistent data
Size and date of the file with the persistent data (setpoints, counter values, control element settings).
Runtime
"running" or "stopped".
Download
"Download project (.upro)", "Project as .zpro", "Persistent data" and "Everything as .tar.gz" (project files and persistent data in one archive). Only the buttons for which a file exists are shown.

Note: The runtime writes the persistent data to the memory card every hour. The download contains the state written last; changes made since then are not included.

Load onto the controller

Project
Project file .upro or .zpro from the Studio, or pt2020_boot.db. Leave empty to load only the persistent data.
Persistent data
File pt2020_persistent.db. Leave empty to keep the current values.
Load onto the controller
Loads the selected files onto the controller after a confirmation prompt. A progress bar shows the process; afterwards the runtime runs with the new state.

Important: The runtime is stopped briefly for this. The current state is backed up first and can be restored in the Studio via Restore backup.


Software update

The runtime of the controller is updated on this page. The installed version is shown at the top. The runtime restarts after an update; the controller cannot be operated for about 30 seconds. A progress bar shows the process.

Via the internet
The button "Start update" downloads the current runtime from the uni-PRO server and installs it. The controller must be connected to the Internet for this; the VPN does not have to be active. If the runtime cannot be downloaded, the current one keeps running.
Upload file
For controllers without internet, or if a specific version is to be installed: select the runtime file (pt2020rt.bin) and click on "Upload and install". Only genuine runtime files for the controller are accepted.
Tip: Only update the controller if there is a reason to do so, for example bug fixes or new features. If the system is running without problems, there is no need for an update.

USB backup

On this page, the data of the controller is backed up to a USB stick or restored from it. The project folder of the controller is saved to the folder pt2020-backup on the USB stick. The USB stick should be FAT formatted.

Back up automatically every day
With this switch, a backup to the USB stick is created automatically once a day at night. It is switched on by default: as soon as a USB stick is plugged in, it is backed up from the next night on. Without a stick nothing is written. To test the function or whether the USB stick is compatible, the backup should be carried out manually once.
Back up to USB stick The data is backed up to the USB stick right away. Afterwards check the data on the USB stick.
Restore from USB stick After a confirmation prompt, the controller data is replaced by the backup on the USB stick. The runtime is stopped for this and started again afterwards.

If no USB stick is inserted, the page reports "No USB stick found". If there is no backup on the stick, "There is no backup on the USB stick (folder pt2020-backup)" appears.


Portal backup

On this page, the data of the controller is backed up to the manufacturer's online portal or restored from it. The current project including the persistent data is saved. Older runtime backups stay on the controller. A token is required for use; you receive it via the portal. The controller must be connected to the Internet for this; whether the portal is reachable can be checked on the Connection test page.

Important: Please note the disclaimer when using the backup service; the link to it is displayed on the page.

Portal access
Enter the token from the portal and click on "Save". The token is hidden; with "Show token" it becomes readable.
Back up automatically every day With this switch, a backup is automatically transferred to the portal once a day at night.
Back up to portal The data is backed up to the portal right away. After a successful backup, the data should be checked on the portal.
Restore from portal After a confirmation prompt, the controller data is replaced by the backup from the portal. The runtime is stopped for this and started again afterwards.

Files

This page shows the files in the project folder of the controller, for example logs and exports.

Upload file
With "Upload", the selected file is placed in the project folder of the controller. The project and the persistent data are not loaded here but on the Project page.
Project folder
List of the files with name, size and date of the last change (Modified) as well as the free space on the memory card. Clicking on the name downloads the file.

With "Delete", only files with the extension .csv, .txt, .mon and .db can be removed. The project file and the persistent data cannot be deleted here; they are managed on the Project page. Deleted files cannot be restored.

Connection test

This page continuously checks whether the controller reaches the servers for update, e-mail, portal and VPN. The check is repeated every 5 seconds. Each line shows "reachable" in green or "not reachable" in red, followed by the server checked.

Name resolution (DNS)
The controller can resolve server names into IP addresses. If this point fails, usually the DNS settings under Network or the gateway are wrong; all other points then fail as well.
Update server
Server for the software update via the Internet, port 80 is checked.
E-mail server
Server for sending emails, port 465 is checked. This test only tests the manufacturer's server. If an alternative mail server has been set, it is not tested.
Portal (backup)
Server of the online portal for the backup, port 443 is checked. See Portal backup.
VPN server
The assigned VPN server is basically reachable; this is the prerequisite for a VPN connection to be established at all. If this point stays red, the connection is usually blocked by a firewall.
VPN connected
VPN connection successfully established - the controller is reachable via the VPN server.

VPN server and VPN connected show "not set up" as long as no VPN server has been assigned to the controller yet. This is not an error.


Reboot

The controller can be restarted on this page. To do this, click on "Reboot now" and confirm the prompt. The restart takes about one minute; the page reloads as soon as the controller is reachable again. A restart is necessary, for example, after changing the network settings.


Technical data

Supply voltage 24V DC +15%, -5%
Current consumption 200mA
CPU ARM quad core up to 1.2 GHz, 512M RAM
Addresses up to 4000 BUS addresses (variants with 128 or 1000 addresses for larger order quantities)
Interfaces RS485, RS232, (optional KNX), Ethernet, USB
Real-time clock Real-time clock with battery
Housing 45mm modular system WxHxD: 70x90x58mm
Terminals Plug-in terminals with push-in connection, up to 1.5 mm²
Mounting DIN rail TS35
Ambient temperature -10...+50°C
Protection class IP20

Re-flashing the SD card

The operating system of the controller is located on an SD card on the CPU board. If this SD card is defective or the system is damaged, a new SD card can be written (flashed) with the image. The following instructions describe step by step how to proceed.

What you need

Step 1: Back up the license (important!)

When flashing, the SD card is completely overwritten, and the license and the VPN link are also lost. Therefore, be sure to back up the license before flashing if the controller is still reachable:

Important: If it was not possible to back up the license (for example because the controller no longer starts), the controller must be re-licensed and enabled for VPN by the support after flashing. This is only possible with direct access to the controller. In this case, please contact our support.

Step 2: Back up the data

If possible, also back up the project, for example by loading the project into the Studio.

Important: Besides the project, the controller creates its own data on the SD card during operation, for example the recordings of the statistics and the files of the block CSV file. This data is not part of the project and is also lost when flashing. Neither loading the project into the Studio nor backing up the persistent values (step 3) covers it. Therefore back up this data beforehand via the web interface:

If the controller no longer starts, this data can only be restored from an existing backup, for example the automatic daily backup to a USB stick.

Step 3: Back up the persistent values

The persistent values (for example meter readings, setpoints or operating hours) are also stored on the SD card and are lost when flashing. They are not backed up together with the project but in a separate file:

Alternatively, the persistent data can be downloaded without the Studio in the web interface under Project. This download contains the state written last; the runtime writes the persistent data every hour.

Note: A backup is not possible without a connection to the controller. If the controller no longer starts, the persistent values can only be restored from a backup, see USB backup or Portal backup.

Step 4: Flash the image to the SD card

Step 5: Insert the SD card into the controller

Important: The controller has an SD card slot that is visible from the outside. This is only for a software update of the IO board, not for the image. The SD card with this image must be inserted in the controller on the CPU board.

Step 6: Restore the license

Step 7: Restore the project and the persistent values

Finally, transfer the data backed up in step 2 back to the controller, for example under USB backup with "Restore from USB stick", and check the settings (network, VPN, time).


Firmware update

The IO board can be updated via the SD card slot on the outside. Important: This update only updates the firmware of the IO board. Not to be confused with updating the runtime, which is updated via the web interface (Software update). Normally, updating the IO board is only necessary in exceptional cases, for example if new IO modules have been added that did not exist at the time of delivery.

Excerpt from the hardware manual:

Insert the SD card with the unzipped file R02_FW.bin into the directly accessible micro SD socket next to the Ethernet socket and then supply the device with power; the new software will then be loaded automatically.

1x short red (0.2 sec): start of the bootloader
2x short red (0.2 sec): bootloader restarts due to a problem (wrong bin file size, verification error, error writing to the memory);
1x red long (3 sec): the R02_FW.bin file cannot be found
red + green lit: memory is being erased
red + green flashing simultaneously: new firmware is being written to the memory;
red flashing fast / continuously: saving successfully completed, waiting for the SD card to be removed – this is absolutely necessary, otherwise a new update would start with every power cycle)

After the application has started, these LEDs are used to indicate communication with the CPU board. A normal start of the system is indicated by flashing red twice (different duration) and green once. The meaning during operation is described under LED.