Quoth Florian Pose:
> Am 23.01.2013 17:36, schrieb Jun Yuan:
> > 1. I must call ecrt_master_application_time() once somewhere before my
> > run loop, otherwise I'll get error "No app_time received up to now",
> > and ec_fsm_master_state_dc_read_offset will not be executed. The app
> > time given to
Hello,
Am 30.01.2013 11:58, schrieb Jun Yuan:
> OK, I believe that I've found the final real solution. The variable
> 'correction' is necessary. Please ignore my last change. Find below my
> final patch for this problem. I'd love to hear any feedback.
I don't understand why it should be better to
Hello,
I read your newer post already, just a quick comment on this.
Am 23.01.2013 17:36, schrieb Jun Yuan:
> 1. I must call ecrt_master_application_time() once somewhere before my run
> loop, otherwise I'll get error "No app_time received up to now", and
> ec_fsm_master_state_dc_read_offset will
Hello Florian,
OK, I believe that I've found the final real solution. The variable
'correction' is necessary. Please ignore my last change. Find below my
final patch for this problem. I'd love to hear any feedback.
diff -r 9cdd7669dc0b master/fsm_master.c
--- a/master/fsm_master.cThu Jan 10 1
Hello Florian,
I think there might be a bug in the calculation of time_diff between the
master clock and the slave clock in fsm_master.c. My temporary solution is
to comment out the line 'system_time32 += correction;' in the function
ec_fsm_master_dc_offset32() and the line 'system_time += correct
