Charles I agree with what needs to be looked at first and thats the downconverter. Its really a starlink GPS receiver that I tapped the RF off of and upconverted to 75.42 Mhz for the 2201. The startlink is driven and controlled from the corrected 10 Mhz 2201signal that would have gone to the original converter. It has operated well in the past. The starlink itself is working very well good S/N etc. So that tends to reduce the possibilities for the issue. Regards Paul.
On Wed, Nov 11, 2015 at 9:42 PM, Charles Steinmetz <[email protected]> wrote: > Paul wrote: > > Indeed the almanac seems to be the problem. I can see what it thinks should >> be in view. Its not been easy to backout if the satelliets are behind or >> in >> the future. My time mis-alignment even though the closks correct within 1 >> second and the same for my location accuracy. I can manually tell it to >> track a satellite and it does. Though even at that it seems to have issues >> I speculate as poor signal to noise. So may have to do some digging. >> > > If there is a signal-to-noise problem, it's either the antenna location, > the antenna, or the front end of the receiver. > > Normally I'd discount the front end entirely and focus on the first two, > but IIRC you said you home-brewed a down-converter -- so that has to be on > the table, as well. > > Anyway, fix the S/N problem, then just let it run and it should sort > itself out. > > Best regards, > > Charles > > > > _______________________________________________ > time-nuts mailing list -- [email protected] > To unsubscribe, go to > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. > _______________________________________________ time-nuts mailing list -- [email protected] To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
