Currency:
USD
  • USD
  • EUR
  • AUD
  • BRL
  • GBP
  • BGN
  • CAD
  • CNY
  • HRK
  • CZK
  • DKK
  • HKD
  • HUF
  • INR
  • IDR
  • MYR
  • MXN
  • NZD
  • NOK
  • PHP
  • PLN
  • RON
  • RUB
  • SGD
  • ZAR
  • KRW
  • SEK
  • CHF
  • THB
  • TRY
  • JPY
Welcome to our store!

Shopping Cart

0 items

Online Chat

Sales (Mon - Fri 08:00 - 17:00 EEST)

Payment

Credit Cards, we accept Visa, MasterCard
Paypal, you can place the order directly via our web shop
Wire transfer, please contact with us for Proforma-Invoice

Verified by

website security

For EU Customers

All prices are WITHOUT VAT 20.00%

If you are located in EU and your company has valid VAT number we will reduce the VAT charge AFTER you make the order as our site does not support online VAT number validation. We do it as partial refund. You can use this online tool for VAT validation: http://ec.europa.eu/taxation_customs/vies/

DRM Software v3

Denkovi Relay Manager v3 (DRMv3) is free software for easy controlling/configurating all kinds of Denkovi Modules.

 

Features

NON-suppored yet Denkovi Modules

Because the DRMv3 software supports most of the Denkovi modules, we list below only the non-supported yet devices from our portfolio:

Order number
Device status
Relay board name and link
DAE-USB_1WIRE In production USB to One Wire converter - Virtual Com Port FT232RL based
DAE-8RELAYS-1WIRE In production One wire relay card - 8 SPDT channels for Home Automation
DAE-8RELAYS-1WIRE-BOX In production One wire relay module - 8 SPDT channels for Home Automation - DIN BOX
DAEnetIP1 Legacy DAEnetIP1 - SNMP Ethernet controller with 28 digital/analog I/O
DAEnetIP1 + DAE-RB/Ro8-12V Legacy Web SNMP controlled 8 Relay Board v1
DAE-PB-RO12/DI8/AI8 + DAEnetIP1 Legacy Internet/Ethernet 12 Channel Relay Board - I/O, SNMP, Web
DAEnetIP1 + DAE-RB/Ro4_v2 Legacy Web SNMP controlled 4 Relay Board

Suppored OS

  • Windows - 7 and above
  • Linux
  • Raspbian - Strech or Buster (Raspberry PI 3 and above)

Requirements

  • Java 1.8 - the recommend is Oracale Java SE Runtime Environment (Java SE Development Kit) 8uXXX. Java version 8u251 seems to be the last, but it is also possible to work with lower version (for example 8u241 or other);
  • OpenJFX (8.60.12) - mostly for Raspbian OS;
  • For some Denkovi modules - additional drivers must be installed. Please refer to their documentation for more information or download the full software packages;
  • Minimal screen size: 1024 x 768 (can work on smaller resolution, but the UI is not optimized yet).
WARNING: Oracale JRE/JDK 8 is the recommended Java. OpenJDK may not work as expected (or at all). Java 9,10,11... are not supported!

Installation and running

The first step must be done is to download the appropriate setup file for DRMv3. If not sure which one, just skip this step and proceed further (will download later).

Version
Release date
Windows
Linux Raspbian
3.0 27.05.2020

DRMv3-full-x86.zip - archive with software, drivers and Oracle Java 1.8 for 32bit Windows OS

DRMv3-full-x64.zip - archive with software, drivers and Oracle Java 1.8 for 64bit Windows OS

DRMv3-full-x86.exe - .exe with software, drivers and Oracle Java 1.8 for 32bit Windows OS

DRMv3-full-x64.exe - .exe with software, drivers and Oracle Java 1.8 for 64bit Windows OS

DRMv3-full-x86.tar - archive with software, drivers and Oracle Java 1.8 for 32bit Linux OS

DRMv3-full-x64.tar - archive with software, drivers and Oracle Java 1.8 for 64bit Linux OS

DRMv3-full-rpi.tar - archive with software, drivers, Oracle Java 1.8 and OpenJFX for Raspbian OS

Version history may be downloaded from here

 

The next step is to check if we have Oracle Java 1.8. Open the cmd.exe or the terminal and write the following command:

java -version

For Oraclae Java you should get similar message like below:

java version "1.8.0_241"
Java(TM) SE Runtime Environment (build 1.8.0_241-b07)
Java HotSpot(TM) 64-Bit Server VM (build 25.241-b07, mixed mode)

If Java version is different than 1.8 or it is not installed, we need to install it.

Windows

In case Java 1.8 must be installed:

Option 1 - We can download and run some of the .exe files for windows and install the Java 1.8 during the installation process.

