# HG changeset patch # User Mychaela Falconia # Date 1534024337 0 # Node ID 19e5a3e2f9c053e2b0a5292188917b1ee73c61aa # Parent b88a37d4f148a10d992ee654d66a6caf67c791d9 fcup-settime: moved time() retrieval a little closer to the output A fundamental problem with all simple time transfer tools is that there is always some delay between the time retrieval on the source system and that transmitted time being set on the destination, and the resulting time on the destination system is off by that delay amount. This delay cannot be fully eliminated when working in a simple environment like ours, but we should make our best effort to minimize it. In the present case, moving the atinterf_init() call before the time() retrieval should make a teensy-tiny improvement. diff -r b88a37d4f148 -r 19e5a3e2f9c0 uptools/atcmd/settime.c --- a/uptools/atcmd/settime.c Sat Aug 11 19:43:44 2018 +0000 +++ b/uptools/atcmd/settime.c Sat Aug 11 21:52:17 2018 +0000 @@ -27,12 +27,12 @@ fprintf(stderr, "usage: %s [options]\n", argv[0]); exit(ERROR_USAGE); } + atinterf_init(); time(&unixtime); tm = localtime(&unixtime); sprintf(command, "AT+CCLK=\"%02d/%02d/%02d,%02d:%02d:%02d%+03d\"", tm->tm_year % 100, tm->tm_mon + 1, tm->tm_mday, tm->tm_hour, tm->tm_min, tm->tm_sec, tm->tm_gmtoff / (15*60)); - atinterf_init(); atinterf_exec_cmd_needok(command, 0, 0); exit(0); }