Upgrading to REX version 2.50.4

New version of REX (2.50.4) is out and all users can upgrade for free. Follow the instructions below for upgrading from REX 2.50.1 or from REX 2.10.x.

In any case, it is recommended to backup the content of the /rex/rexcore directory on your target device prior to upgrading. If you do not know how to do it, don't worry. In such a case the only thing you might need are the licensing keys and you can always find these in your user accout here at our webpage.

Upgrading from REX version 2.50.1

It is recommended to upgrade both the development tools on your desktop/laptop PC and the runtime modules on your target device(s).

Development tools

Install the newest version of development tools. Only Windows 7/8/10 is supported.

Version 2.50.4 allows you to connect to any 2.50.x device, therefore you can uninstall version 2.50.1.

Target device - Full upgrade including operating system

It is highly recommended to upgrade your OS to the newest version.

  • If you are using Raspberry Pi, download the newest Raspbian image and write it to your SD card.
  • Follow the instructions bundled with installation scripts in our GitHub repository.
  • After installation is complete, your target device is running version 2.50.4 and is ready for use.
  • Your licences are valid, just re-apply the licence key (SiteKey) when asked for it while connecting to your target device.

Target device - Upgrade REX only

ONLY IF you are running an up-to-date Debian Jessie based distribution of Linux (e.g. Raspbian Jessie) and want to upgrade only RexCore on your target device, follow the instructions below.

WARNING - Note that your running algorithms will be restarted during upgrade!

Update information about available packages

sudo apt update

and install the newest version of the RexCore runtime module

sudo apt install rexcore

which will also upgrade all dependent packages.

After installation is complete, your target device is running version 2.50.4 and is ready for use. Your licences are valid, check that the algorithm is running after the upgrade. If needed, just re-apply your licence key (SiteKey).

Known problems

There are known problems which you need to solve while upgrading from 2.50.1 to 2.50.4:

  • Modbus communication driver: if Modbus RTU communication (RS-232 or RS-485) fails after upgrade, try increasing the Sync time parameter in Modbus driver configuration. Start at 0.05 and go lower as long as the communication is still working.
  • 1-Wire communication driver (via OWFS, module OwsDrv): make sure to use localhost instead of 127.0.0.1 in OwsDrv configuration in your project.
  • OWFS configuration on the target device: make sure to use localhost instead of 127.0.0.1 in the /etc/owfs.conf configuration file
  • RexHMI Designer: it is necessary to open the SVG source file at least once and Resize it (due to changes in DPI settings of Inkscape 0.92) and run Update Components extension (due to updates in RexHMI components, Extensions->RexHMI->Update Components). Afterwards save the SVG file, compile and download your project again and you should be up and running.
  • The workflow in RexDraw was slightly changed. The connection to the target device is now independent of the application mode (development or watch mode).
  • Should you run into troubles, contact us and we'll be happy to help.
  • Even if everything goes smoothly, we'll highly appreciate your feedback about the new version.

Upgrading from REX version 2.10.x

It is mandatory to upgrade both the development tools on your desktop/laptop PC and the runtime modules on your target device(s).

Development tools

Install the newest version of development tools. Only Windows 7/8/10 is supported.

As long as you have at least one target device with version 2.10.8 or older, you should keep the development tools 2.10.8 installed. As soon as you upgrade all your target devices to 2.50.4, you can uninstall version 2.10.8.

You can have multiple versions of development tools installed at the same time. You just have to pay attention to which version you are running and opening your projects in. The RexTrayMon utility is a big help in this case.

Target device - Full upgrade including operating system

It is highly recommended to upgrade your OS to the newest version. For users of Raspbian Wheezy on Raspberry Pi, this is mandatory.

  • If you are using Raspberry Pi, download the newest [url=https://www.raspberrypi.org/downloads/raspbian/]Raspbian image[/url] and write it to your SD card.
  • Follow the instructions bundled with installation scripts in our GitHub repository.
  • After installation is complete, your target device is running version 2.50.4 and is ready for use.
  • Your licences are valid, just re-apply the licence key (SiteKey) when asked for it while connecting to your target device.
  • It will be necessary to compile and download your project again using the newest version of the development tools.

Target device - Upgrade REX only

ONLY IF you are running an up-to-date Raspbian Jessie image and want to upgrade only RexCore on your Raspberry Pi, follow the instructions below.

WARNING - Note that your running algorithm will be stopped during upgrade! Moreover, it will not restart afterwards. It will be necessary to compile and download your project again using the newest version of the development tools.

Please run the following:

sudo -s 
echo 'deb http://download.rexcontrols.cz/repositories/debian-rex-2.50/ jessie non-free' > /etc/apt/sources.list.d/rexcontrols.list 
apt update 
apt install rexcore 
apt purge lighttpd rexwstcp

After installation is complete, your target device is running version 2.50.4 and is ready for use.

  • Afterwards you can compile and download your project using the newest version of the development tools.
  • Your licences are valid. If needed, just re-apply your licence key (SiteKey).

Things you should know

These are the most important changes and known problems which you should know before upgrading from 2.10.x to 2.50.4:

  • In general, a lot has changed. An upgrade is definitely worth the effort. Although you are experienced users of REX, it is recommended to go through the Getting started manual which will help you with the transition to new version.
  • The workflow in RexDraw was slightly changed. The connection to the target device is now independent of the application mode (development or watch mode).
  • Zoom is available in RexDraw.
  • Connecting blocks is much easier.
  • HMI: there is no need to manually export and download HMI files to the target device. HMI is now included in your project and compiles automatically. See the RexHMI documentation
  • RexCore contains an internal webserver (default port 8008). There is no need to use the lighttpd webserver.
  • RexHMI Designer: it is necessary to open the SVG source file at least once and Resize it (due to changes in DPI settings of Inkscape 0.92) and run Update Components extension (due to updates in RexHMI components, Extensions->RexHMI->Update Components). Afterwards save the SVG file, compile and download your project again and you should be up and running.
  • The REXLANG block now needs a separate licence. Contact us and we'll generate it for you.
  • REXLANG block: there are numerous changes, especially in commands for opening communication buses (UART, SPI, I2C, UDP, TCP). See the REXLANG documentation.
  • Modbus communication driver: if Modbus RTU communication (RS-232 or RS-485) fails after upgrade, try increasing the Sync time parameter in Modbus driver configuration. Start at 0.05 and go lower as long as the communication is still working.
  • 1-Wire communication driver (via OWFS, module OwsDrv): make sure to use localhost instead of 127.0.0.1 in OwsDrv configuration in your project.
  • OWFS configuration on the target device: make sure to use localhost instead of 127.0.0.1 in the /etc/owfs.conf configuration file
  • REST API is available, REX is more open than ever.
  • Database connection driver (via ODBC, module DbDrv): if you are using REX archives, check the numbering of archives in the database driver configuration. The numbering of archives was unified. All places use numbering starting from 1, therefore it is necessary to update your DB driver configuration. Please open the configuration dialog and set ArchiveID=1. Or change it directly in the .rio file.
  • Should you run into troubles, contact us and we'll be happy to help.
  • Even if everything goes smoothly, we'll highly appreciate your feedback about the new version.
published: 2017-05-18
updated: 2017-05-24