Every time the FT8 extension is run times are around 1 minute off. In admin I find the dt correction set to -1. I can change it to 0 and restart the FT8 exitension and the times are Ok. Some time later when I use FT8 again the times are offset again. And the admin ext page dT correction is back to -1. A lot of decodes come through with the -1 time offset but I wonder how many are lost.
In the repo extensions / ft8 / ft8.cpp it find:
ft8_conf.dT_adj = cfg_default_int("ft8.dT_adj", -1, &update_cfg);
if (ft8_conf.dT_adj == 0) { // update to new default
cfg_set_int("ft8.dT_adj", -1);
update_cfg = true;
}
Can this be fixed? The extension seems to work fine when i enter 0 in the admin dT Correction.
Every time the FT8 extension is run times are around 1 minute off. In admin I find the dt correction set to -1. I can change it to 0 and restart the FT8 exitension and the times are Ok. Some time later when I use FT8 again the times are offset again. And the admin ext page dT correction is back to -1. A lot of decodes come through with the -1 time offset but I wonder how many are lost.
In the repo extensions / ft8 / ft8.cpp it find:
ft8_conf.dT_adj = cfg_default_int("ft8.dT_adj", -1, &update_cfg);
if (ft8_conf.dT_adj == 0) { // update to new default
cfg_set_int("ft8.dT_adj", -1);
update_cfg = true;
}
Can this be fixed? The extension seems to work fine when i enter 0 in the admin dT Correction.