Эта страница является переводом страницы IRidium Server UMC C3. Перевод выполнен на 98%.

Other languages:

Содержание

1 iRidium server UMC C3
2 Server Setting-up

iRidium server UMC C3

Installation and launch of iRidium server for iRidium pro on the UMC С3 controller

The documentation was updated on 14.8.2023

General information

This article describes the order of work with iRidium server UMC for iRidium pro, to read about iRidium server UMC for iRidium lite click the link: i3 lite

Some models of the UMC C3 controllers have a new Ethernet jack.
Difference: the yellow diode (link) is off (previosly it was always on), the green diode (RX/TX) is blinking during the exchange as before.

Comparison of UMC controllers:

General information about UMC Technology controllers

Warranty period: 24 months.

Technical specification

Characteristics	Value
Direct current voltage of power supply	24V (From 12V to 30V)
Nominal consumed electric power, no more than	2.5W
Working temperature	From 0 to +40 C
Size	72 x 95 x 61
Weight, no more than	0.25 kg
Work mode	247365
Processor	1GHz CPU NXP imx6
RAM	512 MB
Non-volatile memory	4 GB flash
Additional slots	HDL, KNX, RS-485, CAN
Number of tags	more than (no more than 7000 tags is recommened)
Additional information	It's not recommended to use the built-in database.

Addressing signals when modules are connected

A List of Possible Placement Options of Modules

