Re: [etherlab-users] Problem with reading reference clock time: Slave synchronization datagram was not received.

2018-10-26 Thread Mohsen Alizadeh Noghani
Calling the function after *ert_master_receive* and before *ecrt_domain_queue() *fixed the issue. (At the moment, I have only tested it on stable-1.5). Best, Mohsen On Fri, Oct 26, 2018 at 11:29 AM Mohsen Alizadeh Noghani < m.aliza...@gmail.com> wrote: > Hello everyone. > Following my previous

[etherlab-users] Problem with reading reference clock time: Slave synchronization datagram was not received.

2018-10-26 Thread Mohsen Alizadeh Noghani
Hello everyone. Following my previous email, I have tried reading the 32-bit time of the reference clock by *ecrt_master_reference_clock_time* in various versions of the library. Here are the results of calling this function in userspace code: - 1.5.2 (*Failed to get reference clock time:

[etherlab-users] Failed to get reference clock time: Input/output error

2018-10-26 Thread Mohsen Alizadeh Noghani
Hello everyone. When I call *ecrt_master_reference_clock_time -*right after *ecrt_master_sync_slave_clocks()- *in my userspace code, I get the following error every cycle. *Failed to get reference clock time: Input/output error.* I'm using stable-1.5 branch. Has anyone been able to resolve this