Эта страница является переводом страницы ProAV Server Pro. Перевод выполнен на 91%.

Содержание

1 iRidi Pro Server (ProAV Control Processor)
2 Server Setting up
3 Importing a driver to a panel project
- 3.1 Setting commands and feedback channels
4 Testing the server

iRidi Pro Server (ProAV Control Processor)

Installation and launch of iRidi Pro Server on the basis of ProAV Control Processor

The documentation was updated on 18.11.2023

General information

IRidi Pro Server (ProAV Control Processor) - software implementation of iRidi Pro Server, that runs as a daemon or console application on controllers, in particular on the ProAV Control Processor.

These instructions are used for the following products:

ProAV Control Processor Basic (PX-VM20-Basic);
ProAV Control Processor Advanced (PX-VP100-Advanced).

Technical specification

For current technical specifications, please refer to the article on the respective controller:

First start

1 Comnect the controller to the local network and power supply following the instruction.

2 Define the IP address of ProAV Control Processor 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 server in web-browser:

http://192.168.1.254:8888/ (set the address of your 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.

DHCP-server must be active on the router. In case of an error in obtaining an ip address, a static address is set: 192.168.77.77.

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

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 the instruction Reset to defaults, to return the default settings of IP address.

Server Update

1 Open the web-interface of server on the System > Info tab and press the button Update.

2 Tick the Get latest version from the iRidium website checkbox (activated by default) and press UPDATE. The latest version of the server will be installed automatically from the iRidium website.

If it is necessary, you can install a specific version of the server following the link to the update file. To do this, uncheck the Get latest version from the iRidium website box, paste the download link into the input field and press UPDATE.

You can copy the link at iridi.com, in the Downloads section.

The web-server interface will become unavailable for a few minutes, then the updated server will start.

Do not turn off the power supply of the controller during the update process! The update process may take about half an hour if the database is big!

Reset to Default Settings

To reset iRidi Pro Server (ProAV Control Processor) to default settings, follow the instruction:

Before resetting the controller to default settings, disconnect all connected interfaces from it, including network interfaces.

Trouble shooting

If you can't open the web-interface of the iRidi Pro Server (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 (controller) via SSH protocol is required.

Connecting to a Device (Controller) via the SSH protocol

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 the ProAV Control Processor Basic controller>
Port: 22
Connection Type: SSH

and click Open.

4 In the console that appears enter:

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

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

Connecting to a Device (Controller) via the SSH Protocol with the help of the RNDIS System

Connection to a device via the SSH protocol, with the help of the RNDIS system is available only for ProAV Control Processor Advanced.

1 Connect the microUSB interface on the front of your controller to the USB-A interface of your PC using the appropriate cable.

2 You will see one more network adapter - Remote NDIS among network interfaces.

3 Connect the controller via SSH using the following IP address: 192.168.177.77

Changing the Password

1 To change the standard password, use the passwd command when connecting via SSH.

2 The system prompts you to enter a new password. Enter the new password.

Bad password does not restrict you from saving the password you entered. Even if you see a warning, the system will ask you to repeat the password you entered earlier.

If the passwords match, you will see a message about successful password change: password for root changed by root.

Force Start of Server

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

2 Type the command of server launch in background mode (in this case, the server will not stop working when PuTTY stops working)
./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 ProAV Control Processor Basic firmware to the root folder of the controller:
wget -O iridiumPro.ipk --no-check-certificate https://iridi.com/redirects/?go=iRidium_Server_HS_Server

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

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

Or downgrade the version to the older one:
opkg install --force-downgrade iridiumPro.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 iRidi Pro Server (ProAV Control Processor)>
Port number: 22
User name: root
Password: iridi

Click Login.

2 Copy the file to install ProAV Control Processor (.ipk) to the root folder /root of the iRidi Pro Server controller (ProAV Control Processor), 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 the install of newer or the same version of 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

1 When ProAV Control Processor is installed, you can start developing its configuration and logic: Server Project in iRidi Studio.

2 You have to upload the ready project to iRidi Server: Launch of iRidi server configuration.

Setting the ProAV Control Processor driver

ProAV Control Processor - a driver for creating interfaces to control and set an AV-processor.

The ProAV Control Processor has a number of input and output ports to control a variety of equipment:

Inputs: universal inputs R and V (0-50kOhm, 0-12V DC). They are set up as Buttons by default;
Relays: low-current relays (NO, 3A, 24V DC/250VAC);
IR: IR outputs on the rear panel of the device for equipment control and IR input on the front panel of the device for teaching IR commands.

