Hi! Welcome to extra information about G15 PMN installation in Linux This text updated: 2022:1:20 which is at g15pmn.com, ie, norskesites.org/fic3/fic3inf3.htm ************************************* Some notes when installing neong15ways.zip at Neon KDE Linux: The 015inneon.txt tells of installation of a certain version number of SDL 2; in most recent versions of Neon Linux, it is preferrable to load in libsdl2-dev as that brings the most recent version number of SDL2 into the machine. Also: * Wayland login isn't strictly speaking necessary with superbly simple forms of Linux X-Windows desktops like LXDE, as long as switching between the fullscreen mode and frame mode isn't in focus. [or, when exiting it by a click on the Del key, you are sticking to keyboard rather than mouse]: but the mouse-handling is distinct in Wayland and X Windows mode as regards frames, and g15rwx.zip handles X Windows. But you must use something like the 'neong15rworks' startup of G15 to get the full functionality required to drive robots with G15. The less cluttered the window/frame handling is, generally the better. Lxde, eg started instead of Neon login eg by a command like startx startlxde is eminent, fast, simple, works flawlessly as long as X Windows is the orientation. * You can run the G15 PMN program in a folder that you do 'cd' at, in a terminal, provided that there is read/ write access in that folder. The program itself, when Linux, eg neong15rworks, can be copied eg into /usr/bin area, perhaps under a shorter name. When started, it will look into the .g15 files, that are its disks, in the present folder. A technique for putting stuff like 'mynewfunction' into /usr/bin goes about like this, but only do it when you know what you're doing: sudo -i cd /usr/bin ll mynewfunction This is to check that is not already something there, called the same. cp -i /home/whatevermyusernameis/folder/mynewfunction . chmod 755 mynewfunction exit * By putting the startup commands for G15 there, you can run the G15 PMN platform on a pluggable device even when it is not formatted to permit program performance from it. However, when you run something like 'rworks', to start robotic interaction programs through terminal command from G15 PMN, which includes camera-read programs, you may find that some of these may work best in the computer's home disk. This you must check for each platform, with each external program [eg with some versions of snap- installed fswebcam in some linux'es configured in a standard way that program can store files at home disk and usb card yet not at sdcard; other variations of this sort may arise from time to time]. ************************************* In this setup.txt, the hardware input/output for robotic cameras, robotic engines etc are all Linux oriented, and oriented towards running inside the folder that comes when you unzip the neong15ways.zip package at norskesites.org/fic3/fic3inf3.htm which is oriented towards Wayland sessions in Neon KDE Linux or one that is extremely compatible. There are some BMP conversion routines included there. The other programs referred to in the .sh are very usual standard installable-over-the-net linux commands. Start with neong15ways.zip package, ideally performed in Wayland login modus in Neon KDE Linux or one very similar: ./neong15rworks or similar there to access command line. SETUP OF MAIN SOUND AND SOME IMAGE CONVERT USEFUL FOR CAMERA INPUT Install sox, eg by sudo apt install sox in order to enable the command 'play'. By installing the package 'imagemagick', you enable the command 'convert'. Good programs to capture one image at a time from cameras, eg /dev/video0, /dev/video15 etc, connected eg with USB to a PC are 'fswebcam' and 'streamer'. While hour-long use of fswebcam repeatedly gives consistent use, it seems some versions of streamer leaves a residue in RAM so that the image from the camera changes in brightness over time. However, fswebcam requires clever configuration work in some linux contexts. A solution is 'ffmpeg', which is usually installed with ease and which appears fairly stable and which can be configured in very many ways; however fswebcam appears more stable when you get it to work. To make fswebcam reach out and actually connect to /dev/video .. channels, it may be necessary to type in something like this, once, after install: sudo snap refresh fswebcam --edge sudo snap connect fswebcam:camera TO ENHANCE PERFORMANCE DURING HOURS SUITABLE FOR KDE NEON LINUX AND THE LIKE NOTE: consult with experts as to security in case you are using a PC which must be set up to be very secure and you wish to edit things in the /etc region of it. Create a text file eg in gedit called goodclear.sh, let it contain: sysctl vm.drop_caches=1 sysctl vm.drop_caches=2 sysctl vm.drop_caches=3 Save it to ~ which is /home/yourusername Go into administrator mode using your password: sudo -i cd /usr/bin cp /home/yourusername/goodclear.sh . -i sudo 755 goodclear.sh cd /etc Open text file /etc/sudoers in a text editor that works in administrator mode with great care after making a backup of it, or, with great care copy it to a local area, edit it eg with kwrite, and copy it back while in Administrator mode and give it back its proper permissions with chmod. In the editor you add a last line to it, namely yourusername ALL=(ALL) NOPASSWD: /usr/bin/goodclear.sh Having done this, leave the administrator mode by this command: exit Do a reboot to ensure that sudo goodclear.sh now can be performed inside a batch file without passwords having to be typed in each time. You can now enhance stability by allowing these to be the completing two lines eg in camtogem.sh, with eg sleep 0.15s being used higher up in it, adding up to sleep 0.35s: sudo goodclear.sh sleep 0.25s Remember though that Linux is a vast system and that there are more processes than those covered by such simple commands that ideally should having their caches refreshed for even better performance.