№	Module slot 0	Module slot 1	Module slot 2	Module slot 3	Module slot 4	Code	Example
1	RS-485/ HDL	-	-	-	-	-	A-N-N-N-N-N	HDL Front ModBus Front
2	RS-485/ HDL	ZigBee*	KNX	-	Z-Wave*	-	A-C-B-N-D-N	HDL Front ModBus Front
3	RS-485/ HDL	-	KNX	RS-485	ZigBee*	-	A-N-B-R-C-N	HDL Front ModBus Front
4	RS-485/ HDL	-	KNX	RS-485	Z-Wave*	-	A-N-B-R-D-N	HDL Front ModBus Front
5	RS-485/ HDL	-	KNX	1-Wire	Z-Wave*	-	A-N-B-E-D-N	HDL Front ModBus Front
6	RS-485/ HDL	ZigBee*	KNX	-	-	-	A-C-B-N-N-N	HDL Front ModBus Front
7	RS-485/ HDL	-	KNX	-	Z-Wave*	-	A-N-B-N-D-N	HDL Front ModBus Front
8	RS-485/ HDL	ZigBee*	-	-	Z-Wave*	-	A-C-N-N-D-N	HDL Front ModBus Front
9	RS-485/ HDL	-	-	RS-485	Z-Wave*	-	A-N-N-R-D-N	HDL Front ModBus Front
10	RS-485/ HDL	-	-	1-Wire	Z-Wave*	-	A-N-N-E-D-N	HDL Front ModBus Front
11	RS-485/ HDL	-	KNX	RS-485	-	-	A-N-B-R-N-N	HDL Front ModBus Front
12	RS-485/ HDL	-	KNX	1-Wire	-	-	A-N-B-E-N-N	HDL Front ModBus Front
13	RS-485/ HDL	-	-	RS-485	ZigBee*	-	A-N-N-R-C-N	HDL Front ModBus Front
14	RS-485/ HDL	ZigBee*	-	1-Wire	-	-	A-C-N-E-N-N	HDL Front ModBus Front
15	RS-485/ HDL	ZigBee*	KNX	1-Wire	Z-Wave*	-	A-C-B-E-D-N	HDL Front ModBus Front
16	RS-485/ HDL	ZigBee*	KNX	1-Wire	-	-	A-C-B-E-N-N	HDL Front ModBus Front
17	RS-485/ HDL	ZigBee*	-	1-Wire	Z-Wave*	-	A-C-N-E-D-N	HDL Front ModBus Front
18	RS-485/ HDL	ZigBee*	-	-	-	-	A-C-N-N-N-N	HDL Front ModBus Front
19	RS-485/ HDL	-	KNX	-	-	-	A-N-B-N-N-N	HDL Front ModBus Front
20	RS-485/ HDL	-	-	1-Wire	-	-	A-N-N-E-N-N	HDL Front ModBus Front
21	RS-485/ HDL	-	-	RS-485	-	-	A-N-N-R-N-N	HDL Front ModBus Front
22	RS-485/ HDL	-	-	-	Z-Wave*	-	A-N-N-N-D-N	HDL Front ModBus Front
23	RS-485/ HDL	-	-	CAN	-	ZigBee(USB)	A-N-N-7-N-C	-
24	RS-485/ HDL	-	KNX	CAN	-	ZigBee(USB)	A-N-B-7-N-C	-
25	RS-485/ HDL	-	-	CAN	Z-Wave	ZigBee(USB)	A-N-N-7-D-C	-
26	RS-485/ HDL	-	-	CAN	ZigBee	ZigBee(USB)	A-N-N-7-C-C	-
27	RS-485/ HDL	ZigBee	-	CAN	Z-Wave	ZigBee(USB)	A-C-N-7-D-C	-
28	RS-485/ HDL	ZigBee	KNX	CAN	Z-Wave	ZigBee(USB)	A-C-B-7-D-C	-
29	RS-485/ HDL	-	KNX	CAN	Z-Wave	ZigBee(USB)	A-N-B-7-D-C	-
30	RS-485/ HDL	-	KNX	CAN	ZigBee	ZigBee(USB)	A-N-B-7-C-C	-
31	RS-485/ HDL	ZigBee	KNX	-	Z-Wave	ZigBee(USB)	A-C-B-N-D-C	-
32	RS-485/ HDL	-	KNX	RS-485	ZigBee	ZigBee(USB)	A-N-B-R-C-C	-
33	RS-485/ HDL	-	KNX	RS-485	Z-Wave	ZigBee(USB)	A-N-B-R-D-C	-
34	RS-485/ HDL	-	KNX	1-Wire	Z-Wave	ZigBee(USB)	A-N-B-E-D-C	-
35	RS-485/ HDL	ZigBee	KNX	-	-	ZigBee(USB)	A-C-B-N-N-C	-
36	RS-485/ HDL	-	KNX	-	Z-Wave	ZigBee(USB)	A-N-B-N-D-C	-
37	RS-485/ HDL	ZigBee	-	-	Z-Wave	ZigBee(USB)	A-C-N-N-D-C	-
38	RS-485/ HDL	-	-	RS-485	Z-Wave	ZigBee(USB)	A-N-N-R-D-C	-
39	RS-485/ HDL	-	-	1-Wire	Z-Wave	ZigBee(USB)	A-N-N-E-D-C	-
40	RS-485/ HDL	-	KNX	RS-485	-	ZigBee(USB)	A-N-B-R-N-C	-
41	RS-485/ HDL	-	KNX	1-Wire	-	ZigBee(USB)	A-N-B-E-N-C	-
42	RS-485/ HDL	-	-	RS-485	ZigBee	ZigBee(USB)	A-N-N-R-C-C	-
43	RS-485/ HDL	ZigBee	-	1-Wire	-	ZigBee(USB)	A-C-N-E-N-C	-
44	RS-485/ HDL	ZigBee	KNX	1-Wire	-	ZigBee(USB)	A-C-B-E-N-C	-
45	RS-485/ HDL	ZigBee	KNX	RS-485	-	ZigBee(USB)	A-C-B-R-N-C	-
46	RS-485/ HDL	ZigBee	-	1-Wire	Z-Wave	ZigBee(USB)	A-C-N-E-D-C	-
47	RS-485/ HDL	ZigBee	-	-	-	ZigBee(USB)	A-C-N-N-N-C	-
48	RS-485/ HDL	-	KNX	-	-	ZigBee(USB)	A-N-B-N-N-C	-
49	RS-485/ HDL	-	-	1-Wire	-	ZigBee(USB)	A-N-N-E-N-C	-
50	RS-485/ HDL	-	-	RS-485	-	ZigBee(USB)	A-N-N-R-N-C	-
51	RS-485/ HDL	-	-	-	Z-Wave	ZigBee(USB)	A-N-N-N-D-C	-

Abbreviation:

Name	Code
RS-485/HDL	А
KNX	B
ZigBee* / ZigBee(USB)	C
Z-Wave*	D
1-Wire	E
RS-485	R
CAN	7
-	N

* - out of production.

Installation of Modules

