Differences

This shows you the differences between two versions of the page.

--- en:sw:01-mervis:use-mervis-runtime-licence-hidden [2021/05/03 07:22]
avsetula [Mervis RT licencing]
+++ en:sw:01-mervis:use-mervis-runtime-licence-hidden [2024/04/03 12:06] (current)
avsetula [There are several possible PLC states:]
@@ Line 4: / Line 4: @@
 Every controller running Mervis has to be, since **Mervis IDE 2.3.0**, licenced in order tu run without any limitation.
-The license is provided free of charge for each [[https://www.unipi.technology/patron-c44|Patron]] and [[https://www.unipi.technology/neuron-c2|Neuron]] controller and also for the [[https://www.unipi.technology/unipi-1-1-c7|Unipi 1.1]] - complete set.
+The license is provided free of charge for each [[https://www.unipi.technology/patron-c44|Patron]] and [[https://www.unipi.technology/neuron-c2|Neuron]] controller.
 </WRAP>
 <WRAP half column 15%>
@@ Line 22: / Line 22: @@
   * **Mervis IDE v2.3.0**
   * [[en:sw:01-mervis:updating-a-runtime-hidden|Updating runtime (RT)]]
-  * 24V DC power supply
+  * 24 V⎓ power supply
   * Internet connection (only from the PC running Mervis IDE, not the PLC)
   * Valid registration at [[https://www.unipi.technology/|Unipi]]
   * Valid Mervis RT licence
 </WRAP>
 =====  Why the PLC be has to licenced? =====
 If the PLC is not licenced, it will run in **demo mode**. The demo mode does not limit the functionality, but the program will run only for **20 minutes**. After that time, the program will stop running and RUN LEDs will start blinking in a 2-second interval (on/off).
 ===== How to obtain the licence? =====
@@ Line 40: / Line 43: @@
 <img src="https://kb.unipi.technology/_media/en:sw:01-mervis:getting-licence-for-mervisdb-db-and-mervis-proxy-04-filling-request-id.png" />
 </figure></html>
-===== How are the licences bound to PLCs? =====
-Each Mervis RunTime licence can be used only once to licence a single Unipi PLC. Licences are not bound to a specific PLC before its activation. Activated licences cannot be used again for a different PLC.
-<html><span class="kbBlueText">Unipi 1.1 & Unipi 1.1 Lite</span></html> \\
-The licence is bound to all parts of hardware, eg. Unipi including the Raspberry Pi. It is not possible to use the same licence to a different configuration of the same controller (ie. swapping the Raspberry Pi for a new, unlicenced one).
 ===== How can I find out if the PLC is licenced? =====
-The licence status of the PLC is displayed in the PLC attachment dialog.
+The licence status of the PLC is displayed in the "**[[en:sw:01-mervis:creating-new-project-hidden#attaching_to_the_controller|Attach PLC]]**" dialog. \\
+The current licencing status of the given PLC is displayed in the **Licence** column.
 <html><figure ondblclick="redirectImg(this)" class="zoom" onclick="zoom(event)" style="background-image: url(https://kb.unipi.technology/_media/en:sw:01-mervis:01-use-mervis-runtime-licence-en.png)">
@@ Line 53: / Line 53: @@
 </figure></html>
-The current licencing status of the given PLC is displayed in the **Licence** column.
+----
+Another way to check the license status is to connect to the controller in a debug mode. \\
+Click **Start Debugging** on the upper ribbon.
+<html><figure ondblclick="redirectImg(this)" class="zoom" onclick="zoom(event)" style="background-image: url(https://kb.unipi.technology/_media/en:sw:01-mervis:01b-use-mervis-runtime-licence-en.png)">
+<img src="https://kb.unipi.technology/_media/en:sw:01-mervis:01b-use-mervis-runtime-licence-en.png" />
+</figure></html>
+Then select the **System Status** window in the middle part of the Mervis IDE, where you will find the item **License status**, on the first line, marked according to the controller name.
+<html><figure ondblclick="redirectImg(this)" class="zoom" onclick="zoom(event)" style="background-image: url(https://kb.unipi.technology/_media/en:sw:01-mervis:01c-use-mervis-runtime-licence-en.png)">
+<img src="https://kb.unipi.technology/_media/en:sw:01-mervis:01c-use-mervis-runtime-licence-en.png" />
+</figure></html>
 ==== There are several possible PLC states: ====
@@ Line 75: / Line 88: @@
 <WRAP center round info 85%>
-In case of repair (warranty or post-warranty), the same licence can be used again, but the whole licencing procedure has to be done again.
+In case of [[https://www.unipi.technology/return|repair (warranty or post-warranty)]], the same licence can be used again, but the whole licencing procedure has to be done again. See more: [[#licensing_after_a_repair_warranty_or_post-warranty_of_the_controller|Licensing after a repair (warranty or post-warranty) of the controller]]
 </WRAP>
 <html><span class="kbBlueText">Wrong product</span></html> \\
 The reason is the same as with the Wrong HW error, but in this case, the SD card from a licenced controlled was used in a different product line (ie. a SD card from Neuron is used in Unipi 1.1, or a card from Unipi 1.1 transferred to Unipi 1.1 Lite).
 ===== How to licence a Unipi PLC? =====
-Open Mervis IDE and create a new project, or open an already existing one. Attach a PLC.
+Open Mervis IDE and create a new project, or open an already existing one. **[[en:sw:01-mervis:creating-new-project-hidden#attaching_to_the_controller|Attach a PLC]]**.
 <html><figure ondblclick="redirectImg(this)" class="zoom" onclick="zoom(event)" style="background-image: url(https://kb.unipi.technology/_media/en:sw:01-mervis:02-use-mervis-runtime-licence-en.png)">
@@ Line 125: / Line 139: @@
 </figure></html>
-After rebooting, wait for a minute before re-attaching the PLC. After this short period, the PLC will display with an active licence (see the picture below).
+After restarting the controller, wait at least one minute for the controller to start. To verify licensing, run the **[[en:sw:01-mervis:creating-new-project-hidden#attaching_to_the_controller|Attach PLC]]** dialog, or enter debug mode and check the license status in **System Status**. Each time you **Attach PLC**, you will see the controller with a valid and active license, as shown on the picture below. The running time of the program is no longer limited.
 <html><figure ondblclick="redirectImg(this)" class="zoom" onclick="zoom(event)" style="background-image: url(https://kb.unipi.technology/_media/en:sw:01-mervis:09-use-mervis-runtime-licence-en.png)">
@@ Line 131: / Line 145: @@
 </figure></html>
-<WRAP center round info 60%>
+<WRAP center round info 90%>
 The licencing procedure can also be done remotely using Mervis Proxy.
 </WRAP>
+The last important step is to write [[https://www.unipi.technology/getmervis|licence notes]]. We always recommend stating at least: **model, serial number and location/placing of the controller**.
+<html><figure ondblclick="redirectImg(this)" class="zoom" onclick="zoom(event)" style="background-image: url(https://kb.unipi.technology/_media/en:sw:01-mervis:license-note-en.png)">
+<img src="https://kb.unipi.technology/_media/en:sw:01-mervis:license-note-en.png" />
+</figure></html>
+===== How is the license bound to the PLC? =====
+Each Mervis RT (RunTime) license can be used only once and just one controller can be licensed. Once you use a license it cannot be used again on another controller.
+<html><span class="kbBlueText">Unipi Patron, Axon, Gate</span></html> \\
+After activation, the license is bound to the controller. After flashing OS in the controller ([[en:hw:007-patron:image|Patron]], [[en:hw:025-gate:image|Gate]], [[en:hw:01-axon:image|Axon]]) it is necessary to upload the license from Mervis IDE, see: [[#licensing_mervis_rt_after_flashing_os|Licensing Mervis RT after flashing OS]].
+<html><span class="kbBlueText">Unipi Neuron</span></html> \\
+After activation, the license is bound to the controller (not to the SD card). After replacing the SD card or [[en:hw:02-neuron:image|fleshing OS]] on the card, it is necessary to upload the license from Mervis IDE, see: [[#licensing_mervis_rt_after_flashing_os|Licensing Mervis RT after flashing OS]].
+<html><span class="kbBlueText">Unipi 1.1 & Unipi 1.1 Lite</span></html> \\
+After activation the license is bound to the given Raspberry Pi and Unipi 1.1 set (not to the SD card). The activated license can no longer be used on another combination of Raspberry Pi and Unipi 1.1. After replacing the SD card, or [[en: hw: 03-unipi11: image|flashing OS]] on the card, it is necessary to reactivate licence in the Mervis IDE, see: [[#licensing_mervis_rt_after_flashing_os|Licensing Mervis RT after flashing OS]].
+==== Licensing Mervis RT after re-flashing OS ====
+If you have already licensed the controller once and have now flashed OS on the controller ([[en:hw:007-patron:image|Patron]], [[en:hw:025-gate:image|Gate]], [[en:hw:01-axon:image|Axon]]), or you have replaced the SD card or flashed OS on it ([[en:hw:02-neuron:image|Neuron]] / [[en:hw: 03-unipi11:image|Unipi 1.1]]), the process [[#how_to_licence_a_unipi_plc|Upload license to PLC]] must be completed again. The request for the confirmation "**License cannot be activated. Do you want to use the result of the last successful activation?**" dialog by clicking **OK** is the only difference:
+{{ :en:sw:01-mervis:license_last-activation_en.png?nolink |}}
+<WRAP center round important 90%>
+If you click the **Cancel** button instead of the **OK** button, licensing will end with an error message.
+</WRAP>
+==== Licensing after a repair (warranty or post-warranty) of the controller ====
+If the HW in the controller has been replaced or the Unipi 1.1 board has been replaced due to a complaint or service, reactivation is allowed for the given license and it is therefore necessary to perform the process [[#how_to_licence_a_unipi_plc|license activation]] again.
+**Before licensing it is NECESSARY** to check whether the serial number in the project corresponds to the current controller and if not, it is necessary to **[[en:sw:01-mervis:creating-new-project-hidden#attaching_to_the_controller|Attach PLC]]** again. Furthermore, it is **NECESSARY** to download the HW description again, even if the license dialog displays a green marked message //"Hardware Description downloaded"//.
+If you are unable to activate the controller with the original license, do not hesitate to contact our [[en:contact:00-start|technical support]]. Be sure to include the **license code** Mervis Runtime you want to use, as well as the exact **controller model, including the serial number.**