The assignment and functionality of the inputs and outputs is determined by the server project with the ProAV Control Processor driver.

You can add one ProAV Control Processor driver in one server project.

Setting of inputs profiles, as well as selection of processor model is performed only when adding ProAV Control Processor driver from the driver database. Once the driver is added to the project, these settings cannot be changed.

Setting in iRidium Studio

1 Add the ProAV Control Processor driver in the Devices tab in the created server project.

2 In the window that opens, select your ProAV Control Processor model and the required jnputs profile.

Profile:

Button,
Temperature Sensor,
Voltage Sensor.

3 Fill in the required settings of the driver.

Network Setting

Protocol - Serial;
Log Level - level of logging;
Device model - model of the device (PX-VM20-basic);
COM 1 Mode- COM 1 mode:
- RS-232 + RS-485;
- RS-232(CTS+RTS);
Driver Version - version of the driver.

Depending on the selected model, network configuration can be changed.

Setting I/O Interfaces

The ProAV Control Processor has a number of input and output ports to control a variety of equipment:

Inputs: universal inputs R and V (0-50kOhm, 0-12V DC). They are set up as Buttons by default;
Relays: low-current relays (NO, 3A, 24V DC/250VAC);
IR: IR outputs on the rear panel of the device for equipment control and IR input on the front panel of the device for teaching IR commands.

The assignment and functionality of the inputs and outputs is determined by the server project with the ProAV Control Processor driver.

You can add one ProAV Control Processor driver in one server project.

Setting of inputs profiles, as well as selection of processor model is performed only when adding ProAV Control Processor driver from the driver database. Once the driver is added to the project, these settings cannot be changed.

Inputs

Configuration of inputs can be set if the ProAV Control Processor driver is added in the server project. The following configurations are supported:

Button

Dry contact input is used by default, if it isn't configured with the ProAV Control Processor driver. You can enable inversion in the subdevice settings.

Name - device name,
Driver Type - ProAV Control Processor,
Inversion - input inversion (true, false).

Temperature sensor

It allows to connect one of the supported temperature sensors:

VT.AC501
B57164-K_103-J_10
iRidiNTC.

You can enter a calibration value in the subdevice settings.

Name - device name,
Driver Type - ProAV Control Processor,
Sensor Type - type of the sensor,
Calibration value - allowed value of error when measuring temperature,
Deadband - minimum value by which the value from the sensor (from the current one) must change so that the event of changing a feedback channel occurs, regardless of the Pulse setting.
Pulse (min) - timer, through which the value is sent to the bus (in min). 0 - off, minimum value 1, maximum value - an hour.

Voltage sensor

It allows to measure the input voltage value in the range of 0-12VDC

Name - device name,
Driver Type - ProAV Control Processor,
Deadband - minimum value by which the value from the sensor (from the current one) must change so that the event of changing a feedback channel occurs, regardless of the Pulse setting.
Pulse (min) - timer, through which the value is sent to the bus (in min). 0 - off, minimum value 1, maximum value - an hour.

Relay

Normal open by defailt. You can change the behaviour on start, enable inversion and enter the switch-off time in the subdevice settings. Behaviour on start is activated at the next power supply after the device is de-energised.

Name - device name,
Driver Type - ProAV Control Processor,
Inversion - input inversion (true, false),
Auto off time (ms) - time range after which the relay is opened by software,
Behavior on start - starting behaviour.

IR

It allows to control equipment with the help of IR commands. You can set repetition of sending commands and delay between sending commands. To set control you need to perform learning IR commands.

Learning IR commands

1 Launch iRidium Studio.

2 Create a server project and add the ProAV Control Processor driver.

3 Create the required number of commands for the selected subdevice (amount of IR commands depends on AV processor model).

4 Click right mouse button on the subdevice and choose the IR Learning point of the menu (each command can be "learned" separetly, to do it click right mouse button on the required command and select the IR Learning point of the menu).

5 Enter IP address of ProAV Control Processor and select equipment manufacturer from the list. If you don't find your manufacturer, select the Other point and enter the required frequency.

6 Click "Start" button.

7 Point the IR source to the IR receiver on the front of the ProAV Control Processor.

8 Send the required command.

9 Repeat steps 8-9 for other commands.

10 After all commands are learned, the learning process ends automatically.

11 To stop learning process, click the Stop button in the Learning window.

After learning connect IR transmitter to the output that learnt commands and upload the prepared project to the iRidium Server app in ProAV Control Processor. Now you can set sending IR commands from graphic items in i3Pro with the help of the iRidium Server driver.

