Re: [etherlab-users] Problem with distributed clocks in RTAI: "Slave did not sync after 5000 ms" & "No Sync Error"

I think I'm dealing with two separate problems here: 1- `abs_sync_diff` doesn't converge. 2- After the period specified by `EC_DC_SYNC_WAIT_MS`, something happens that disrupts the real-time cycle, hence EtherCAT error code 0x002D

Re: [etherlab-users] Problem with distributed clocks in RTAI: "Slave did not sync after 5000 ms" & "No Sync Error"

Both problems were fixed by using the latest snapshot of stable-1.5 branch (commit 336963) in SourceForge. Best, Mohsen On Mon, Oct 22, 2018 at 11:07 AM Mohsen Alizadeh Noghani < m.aliza...@gmail.com> wrote: > I think I'm dealing with two separate problems here: > 1- `abs_sync_diff` doesn't conv

[etherlab-users] Unable to write servo drive control word

Hi all, I'm very new to the world of EtherCat so please excuse me if the question is 'dumb'. I'm a CNC hobbyist that was so lucky to stumble upon 3 Mitsubishi servo drives with EtherCat option. I've been trying to get the drive to respond via EtherCat and I have partial successful. I can read par

[etherlab-users] Unable to write servo drive control word

Hi Jan. I don't think requesting OP mode is a good idea. Drive configuration (e.g. setting the control word) is often done in the PRE-OP state, which, if the master module is active, is automatically requested. Additionally, even if you do enter OP mode, you have to continually send frames in order