About sanX

Introduction In this tutorial it will be shown how to configure Node-RED to be able to get CSV files stored in an IndraControl and represent the content of these files in InfluxDB. To be able to communicate with the IndraControl, the FTP communication protocol is used. For this purpose it is required to install the FTP nodes in Node-RED. On the other hand, with the use of function and csv nodes, the content of the csv files will be read and processed, so that the information can be sent to InfluxDB in the correct format. Finally, with the use of the InfluxDB node, data is sent and represented. Prerequisites ctrlX CORE - Node-RED App  ctrlX CORE - InfluxDB App Establish communication between both devices First, it is required to connect the IndraControl and the ctrlX CORE to be able to establish the FTP communication. For this purpose, please connect them as shown in the image: Communication overview Secondly, it is required to configure the IP address between both devices. For that, connect to the ctrlX CORE with the Engineering computer. In the case, the user does not know how to achieve this, please check this tutorial. Once we are inside the ctrlX CORE web interface, it is required to follow the steps: Access the "Settings" menu Press "Network Interfaces" Select the "XF51" interface Select the "IPv4" tab Enter an IP address in the same range as the IndraControl, but not with the same IP address because otherwise it will have conflicts. Additionally, enter the subnet mask. Press the "Save" button and store the configuration Connection configuration between ctrlX CORE and IndraControl Once the configuration has been saved, a "Connected" message should appear: Successful connection check To make sure, the device is correctly connected, it is of interest to ping to the IndraControl from the ctrlX CORE. For that, return back to "Settings" and press over "Network Diagnostics" Network diagnostics menu access In the "Network diagnostics" menu, enter the IndraControl IP address and check if data is transmitted and received as shown below: Connection check between ctrlX CORE and IndraControl Finally, it is recommended to check that the IndraControl has the FTP communication protocol active. Disconnect the IndraControl with the ctrlX CORE and connect the IndraControl with the Engineering computer. Once done that, configure the static IP address accordingly.  Start IndraWorks and communicate with the IndraControl Access the communication protocols menu: Right click over the device --> Communication --> Protocols Access IndraControl communication protocols 4  Check that FTP is active as shown below: Check FTP protocol Configure InfluxDB Step 1: Install InfluxDB Download the app from this link and install it. In the case, it is the first time installing an app in the ctrlX CORE, please check the steps shown in this tutorial. Step 2: Configure InfluxDB Define user settings Provide a username, password, organization name, an initial bucket name, and press "Continue". Note: A bucket is a named location where all our data is stored.  InfluxDB initial configuration In the next window, select any of the options. Step 3: Get API token To be able to use the InfluxDB node in Node-RED it is required to get a bearer token from InfluxDB. Hover the mouse over the Load data symbol in the InfluxDB homepage Select "API Tokens" and the window as shown below will appear Press over "Generate API Token" Select the "All access API Token" option Bearer token creation Provide a description, click over "Save" and a new window with the API token will appear Bearer token creation Press over "Copy to clipboard" and keep the token in a safe place because later this will be required Step 4: Create bucket To store all the data sent from Node-RED to InfluxDB, a bucket es required to define.  Hover with the mouse over the Data explorer symbol Press over "Create bucket" Provide a name. In this case, we will name this bucket "FTP" Press the "Create" button Bucket creation in InfluxDB Configure Node-RED Step 1: Install the Node-RED app Download the app from this link and install it. In the case, it is the first time installing an app in the ctrlX CORE, please check the steps shown in this tutorial. Step 2: Provide internet connection to the ctrlX CORE To be able to install some nodes required to successfully connect per FTP to the IndraControl, it is necessary to connect to the Internet. For this purpose, connect the XF51 port to a router and make sure that in the Network Interfaces menu, the automatic settings configuration is enabled. ctrlX CORE internet access configuration If the connection has been correctly established, a similar window as the previously shown should appear. Note: It is required to have internet access in the ctrlX CORE and in the Engineering computer. Step 3: Start Node-RED and install the required nodes Press over the three horizontal lines Select "Manage palette" Access Node-RED palette Menu Install the FTP nodes: In the palettes menu, press over "Install" Write ftp and find the node-red-contrib-ftp package Press over the "Install" button FTP nodes installation Once the nodes have been successfully installed, the following message should appear: FTP nodes addition In addition to these nodes, it is also required to install the following ones: node-red-contrib-influxdb node-red-contrib-fs Step 4: Download Node-RED flow and import it At the end of this tutorial, there is a zip file which contains the json file required to upload to Node-RED. Press over the three horizontal lines Press over "Import" Flow import in Node-RED In the "Import nodes" menu follow the steps: Press "Select a file to import" Select downloaded and extracted json file and the following code should be visible Import the flow Flow import in Node-RED Once the flow has been imported, the following overview should be visible: Node-RED flow overview Step 5: Connect ctrlX CORE with IndraControl As we previously used the XF51 port to connect the ctrlX CORE to the internet, now it is required to connect again both devices to be able to establish a FTP connection. For this purpose, please connect both devices as shown in the first image of this tutorial with their corresponding IP addresses. Step 6: Configure nodes Once the file has been imported, the flows need to be configured to be able to connect to the IndraControl. 1. FTP nodes: List directories node access Double click over the node and a new window will be opened. In the filename, introduce the path of where the csv files are located in the FTP server.  On the other hand, provide the FTP server configuration by clicking over the pencil. With the FTP server IP address, port, username and password, the ctrlX CORE will be able to connect to the server. Once all the information has been introduced, press over "Update" and you will return back to the first window where it is required to click over "Done" to close it FTP node configuration Once this information has been introduced, all the FTP nodes used in this flow will automatically be updated with this data.  FTP nodes in the general flow 2. InfluxDB nodes: InfluxDB node configuration access Double click over the node and a new window will be opened: Check that the organization name matches with the one introduced when configuring InfluxDB Check the bucket name  Enter the InfluxDB configuration menu InfluxDB node configuration In the new window, it is required to follow these steps: Select version 2.0 Introduce the ctrlX CORE url with port 8086 per default Introduce the previously stored API token Press over the "Update" button to store the configuration InfluxDB node configuration Once this node has been updated, the other three influxDB nodes will automatically be updated. 3. Return url node: In this function node, the ctrlX CORE IP address is introduced and it is required to make sure that it matches with your ctrlX CORE address ctrlX CORE IP address check 4. Delete files in Active node: In this node it is required to introduce the ctrlX CORE credentials to be able to make HTTP requests Credentials configuration in HTTP request node Step 7: Deploy  Once all the nodes have configured, we can deploy the flow by clicking over the "Deploy" button Flow deployment Testing  Data visualization Once the deploy button is clicked, if everything has correctly been configured, these debug messages will appear: Check debugging nodes In these messages the user can read the csv values and their corresponding timestamps. Now that data is sent to InfluxDB, we can check in the Data explorer if data is arriving: Select the Data explorer button Select the FTP bucket to visualize the data that has been stored there Select which column of the csv file you want to visualize. Note: It is possible to select multiple columns Press over "Custom" in the window period Select 1ms to be able to read data at ms level if data is sent at this frequency In "Aggregate function", select custom and do not select any function sot hat raw data is shown Choose the data you want to visualize. In the case, the csv files have been generated in a defined hour, it is possible to configure this Press over the "Submit" button to visualize the received data Visualize received data in InfluxDB Delete IndraControl csv file In the case the user wants to delete all the csv files stored in the IndraControl, there is a button in the Node-RED flow which provides this capability. Delete IndraControl csv files In the debug messages, it is possible to see all the files which will be deleted. In this case, 445 csv files will be deleted. Additionally, for every deleted file, a "File deleted" message will appear. Delete ctrlX CORE csv files As all the read csv files are also stored in the ctrlX CORE, the user may be interested on deleting these files.  Note: In this case, the flow has been configured so that all the csv files are stored in active configuration folder of node-RED csv files location in the ctrlX CORE To change the path where the folders have to be stored, open the "Check new objects" node and change the local path variable: csv files path in the ctrlX CORE Keep in mind, that in the case the path is changed, it is required to modify the code in the following nodes: 1. "Check if file has been stored" node Path check in Check if file has been stored node 2. "List files" node Path check in list files node 3. "Return url" node Path check in Return url node Once we have understood where the csv files are stored in the ctrlX CORE, we can test the button to delete the files by using the inject node: Delete ctrlX CORE csv files In this case 38 files have been deleted ... View more