Setting RS232/485 interface

The working mode of this interface is determined by the ProAV Control Processor driver.

Depending on the model, amount of RS-232/485 interfaces can be different:

ProAV Control Processor Basic (PX-VM20-Basic) - 1 (COM1)
ProAV Control Processor Advanced (PX-VP100-Advanced) - 2 (COM1, COM2)

Simultaneous work of RS-485 and RS-232 (without HRDW Flow Control), the sequence of pins used (from left to right):

Pin	RS-232	RS-485
GND	GND	GND
TX	TX	X
RX	RX	X
RTS	X	В
CTS	X	А

2 Only RS-232 с HRDW Flow Control. The sequence of pins used (from left to right): GND - TX - RX - RTS - CTS
This mode is used by default.

To choose working mode, do the following:

1. Launch iRidium Studio.

2. Create a server project and add the ProAV Control Processor driver.

3. In driver settings change the value of the "COM 1 Mode" parameter, for example to RS-232 + RS-485.

4. Upload the project to iRidium Server.

After these actions the working mode of the COM1 output switches to the chosen one. It allows you to connect the related equipment and control it via the output.

Below you will find an example of setting RS-485 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… and add the "ProAV Control Processor" driver to the created project or use the already created project with the "ProAV Control Processor" driver.

2. Add Modbus RTU driver to the project:

3. Select the value of the "Used with iRidi device" parameter equal to the RS-485 port, for example, ProAV Processor Basic COM 1 (RS-485).

4. Set the connection parameters:

Host: /oem/hal/485_1_port;
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, typically 9600);
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 None);
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 (depends on the presence of support of Modbus multiple function in devices in the bus);
Holding Write Function: type of Modbus-function to send analogue data to the bus (depends on the presence of support of Modbus multiple function in devices in the bus).

In the web-interface, stop bits are displayed as:

iRidium studio:	Web-interface:
1	0
1,5	1
2	2

Read the manuals for 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).

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.

6. After it the project is set to send data via Modbus RTU.

Activation of HRDW Flow Control (RS-232)

HRDW Flow control is a flow control mechanism that is part of the RS232 standard. It makes use of two further pins on the RS232 connector, RTS (Request to Send) and CTS (Clear to Send). These two lines allow the receiver and the transmitter to alert each other to their state. The raising and lowering of these lines allows device drivers which implement hardware flow control code to maintain a reliable data connection between transmitter and receiver. The advantage to this approach is that damaging data in transit does not affect the flow control mechanism (as in Xon/Xoff).

Activation of the HRDW Flow Control mode is available:

for AV&Custom System driver with the Serial protocol type,
in the Used With iRidi Device parameter choose RS-232 port, which has physical outputs with support of CTS and RTS (for example, ProAV Processor Basic COM 1 (RS-232), ProAV Processor Advanced COM 1 (RS-232)).

To activate HRDW Flow Control do the following:

1. Create a new project for iRidium Server in iRidium Studio:File> New > New Server Project… and add the "ProAV Control Processor" driver to the created project or use the already created project with the "ProAV Control Processor" driver.

2. Add the AV&Custom System driver to the project.

3. Select Serial protocol type.

4. Select the value of the "Used with iRidi device" parameter equal to RS-232 port, for example, ProAV Processor Basic COM 1 (RS-232).

5. Change a value of the "HRDW Flow control" parameter to Enable.

6. Change other parameters according to the requirements of the connected equipment.

7. After it your project is set to work through the COM 1 port in the RS-232 with HRDW Flow Control mode.

Setting RS-232 interface

The ProAV Control Processor controller has built-in RS232 ports, which can be used, for example, for data exchange via Modbus RTU or Modbus ASCII protocol.

Below you will find an example of setting RS-232 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… and add the "ProAV Control Processor" driver to the created project or use the already created project with the "ProAV Control Processor" driver.

2. Add Modbus RTU driver to the project:

3. Select the value of the "Used with iRidi device" parameter equal to RS-232 port, for example, ProAV Processor Basic COM 2 (RS-232).

4. Set the connection parameters:

Host: /oem/hal/485_1_port;
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, typically 9600);
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 None);
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 (depends on the presence of support of Modbus multiple function in devices in the bus);
Holding Write Function: type of Modbus-function to send analogue data to the bus (depends on the presence of support of Modbus multiple function in devices in the bus).

In the web-interface, stop bits are displayed as:

iRidium studio:	Web-interface:
1	0
1,5	1
2	2

Read the manuals for other devices in the RS-232 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).

5. 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.

6. After it the project is set to send data via Modbus RTU.

Setting the Bus77 (TCP\IP) interface

By default, the Bus77 interface is activated and you can start working with Bus77 equipment without setting up:

1 In the web-interface of the server go to the System > Other tab and make sure that connection of CAN 0 (TCP Port 30467) (on by default) and CAN 1 (TCP Port 30468) (ProAV Control Processor PX-VP100 is on by default) is activated.

2 In the iRidium Studio create a new Bus77 project: File> New > New Bus77 Project.

3 Connect and scan the Bus77.

4 Add the found devices to the Bus77 project.

If you deactivate the CAN 0 (TCP Port 30467) parameter on the web-interface, it will be impossible to connect to the Bus 77 bus by IP. This mode can be useful to limit TCP connections to the bus during commissioning (scanning and setting the bus is possible only via TCP).

Setting the Bus77 (CAN-bus) interface

To work with Bus77 directly from the iRidium Server app via the CAN interface, do the following:

1 In the web-interface of the server, go to the System > Other tab and deactivate the parameter CAN 0 (TCP Port 30467) (on by default).

2 Create a new server project in the iRidium Studio: File> New > New Server Project.

3 Add the Bus77 driver to the project by importing devices from the Bus77 Home app or using the Bus77 project in iRidium Studio.

4 Upload the ready server project to the iRidium Server application on the ProAV Control Processor.

To control two Bus77 outputs from one server project on the ProAV Control Processor PX-VP100 device, do the following:

1 Open iRidium Studio and create two Bus77 projects.

2 Click “Device is not found” in the first project.

3 Enter IP address of the device and enter port as 30467 (for CAN0 output).

4 Drag'n'drop the found device to the “Device in project” tab.

5 Save a project.

6 Go to the second Bus77 project.

7 Repeat steps 2-5, but enter port as 30468 (for CAN1 output).

8 Create a server project.

9 Import two saved Bus77 projects to the server project.

10 Change the protocol type of Bus77 drivers to CAN.

11 Go to the second Bus77 project with port 30468, that was entered when scanning. Change the port of the driver to CAN1.

Setting KNX interface

iRidi Pro Server (ProAV Control Processor) controller can work as a KNX bus device: it can receive and send commands via the KNX TP1 interface.

iRidi Pro Server (ProAV Control Processor) 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

iRidi Pro Server (ProAV Control Processor) can connect to any remote KNX IP interface or gateway to control it via KNXnet/IP protocol (UDP) through the network. But, if the ProAV Control Processor is connected to the bus via KNX TP1, it is necessary to choose the bus communication using this interface.

1 Connect iRidi Pro Server (ProAV Control Processor) to the KNX bus via 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 Scanner/ 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 Protocol driver setting to Serial - it provides communication between iRidi Pro Server (ProAV Control Processor) and the KNX TP1 interface. Settings of connection to KNX will change completely.

6 Set connection parameters.

To set up the driver fast, select your device in the Used with iRidi device parameter.

Host: /oem/hal/knx_port
Baud Rate: 38400
Data Bits: 8
Parity: None
Stop Bits: 1
Physical Address: the physical address of iRidi Pro Server as a bus device

In the web-interface, stop bits are displayed as:

iRidium studio:	Web-interface:
1	0
1,5	1
2	2

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

This setup don't provide work of iRidi Pro Server (ProAV Cintrol Processor) in the mode of a KNX/IP gateway. To do it, do the following steps.

Read about the further setting up of iRidi Server and the KNX driver in the following sections:

Server as KNX-device and KNX/IP gateway

After the special setting up iRidi Pro Server (ProAV Control Processor) can function as 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.

1 Connect iRidi Pro Server (ProAV Control Processor) to the KNX bus via KNX TP1 interface.

2 Create a new project for the iRidi Server in iRidi studio: File> New > New Server Project...

3 Import and configure as in the previous section or set the KNX Router (KNXnet/IP) / Serial driver manually for communication of iRidi Pro Server (ProAV Control Processor) with the bus via KNX TP1.

Host: /oem/hal/knx_port
Baud Rate: 38400
Data Bits: 8
Parity: None
Stop Bits: 1
Physical Address: the physical address of iRidi Pro Server (ProAV Control Processor) as a bus device.

In the web-interface, stop bits are displayed as:

