patches
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
patches [2024/08/22 11:53] – [Case B. Newer firmwares which create neccessary link] emozolyak | patches [2024/08/22 12:02] (current) – [Case A. Older firmware which don't generate link to patch] emozolyak | ||
---|---|---|---|
Line 5: | Line 5: | ||
To handle this, we developed a patch mechanism, to minimize possible issues. The process is similar to firmware upgrade with the code - you just get the patch code and apply it. | To handle this, we developed a patch mechanism, to minimize possible issues. The process is similar to firmware upgrade with the code - you just get the patch code and apply it. | ||
- | ===== Getting to the patch page ===== | + | ===== 1. Getting to the patch page ===== |
Depending on your firmware version there are 2 possible methods to getting to the page. Both methods require **admin** rights to do this operation. | Depending on your firmware version there are 2 possible methods to getting to the page. Both methods require **admin** rights to do this operation. | ||
Line 14: | Line 14: | ||
http:// | http:// | ||
</ | </ | ||
- | Here 192.168.1.222 is your WebHMI address and E44...75 is the patch code you obtain from the service. | + | Here //192.168.1.222// is your WebHMI address and //E44...75// is the patch code you obtain from the service. |
Line 23: | Line 23: | ||
{{: | {{: | ||
+ | ===== 2. Checking and applying the patch ===== | ||
+ | Press //Check// button to check the patch. | ||
+ | {{: | ||
+ | if the patch has been check, //Apply// button will become available. | ||
+ | {{: | ||
+ | In case of failed check you may see similar message: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | After successful applying you will see the following message: | ||
+ | {{: | ||
patches.1724327630.txt.gz · Last modified: 2024/08/22 11:53 by emozolyak