Hi all,
The problem is not the 2100. It is the Trimble Ace III receivers inside
of it. There is a company in France, Heol Design, that makes what is
essentially a replacement for the Ace III, they call it an N024 model. I
am currently in contact with them to see if their units will correct
this issue. I first noticed the problem in the Datum BC635 cards and
when I tried to go back to a 2100 is when it was confirmed for me. The
French units are about $100 apiece and I'll keep you updated on if they
work or not.
In other 2100 news if you revert the firmware back to it's oldest
version (2.something) that is embedded in the 2100 it gets rid of the 1
second leap issue. You'll lose quite a few options and functionality
like the NIST ACTS connection, which I don't think works anyway, but
your time will finally be right again. I did this by beginning the
firmware update process and power cycling my machine during it.
Basically by screwing it up you can make it better.
Sean Gallagher
On 5/4/2015 10:09 PM, Robert Watzlavick wrote:
Mine was fine until I power cycled it :( I can confirm that even
with the v4.1 firmware, power cycling it causes the date to revert
back to 1995. A software restart as listed below seems to restore the
correct date for awhile but it eventually reverts back to the wrong
year. Maybe some smart guy can reverse engineer the binary and patch
it. It must have already been patched once by the vendor since it
seems unlikely the GPS firmware would have been updated.
Luckily I have an ET-6000 so I can always feed IRIG-B from it into the
TS-2100 until it too exhibits the rollover bug. After that runs out,
I can use the 1 PPS input.
-Bob
On 05/04/2015 01:23 PM, Mark Strovink wrote:
Bob Martin<k6rtm@...> writes:
Additional information --
Power cycling (leaving it off for about 5 minutes) didn't do any good.
Once at the correct time/date, it bounces back to 1995 at about 30
seconds
after the hour (now to Sep 18, 1995).
--------------------------------------------
My Tymserve 2100 gps unit (Rev 4.1) thinks it's 1995 -- September
17, 1995.
But a restart (connect via telnet and give the commands util restart)
brings it back to the correct time and
date -- for a while? I haven't caught it dropping back, so i don't
know if
it's doing this on the hour, after an
hour, or what, but I noticed it last night, and I've restarted it a few
times today.
Any clues?
I know about the off-by-a-second issue with the pending leap second.
This
one is more interesting!
So far I've just been issuing software restarts. The next time I'll
power
cycle the sucker and see if that
does any good.
GPS signal isn't the issue; the 2100 shares an external GPS antenna
with
my Thunderbolts through a
Symmetricom 58536A GPS splitter, and the Thunderbolts are as happy as a
Thunderbolt can be.
cheers
bob k6rtm
What a great way to start a Monday: phone call that the entire domain
was
back in 1995.
The good news: Tymserve units will keep the correct date in Free mode.
GPS handling, not the GPS signail, is the problem. The GPS unit is
rolling
the date over to its initial date once the date is past May 2 or 3,
2015.
The bad news: Tech support said the company will not be providing a
fix for
a product 5 years past end of support.
_______________________________________________
time-nuts mailing list [email protected]
To unsubscribe, go
tohttps://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.
--
Respectfully,
Sean Gallagher
Malware Analyst
571-340-3475
_______________________________________________
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.