Introduction In this tutorial it will be shown how to create a snap with the capability to create and delete folders located in the snap active configuration. Additionally, this snap will be able to upload and delete files from the same active configuration folder. To be able to achieve this, a Flask webserver will be used with the purpose to provide a visualization interface and allow the user to easily upload files from the local computer to the ctrlX CORE active configuration folder. At the end of this tutorial, it will be explained how the snap works, with the purpose to allow users easily integrate this capability in their own snaps. To find more information about data persistence, please check this explanation. Otherwise, there is also a similar How-to where these concepts are also explained. Prerequisites ctrlX Works App build Environment configured Snap development To be able to build the snap, it is required to have the app build environment configured. To be able to perform this step, please check this tutorial. Step 1: Download the required files The required files can be found at the end of this tutorial Step 2: Create project folder in the App build environment Enter the app build environment and create a new folder New folder creation in Visual Studio Code Extract the zip file and drag the unzipped files folders in the new created folder. Copy folder to project folder Step 3: Access the project folder Press over "File" Select "Open folder" Choose the project folder Press "Ok" and the project folder will be opened Folder access Step 4: Create snap Press "Terminal" and open a "New terminal" Terminal access Make files executable To be able to successfully build the snap, it is required to make the bash file executable because otherwise the following message will appear: Failure message in the case the run.sh file has not been made executable In the terminal, with the "cd" command, access the configs folder where the run.sh file is located: cd configs Next, use the "chmod +x" command to make the file executable: chmod +x run.sh Return to the main folder using the command "cd ..": cd .. Make run.sh file executable Build the snap executing the "snapcraft --destructive.mode" command: sudo snapcraft --destructive-mode --target-arch=arm64 --enable-experimental-target-arch Note: This command is for generating an arm64 compatible snap. In the case the user, wants to create an amd64 snap just change arm64 with arm64 Create snap command Once the snap has been built, the file will be visible in the project folder: Generated snap Clean the directory using the "snapcraft clean --destructive-mode" command: snapcraft clean --destructive-mode Clean snap creation folders Overall explanation This snap consists of two basic programs: Python program (main.py). This program is located in the main project folder and it creates the Flask webserver so that the user can interact with the internal directories and files. Additionally, it also gives the option to easily upload files or create new directories in the snap active configuration folder. Shell script (run.sh). This script is located in the configs folder and it has the purpose to copy some internal files from the project folder to the active configuration folder when the app is installed. It creates a folder in the active configuration and checks the availability of one of the files that should be there, and in the case it is not there, it copies the "Example" file to that folder. This script is in this tutorial just to show that it is possible to copy files during the snap installation, but if the user does not require this functionality and wants to add files later, this shell script is not necessary. main.py To be able to run this Python program, some dependencies are necessary. Additionally, it is required to define the snapcraft configuration files correctly to download and include the required modules in the final snap along with the installation. Two folders are required to run correctly the webserver: static: this folder contains files of static elements of the webserver. In the case the website contains static elements such as images, it is mandatory to define this folder to be able to create the Flask webserver correctly. In this case, only an image is used, but in the case the user does not want to include any image or there is no static element, this folder is not mandatory to be able to run Flask. templates: this is the most important folder because it contains the html file for creating the webserver. How the website is designed and how all the dynamic elements interact between the Python program and the webserver are defined in this file.  On the other hand, the main.py file is almost self explanatory due to all the comments provided in the code. At the beginning, it imports all the required modules to run the program, it creates a variable with the general path to the active configuration folder and defines the Flask program. The rest of the code basically consists of 6 sections with the following purposes: Initial website. This function returns the index.html file to shows the initial website. First it checks the folders, subdirectories and files located in the general path to provide the user a general overview of what is inside the active configuration folder. Additionally, the function returns all these folders, files and subdirectories to visualize them in the website. Create new directory. As the name says, this function just reads what the user has entered in the website so that it can create a new directory with the makedirs function of the os module.  Delete directory. Similar to what the the previous function does, this function reads what directory the user enters in the website, and deletes the directory with the rmtree function of the shutil module.  Upload file. This function used the files and form functions of the request module to get the file that the user wants to upload and in which directory wants to put the selected file. Once all this information has been got, with the save function, the file is stored. Delete file. As the name says, this function is used to delete files located in the active configuration folder. To achieve this, the remove function from the os module is used. Flask initialization. There are many possibilities, but in this case, debug has been activated, host has been defined so that it automatically takes the ctrlX CORE IP address and the 8001 port has been selected.  In the case the user wants to add some functionalities to the webserver or wants to understand better how the program works, please check the official Flask module. To be able to run correctly this Python program, it is necessary to configure the yaml and setup.py files.  setup.py. In this file, the folders the main.py needs to be able to work, are defined so that when the snap is built they are included. On the other hand, the required Flask module is also defined so that, when the snap is built, the module is downloaded and included in the final snap. Additionally, the script, version, licence and other things are defined. snapcraft.yaml. There are different sections that has to be considered to be able to correctly run the Python program: To correctly run the main.py it is required to define its location when the snap is built, which plugs it needs and when it is started. All this is defined in the apps section inside the yaml file: apps:   active:     command: bin/main.py     plugs:       - network       - network-bind       - active-solution                                      daemon: simple     passthrough:       restart-condition: always       restart-delay: 10s In the parts section, the location inside the project folder of the Python program is defined and which plugin has to be used: parts:   active:     plugin: python     source: . Additionally, the dependencies folder is copied from the project folder to the bin folder of the final snap using the dump plugin:   flask-dependencies:     source: .     plugin: dump     organize:       'dependencies/*': bin/ run.sh  For this shell script, it is just required to correctly define the snapcraft.yaml file. In the apps section, the location of the script, the command that has to be executed and the required plugs are defined: apps:  activeconfiguration:     command: ./bin/run.sh     daemon: simple     plugs: [network, network-bind, active-solution] Active configuration access In addition to correctly define the location, plugins, commands of the two programs that work in the background, it is necessary to give to the snap access to the active configuration folder in the ctrlX CORE. For that purpose, the following actions are required to do: On the snapcraft.yaml file, the following lines have to be added: On the parts section it is required to add the following lines: parts:     activeconfiguration:         source: ./configs/           plugin: dump         organize:           '*': bin/ On the hooks section it is required to add the following lines: hooks:          connect-plug-active-solution:           plugs: [active-solution] On the plugs section these lines: plugs:       active-solution:           interface: content         content: solutions         target: $SNAP_COMMON/solutions Note: on the apps section make sure that the active-solution plug is included: apps:   active:     command: bin/main.py     plugs:       - network       - network-bind       - active-solution                                 #<--------------------------------------------     daemon: simple     passthrough:       restart-condition: always       restart-delay: 10s   activeconfiguration:     command: ./bin/run.sh     daemon: simple     plugs: [network, network-bind, active-solution]     #<--------------------------------------------   On the snap/hooks/connect-plug-active-solution: This file creates an active folder in the active configuration folder in the ctrlX CORE. ctrlX CORE interface In this section it will be shown how to create the menus and sidebars in the ctrlX CORE interface to be able to access to the webserver. To be able to define this, the novnc.package-manifest.json file is used. This file is located in the configs/package-assets folders. Additionally, it is required to tell to the snapcraft.yaml file that copies this file to the final snap: parts:   configs:          source: ./configs     plugin: dump        organize:       'package-assets/*': package-assets/${SNAPCRAFT_PROJECT_NAME}/ On the other hand, in the slots section it is also required to write some lines of code to correctly integrate this to the ctrlX CORE interface: slots:     package-assets:                 interface: content         content: package-assets         source:             read:             - $SNAP/package-assets/${SNAPCRAFT_PROJECT_NAME}     package-run:         interface: content         content: package-run         source:             write:             - $SNAP_DATA/package-run/${SNAPCRAFT_PROJECT_NAME} ... View more

