| Electronics > Repair |
| Symmetricom NTS-200 Time Server |
| (1/17) > >> |
| BloodyCactus:
So, I got an NTS-200 off ebay for an absolute score, in unworking condition. Seller said it would not find satellites and nothing worked. ok. So, it finds satellites just fine (it can take 10 minutes to acquire, thats not unusual, maybe seller thought it would be instant.. shrug).. so I finally got into the remote system and reset the passwords, now the last problem its like dealing with racal dana all over again... dead buttons! Under the rubber button, there was supposed to be some conductive material, but its all gummed up and nasty. I need to figure what I can do to replace it. :/ anyone got any ideas. At worst I could try and jury rig a tactile button replacement and fit the black rubber pad back over top of it. Here is the dead input board; |
| uncle_bob:
Hi When you get it up and running, I suspect you will find that the GPS has the decade rollover bug and needs to be replaced. I would double check that before you go much further. Bob |
| BloodyCactus:
Ive had it working fine, just the front buttons dont work. had it tracking 6+ sats and feeding time to several devices on my network without issue. whats the decade rollover bug? pulling the version I get "Network Interface 182-9004v8.2 (c) 1998 - 2003 Symmetricom Inc." so its 8.2 (there is/was a 8.4 but nobody seems to have it). |
| uncle_bob:
Hi The wonderful people who defined the standard GPS messages did not consider gear that would be running for a long time. The assumption was that anything past a few years was about all that needed to be covered. They came up with a coding system that rolls over every 1024 weeks. A lot of gear only knows that it was built in some year and it must not be before than year. Once you get past 1024 weeks past that, it gets confused. Symmetricom had a problem with a bunch of the NTS boxes fairly recently. I have no idea if the 200 was in that group or not. Bob |
| BloodyCactus:
aah ok, so its an uptime bug. I was thinking it was like a y2k bug. I dont expect I'd have such serious 1024 WEEK uptimes, thats like 18+ years... as for time, its fine on this end |
| Navigation |
| Message Index |
| Next page |