X-Git-Url: https://rtime.felk.cvut.cz/gitweb/ert_linux_web.git/blobdiff_plain/b3df0c32948f4fc7b759dbf8d7d8266f84f893ff..HEAD:/index.mdwn diff --git a/index.mdwn b/index.mdwn index 214dc76..22c704d 100644 --- a/index.mdwn +++ b/index.mdwn @@ -13,7 +13,13 @@ visualized with Simulink scopes. Linux ERT target uses heavily real-time capabilities of [real-time variant of the Linux kernel](https://rt.wiki.kernel.org/index.php/CONFIG_PREEMPT_RT_Patch) that provides bounded maximal latencies. The resulting control system -supports sampling frequencies up to 20 kHz.
+supports sampling frequencies **up to 20 kHz**. Matlab/Simulink GUI +running on the same GNU/Linux desktop system as the generated +real-time application is supported. + +More information about initial version developed by Michal Sojka at [Department of Control Engineering](https://control.fel.cvut.cz/) [FEE](http://www.fel.cvut.cz/) +[CTU](https://www.cvut.cz/) can be found in +[Michal Sojka's blog post](http://rtime.felk.cvut.cz/~sojka/blog/on-generating-linux-applications-from-simulink/). [MathWorks]: http://www.mathworks.com/ [Simulink]: http://en.wikipedia.org/wiki/Simulink @@ -24,9 +30,14 @@ supports sampling frequencies up to 20 kHz. Recent News -------------------- -- We will present the a paper +- The real time control of DC and BDLC motors from plain C and Matlab/Simulink with + ert_linux target hands-on session is planned at 29th February 2020 at 15:00â16:55 + at place of the project origin ([DCE](https://control.fel.cvut.cz/) labs) in the frame + of [InstallFest 2020](https://installfest.cz/if20/) conference. + See [details](https://pretalx.installfest.cz/installfest-2020/talk/HSNJCM/). +- The a paper [Usable Simulink Embedded Coder Target for Linux](https://www.osadl.org/?id=2018) - and RPi motor control demonstartion at + and RPi motor control has been presented at [16th Real Time Linux Workshop](https://www.osadl.org/RTLWS-2014.rtlws-2014.0.html) taking place on 12 and 13 October 2014 in Dusseldorf Germany. The [Paper](http://rtime.felk.cvut.cz/publications/public/ert_linux.pdf) @@ -34,7 +45,7 @@ Recent News [slides](http://rtime.felk.cvut.cz/publications/public/ert_linux-rtlws2014.pdf) are available from our [publications archive](http://rtime.felk.cvut.cz/publications/). -- We will present the ert_linux project at +- The ert_linux project has been presented at [Amper exhibition](http://www.amper.cz/en/online-catalog/list-of-exhibitors.html/e9595_0-fakulta-elektrotechnicka-cvut-v-praze) from 18th to 21st March 2014 in Brno, Czech Republic. - Linux ERT at Embedded World exhibition â 25 until 27 February 2014 - Visit @@ -44,7 +55,7 @@ Recent News I/O and communication interface support -------------------- -- [Humusoft MF624 data acquisition card](http://www.humusoft.com/data/session.php?redirect=/produkty/datacq/mf624/&lang=en). +- [Humusoft MF624 data acquisition card](https://www.humusoft.com/datacq/mf624/). UIO driver and Simulink blockset has been developed. The UIO driver is already @@ -56,75 +67,67 @@ I/O and communication interface support - The Bhanderi's [ComediToolbox](http://www.mathworks.com/matlabcentral/fileexchange/15792-comedi-toolbox-v1-0-for-linux-based-rtw-targets) suitable for most Linux [Comedi](http://www.comedi.org/) driver supported analog and digital inputs/output cards has been - successfuly tested with ert_linux target. The little updated + successfully tested with ert_linux target. The little updated version with target configuration example is available in **lintarget** project [download area](https://sourceforge.net/projects/lintarget/files/). -- The basic blocks for - [CAN messages sending and receiption](can_bus/index.html) under - Linux are implemented. - - - - - - - - - +- The basic blocks for [CAN bus communication](can_bus/index.html) + under Linux are implemented. RT-Capable Platform and Kernel -------------------- -Standard distribution Linux kernel does not guarantee bounded latencies for many operations. -The use of [real-time variant](http://rt.wiki.kernel.org/) of [Linux](http://en.wikipedia.org/wiki/Linux) -kernel is required to make system durable. This kernel variants minimizes regions -where switch to the highest priority (i.e. Linux ERT generated) task is blocked by -kernel when servicing system calls for other tasks. - -Selection of the right version of the kernel is not enough for non-disruptive -operation. Computer system hardware selection is critical as well. The system -has to provide enough computational power for compiled in blocks data evaluation -evaluation and Linux kernel services processing. Other critical disturbance sources -are hardware caused latencies and lags in a program processing by CPU. The source -can be bus systems load by other subsystems (i.e. graphic processor memory access, -peripheral DMA - SSD, SD-card, Flash controller etc.). The other critical source of -latencies in x86 based systems is [SMI](http://en.wikipedia.org/wiki/System_Management_Mode) -processing. The SMI enable and processing is under BIOS and motherboard vendor control -and this problem cannot be resolved by operating system. This means that proper -hardware selection is critical. - -A long period evaluation data of different combinations of Linux kernel version -runing on many CPU architectures and boards from many vendors is [OSADL](http://www.osadl.org/) +Standard distribution Linux kernel does not guarantee bounded +latencies for many operations. The use of +[real-time variant](http://rt.wiki.kernel.org/) of +[Linux](http://en.wikipedia.org/wiki/Linux) kernel is required to +guarantee bounded latencies. This kernel variants minimizes regions +where switch to the highest priority (e.g. Linux ERT generated) task +is blocked by kernel when servicing system calls for other tasks. + +Selection of the right version of the kernel is not enough for +non-disruptive operation. Computer system hardware selection is +critical as well. The system has to provide enough computational power +for compiled in blocks data evaluation evaluation and Linux kernel +services processing. Other critical disturbance sources are hardware +caused latencies and lags in a program processing by CPU. The source +can be bus systems load by other subsystems (i.e. graphic processor +memory access, peripheral DMA - SSD, SD-card, Flash controller etc.). +The other critical source of latencies in x86 based systems is +[SMI](http://en.wikipedia.org/wiki/System_Management_Mode) processing. +The SMI enable and processing is under BIOS and motherboard vendor +control and this problem cannot be resolved by the operating system. +This means that proper hardware selection is critical. + +A long period evaluation data of different combinations of Linux +kernel version running on many CPU architectures and boards from many +vendors is [OSADL](http://www.osadl.org/) [Quality Assurance Farm](http://www.osadl.org/Quality-assurance-at-the-OSADL-QA-Farm.osadl-services-qa.0.html). -According to these track records carefully selected x86 or embedded GNU/Linux system can run -real-time tasks with sampling frequencies up to 20 kHz with no losing sample per months. +According to these track records carefully selected x86 or embedded +GNU/Linux system can run real-time tasks with sampling frequencies up +to 20 kHz with no losing sample per months. Source Code and Download -------------------- -