Option 2 - We can download and extract some of the .zip files for windows with included java. It is in the Java\ directory.

Option 3 - Download and install Java 1.8 from this link: https://www.oracle.com/java/technologies/javase-jre8-downloads.html. We need some of the Windows packages.

 

In case Java 1.8 is installed already:

Just download the some of the .exe or .zip DRMv3 files and skip the Java 1.8 installation.

Please note: If any problems with the .exe file installation, then we can download the archived version of the DRMv3 software from this link: DRMv3-full-x86.zip or DRMv3-full-x64.zip

 

After successful installation, the DRMv3 icon should be on your desktop. From the archived .zip package - we need to run the DRMv3\DRM_v3.jar file.

hint: For Windows in most cases we can run .jar file with double click on it. We can also execute it from the command line promt with:
java -jar path/to/drm/DRM_v3.jar

Linux

Download and extract DRMv3-full-x86.tar or DRMv3-full-x64.tar lets say in /home/user/Downloads/DRMv3/

In case Java 1.8 must be installed:

Option 1 - we can extract the Java 1.8 from the Java\ directory from the .tar archived package.

Option 2 - we donwnload and install it from this link: https://www.oracle.com/java/technologies/javase-jre8-downloads.html (we need some of the Linux packages).

To run the software, we execute the below command (replacing with the respective paths to files):

/home/user/Downloads/jre1.8.0_91/bin/java -jar /home/user/Downloads/DRMv3/DRM_v3.jar

 

In case Java 1.8 is already available:

java -jar /home/user/Downloads/DRMv3/DRM_v3.jar

In the below steps examples we will use only java command for shorter.

Raspbian

Please note: Raspbian OS is not the perfect option to run DRMv3 since it uses JavaFX and it requires more resources for the graphics. Here still remains the rule: the bigger Raspberry PI, the better. We tested with Raspberry PI 3 (Strech) and Raspberry PI 4 (Buster) and for both relaively stable. Of course Raspberry PI 4 with 8GB RAM works quite better.

We also tried to describe all the steps during the installation and running all the packages and libraries for Raspbian, but it still may be additional/different things to do. Please contact us if you find something so we can update the documentation for rest of the users.

In case Java 1.8 must be installed:

Option 1 - we can extract the Java 1.8 (jdk) from the Java\ directory from the .tar archived package.

Option 2 - download and extract the Linux ARM 32 Hard Float ABI package for our Raspberry from this link: https://www.oracle.com/java/technologies/javase/javase-jdk8-downloads.html.

WARNING: Soft Float most probably won't run on Raspberry PI!

Now, we have the java in /home/pi/Downloads/jre/

 

Next is to extract the OpenJFX libraries:

Option 1 - we can extract the armv6hf from the Java\ directory from the .tar archived package.

Option 2 - download from this website: https://gluonhq.com/products/mobile/javafxports/get/. We need JavaFX Embedded SDK for armv6 hard float.

We extract it in /home/pi/Downloads/javafx/

 

If we didn't download DRMv3, we can do that at this step from here: DRMv3-full-rpi.tar and extract to /home/pi/Downloads/DRMv3/

 

Next, after that we need to fix the graphics problem. From our experience JavaFX works best X11 graphics driver option. However by default this package is not installed in Raspbian Strech/Buster. So, below it is shown how to install it:

sudo apt-get update

sudo apt-get install gstreamer0.10 libgstreamer-plugins-base0.10-dev

Now we can add the JVM parameter -Djavafx.platform=x11

 

Next step is to run. Before that however, we have to prepare our -Djava.ext.dirs JVM parameter. For sure we need to include the JavaFX libraries, which we installed above, which means -Djava.ext.dirs=/home/user/Downloads/javafx/armv6hf-sdk/rt/lib/ext

This however will unset the default library path for our application and we need them also. The question is how to find them? The answer is just to run DRMv3 without -Djava.ext.dirs parameter and it will show you these libraries:

java -jar /home/pi/Downloads/DRMv3/DRM_v3.jar

and most probably we will get the following result:

Please add JVM parameter -Djava.ext.dirs=/usr/lib/jvm/jdk-8-oracle-arm32-vfp-hflt/jre/lib/ext:/usr/java/packages/lib/ext:~/armv6hf-sdk/rt/lib/ext where ~ is path to the OpenJFX directory.

Ofcourse the libraries paths may be others, but the idea is the same. Now, we just need to construct our -Djava.ext.dirs. The most important here is to replace the ~ with the /home/user/Downloads/javafx/ from the above step and we get finally for our case:

-Djava.ext.dirs=/usr/lib/jvm/jdk-8-oracle-arm32-vfp-hflt/jre/lib/ext:/usr/java/packages/lib/ext:/home/pi/Downloads/javafx/armv6hf-sdk/rt/lib/ext

