rams UNMATCHED - DC 0.2ms / 5kHz
// igb kernel 3.18
Hi Jürgen,
I can share with you some results with the 8139too and r8169 ethercat native
drivers when used with RTAI and Preempt-RT kernel.
- with RTAI and 8139too you can achieve 10 KHz for the ethercat control loop
without losing data
Hi Jürgen,
I can share with you some results with the 8139too and r8169 ethercat native
drivers when used with RTAI and Preempt-RT kernel.
- with RTAI and 8139too you can achieve 10 KHz for the ethercat control loop
without losing datagram. (tested on Debian 6.0 i386 with RTAI-3.8.1). The
Hi Jürgen,
On 02/13/2018 10:01 AM, Jürgen Walter • DATATRONiQ wrote:
I see- will get another Intel card (although compatible ones (kernel driver
e1000, e1000e) seem to be hard to come by these days) and try with anther
kernel driver.
I also did some tests with the EtherCAT master, Xenomai and
Hello Gavin,
many thanks for the detailed reply!
On 13 Feb 2018, at 5:04, Gavin Lambert wrote:
The ec_igb driver is relatively new (and only exists in 3.18 in the
stable-1.5 branch, although the unofficial default-branch patchset
ggered by the DC sync clock).
From: Jürgen Walter • DATATRONiQ
Sent: Tuesday, 13 February 2018 14:23
To: etherlab-users@etherlab.org
Subject: [etherlab-users] yet another datagrams UNMATCHED - DC 0.2ms / 5kHz //
igb kernel 3.18
Hello list,
I have been fighting with an ethercat slave (measu
Hello list,
I have been fighting with an ethercat slave (measurement device from
imc) over the past week. I got it somewhat (mostly?) working but I am
seeing really a lot of the dreaded "datagrams UNMATCHED" in syslog.
My setup is an APU2 (AMD Chipset but "Ethernet controller: Intel