Code	Front RS-485 (Modbus or HDL)	ZigBee inside	KNX	1-Wire	Back RS-485 (Modbus or HDL)	Z-Wave/ZigBee inside
A-N-N-N-N	modbus (dev/ttymxc2): P1: A; P2: B; HDL (dev/ttymxc2): P1: D+; P2: D-
A-C-B-N-D	modbus (dev/ttymxc2): P1: A; P2: B; HDL (dev/ttymxc2): P1: D+; P2: D-	ZigBee (dev/ttymxc3): Z2 - antenna	KNX (dev/ttymxc1): Black(K1): - ; Red(K2): + ;			Z-Wave (/hal/zwt_m3)
A-N-B-R-C	modbus (dev/ttymxc2): P1: A; P2: B; HDL (dev/ttymxc2): P1: D+; P2: D-		KNX (dev/ttymxc1): Black(K1): - ; Red(K2): + ;		modbus (dev/ttymxc3): 2: GND; 3: A; 4: B; HDL (dev/ttymxc3): 3: D+; 4: D-	ZigBee (dev/ttymxc4): Z1 - antenna
A-N-B-R-D	modbus (dev/ttymxc2): P1: A; P2: B; HDL (dev/ttymxc2): P1: D+; P2: D-		KNX (dev/ttymxc1): Black(K1): - ; Red(K2): + ;		modbus (dev/ttymxc3): 2: GND; 3: A; 4: B; HDL (dev/ttymxc3): 3: D+; 4: D-	Z-Wave (/hal/zwt_m3)
A-N-B-E-D	modbus (dev/ttymxc2): P1: A; P2: B; HDL (dev/ttymxc2): P1: D+; P2: D-		KNX (dev/ttymxc1): Black(K1): - ; Red(K2): + ;	1-Wire: 2: 5V; 3: DATA; 4: GND		Z-Wave (/hal/zwt_m3)
A-C-B-N-N	modbus (dev/ttymxc2): P1: A; P2: B; HDL (dev/ttymxc2): P1: D+; P2: D-	ZigBee (dev/ttymxc3): Z2 - antenna	KNX (dev/ttymxc1): Black(K1): -; Red(K2): +;
A-N-B-N-D	modbus (dev/ttymxc2): P1: A; P2: B; HDL (dev/ttymxc2): P1: D+; P2: D-		KNX (dev/ttymxc1): Black(K1): -; Red(K2): +;			Z-Wave (/hal/zwt_m3)
A-C-N-N-D	modbus (dev/ttymxc2): P1: A; P2: B; HDL (dev/ttymxc2): P1: D+; P2: D-	ZigBee (dev/ttymxc3): Z2 - antenna				Z-Wave (/hal/zwt_m3)
A-N-N-R-D	modbus (dev/ttymxc2): P1: A; P2: B; HDL (dev/ttymxc2): P1: D+; P2: D-				modbus (dev/ttymxc3): 2: GND; 3: A; 4: B; HDL (dev/ttymxc3): 3: D+; 4: D-	Z-Wave (/hal/zwt_m3)
A-N-N-E-D	modbus (dev/ttymxc2): P1: A; P2: B; HDL (dev/ttymxc2): P1: D+; P2: D-			1-Wire: 2: 5V; 3: DATA; 4: GND		Z-Wave (/hal/zwt_m3)
A-N-B-R-N	modbus (dev/ttymxc2): P1: A; P2: B; HDL (dev/ttymxc2): P1: D+; P2: D-		KNX (dev/ttymxc1): Black(K1): -; Red(K2): +.		modbus (dev/ttymxc3): 2: GND; 3: A; 4: B; HDL (dev/ttymxc3): 3: D+; 4: D-
A-N-B-E-N	modbus (dev/ttymxc2): P1: A; P2: B; HDL (dev/ttymxc2): P1: D+; P2: D-		KNX (dev/ttymxc1): Black(K1): -; Red(K2): +.	1-Wire: 2: 5V; 3: DATA; 4: GND
A-N-N-R-C	modbus (dev/ttymxc2): P1: A; P2: B; HDL (dev/ttymxc2): P1: D+; P2: D-				modbus (dev/ttymxc3): 2: GND; 3: A; 4: B; HDL (dev/ttymxc3): 3: D+; 4: D-	ZigBee (dev/ttymxc4): Z1 - antenna
A-C-N-E-N	modbus (dev/ttymxc2): P1: A; P2: B; HDL (dev/ttymxc2): P1: D+; P2: D-	ZigBee (dev/ttymxc3): Z2 - antenna		1-Wire: 2: 5V; 3: DATA; 4: GND
A-C-B-E-D	modbus (dev/ttymxc2): P1: A; P2: B; HDL (dev/ttymxc2): P1: D+; P2: D-	ZigBee (dev/ttymxc3): Z2 - antenna	KNX (dev/ttymxc1): Black(K1): -; Red(K2): +.	1-Wire: 2: 5V; 3: DATA; 4: GND		Z-Wave (/hal/zwt_m3)
A-C-B-E-N	modbus (dev/ttymxc2): P1: A; P2: B; HDL (dev/ttymxc2): P1: D+; P2: D-	ZigBee (dev/ttymxc3): Z2 - antenna	KNX (dev/ttymxc1): Black(K1): -; Red(K2): +.	1-Wire: 2: 5V; 3: DATA; 4: GND
A-C-N-E-D	modbus (dev/ttymxc2): P1: A; P2: B; HDL (dev/ttymxc2): P1: D+; P2: D-	ZigBee (dev/ttymxc3): Z2 - antenna		1-Wire: 2: 5V; 3: DATA; 4: GND		Z-Wave (/hal/zwt_m3)
A-C-N-N-N	modbus (dev/ttymxc2): P1: A; P2: B; HDL (dev/ttymxc2): P1: D+; P2: D-	ZigBee (dev/ttymxc3): Z2 - antenna
A-N-B-N-N	modbus (dev/ttymxc2): P1: A; P2: B; HDL (dev/ttymxc2): P1: D+; P2: D-		KNX (dev/ttymxc1): Black(K1): -; Red(K2): +.
A-N-N-E-N	modbus (dev/ttymxc2): P1: A; P2: B; HDL (dev/ttymxc2): P1: D+; P2: D-			1-Wire: 2: 5V; 3: DATA; 4: GND
A-N-N-R-N	modbus (dev/ttymxc2): P1: A; P2: B; HDL (dev/ttymxc2): P1: D+; P2: D-				modbus (dev/ttymxc3): 2: GND; 3: A; 4: B; HDL (dev/ttymxc3): 3: D+; 4: D-
A-N-N-N-D	modbus (dev/ttymxc2): P1: A; P2: B; HDL (dev/ttymxc2): P1: D+; P2: D-					Z-Wave (/hal/zwt_m3)

