-
Notifications
You must be signed in to change notification settings - Fork 2
Installation
Follow these instructions thoroughly to get you a copy of the project up and running on your local machine for development and testing purposes. Please contact a maintainer if you incur any trouble.
- A PC case with at least one USB 2.0 port
- A power supply unit; better use low power ones with high efficiency (more stable voltage and faster response)
- A 6th or 7th Intel CPU
- Any recent standard or micro ATX motherboard compatible with the processor. A recent test demonstrated that the most simple choice would be one with and integrated network card using e1000e driver, but it is not mandatory
- At least 16 GB of the fastest RAM compatible with the CPU and motherboard
- a PCIe network card with at least one ethernet port. It is important that at least one between the integrated network card and the PCIe one is based on one of these drivers: 8139too, e1000, e100, r8169, e1000e. Usually, the modern Intel integrated network cards are based on e1000e but it is necessary to check. If an integrated network card with e1000e driver is embedded onto the motherboard, an r8169 lan card must be chosen
- It is strongly recommended to use the r8169 LAN card as the internet port and the e1000e one as the EtherCAT port due to some minor compatibility issue with newer Linux kernels and EtherLab software, that need to be installed next
It is best to keep the configuration of the PC to its minimum, not adding a video card or any other PCI card, if it is not crucial to the application.
First of all, a basic Debian based operating system must be installed on the machine. For this project distribution, Ubuntu 16.04.4 LTS is fully supported and tested for. If you are already working on such a platform you can skip this section, and if you have some hardware constraints (such as post-2018 hardware) please follow the guide on this page. Please note that since RT features are required for this application, it is not recommended to run Linux on a virtual machine.
- Download Ubuntu 16.04.4 LTS image from here
- Create a bootable USB stick (for instance using Rufus for Windows)
- Install the operating system alongside Microsoft Windows (it is necessary because the majority of drive systems has to be set up in a Windows-based environment)
- Make sure to leave twice the RAM space as swap area and to have only one additional partition as root
(/)
- Download all the necessary updates during installation (better having wired ethernet connection)
Once Ubuntu is up and running, a real-time kernel must be installed.
Some kernel versions cannot be installed, depending on the Linux distribution used. For example, with Ubuntu 16.04.4 LTS only 4.x kernel can be used. One of the latest stable releases of the RT kernel is the 4.13.13, which is employed here. To obtain it, follow the instructions below:
- Go to https://www.kernel.org/pub/linux/kernel/v4.x/ and download linux-4.13.13.tar.xz (use
CTRL+F
to quickly spot it); - Go to https://www.kernel.org/pub/linux/kernel/projects/rt/4.13/ and download patch-4.13.13-rt5.patch.xz (it may be in
older/
); - Open a terminal and execute the following commands:
cd Downloads
tar xf linux-4.13.13.tar.xz
cd linux-4.13.13
xzcat ../patch-4.13.13-rt5.patch.xz | patch -p1
cp /boot/config-$(uname -r) .config
yes "" | make oldconfig
sudo apt-get install libncurses-dev libssl-dev libelf-dev
make menuconfig
In the DOS-style window, you are prompted to, use the keyboard to navigate to Processor type and features
-> Preemption Model
and select Fully Preemptible Kernel (RT)
. Then save and exit.
Next, conclude the installation by compiling the kernel as follows (it will take some minutes):
make modules -j$(nproc)
make -j$(nproc)
sudo make modules_install
sudo make install
sudo update-grub
Now you should be able to boot with the newly installed real-time kernel by using the advanced option in the grub at start-up. As far as the user is concerned, some minor lagging in the monitor might be experienced but it is normal. To test the kernel and getting an idea of how a real-time application is set up, https://wiki.linuxfoundation.org/realtime/start can be consulted.
To set up an EtherCAT Master application, please open a terminal and follow the instructions below. Further information can be found at original source at https://sourceforge.net/u/uecasm/etherlab-patches/ci/tip/tree/.
sudo -s
apt install mercurial
gedit ~/.hgrc
And add the following lines:
[extensions]
mq =
[ui]
username = GrabLab <grab.lab@unibo.com>
Save, exit, and return to the open terminal:
cd /usr/src
hg clone -u 33b922ec1871 http://hg.code.sf.net/p/etherlabmaster/code etherlab
hg clone http://hg.code.sf.net/u/uecasm/etherlab-patches etherlab/.hg/patches
cd etherlab
hg qpush -a
At this point, we retrieved the source code of EtherCAT master and patched it so that it is compatible with newer kernel versions, up to 4.19, and the relative network card drivers. We have now to configure the source code so that it builds according to our needs (among several available configurations, we will use the fully-preemptible one with dedicated network devices and drivers, see https://www.etherlab.org/en/ethercat/index.php for the details).
In the same terminal, type:
apt-get install dh-autoreconf
./bootstrap
./configure --disable-8139too --enable-$(YOUR_PCI_DRIVER) --enable-generic --enable-rtmutex --disable-eoe
where $(YOUR_PCI_DRIVER)
needs to be replaced by your PCI driver. If you do not know which driver is installed on your machine, on a different terminal type lshw -class network
and note down the driver name as well as the serial under the group described as Ethernet interface
.
Due to a bug in the patched version of the modules, you need to manually fix a header file in the source code of Etherlab. In particular, go back to the original terminal and type:
gedit master/slave.h
And remove lines 286 and 288 (the #ifdef commands), save and close the editor. Now you can proceed to the build step. In the same terminal, type:
make modules -j$(nproc)
make -j$(nproc)
make modules_install
make install
Now the ethercat master is installed in ”/opt/etherlab” and has to be configured at application level. Therefore:
cd /opt/etherlab/
mkdir /etc/sysconfig
cp etc/sysconfig/ethercat /etc/sysconfig/
ln -s /opt/etherlab/etc/init.d/ethercat /etc/init.d/ethercat
/usr/lib/insserv/insserv /etc/init.d/ethercat
Open "/etc/sysconfig/ethercat" (for instance with gedit) and edit it with the previously noted information:
MASTER0_DEVICE="$(YOUR_PCI_SERIAL)"
DEVICE_MODULES="$(YOUR_PCI_DRIVER)"
Now we are good to go and we can test if the master can work properly with:
./etc/init.d/ethercat start
You should see the following line printed on the console:
Starting EtherCAT master 1.5.2 done
Additional commmand line tools can be installed by creating the following link:
ln -s /opt/etherlab/bin/ethercat /usr/local/bin/ethercat
At this point, if you reboot the PC, at the startup of the real-time kernel the EtherCAT master will be automatically loaded, so that it can be used right away by any application. If for any reason you are not using e1000e as the Ethercat communication port, but the r8169 one, you might experience the failure of the driver to load at boot. This is still an unresolved issue by the developers but a pretty easy workaround is to shut down the PC and unplug it from its power cord: in this way the LAN card is initialized again and will work properly next time you boot with the real-time kernel.
In order to compile you also need the following packages:
sudo apt-get install libgl1-mesa-dev
To be able to read camera streams and implement vision-based algorithms, we make use of OpenCV open source library.
Please follow this tutorial to install it up to Step 8, but before Step 5 move the opencv directory in the following location (you will need to prepend sudo
to the commands on terminal in the successive steps):
sudo mv ~/Downloads/opencv-x.x.x /usr/local/lib/