[etherlab-users] dc_user example understanding
Peter van Knippenbergh
peter.van.knippenbergh at sioux.eu
Thu Jan 21 10:39:53 CET 2010
Hi
I try to understand the synchronization mechanism in the IGH master for DC.
I try to understand what happens in the example/dc_user directory
Here is part of the code I try to understand including the questions
app_time.tv_usec += 1000000 / FREQUENCY;
if (app_time.tv_usec >= 1000000) {
app_time.tv_usec -= 1000000;
app_time.tv_sec++;
}
ecrt_master_application_time(master, EC_TIMEVAL2NANO(app_time));
What is the result of this call for the slaves (after the ecrt_master_send
call)??
if (sync_ref_counter) {
sync_ref_counter--;
} else {
sync_ref_counter = 9;
ecrt_master_sync_reference_clock(master);
What is the result for the slaves of this call for the slaves (after the
ecrt_master_send call) ??
}
ecrt_master_sync_slave_clocks(master);
Here I assume that after the ecrt_master_send all the slave clocks are
synchronized with the DC master clock and the DC master clock will not be
changed. Correct ??
// send process data
ecrt_domain_queue(domain1);
ecrt_master_send(master);
Kind regards
Peter
Peter van Knippenbergh
Test and Software designer
------------------------------------------__________________________________
___________________________
Sioux. Source of your development.
Sioux Embedded Systems B.V.
Esp 405 | 5633 AJ Eindhoven | The Netherlands
KvK Eindhoven 17093039
T +31 (0)40 2677100
T +31 (0)40 2677108 (direct)
F +31 (0)40 2677101
E <mailto:peter.van.knippenbergh at sioux.eu> peter.van.knippenbergh at sioux.eu
Visit us at: www.sioux.eu
e-mail <mailto:peter.van.knippenbergh at sioux.eu>
peter.van.knippenbergh at sioux.eu
"Sioux, the embedded systems specialists adding (more) value"
DISCLAIMER:
De informatie opgenomen in dit bericht kan vertrouwelijk zijn en is
uitsluitend bestemd voor de geadresseerde. Indien u dit bericht onterecht
ontvangt, wordt u verzocht de inhoud niet te gebruiken en de afzender direct
te informeren door het bericht te retourneren.
The information contained in this message may be confidential and is
intended to be exclusively for the addressee. Should you receive this
message unintentionally, please do not use the contents herein and notify
the sender immediately by return e-mail.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.etherlab.org/pipermail/etherlab-users/attachments/20100121/a6e81626/attachment-0003.htm>
More information about the Etherlab-users
mailing list