RS-485 Modules

There are the following types of RS-485 modules:

Module with galvanic isolation, two outputs (A and B signals);
Module with galvanic isolation, three outputs (A, B and GND signals);
Module without galvanic isolation, two outputs (A and B signals);
Module without galvanic isolation, three outputs (A, B and GND signals).

List of possible placement options of the module

Placement of module / modules	Signals on the outputs of the external X6 jack
Placement of module / modules	1	2	3	4	5	6
A two-output module in place 1					A	B
A two-output module in place 2			A	B
A two-output module in place 3	A	B
Two-output modules in places 1, 2 and 3	A1	B1	A2	B2	A3	B3
A three-output module in place 2		GND	A	B
A three-output module in place 2 and a two-output module in place 1		GND	A1	B1	A2	B2

Installation of RS-485 module:

If the module in place 1 — the device is in the /dev/ttymxc1 system;
If the module in place 2 — the device is in the /dev/ttymxc3 system;
If the module in place е 3 — the device is in the /dev/ttymxc4 system.

The front RS-485 module won't work for Modbus if the server is set to work as HDL gateway on the web-interface.

CAN Module

List of possible placement options of the module

Placement of module / modules	Signals on the outputs of the external X6 jack
Placement of module / modules	1	2	3	4	5	6
A two-output module in place 2			L	H
A two-output module in place 3	L	H
Two-output modules in places 2 and 3	L1	H1	L2	H2

Installation of Can module:

If the module is in place 2 — the interface is in the can0 system;
If the module is in place 3 — the interface is in the can1 system.

Before working the interface must be initialized. The following commands must be done in the console:
ip link set canX type can bitrate 125000
ip link set up canX

*Value of parameter bitrate:

10000
20000
50000
100000
125000
250000
500000
800000
1000000

To view statistics of the interface:
ip -details -statistics link show canХ

* Enter the interface depending on the placement instead of canХ.

1-Wire

Now installation of i-wire module is possible in place 2. When it is installed this way, 5V, DATA, GND signals can be received from the green terminal box.

Placement of module / modules	Signals on the outputs of the external X6 jack
Placement of module / modules	1	2	3	4	5	6
A three-output module in place 2		5V	DATA	GND

First start

1 Connect UMC controller to the local net with a PC and a router with the help of Ethernet-cable to LAN port. Supply 24 V power. Wait for about 30 seconds after the power supply, a green LED must be lit.

DHCP-server must be active on the router.

2 Define the IP address of UMC controller with the help of iRidium transfer app or a standard scanner of LAN (for example, Advanced Port Scanner).

3 Use this address to open the web-interface of iRidium server in web-browser:

http://192.168.1.254:8888/ (set the address of your UMC controller!)

The server receives the license and the project from the cloud but the developer (integrator) NOT the user must authorize on the server using the login and password on the iridi.com web site. Launch the server, open the web-interface and activate the server:

