====== 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 [[en:sw:01-mervis:06-tutorials|Mervis-tutorials]] have also been updated. ==== Setting up network interfaces ==== 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 [[en:sw:01-mervis:updating-a-runtime-configuration-hidden#network_configuration|this article]]. ==== Data points do not communicate after the solution is deployed ==== 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 [[en:sw:01-mervis:changing-prototypes-hidden|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**. == Definition change procedure: == - add new device definition from the library - copy the name and remove variables of the original device (reset autogen) - i the "autogen name " is used, the names of the data points in the new device must also be set - delete the original device and set the name of the new one to the original name - set autogen - compile & done For Unipi 1.1 & Lite the I/O access has been changed completely and therefore the original device definitions (Modbus and I2C) have to be remapped to the new Modbus only device definition **v2_0** with port 50200. ==== CNT input or PWM output data types are different ==== 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. ==== Optimization ==== 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 warns about a used obsolete device ==== 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 [[#data_points_do_not_communicate_after_the_solution_is_deployed|procedure described above]] applies. ==== Firmware update ==== 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 [[en:automation:unipi-ssh-connect-hidden|connecting via SSH]]. For controllers that have been purchased with FW 6 or have been upgraded to FW 6 before, the firmware will be automatically updated after flash the new Mervis OS 2.6.5.24 We recommend upgrading the firmware to version 6.X even if the inputs and outputs are communicating, so that future updates will be automatic. Always stop the program in the Mervis IDE with the STOP command before the upgrade. If you are not sure how to use //fwspi// or //fwserial// (location: ///opt/unipi/tools/ //), [[en:contact:00-start|contact Unipi Technical Support]] for more information.