-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
Am 01.03.2012 20:59, schrieb Soo-Hyun Yoo:
My tenuous understanding of this is that since the EtherCAT
character device tries to use the kernel's ioctl calls, the
kernel's ioctl interface (?) needs to be patched. Since
RT_PREEMPT is the
signal checked on a scope, shows very little jitter - 1us. or less.
sorry, that was a wrong number...
the module I have advertises Ton=60 us, not clear how to exactly
interpret time values below that, but zooming in the scope trace looking
at beginning of transition, jitter is more like ~30
On Thu, Mar 1, 2012 at 1:51 PM, Graeme Foot grae...@touchcut.com wrote:
** ** **
Hi,
** **
There is an RTDM patch for EtherLabs EtherCAT master for use with RTAI /
Xenomi. It allows certain ethercat calls to be made from user space from a
real-time context.
Thank you for the
Hello Soo-Hyun Yoo,
Here I have RT_PREEMPT (3.0.8-rt23), we dont use the ioctl interface as
provided by ethercat master, but a similar scheme so I was curious...
Anyways, setting up a simple mini-usr-rt.c that *does* use the etherlab
API was easy - a simple digital-out square wave @1kHz
Hi,
There is an RTDM patch for EtherLabs EtherCAT master for use with RTAI /
Xenomi. It allows certain ethercat calls to be made from user space
from a real-time context.
I don't know know about the RT_PREEMPT side of things.
Regards,
Graeme.
