Hello,
For EME tracking and using, it is better to track the moon on last 10 seconds of every minute...
Due to default behavior of JT65 and similar programs, on EME communication, TX and RX cycles takes place between 0-50 seconds of every minute then, system gets idle on 51-59 seconds..
I made a modification manually on the code to stop tracking between 0-50 seconds.. but it will be nice to make it as a feature on general settings with a better coding approach..
Change I made on the code as follows to give a hint...
#ifdef FEATURE_MOON_TRACKING
void service_moon_tracking(){
int year;
byte month, day, hour, minute, gpssec, hundredths;
unsigned long fix_age;
gps.crack_datetime(&year,&month,&day,&hour,&minute,&gpssec,&hundredths);
then changed the check parameter and added 50 secs limit to that area also
Hello, For EME tracking and using, it is better to track the moon on last 10 seconds of every minute... Due to default behavior of JT65 and similar programs, on EME communication, TX and RX cycles takes place between 0-50 seconds of every minute then, system gets idle on 51-59 seconds.. I made a modification manually on the code to stop tracking between 0-50 seconds.. but it will be nice to make it as a feature on general settings with a better coding approach..
Change I made on the code as follows to give a hint...
then changed the check parameter and added 50 secs limit to that area also
if ((moon_azimuth >= MOON_AOS_AZIMUTH_MIN) && (moon_azimuth <= MOON_AOS_AZIMUTH_MAX) && (moon_elevation >= MOON_AOS_ELEVATION_MIN) && (gpssec >= 50) && (moon_elevation <= MOON_AOS_ELEVATION_MAX)) {