Hi:
Thank you for the reply, I still have a problem:
In the master code: the function "ec_fsm_slave_config_state_dc_sync_check"
use the shift_time in the below code:
start = start_time +sync0->cycle_time - remainder + sync0->shift_time;
I can't understand why add the sync0->shift_time to make
Hi,
We are using e1000e too. We are using RTAI kernel modules instead of
user space. We are not using any patch or any configuration for the
e1000e either.
If I only run the latency test it goes around 10us. But when our program
is running, jitter is around 50us. I suspect somehow the semaphor
Hi,
If I want to access a slave on the Ethercat bus, we use the position of the
slave on the bus to access it with ecrt_master_slave_config(). If we then put a
new slave on the bus before this slave for example, this means that the
position number of the first slave will change and we need to re
Make sure you are not sending anything like
ecrt_master_sdo_download/ecrt_master_sdo_upload from additional threads or
anything else.
We use xenomai but always in kernel mode. We can control up to 8kHz without
issues.
On Fri, 2016-04-15 at 00:16 +0200, Richard Hacker wrote:
> On 14.04.201
Hi Paul,
The "Secondary slave address" is used for this purpose. The slaves
address is programmed with "ethercat alias".
For usage in your application code see ecrt.h.
Regards Wilhelm.
Am 15.04.2016 um 15:38 schrieb Paul Mulligan:
Hi,
If I want to access a slave on the Ethercat bus, we use
Hi Paul,
The way to do this is to use aliases. Every slave can store an alias
(which is a number) in EEPROM. To set the alias of a slave, use
# ethercat alias -p10 100
This will set the alias of slave 10 to 100.
The master can address a slave at an absolute position or relative to an
aliassed
Going into the kernel sounds like the only option I have left.
On 4/15/16, 9:59 AM, "Henry Bausley" wrote:
>
>Make sure you are not sending anything like
>ecrt_master_sdo_download/ecrt_master_sdo_upload from additional threads or
>anything else.
>
>We use xenomai but always in kernel mo