Differences

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

--- en:sw:04-unipi-firmware:01-custom-image [2020/11/10 13:17]
avsetula
+++ en:sw:04-unipi-firmware:01-custom-image [2023/09/14 10:30] (current)
avsetula [Technical part]
@@ Line 7: / Line 7: @@
 We offer two types of images for our PLCs: **OpensourceOS** and **MervisOS**. Both of them can be downloaded for free in the [[en:files:software:os-images:00-start|Download section]] and used without any constraints.
-The MervisOS is the one which is shipped with each Axon. Apart from the basic settings, it contains preinstalled MervisRT and it is meant to be used with the MervisIDE.
+The MervisOS is the one which is shipped with each Patron. Apart from the basic settings, it contains preinstalled MervisRT and it is meant to be used with the MervisIDE.
 The OpensourceOS is the cleanest and smallest image we were able to put together. As with the MervisOS, it contains current, debootstrapped Debian GNU/Linux with the preinstalled Unipi packages mandatory for accessing the underlying IOs. This image is to be used as a base image for further development.
-Because of the different needs of different PLCs (Axon, Neuron and Unipi 1), there has to be image built for each PLC separately. This results in having separate MervisOS image for Unipi 1.1, Neuron and Axon and the same applies to the OpensourceOS image.
+Because of the different needs of different PLCs (Patron, Neuron, Axon and Unipi 1.1), there has to be image built for each PLC separately. This results in having separate MervisOS image for Unipi 1.1, Patron, Neuron and Axon and the same applies to the OpensourceOS image.
 Due to our openness, we allow you the full access to the OS via SSH, so you are free to install and configure anything you want. And since our [[https://www.unipi.technology/products/neuron-patron-oem-solutions-92|OEM customers]] typically need to install additional software and do a custom configuration of the OS, we decided to open the image creation process as well.
@@ Line 25: / Line 25: @@
 The result is that you have always have access to up-to-date images, which are automatically versioned, so you will not get lost in the modifications. The image can be then installed on-site to any of our PLCs.
-Since Axons include internal eMMC storage, your custom OS image can be deployed into the units during productions. This greatly reduces the post-receive time spent by your IT experts doing all the required modifications.
+Since Patrons include internal eMMC storage, your custom OS image can be deployed into the units during productions. This greatly reduces the post-receive time spent by your IT experts doing all the required modifications.
 ===== Technical part =====
-The OS images are defined and built by [[https://about.gitlab.com/product/continuous-integration/|Gitlab CI]] running on our premises. Each image has its own [[https://git-scm.com/|GIT]] repository, which contains a definition of what software should be installed and what configuration needs to be performed. To make this process as easy as possible, these definitions are nothing more than a set of [[https://www.gnu.org/software/bash/|bash]] scripts which are executed in a particular time and order. The building of the OS image is roughly split into these parts:
+The OS images are defined and built by Gitlab CI running on our premises. Each image has its own [[https://git-scm.com/|GIT]] repository, which contains a definition of what software should be installed and what configuration needs to be performed. To make this process as easy as possible, these definitions are nothing more than a set of [[https://www.gnu.org/software/bash/|bash]] scripts which are executed in a particular time and order. The building of the OS image is roughly split into these parts:
   - [[https://wiki.debian.org/Multistrap|Debootstrap]] on the Debian GNU/Linux