April-13th-2019, 08:59 AM
(This post was last modified: April-13th-2019, 09:16 AM by Armin@netPI.)
Well, using netPI and its Docker technology need a set of basic knowledge of Linux and its base commands like changing to folders and editing files, remove files, list files etc.
For finding files in Linux you could use the command „find“ like „find -name ‘firmwares‘“ if you are in the root folder using „cd /“.
But I have a tip for you. The file that builds the netx programming example container is located here https://github.com/HilscherAutomation/ne...Dockerfile. With this file you see where all the files are copied to in the container.
Also I have one more tip. The dpkg command you mentioned above just installs the firmware to the right position in the Linux file system so that the driver finds it correctly. Only calling the driver afterwards with DevOpenDriver() will initialize netX with the firmware. This happens for example if you start just the precompiled ethercat example code.
For finding files in Linux you could use the command „find“ like „find -name ‘firmwares‘“ if you are in the root folder using „cd /“.
But I have a tip for you. The file that builds the netx programming example container is located here https://github.com/HilscherAutomation/ne...Dockerfile. With this file you see where all the files are copied to in the container.
Also I have one more tip. The dpkg command you mentioned above just installs the firmware to the right position in the Linux file system so that the driver finds it correctly. Only calling the driver afterwards with DevOpenDriver() will initialize netX with the firmware. This happens for example if you start just the precompiled ethercat example code.
„You never fail until you stop trying.“, Albert Einstein (1879 - 1955)
