On 2 April 2014 22:40, quoth Jun Yuan: > But there is a reason why we all put the ecrt_master_application_time() > outside > the loop. Because we all got burned by the error "No app_time received up to > now, but master already active.", which is a timing bug in Etherlab. I've > resolved the problem by change the code of Etherlabmaster, which get rid of > the "No app_time" bug. Now I don't need to call > ecrt_master_application_time() > outside the loop any more. I will publish the bundle to the mailing list when > I have time.
I'd be very interested to see this. Slave sync timing, "no app time", and the 5000ms sync timeout have been a recurring bugbear for me. _______________________________________________ etherlab-users mailing list etherlab-users@etherlab.org http://lists.etherlab.org/mailman/listinfo/etherlab-users