Introduction In this article, it will be shown how to build a noVNC snap. NoVNC is a HTML client which allows to connect to a VNC server from a browser. As noVNC is a HTML file along with several JavaScript and CSS files, it is required to launch them with a program. This program is called Websockify and it basically creates the noVNC website. Additionally, it also helps noVNC to communicate with the VNC server as noVNC only understands WebSocket. Websocket is a communication protocol which allows to establish a bidirectional communication between client and server. Comparing it to HTTP where it is only unidirectional and the communication is closed after each request, WebSocket allows to have unlimited number of requests and responses. This persistent data stream make this communication a much faster option compared to HTTP. Communication scheme between noVNC, VNC server and Websockify To start noVNC it is required to start websockify first. Websockify is programmed in Python and noVNC with JavaScript and HTML. With the original noVNC program it is required to start it by the terminal introducing the html directory of noVNC, the VNC server IP address and port, and the local port that will be used to establish the connection both devices. To be able to introduce this data and avoid the user to open a terminal, a webserver will be programmed where it will be possible to introduce the required data and with that information start automatically the app. All this will be packed in a snap compatible with the ctrlX CORE. Prerequisites ctrlX Works App build Environment configured Development The app basically consists of four different programs that run simultaneously: noVNC which execute JavaScript, css and HTML files Websockify which execute Python files  Flask webserver which execute Python files Active configuration which execute bash files Step 1: Download noVNC and Websockify from GitHub Download the zip files from GitHub and extract them in a reachable folder noVNC can be downloaded here Websockify can be downloaded here Step 2: Create project folder in the App build environment Note: In the case the user does not know how to configure the app build environment, please check the following tutorial Enter the app build environment and create a new folder. New folder creation in Visual Studio Code Introduce the downloaded files in the new created folder. For that, first drag all the noVNC files into the main folder as shown below: novnc files copy to the project folder Secondly, change the websockify folder name to "websockify", to simplify the access to that folder later on, and copy the folder in the main project folder. websockify folder copy to the project folder Step 3: Introduce the Flask webserver and configuration files in the project folder These files can be obtained from the zip file provided at the end of this article. Drag the "flask_webserver.py" and the "setup.py" file and the "dependencies" folder into the "websockify" folder Webserver files copy Drag the "configs" folder into the general project folder configs folder copy to the project folder Drag the file and folders inside the snap folder into the "snap" folder Snap files copy Accept the "Replace" messages as the internal files have to be replaced. Check that all the added folders are in the project: Copied files check Step 4: Create snap First the user must be located in the project folder Press "File" --> "Open folder" Select the folders until selecting the main project folder Press "Ok" and the folder will be opened Terminal window access Press "Terminal" and open a "New terminal" Terminal window access Make files executable To be able to succesfully build the snap, it is required to make some bash files executable because otherwise the following messages will appear for the different files: Error message when the chmod +x command has not been executed In the terminal, with the "cd" command, access the snap/local folder where the svc_wrapper.sh file is located: cd snap/local Next, use the "chmod +x" command to make the file executable: chmod +x svc_wrapper.sh Return to the main folder using the command "cd .." twice: cd .. cd .. Perform similar steps for the novnc_proxy file: cd utils chmod +x novnc_proxy cd .. Perform similar steps for the run.sh file: cd configs chmod +x run.sh cd ..  Executed commands overview Build the snap executing the "snapcraft --destructive.mode" command: sudo snapcraft --destructive-mode --target-arch=arm64 --enable-experimental-target-arch Note: This command is for generating an arm64 compatiable snap. In the case the user, wants to create an amd64 snap just change arm64 with arm64 Clean the directory using the "snapcraft clean --destructive-mode" command: snapcraft clean --destructive-mode Overall explanation The snap file cosists of the required files for running noVNC, Websockify, Flask webserver and configuration files for the ctrlX CORE interface. noVNC It consists of HTML, JavaScript and CSS files where it is not necessary to perform any change. Basically, the HTML files access to the JavaScript files for all the dynamic behaviour of noVNC and the CSS files are used for the visualization of the noVNC interface. The noVNC files are located in the following folders: app core snap/hooks/configure utils vendor HTML files In the yaml file it is required to define the following sections to be able to install novnc and make it work properly: apps: novnc defining command and plugs, novnsvc for the same purpose parts: novnc where all certain files and folders are copied to the main snap file. Additionally, with novnc-deps, other novnc dependencies are also copied with the same purpose. Finally, svc-script and svc-script-deps perform similar tasks hooks: configure to define correctly the novnc hook configuration file Websockify It consists of several Python files and inside the websockify folder all the webserver files will be introduced. On the other hand, it is not required to perform any change in the Websockify files. Basically, Websockify is started with the VNC server IP address and port, local port and IP address if desired, and with which HTML file. There are other many functions, but these are the inputs that are required to give to Websockify to be able to start. In the yaml file it is required to define the following sections to be able to install websockify and make it work properly: parts: websockify where the Python plugin is defined and the required packages are defined Webserver It consists of Python and HTML files. The required folders and files required to run the webserver are located here: websockify/flask_webserver.py This is the main Python file which starts Flask and imports all the required files required to create the webserver websockify/setup.py This is the configuration file required to setup Python in the snap. Here the main is defined, the Python modules are defined so that they are downloaded and installed in the snap and other descriptions are described in this file. websockify/dependencies/static/image In this folder the image used for the webserver interface is located websockify/dependencies/Target/target In this folder the file used to store the VNC server IP address and port is located websockify/dependencies/Target/templates/index.html Here, the index.html file is found and is used by Flask to create the web interface In the yaml file it is required to define the following sections to be able to install Flask webserver and make it work properly: apps: websockify: where the main Python command is defined, a "simple" daemon is used so that the file is always executed, and all the required plugs are defined. parts: the websockify plays here also a role because it includes the Flask webserver files. Additionally, with flask-dependencies, the files required for the webserver to run, are copied to the /bin folder so that flask_webserver can work properly. ctrlX CORE interface On the one side, it is required to define menus and sidebar to be able to access to the Flask webserver interface and to the noVNC visualization. To be able to define this, the novnc.package-manifest.json file is used. This file is located in the configs/package-assets folders. On the other side, the active configuration has to also be configured. This configuration gives the option to store and write files internally in the ctrlX CORE. To be able to achieve this it is required to create several files and perform some configurations in the yaml file. The required files are located in the following directories: configs/run.sh  This bash file creates a noVNC directory in the active configuration folder and checks that the Target directory is created and in the case it is not, it creates it and copies the target file to the directory. Note: To be able to run this bash rile it is required to define it in the yaml file snap/hooks/connect-plug-active-solution This file creates a novnc folder in the active configuration folder in the ctrlX CORE. snap/snapcraft.yaml On the parts section it is required to add the following lines: parts:     activeconfiguration:         source: ./configs/           plugin: dump         organize:           '*': bin/ On the hooks section it is required to add the following lines: hooks:          connect-plug-active-solution:           plugs: [active-solution] On the plugs section these lines: plugs:  #Plug to give the novnc snap access to the active configuration. This habilitates the snap to read the memory     active-solution:           interface: content         content: solutions         target: $SNAP_COMMON/solutions On the apps section it is required to add the active-solution plug to those apps that need it:     apps:     activeconfiguration:         command: ./bin/run.sh         daemon: simple         plugs: [network, network-bind, active-solution]    # <-------------------------------     websockify:         command: ./bin/flask_webserver.py          daemon: simple                             plugs:             - network             - network-bind             - active-solution     # <-------------------------------- Related links Connect ctrlX CORE to a VNC server using noVNC  ... View more

