My clock had the same issues, as I mentioned. It would go through the startup function, then it would start beeping and displaying invalid data. Put a scope on the output of the RS232 -> TTL level converter when the clock exhibits the issue, pins 11 and 12 of the MAX232CPE chip. Also, check the HVENABLE line, pin 4 on the CPU. If the MAX chip is socketed, I'd just swap it. The chip in my clock was putting garbage data on the CPU and that affected the HV supply and probably other functions of the CPU, as well. At least that's my non-EE, theory. In any case, it fixed the problem and the clock has been running perfectly for a couple months.
On Thursday, May 5, 2016 at 12:33:45 PM UTC-4, Quincy wrote: > > My much loved Jeff Thomas NixiChron began behaving oddly last night. And I > haven't a clue how to get it fixed. Who does one hire in this sort of > situation, how do you find someone? > > The problem the clock is exhibiting is pretty weird. It began to beep > every few minutes (it's supposed to only beep on the hour) and the display > began to show impossible times, like "25:34:12", and the digits would > change in ways not consistent with the normal passage of time. I tried > powering off and powering on, and it still seems like it's trying to be > sort of normal. Normally when you power it on it cycles the tubes back and > forth, and beeps, and tries to get a lock on GPS satellites to get the > time. And when I power it on it does cycle the tubes and does beep as it > does when you turn it on, but all the tubes don't cycle normally, some are > out, at least partly, others are on but locked on numbers, some are showing > multiple digits at once. > > I bought it assembled. I haven't yet opened up the clock. Sometimes I > can do more harm than good, so I try to explore other options first before > turning myself loose on the problem. Occasionally I manage to fix things, > but I've also lost parts, ruined components with weak soldering skills, > shorted out things. I want to be handy with electronics, but am more used > to working in computer code where a serious error can be instantly fixed > and undone, not real life where a slight screw up can effectively ruin > something you care about forever. > > The clock is important to me, so I'd like to get it fixed by someone who > is highly likely to be successful and not cause further damage. I'm outside > Frederick, MD (just north of Washington, DC), should that matter. > > Any recommendations? > -- You received this message because you are subscribed to the Google Groups "neonixie-l" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send an email to [email protected]. To view this discussion on the web, visit https://groups.google.com/d/msgid/neonixie-l/8307159c-ba17-4ae8-a2f3-1d83e33d64df%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
