Upgrading the IDE Solution to version 2.6.5

When upgrading from an older version of Mervis IDE to version 2.6.5, you may encounter problems. The most common problem may be an old Unipi device definition. However, many things have changed in new version, so the Mervis-tutorials have also been updated.

Since the configuration of the network interfaces has been completely redesigned, it is necessary to check and set the entire network configuration according to your own requirements. This setup is part of the RT configuration and is described in this article.

If the data points do not communicate (they are red during debugging and there are many errors in the system status), it is necessary to change the device port from 502 to 50200 in the solution, or replace the Unipi device definition with a new version from the library. The new version, labeled v2_3, is available for Patron, Neuron, and Gate. The exception is Patron LTE with v2_4.

1. add new device definition from the library
2. copy the name and remove variables of the original device (reset autogen)
3. i the “autogen name ” is used, the names of the data points in the new device must also be set
4. delete the original device and set the name of the new one to the original name
5. set autogen
6. compile & done

In this version we have changed the counter data types for the new Unipi device definitions from dword to udint and for PWM from word to uint, so that mathematical operations can be implemented without the need to convert data types.

All new Unipi device definitions have been modified to better optimize communication with them.

For example, for analog controllers, the NStatus2_rd group was shortened (from 16 to 2 registers) and the NAiAo2_rd and NStatus_WDboot2_rd groups were newly created. Since they are separate groups, it is now easier to set different Modbus polling intervals for DI and for AI or MWD.

Mervis IDE reports the message “An outdated version of the “Patron L527” device is used. The device must be replaced with a suitable device from the current library.” to inform the user that an obsolete device definition is used. This is because the Mervis IDE in which the solution is opened includes a newer version of the device - older versions are therefore marked as obsolete.

If this happens, it is very likely that the data points of this older device definition will not communicate. Therefore, the procedure described above applies.

If you have followed all the steps above and still failed to communicate the inputs and outputs, you will probably need to update the firmware of all the controller's input and output boards. This can occur on controllers with FW 5.40 and older. FW update is only possible from the OS Linux command line after connecting via SSH.

If you are not sure how to use fwspi or fwserial (location: /opt/unipi/tools/ ), contact Unipi Technical Support for more information.