Not sure that I understanding you right but you have to adjust trimmer capacitors inside of the 6669 meter to match display readings to 10Mhz from GPSDO

Hi, I'm using Arduino mini in this project, here is a parsing code for date section: // receiver status array // 0=leapsecs, 1=tfom, 2=10M, 3=1PPS, 4=ant, 5=hold, 6=nsat, 7=state, 8=year, 9=month, 10=day, 11=hours, 12=mins, 13=secs, 14=day of week // 15=survey, 16=numsat long unixdelta = 315964800; //delta between GPS and unix time valPosition = strtok(dataBuffer, delimiters); long secs = 0; if (strcmp(valPosition, "CLOCK") == 0) //have a clock message { valPosition = strtok(NULL, delimiters); secs = atol(valPosition); //time in seconds valPosition = strtok(NULL, delimiters); data[0] = atoi(valPosition); //leapseconds valPosition = strtok(NULL, delimiters); data[1] = atoi(valPosition); //tfom Time figure-of-merit (1=good, 7=bad) secs = secs - data[0] + unixdelta; // subtract out the leap seconds, add in the unix to GPS epoch delta data[8] = year(secs); data[9] = month(secs); data[10] = day(secs); data[11] = hour(secs); data[12] = minute(secs); data[13] = second(secs); dataBuffer[0] = 0; }

Remember than MANY older GPS Receiver outputs will NOT have correct date, WNRO issue (after 2017). Majority of the mfg. (like Trimble) never offered firmware upgrade. This can be corrected, BUT you must do the correction with your external software. TruePosition used Furuno (Japan/South Korea GPS rcvr). === ALSO Lady Heather Source Code is available .... for Algorithms you lack. EEVBlog has a running discussion and other TruePosition owners requested information for refinements,

Yea, i got my date issue figured out. Unit is still running strong. Might get another as a spare.