Introduction In this article, it will be shown how to connect a ctrlX CORE with a VNC server using noVNC. To achieve this, the TightVNC server will be used. VNC(Virtual Network Computing) is a communication system that allows to remotely access from another device being able to control and see the dektop environment of the device that is sharing. The VNC server will be configured in the device that shares the desktop (Raspberry Pi in this case) and the VNC client will be configured from another device (ctrlX CORE in this case) or even it is possible to use it in the same device.  Raspberry Pi and ctrlX CORE communication using TightVNC and noVNC On the other hand, noVNC is a HTML client which allows to connect to a VNC server from a browser. As noVNC is a HTML file along with several JavaScript and CSS files, it is required to launch them with a program. This program is called Websockify and it basically creates the noVNC website. Additionally, it also helps noVNC to communicate with the VNC server as noVNC only understands WebSocket. WebSocket is a communication protocol which allows to establish a bidirectional communication between client and server. Comparing it to HTTP where it is only unidirectional and the communication is closed after each request, WebSocket allows to have unlimited number of requests and responses. This persistent data stream make this communication a much faster option compared to HTTP. Communication scheme between noVNC, VNC server and Websockify Prerequisites VNC server (In this case, TightVNC will be used) ctrlX CORE with Root user noVNC App MobaXterm VNC server configuration In this section it will be shown how to configure the VNC server. These steps can be followed on any Linux device and it is not required to have a Raspberry Pi. The VNC server will provide a desktop environment for the device that will connect remotely. Step 1: Install VNC Server Connect the device to Internet and check if there are system updates: sudo apt-get update && apt-get upgrade Install TightVNC  sudo apt-get install tightvncserver TightVNC installation Step 2: Configure TightVNC Configure password: /usr/bin/tightvncserver Now it will be shown how to configure TightVNC so that is automatically starts when booting the system. Open a terminal window and enter: sudo nano /etc/systemd/system/tightvncserver.service Write or copy the following lines: [Unit] Description=TightVNC remote desktop server After=sshd.service [Service] Type=dbusExecStart=/usr/bin/tightvncserver :1 User= Enter your username Type=forking [Install] WantedBy=multi-user.target TightVNC configuration Note: To save the configuration, press "ctrl" + "O" --> Press "Enter" --> Press "ctrl" + "X" to return back to the terminal Change the file so that it is owned by root: sudo chown root:root /etc/systemd/system/tightvncserver.service Make the file executable by running: sudo chmod 755 /etc/systemd/system/tightvncserver.service Reboot the device and check that the script works by running: sudo systemctl start tightvncserver.service Enable startup at boot using: sudo systemctl enable tightvncserver.service Restart again and check that it has automatically started by running the command: sudo systemctl status tightvncserver.service TightVNC Server status Step 3: Perform additional configurations With this command it is possible to configure resolution and depth for a VNC Server 2 vncserver :2 -geometry 1920x1080 -depth 16 Note 1: Now there will be a VNC server in the port 5901 with the default configuration and another VNC server in the port 5902 with the previously shown configuration Note 2: This configuration can also be included in the default file that was previously configured Open the terminal, write the command, and change was is shown in the following image: sudo nano /etc/systemd/system/tightvncserver.service TightVNC server personalization Save the configuration, reboot the device and check that now the VNC server 1 has the previously configured resolution and depth: VNC server status check ctrlX CORE configuration Step 1: Connect ctrlX CORE with Raspberry Pi First, it is required to connect the Raspberry Pi and the ctrlX CORE as shown in the first image of this article. To configure the IP address, please follow the steps shown in this tutorial. Step 2: Install noVNC Download the file provided in this article and access the ctrlX CORE web interface To access the ctrlX CORE web interface check the Quick Start Guide To install the file provided in this article, check the tutorial or follow the steps: Go to Settings Access the Apps interface Change from Operating to Service mode to be able to install apps Press over "Install from file" Select the downloaded file Open it and install the noVNC app noVNC Snap installation in ctrlX CORE Step 3: Install MobaXterm Download the Windows program in the official webpage and install it MobaXterm interface Step 4: Configure MobaXterm to access per SSH to the ctrlX CORE Open MobaXterm and press over "Session" In the new window, select "SSH" Write the ctrlX CORE IP address Press "Ok" to establish the connection ctrlX CORE SSH connection Enter the root username and password, and the following window shuld be visible: MobaXterm interface Step 5: Configure and start noVNC Execute the command shown below. After --vnc write the VNC Server device IP address (In this case the Raspberry Pi) and the assigned port by the server novnc --listen 6081 --vnc 180.254.3.2:5901   Note: Make sure to write the correct port where the VNC server is configured. To check the assigned ports, open a terminal in the Raspberry Pi and write: netstat -tulpn Port check in Linux When the command is executed, noVNC generates a link where it is possible to access the noVNC interface noVNC Start from MobaXterm Open a web browser, enter the generated link and press over the "Connect" button noVNC start Note: In the case it does not work with the link, in the same link address, change the ctrlx-core part with the ctrlX CORE IP address noVNC IP address troubleshooting On the other hand, it is also required to access the noVNC settings and enter the ctrlX CORE IP address before pressing the "Connect" button noVNC Configuration Enter the credentials and press "Send credentials" Credentials introduction The device's desktop environment will be visible Raspberry Pi desktop shared to noVNC Generate certificate to increase VNC connection security Step 1: Generate certificate using MobaXterm Write the the following command in MobaXterm: sudo openssl req -x509 -nodes -newkey rsa:2048 -keyout novnc.pem -out novnc.pem -days 365 Note: The file name can be defined as desired. In this case the name will be novnc The command is written All the information is written The certificate file is generated in the /home/user folder Security certificate generation Step 2: Test the VNC connection with the generated certificate file When running the noVNC command it is required to add the certificate file as shown below: novnc --listen 8443 --cert novnc.pem --vnc 180.254.3.2:5902 noVNC with certificate command Now, when noVNC is running, SSL/TSL support wll appear active SSL/TLS Support check ... View more