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

[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.alizad3h at gmail.com> wrote:

> 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: Input/output error*)
>    - stable-1.5 branch of SourceForge (*Failed to get reference clock
>    time: Input/output error*)
>    - default branch of SourceForge. (Returns -5: *Slave synchronization
>    datagram was not received*)
>    - default branch of SourceForge + gavinl's patchset (Returns -5: *Slave
>    synchronization datagram was not received*).
>
>
> - As expected, *ecrt_master_64_bit_reference_clock_time* (in the patched
> version) also returns -5 (*Slave synchronization datagram was not
> received*
> ).
> - By reading the register "0x92c" on the reference slave, I can verify
> that the DC mechanism is working as it should.
> So what is causing the error *Slave synchronization datagram was not
> received*?
> Best,
> Mohsen
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.etherlab.org/pipermail/etherlab-users/attachments/20181026/f72b629d/attachment-0004.htm>