iRidium studio:	Web-interface:
1	0
1,5	1
2	2

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";   // 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 is launched with the configured driver and script on iRidi Pro Server (ProAV Control Processor) you will be able to find ProAV Control Processor 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). To do this, you need 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 you need to 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 the Line Address field and select the transmission medium.

Press Scan.
The server scans the bus and displays addresses 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 the 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 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.

Setting HDL Buspro interface

HDL gateway is connection between LAN port and CAN port. When HDL gateway of the device is on, devices in the CAN bus can exchange data with devices in the Ethernet as if they were on the one side of the bus. UDP protocol isvused on the side of the Ethernet.

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

Activatng HDL gateway via web-interface

HDL gateway is connection between LAN port and RS-485 port. When HDL gateway of the device is on, devices in the RS-485 bus can exchange data with devices in the Ethernet as if they were on the one side of the bus. UDP protocol is 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.

Activatoin of HDL gateway via web-interface is possible when COM 1 port is connected. To set the gateway to work via COM 2 port, follow the instruction: Setting HDL Buspro on the side and Activating HDL gateway with the help of script.

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

In this case it is impossible to control HDL devices from the iRidium Server application, as there are no 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:

go to the server web-interface, the System/Other tab;

set HDL value in the Server working mode field;

set Enable value in the Gateway HDL filter field;
enter Subnet ID 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, if 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 the HDL Buspro Network driver and the required number of HDL Buspro devices to the project:

3 Set the general parameters of the bus.

To set the interface fast, enter your device in the Used with iRidi device parameter.

Host: /oem/hal/485_1_port
Baud Rate: 9600
Data Bits: 8
Parity: Even
Stop bits: 1
Send Timeout: period to send data to HDL Buspro bus in milliseconds

В веб интерфейсе стоповые биты отображаются как:

iRidium studio:	Web-интерфейс:
1	0
1,5	1
2	2

4 Set parameters of each device in the 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 the 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 for the HDL Buspro device to set the server correctly for data exchange.

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

Setting HDL Buspro on the side of LAN

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

2 Set the general parameters of the network:

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

3 Set parameters of each device in the 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 the 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 (RS-485)"); //name of HDL Buspro (RS-485) 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 with the preset HDL Buspro Network (UDP), HDL Buspro Network (RS485) drivers and the script you can use LAN port of the ProAV Control Processor controller as an interface to access the HDL Buspro serial bus.

As the HDL gateway provides logic connection of two types of buses (Ethernet/UDP and RS485), there is no difference which interface ProAV Control Processor uses 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 convenient functionality that saves time on adding each device to a project manually. iRidium studio requests the status of all devices in Ethernet via the HDL Buspro protocol, gets answers and saves the network configuration and parameters of each device in the project.

1 To scan the devices, click the Scanner/ Import button in the Drivers panel, then click HDL-Bus Pro network scanner:

2 Then scanning starts and you see found devices:

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 will be written in the 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 the HDL gateway is activated in the ProAV Control Processor controller, then all HDL Buspro devices located in RS485 bus will be found when scanning its LAN port. To do it supply power to the controller and devices.

Importing a driver to a panel project

There are several ways to add the ProAV Control Processor driver to a panel project:

to a new panel project,
to a ready visualization project.

Adding a driver to a new panel project

Click right mouse button on the server project and choose "Create panel project" in the menu:

A panel project with an empty page and the iRidium Server driver with all server tags will be created. You can work with them like with commands and feedback channels, i.e., you can assign them to items for control and display and to process with the help of iRidium Script.

After you make changes in a server project, you can synchronize it with a panel project quickly. Choose the iRidium Server driver and click Synchronize.

The file of the server project with which the driver will synchronize can be substituted in Source Project

</div></div>

Adding a driver to a ready visualization project

If you have already created a visualization project and you want to add ProAV Control Processor to it, do the following:

Add the iRidium Server driver from the database;
Enter a path to a *.sirpz project with the ProAV Control Processor driver;
You will get the iRidium Server driver with a list of commands and feedback channels.

If a server project is already created, it can be opened with a right mouse click on a panel project by choosing Open Server Project in the menu.

If a required server project is not entered in the settings of the iRidium Server driver, you see a window to open it in iRidium Studio via Explorer.

Setting commands and feedback channels

To control equipment it is required to set commands (Commands) and feedback channels (Feedbacks). To send a command, drag'n'drop it on a graphic item and enter a value to send. To display feedback drag'n'drop a feedback channel on a graphic item and choose how to output a value.

Read more about work with graphic items in the "Types of graphic items" article.