When I removed it from storage, communication was gone. It took a very long
while to lock, but did so and maintained lock for a couple of weeks before
going into holdover. It then locked back for a while.
I definitely need to do more trouble shooting on it before I give up
completely. It was the
kb...@n1k.org said:
> If still nothing, put a scope on the RX output of the serial chip in the
> 3801. Do the same for the TX input of the same chip.
I think the Z3801A prints out a version string at power up. Sometimes that
helps debug the transmit path.
--
These are my opinions. I
Hi
Basic troubleshooting:
Check the regulator output voltages and repair as needed.
Basic serial troubleshooting:
Bring up a terminal program, loop back the serial with a jumper, see if you
have
a connection.
If you do, issue basic commands, see what happens.
Switch to likely baud rates
wpxs...@gmail.com said:
> Hal, I can't communicate with it. That has been gone for a while now.
I assume it worked at some point. Did talking to it stop working at the same
time the frequency stopped tracking? If so, I'd guess the CPU inside has
stopped working and isn't setting the DAC
Hal, I can't communicate with it. That has been gone for a while now.
On Sat, Mar 3, 2018 at 9:05 PM, Hal Murray wrote:
> > Mine has quit achieving lock.
> ...
> > After reading about someone else's trouble, i wonder if my OCXO has aged
> > out.
>
> Have you checked the
> Mine has quit achieving lock.
...
> After reading about someone else's trouble, i wonder if my OCXO has aged
> out.
Have you checked the status page? Is the GPS unit seeing satellites?
--
These are my opinions. I hate spam.
___
time-nuts
Mine has quit achieving lock. It goes back a ways. I had it in storage for
a while. When I got it out of storage, It took about 2 weeks to lock. It
would go into holdover sometimes for no reason I could ever discover. I
lost the ability to communicate with it. Then, one of the Lucent DC/DC