Input the login and password of the integrator account where you created the object with the server project
Select the service password to access the server settings. It is 2007 by default.
Then you will see the list of objects and server projects. Select the project which has to work on the server and click on it to download (skip this step if you didn't use iRidium Cloud yet).
In the server web-interface (the Cloud tab) you can download project for the server (Projects) or deactivate the server (Deactivate Server). At the server with an active Test Mode you can download projects from iRidium Transfer.

Feature: On some models of mikrotik and Cisco routers, there may be a problem with obtaining an IP address from a DHCP server, this is due to a longer delay in obtaining an ip address than the server driver subsystem expects when it starts.

Possible solutions:

1. Check that Loopback Detection is disabled.
2. add the port to which the UMC server is connected to firewall exceptions.
3. use another router to set up a static address.

The advice given here is advisory in nature and does not guarantee a 100% solution.

Changing IP address

Change the IP address of the controller to suit your net infrastructure. The settings are available in the server web-interface on the following page System > Network.

You can set:

Dynamic address (DHCP) or
Static address

DHCP address (given automatically):

Static IP address:

To save settings click Save, go to the main page of the web-interface and click Reboot System. The web-interface will become available on the new address.

If you lose access to the web-interface, use this manual Reset to defaults, to return the default settings of IP address.

MAC address must be unique for every device!

Changing hostname

To change the hostname on UMC, you need to:

1. Open the file with a text editor S90hostname;

2. Change the name UMC-HostName to the one you need:

#!/bin/sh

case "$1" in
  start)
     hostname UMC-HostName
     [ $? = 0 ] && echo "OK" || echo "FAIL"
    ;;
  stop)
     [ $? = 0 ] && echo "OK" || echo "FAIL"
    ;;
  restart|reload)
     "$0" stop
     "$0" start
    ;;
  *)
    echo "Usage: $0 {start|stop|restart}"
    exit 1
esac

exit $?

3. Add the file to the /etc/init.d/ folder on the UMC C3;

4. Provide access rights for the file with the chmod 777 "/etc/init.d/S90hostname" command;

5. Restart the UMC C3.

Server Update

Open the web-interface of Server on the System > Info tab and press the button Update. You'll see the edit-box where you have to add the link to the file of update.

You can find the update link on iRidium mobile web-site in Downloads tab.

Link to the latest version of iRidium server UMC software for iRidium pro:

https://www.iridiummobile.net/redirects/?go=iRidium_Server_UMC

Paste the link to the edit-box and press the UPDATE button.

The web-interface of iRidium server will be unavailable for some time and then server will be started automatically.

Do not turn off the power supply of iRidium server when the update process occurs. For the UMC with the big database the update process may take about half an hour!

Factory Reset

To reset the UMC controller to factory settings you must perform the following steps.

1 Press the Prog button on the turned off controller.

2 Holding the Prog button, supply power to the controller.

3 Hold the button Prog till the diode changes its color three times in the following succession (red > green > blue) > and the red color lasts about 1 second. The button can be released only after this succession is done.

4 After it the controller has default settings: initial firmware is respored and automatic getting the IP address via DHCP is activated.

You will get a server version that was installed on the controller at the time or purchase. You must update it up to the release version in the web-interface. If there is a great difference in versions you may have to update the server manually ( see the manual).

Trouble shooting

If you can't open the web-interface of iRidum server UMC (the server won't start, the web-interface doesn't work), use the manual on emergency launch/update/downgrade of the software. To do it, access to a device via a console line is required.

Getting access via a console

1 Define the IP address of the controller in any convenient way (for example, with the help of iRidium transfer or a scanner of LAN).

2 Download and launch the following program PuTTY.

3 Make the following settings:

Host Name (or IP address): <IP address of UMC controller>
Port: 22
Connection Type: SSH

and click Open.

4 The console that appears enter:

Login as: root
root@XXX.XXX.XXX.XXX's password: root (password is not displayed during entering)

5 If the login and password are entered correctly, you'll see a welcome message from iRidium server UMC. A console line becomes available and with its help forced start, update and downgrade can be done.

Force start of server

1 Open the /iridiumserver/: folder:
cd /iridiumserver/

2 Type the command of server launch in background mode (to make it work all the time)
./iridium --force --hidden

3 If everything is successful, the server will start and be ready for work.

Update and downgrade of firmware

The following actions are done if all access to the server web-interface is lost. If there is no Internet access, use this manual Update and downgrade of firmware if there is no access to the Internet.

1 Download the latest version of iRidium server UMC firmware to the root folder of the controller:
wget -O iridiumPro.ipk --no-check-certificate http://iridi.com/redirects/?go=iRidium_Server_UMC

For i3 lite server:
wget -O iridiumLite.ipk --no-check-certificate https://iridi.com/ru/redirects/?go=iRidium_Server_UMC_lite

2 Check the folder contents (make sure that the folder has .ipk file):
ls

3 Start installing a newer or the same version of iRidium server:
opkg install iridiumserver.ipk

Or downgrade the version to the older one:
opkg install --force-downgrade iridiumserver.ipk

If --force-downgrade key is not used when installing an older version, installation won't be done.

4 After installation the server starts automatically. The server is ready to work.

Update and downgrade of firmware if there is no Internet access

1 Install and start WinSCP:

