Activating the master resolved this issue. ecrt_master_activate takes care
of state transitions from PREOP to OP.
Best,
Mohsen
On Fri, Sep 28, 2018 at 3:56 PM Mohsen Alizadeh Noghani <
m.aliza...@gmail.com> wrote:
> Having read EtherCAT and EtherLab documentation a bit more,
>
> 1- I should set
If you have hardware access to a slave then you can also hook a scope or other
monitor to the ESC pins which indicate sync pulses or SOF/EOF (packet arrival).
This is probably easiest if you have a custom slave or if the particular slave
you’re using exposes these for diagnostic purposes; other
Two options:
1) You can use wireshark on another computer.
- Plug in a switch inline somewhere on your EtherCAT network, make sure it
forwards without delay
- Also plug your second computer into the switch, make sure you disable all
protocols on the network card (but not the card itself)
1a)
-
They need to be called some time prior to activating the master. It is not
necessary to call them earlier than this, but it’s also not harmful to do so
either (provided that the MCL_FUTURE option was specified).
From: Mohsen Alizadeh Noghani
Sent: Tuesday, 2 October 2018 22:39
To: etherlab-user
In motion control applications, smooth motion and small error often
requires an update rate of at least 1 KHz.
When defining a task in RTAI, we can set its execution frequency.
Therefore, if we set the frequency to 2 KHz, the master is expected to send
EtherCAT frames every 0.5 ms + jitter.
Other t
In the example codes, for instance dc_user, mlockall is called after
defining the slaveconfig and setpriority is called after ecrt_domain_data.
Is there a reason for not calling these functions earlier (for example in
the first line of main)?
Best,
Mohsen
___