then we run the following command:

java -Djava.ext.dirs=/usr/lib/jvm/jdk-8-oracle-arm32-vfp-hflt/jre/lib/ext:/usr/java/packages/lib/ext:/home/pi/Downloads/javafx/armv6hf-sdk/rt/lib/ext -Djavafx.platform=x11 -jar /home/pi/Downloads/DRMv3/DRM_v3.jar

It is possible to get exception: Exception in thread "main" java.lang.UnsupportedOperationException: Unable to open DISPLAY

In such cases, adding DISPLAY=:0 at the beginning may solve the problem:

DISPLAY=:0 java -Djava.ext.dirs=/usr/lib/jvm/jdk-8-oracle-arm32-vfp-hflt/jre/lib/ext:/usr/java/packages/lib/ext:/home/pi/Downloads/javafx/armv6hf-sdk/rt/lib/ext -Djavafx.platform=x11 -jar /home/pi/Downloads/DRMv3/DRM_v3.jar

and finally the splash screen should popup.

UI overview

  1. Menu bar - open/save files, program settings, program skins etc;
  2. Device name and firmware version (if available);
  3. Devices tab - access current selected device resources;
  4. Notifications tab - monitoring of the notifications, sent by some device;
  5. Monitoring and Control tab - access to the device I/O resources (relays, analog inputs, digital inputs etc);
  6. Timers and Pulses tab - access timers, schedules, pulses. Available only for devices with outputs;
  7. Configuration tab - access the device configuration parameters via some protocol. Available only for some devices;
  8. Tools - various tools;
  9. Connection Settings - the settings that are needed for the software to be connected with the device (ip address, port, password etc);
  10. Device image;
  11. Device list - contains list with all currently opened devices;
  12. Available devices list - list with all available device models;
  13. Add - add new device to the list;
  14. Delete - delete the selected device from the list;
  15. Reboot - reboot the device (software reset), only if supported by the device;
  16. Copy - copy selected device and add it to the list;
  17. Del all - delete all devices from the list;
  18. Refresh - read the i/o values for the selected device and refresh them in the UI;
  19. Enable Auto Refresh - enable/disable refreshing of the i/o values automatically (periodically, via the specified refresh interval);
  20. Sample i/o visualization;
  21. Status bar - show the connection status, current time, last seen time, error messages etc;
  22. I/O tabs - device i/o are grouped into tabs as digital outputs, digital inputs, analog inputs etc. Every device may have different number of i/o in each group and not all groups may be present in each device. These tabs depend on the device i/o resources.

Connection Settings

Buttons

  1. Test Connection - this will test if the software is able to connect to the device, based on the entered settings;
  2. Connect - connect to the device. After the device is with status CONNECTED, we can work with it;
  3. Disconnect - disconnect from the device.

Common settings

These settings are available for all devices.

  1. Device type - the main type of the device. Below they are described the settings for every device type separately;
  2. Refresh period, ms - the refresh period between i/o values readings;
  3. Device name - the name of the device shown in the software.
warning: Some devices can appear as more than one device type as they support more than one protocol. For example smartDEN Opener - XML (device_XML) and smartDEN Opener - MQTT (device_MQTT). In such cases the user can select the most suitable connection type.

Also all devices with digital outputs (relays), have the following option:

When it is unchecked - single command, checked - multiple command. Single command sets only one output, while multiple command sets all outputs at a time. Single command does not affect hardware timers, but timings are less aqurate. Multiple command affects hardware timers, but the timings are more aqurate. This option is reasonable only if there are more than one pulising digital outputs lines at the same moment.

Settings for device_DAEnetIP3

  1. Device IP/URL - it can be IP address or DNS name of the device (by default 192.168.1.100);
  2. HTTP API password - must be the same password from DAEnetIP3 web server -> Admin Settings -> HTTP -> HTTP API password (by default admin);
  3. HTTP port - the HTTP port on which the DAEnetIP3 web server can be found (by default 80);
  4. Timeout,ms - the connection timeout in milliseconds;
  5. Retries - the number of retries to connect after unsuccessful connection before give up;

Settings for device_SNMP

  1. Device IP/URL - it can be IP address or DNS name of the device;
  2. SNMP R/W community - can be found from the device web server settings (depending on the device model);
  3. SNMP port - the SNMP server listening port of the device (by default 161);
  4. Timeout,ms - the connection timeout in milliseconds;
  5. Retries - the number of retries to connect after unsuccessful connection before give up;

