2022-01-16 - 12:03

Dates and Events:

OSADL Articles:

2022-01-13 12:00

Phase #3 of OSADL project on OPC UA PubSub over TSN successfully completed

Another important milestone on the way to interoperable real-time Ethernet has been reached


2021-09-06 12:00

OSADL Talks at EWC 2022

All about legal and technical issues and solutions when using Open Source software in industry


2021-02-09 12:00

Open Source OPC UA PubSub over TSN project phase #3 launched

Letter of Intent with call for participation is now available


2016-11-12 12:00

Raspberry Pi and real-time Linux

Let's have a look at the OSADL QA Farm data



OSADL Projects

OSADL QA Farm on Real-time of Mainline Linux

About - Hardware - CPUs - Benchmarks - Graphics - Benchmarks - Kernels - Boards/Distros - Latency monitoring - Latency plots - System data - Profiles - Compare - Awards

Real-time Ethernet (Ethercat) worst-case round-trip time monitoring

Wakeup latency of all systems - Real-time optimization - Peer-to-peer UDP duplex link - OPC UA PubSub over TSN - Powerlink - Ethercat - Network load - kvm - Sleep states

One of the Linux real-time test systems (rack #5, slot #1) runs a commercial proprietary user-space Ethercat master that is connected to a Beckhoff EK1100 Ethercat coupler and EL2004/EL1012 input/output terminals. The plot below is generated from 5-minute maxima of the time elapsed between sending an Ethercat frame and receiving the response packet. The test is running at a cycle interval of 500 µs. Thus, the maximum at the rightmost column of the below 30-h plot is based on a total of 216,000,000 individual timed cycles. In addition, the maxima per week, per month and per year are stored as well to further add to the confidence of the result. Access to these data, however, requires additional user rights such as granted to OSADL members.

Last update 2 minutes ago

Real-time Ethernet worst-case round-trip time recording
Please note that the recorded values represent maxima of 5-min intervals. Thus, the data in the columns labeled "Min:" and "Avg:" should not be considered; the only relevant result is the maximum of consecutive 5-min maxima at the rightmost column labeled "Max:".