Click New Site folder and set:
File Protocol: SCP
Host name: <IP address of UMC controller>
Port number: 22
User name: root
Password: root

Click Login.

2 Copy the file to install UMC server (.ipk) to the root folder /root of UMC controller, using WinSCP.

3 Check the contents of the root folder in the console line (make sure that the .ipk file is there):
ls

4 Start installing a newer or the same version of iRidium server:
opkg install <file-name>.ipk

Or downgrade the version to the older one:
opkg install --force-downgrade <file-name>.ipk

If --force-downgrade key is not used when installing an older version, installation won't be done.

5 After installation the server starts automatically. The server is ready to work.

Server Setting-up

When the server is installed, you can start developing its configuration and logic: Server Projects in iRidium studio

You have to upload the ready project to iRidium server: Launch of iRidium server configuration

Setting RS485 interface

UMC C3 controller has a built-in RS485 port, that can be used for example for data exchange via Modbus RTU or Modbus ASCII protocols.

The main RS485 port of UMC C3 controller does not have galvanic isolation. Use the optional port (in the upper part) if you need galvanic isolation.

Below you'll find an example of setting RS485 interface to work via Modbus RTU. Other protocols (drivers) are set the same way.

1 Create a new project for iRidium server in iRidium studio: File> New > New Server Project...

2 Add Modbus RTU driver to the project:

3 Set connection parameters:

Host: port number in Linux OS (standard /dev/ttymxc2 or optional /dev/ttymxc3). Port numbers in UMC C2 and UMC C3 are different.
Update Time: time for data update in milliseconds
Baud Rate: speed of data exchange, bit/s (depends on the settings of devices in the bus)
Data Bits: number of data bits (depends on the settings of devices in the bus, typically 8)
Parity: checking parity (depends on the settings of devices in the bus, typically - Even)
Stop bits: number of stop bits (depends on the settings of devices in the bus, typically - 1)
Coil Write Function: type of Modbus-function to send binary data to the bus (it is determined by the presence of support of Modbus multiple function by devices in the bus)
Holding Write Function: type of Modbus-function to send analogue data to the bus (it is determined by the presence of support of Modbus multiple function by devices in the bus)

Read manuals of other devices in the RS485 bus: set the same speed of data exchange on all devices, set the same parameters in Data Bits, Parity, Stop Bits. In addition to it, each device in the bus must have a unique ID (Device ID).

4 Set the required number of channels. Set Modbus RTU parameters in each channel:

Device ID: ID of slave device
Type: type of data (Coil, Discrete Input, Holding Register, Input Register)
Address: address where data in a slave device are stored.

5 After it a project is set to send data via Modbus RTU.

Setting HDL Buspro interface

RS485 and LAN ports can be used to exchange data via HDL Buspro protocol.

The main RS485 port of UMC C3 controller does not have galvanic isolation. Use the optional port (in the upper part) if you need galvanic isolation.

Activating HDL gateway via web-interface

HDL gateway is connection between LAN port and RS485 port: when HDL gateway of the device is on, devices in the RS485 bus can exchange date with devices in the Ethernet as if they were on the one side of the bus. UDP protocol used on the side of the Ethernet.

The easiest way to activate the mode of HDL gateway is to do it in the server web-interface in the following folder Network > SYSTEM > Other > Server working mode.

There must be no "HDL-BUS Pro (Serial)" and "HDL-BUS Pro (UDP)" drivers in the project.

In this case the server can't control HDL Buspro devices, as there won't be required drivers in the project.

Filter of HDL-gateway

HDL gateway can filter sending commands in the bus by Subnet ID.
To use this function, do the following:

enter the server web-interface and go to the System/Other tab

set HDL value in the Server working mode field

set Enable value in the the Gateway HDL filter field
enter Subnet ID that is to be used for filtering in the Gateway HDL subnetid filter field.

When the sever gets data, it checks Subnet ID of a device, if it agrees with the one set in the filter, the server processes them, it the ID differs, the server ignores data.

Setting HDL Buspro on the side of RS485

1 Create a new project for iRidium server in iRidium studio: File> New > New Server Project...

2 Add HDL Buspro Network (RS232) driver and the required number of HDL Buspro devices to the project:

3 Set the general parameters of the bus:

Host: port number in Linux OS (standard /dev/ttymxc2 or optional /dev/ttymxc3). Port numbers in UMC C2 and UMC C3 are different.
Baud Rate: 9600
Data Bits: 8
Parity: Even
Stop bits: 1
Send Timeout: period to send data to HDL Buspro bus in milliseconds

4 Set parameters of each device in HDL Buspro bus.

Subnet ID: number of subnet
Device ID: unique ID of a device

Each device in the device subnet must have a unique ID (Device ID).

5 Set parameters of each channel:

The most important parameters of Command and Feedback of HDL Buspro driver:

Operation code: operation (command of HDL Buspro protocol)
Option: option of operation
Channel: channel of a multichannel device
Parameter: parameter of a multifunctional device
Need confirm: confirmation is required (it is recommended to set Disable)
Use Timer: cyclic sending a command (true - turn on, false - turn off)
Timer, s: period to send a cyclic command in seconds

Read the manual of HDL Buspro device to set the server correctly for data exchange.

6 After it the project is set to send data by HDL Buspro protocol via RS485 port.

Setting HDL Buspro on the side of LAN

1 Add HDL Buspro Network (UDP) driver and the required number of HDL Buspro devices to the project:

2 Set the general network parameters:

Send timeout: a period to send data to HDL Buspro net in milliseconds
Connect mode: way to connect to HDL Buspro net (Local - in the local net, Internet - with authorization with login and password, Remote Server - using HDL Remote Server)
Broadcast: mask of IP addresses of broadcasting
Fast Feedback: getting fast feedback without waiting for feedback from a real device
Host: server IP address
Port: server port
Remote Server Priority: priority of remote server (true value is recommended)
Login: login to access HDL Remote Server or the Internet
Password: password to access HDL Remote Server or the Internet
External Port: remote port
Project Name: name of project
Group Name: name of group

3 Set parameters of each device in HDL Buspro bus and parameters of each channel (the way it is described above).

4 After it the project is set to send data by HDL Buspro protocol via LAN port.

Activating HDL gateway with the help of script

Create an empty script file (JS icon on the top toolbar + New Script) and paste the script in it:

IR.AddListener(IR.EVENT_START, 0, function() 
{                                   
   var HDL_UDP = IR.GetDevice("HDL Buspro Network (UDP)"); //name of HDL Buspro (UDP) driver in your project
   var HDL_Serial = IR.GetDevice("HDL Buspro Network (RS232)"); //name of HDL Buspro (RS232) driver in your project
 
    if (HDL_UDP && HDL_Serial) { //check for drivers existence in project
      HDL_UDP.SetParameters({RouteDevice: HDL_Serial.Name});
      HDL_Serial.SetParameters({RouteDevice: HDL_UDP.Name});
   }; 
});

After you launch a project where HDL Buspro Network (UDP), HDL Buspro Network (RS232) drivers are set and that has a script you can use LAN port of UMC controller as an interface to access HDL Buspro serial bus.

As HDL gateway provides logic connection of two types of buses (Ethernet/UDP and RS485), there is no difference which interface UMC controller will use to control devices: commands and feedback will easily go through the gateway. It is enough to set channels in one of the two drivers.

Scanning Ethernet for HDL Buspro devices

iRidium studio has a convenient function that saves time on adding each device to a project manually. iRidium studio requests the status of all devices in Ethernet via HDL Buspro protocol, gets answers and saved the network configuration and parameters of each device in the project.

1 To scan the network, click Scan button in Drivers panel, then click Scan HDL-Bus Pro Net (UDP):

2 After it scanning starts and found devices appear:

3 You can choose what devices to add or not to add to a project by ticking. After clicking OK the selected devices with all parameters are written in в HDL Buspro Network (UDP) driver of the project'.

If there is no HDL Buspro Network (UDP) driver in the project', it will be created automatically.

If HDL gateway is activated in UMC controller then its LAN port is scanned all HDL Buspro devices located in RS485 bus will be found. To do it supply power to the controller and the devices.

Setting KNX interface

UMC controller can work as a KNX bus device: it can receive and send commands via the KNX TP1 interface.

UMC controller can also function as a KNX/IP gateway, i.e. to provide connection of Engineering Tool Software (ETS) with the bus and work as client via the KNXnet/IP protocol (only after setting-up).

Server as KNX device

A UMC controller can connect to any remote KNX IP interface or gateway to control it by the KNXnet/IP protocol (UDP) through the network. But, if the UMC is connected to the bus via KNX TP1, it is necessary to choose the bus communication using this particular interface.

1 Connect the UMC to the KNX bus through the KNX TP1 interface

2 Save the project file in one of the formats: *.pr3, *.pr4, *,pr5, *.knxproj, *.csv. It is recommended to use Latin when giving the name to the project. The Windows language has to be the same with the project language to import names of group addresses correctly.

3 Create a new project for iRidium server in iRidium studio: File> New > New Server Project...

4 Select your ETS project in the menu File > Import and import it. The list of available KNX IP interfaces and group addresses will be formed on the base of the ETS project.

5 After you import the project, change the driver setting Type Driver to KNX (Serial) - it is a KNX driver which provides communication between the UMC and the KNX TP1 interface. Settings of connection to KNX will change completely.