Settings for device_XML

  1. Device IP/URL - it can be IP address or DNS name of the device;
  2. HTTP password - usually it can be found from the device web server -> General Settings -> Password (by default admin);
  3. HTTP port - the HTTP server listening port of the device. Usually it can be found from the device web server -> HTTP/XML/JSON Settings -> Web HTTP port (by default 80);
  4. Timeout,ms - the connection timeout in milliseconds;
  5. Retries - the number of retries to connect after unsuccessful connection before give up;

Settings for device_XML (smartDEN Logger)

The settings are the same as device_XML but including one more parameter - the directory where the downloaded logs from the smartDEN Logger are stored.

WARNING: It is strongly recommend every smartDEN Logger device to be with different local directory.

Settings for device_FT245

Here we need to select just the FT245RL ID of our board from the drop down menu.

WARNING: For Linux/Raspbian OS it is highly possible at the first moment the software not to detect the FTDI board chip ID. To solve this issue, we need to:

Settings for device_MCP2200

  1. MCP2200 ID - the ID of the board of our board from the drop down menu;
  2. Save relay states - if this option is enabled, when setting the relays, their states will be saved in EEPROM and will be restored after board is booted. This is also used to predefine the relays boot states.

WARNING: For Linux/Raspbian OS it is highly possible at the first moment the software not to detect the MCP2200 board chip ID. To solve this issue, we need to:

Settings for device_VCP

  1. VCP Device ID - the FTDI FT232RL Chip ID (Device ID) of the board;
  2. Read Timeout, ms - read timeout. Normally it shouldn't be changed;
  3. Write Timeout, ms - write timeout. Normally it shouldn't be changed.

WARNING: For Linux/Raspbian OS it is highly possible at the first moment the software not to detect the FTDI board chip ID. To solve this issue, we need to:

Settings for device_WiFi16

  1. Device IP/URL - it can be IP address or DNS name of the device;
  2. TCP/UDP port - it can be found from the device web server -> Sockets -> SOCKET_A Settings / SOCKET_B Settings Port ID (by default 8899);
  3. Protocol - TCP or UDP, depending on the desired preference;
  4. Response timeout,ms - the respone timeout in milliseconds;
  5. Connection timeout,ms - the connection timeout in milliseconds;
  6. Retries - the number of retries to connect after unsuccessful connection before give up.

Settings for device_modbus_tcp

  1. IP/URL - it can be IP address or DNS name of the device;
  2. Modbus port - it can be found from the device web server -> Sockets -> SOCKET_A Settings / SOCKET_B Settings Port ID (by default 502);
  3. Slave ID - the modbus slave id of the device;
  4. Response timeout,ms - normally it shouldn't be changed;
  5. Retries - the number of retries to connect after unsuccessful connection before give up.

Settings for device_modbus_vcp

  1. Serial Port - the serial port of the board;
  2. Slave ID - the modbus slave id of the device;
  3. Response timeout,ms - normally it shouldn't be changed;
  4. Retries - the number of retries to connect after unsuccessful connection before give up.

Settings for device_mqtt

  1. MQTT server - it can be IP address or DNS name of the MQTT server (broker);
  2. MQTT port - the port of the MQTT server (by default 1883);
  3. MQTT username - can be found on the device web server (by default admin);
  4. MQTT password - can be found on the device web server (by default admin);
  5. MAC address - the MAC address of the device;
  6. Timeout,ms - the connection timeout in milliseconds;
  7. Enable notifications - flag for enable/disable notifications receiving for this device by the DRMv3 software.

Status bar

Connection status

It can be the following:

  • CONNECTED - it means the device is connected and we can work with it;
  • CONNECTING - the software is still trying to connect to the device and we can not work with it until we connected to it;
  • DISCONNECTED - the device is disconnected and we can not work with it until we connected to it.

Last seen status

Indicates when the device was seen for last time. Date/Time format can be adjusted ftom Settings -> Application Settings -> Date/Time Format.

Date/Time

System Date/Time. Date/Time format can be adjusted ftom Settings -> Application Settings -> Date/Time Format.

Error status

It shows detailed error message. Usually this explains the reason why is not possible to connect to the device.

Retries

It shows the number of the current connection attempt (given by Connetion Retries parameter if available) to the device before error message appear and status become CONNECTING.

Information status

Detailed information about the current request to the device.

Menu bar

File

  • Open - open existing file with devices;
  • Save - save current file with devices;
  • Save As - save current file witdh devices under different name;
  • Exit - exit from program.

Settings

  • Application Settings - opens window with software settings;
  • Look & Feel Theme - changes the software UI theme (skin) from the built-in list;
  • Custom Look & Feel Theme - changes the software UI theme (skin) from the list defined by the user.

Help

  • Update Devices - upade available device models list (if avaibale);
  • About - information about current version;
  • Documentation - link to this document.

 

 

NEWSLETTER

We accept

 

 

 

Stores

Scroll To Top