Материал из for iRidium developers
Перейти к: навигация, поиск
Эта страница является переводом страницы IRidium Server UMC C3. Перевод выполнен на 100%.

Other languages:
English • ‎русский


the documentation is updated 31.5.2018


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


Comparison of UMC controllers:

General information about UMC Technology controllers


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:


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 iRidium Mobile web site. Launch the server, open the web-interface and activate the server:

  1. Input the login and password of the integrator account where you created the object with the server project
  2. Select the service password to access the server settings. It is 2007 by default.
  3. 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).
  4. n the server web-interface (the Cloud tab) you can download project for the server (see Projects) or deactivate the server (see Deactivate Server). At the server with an active Test Mode you can download projects from iRidium Transfer


CloudServerAuthorize.png
CloudServerServicePass.png
CloudServerProj.png
CloudServerWebCloudTools.png



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:

  • Dinamic address (DHCP) or
  • Static address


DHCP address (given automatically):

UMC StaticAddr2.png

Static IP address:

UMC DHCPAddr.png

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!


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.

UMCWebUpdate.png

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 When holding the Prog button supply power to the controller.

3 Hold the button Prog till the diod changrs its color from red to green and to blue.

4 After it the controller has default settings: automatic getting the IP address is activated (DHCP).


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.

SetupUMCServer01.png
SetupUMCServer02.png


4 The console that appears enter:

  • Login as: root
  • root@XXX.XXX.XXX.XXX's password: root (password is not diplayed during entering)
SetupUMCServer03.png

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.

SetupUMCServer04 2.png


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 iridiumserver.ipk http://www.iridiummobile.net/redirects/?go=iRidium_Server_UMC

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.

Cl server update online.png

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.

Winscp login.png

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

Winscp copy c3.png

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.

Cl server update offline.png

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:


You have to upload the ready project to iRidium server:


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 ACSII 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:

Modbus RTU add.png

3 Set connection parameters:

  • Host: port number in Linux OS (/dev/ttymxc0 or /dev/ttymxc1)
  • 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.
Modbus RTU channel params.png

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.

HDL gate.png

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.


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:

HDL Buspro add.png

3 Set the general parameters of the bus:

  • Host: port number in Linux OS (/dev/ttymxc0 or /dev/ttymxc1)
  • 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.

HDL Buspro device params.png
  • 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:

HDL Command params.png

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:

HDL Buspro UDP add.png

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):

Drivers scan.png

2 After it scanning starts and found devices appear:

HDL Found devices.png

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.

KNX import project ETS.png

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. Leave them by default and specify only the Physical Address - the physical address of the UMC as a bus device.

KNX UMC DeviceType-OnServer.png

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. Indicate an unused physical address for the UMC.

KNX ass Serial UMC.png

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 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
                  });
});

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.

KNX gate.png

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

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


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)

SetupOBserver1.png

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.

ServerTestModeOn.png

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

Test mode checking.png

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