6 Set parameters:

Host: /dev/ttymxc1
Baud Rate: 19200
Data Bits: 8
Parity: Even
Stop Bits: 1
Physical Address: the physical address of the UMC as a bus device

7 Now the setup is complete. When you start the project on the UMC server the connection will be established to the bus via the TP1 interface, the UMC will be shown as a bus device (it will have its physical address) although it will not have its own group addresses.

This setup will not provide work of UMC controller in the mode of a KNX/IP gateway. You have to do the settings described below.

Read about the further setting up of iRidium server and the KNX driver in the following sections:

Server as KNX-device and KNX/IP gateway

After the special setting up the UMC can perform functions of a KNX/IP gateway:

it provides connection of ETS with the bus (it is searched and added to ETS as a KNX interface)
it provides connection of clients to the bus by the KNXnet/IP protocol
it provides transfer of multicast packets from other KNX IP interfaces to the bus (routing)

1 Connect the UMC to the KNX bus through the KNX TP1 interface

2 Create a new project for iRidium server in iRidium studio: File> New > New Server Project...

3 Import and configure (see the previous section or manually) the driver KNX Serial (UMC) for communication of the UMC with the bus via KNX TP1.

Host: /dev/ttymxc1
Baud Rate: 19200
Data Bits: 8
Parity: Even
Stop Bits: 1
Physical Address: the physical address of the UMC as a bus device

4 Create an empty script file (JS icon on the top toolbar + New Script) and paste the script in it:

IR.AddListener(IR.EVENT_START,0,function() 
{
   var KNXSerial = "KNX Router (KNXnet/IP) / Serial (UMC)";   // name of KNX Serial driver in your project
 
   if(IR.GetDevice(KNXSerial)) { 
      IR.GetDevice(KNXSerial).SetParameters({ServerDevice: "KNX IP"});
   }
   IR.CreateDevice(IR.DEVICE_KNX_IP_SERVER, 
                  "KNX IP",
                  {Port: 3671, 
                  ClientDevice: KNXSerial
                  });
});

5 After the project with the configured driver and script is launched on the UMC, you will be able to find the UMC in ETS and use it as an interface to access the bus.

Server as KNX/IP gateway

There is an easier way to activate the KNX/IP gateway function without creating a driver or scripts as described above. All that has to be done is to activate the KNX/IP gateway mode in the web-interface in the following folder Network > SYSTEM > Other > Server working mode.

There must be no driver of "KNX Serial" type in the project.

The server can't work as a KNX device in this case.

Scanning and monitoring KNX bus

To monitor and scan the bus set server as KNX/IP-gateway.
After it launch ETS app to set and debug KNX devices and go to the Bus tab. Connect a required interface.

Scanning KNX bus

Scanning the bus allows to see devices connected to one bus of KNX network.
To do it, go to the corresponding tab of the menu:

Fill in Line Address field and select data transfer medium

Click Scan.
The server scans the bus and displays on the screen addressed of all devices connected to the bus.

Monitoring KNX bus

There are 2 types of monitoring in ETS

monitoring of group operations;
monitoring of the bus.

Monitoring of group operations allows to read the current state of a definite device and write a new value in it. To do it, go to the Group Monitor tab and click Start.

To read a value or to write a value to a device, enter the device address in the Group Address field.

When Read button is clicked, a value from a device in the bus appears in the table

To change this value, write a new value in the Value field and click Write.

Monitoring of the bus displays all data packets sent in the bus.
To do it go to the Bus Monitor tab and click Start

Starting a project in test mode

Test mode allows you to upload and test the projects from iRidium studio without buying of license. When you upload the project from iRidium cloud it uses commercial or Trial license.

You can upload the project from iRidium Studio to the Server with help of iRidium transfer software. The "Test mode" on Server must be turned on.

In iRidium transfer press Search button when the server are ready. As a result of the search you will see a new device in Transfer with the name <NAME> (Server)

Activate the option "Test Mode: ON" in the server settings to use it in the fully functional mode. You can see more information about the use modes in the section Licensing Policy.

Check if the Test Mode is activated by clicking a button in the bottom left corner.

With the activated Test Mode you can also test work of cloud projects and upload projects from iRidium transfer (locally, without iRidium cloud).

Monitoring KNX bus with the help of ETS

iRidium server pro version 1.2.11 and later supports monitoring KNX bus with the help of Engineering Tool Software (ETS). To do it, activate KNX/IP-gate, as written in the manual Server as KNX/IP gateway.

1 Launch ETS. Go to the Diagnostics tab.

2 Next go to the Bus Monitor tab.

3 Select from the list the GatewayKNXServerIP interface that you want to monitor.

4 Click Start. You can see all data that go via the KNX/IP gateway in real time.