Hi,
I have a very strange problem.
I'm running V1.5 in user mode. My app clocks the bus at 1KHz with
ecrt_domain_queue/ecrt_master_send /ecrt_master_receive/ecrt_domain_process and
get my data back with EC_READ's.
Devices on the bus vary, but include Kollmorgen S300, Festo pressure
Hello Ian
Are you trying to get an application running in real time to talk to
your X-screen? If that is true, you're in for trouble IMHO :(
Regards
Richard
Am 02/04/2013 12:06 PM, schrieb Ian Norton:
Hi,
I have a very strange problem.
I'm running V1.5 in user mode. My app clocks the bus
Hi Richard
No, no, no.
I'm not in real time, it's not important. I just have a thread that ticks away
at 1Khz and calls the relevant master routines. In the the millisecond between
ticks I calculate a few things and control the motor. The X windowy bit is just
for the programs GUI, and
Hello Ian
But it does look like you are talking to the X-Server from within the
same process (Note: process, which includes its threads!) that is also
handling EtherCAT. Am I correct?
Am 02/04/2013 03:02 PM, schrieb Ian Norton:
Hi Richard
No, no, no.
I'm not in real time, it's not
Has anyone else gotten this combination of driver and kernel to work?
Here's the /var/log/messages output when I start the ethercat master:
[ 869.854110] EtherCAT: Master driver 1.5.1 9cdd7669dc0b
[ 869.854252] EtherCAT: 1 master waiting for devices.
[ 869.944866] e1000e :04:00.0: PCI INT
Hi Jürgen Daniel,
I have a fix for the first issue in my local copy of the driver (see my post
to the dev list on 25 October for specific details). I have seen the second
issue but not chased down a fix for it yet.
Also I just noticed that Florian updated the drivers on 4 January (posted
Hello Gavin,
thanks for the hint, I'll have a look for Florians patch and your post.
I applied Florians Link detection patch for e1000e driver 3.4 to the
3.2er driver (see attatchment), it solves the link detection issue here.
Regards,
Jürgen Kunz
Am 05.02.2013 06:26, schrieb Gavin Lambert:
