On 07/06/12 00:44, Alan Melia wrote:
Then there is the NPL Time Frequency Club at Teddington..oh sorry
that is the wrong side of the Atlantic :-))
Depends on where you are. :)
The time-nuts now has a social web all from the happy hobbyist, advanced
hobbyists (and I've just learned that
Hi Dennis, it is part of the Comms and Electronics Metrology Network now. I
guess the DoTI or whatever they call it now has slashed the budget. There
certainly have been meetings since 2004, and with Galileo proceeding there
should be more though possibly under Tracking and Location. I have
On 06/06/12 21:21, Tom Knox wrote:
We put a few Magnetometers on Magnus and he must have burned them out, because
when they next put them on my head they saw no brain activity.
LOL!
NIST has a trouble doing Baseline measurements because they at over at
Broadway.
Cheers,
Magnus
Every GPS unit made after 1999 (the TBolt is 2003) is 1024 week aware, so
there should be no problem for the TBolt.
On Thu, Jun 7, 2012 at 6:23 AM, Robert Watzlavick.com roc...@watzlavick.com
wrote:
I poked around a bit on that site-I'll check it out more tomorrow. My
vehicle is a liquid so
The YouTube link is a hoot, IMO.
Best,
-John
Original Message
Subject: [GenRad] Re: Callibration
From:ietlabs bshe...@gmail.com
Date:Thu, June 7, 2012 5:35 am
To: gen...@yahoogroups.com
Paul,
I think the next 1024 week rollover is in the year 2020. About 8 years from
now.
Regards, Doug
Connected by DROID on Verizon Wireless
-Original message-
From: paul swed paulsw...@gmail.com
To: Discussion of precise time and frequency measurement
time-nuts@febo.com
Sent:
GPS week number roll-overs happen exactly every 1024*7 = 7168 days, which is
about 19.6 years.
0: 1980-01-06 00:00:00 UTC = MJD 44244
1: 1999-08-22 00:00:00 UTC = MJD 51412
2: 2019-04-07 00:00:00 UTC = MJD 58580
3: 2038-11-21 00:00:00 UTC = MJD 65748
4: 2058-07-07 00:00:00 UTC = MJD 72916
See
Maybe you can avoid COCOM limits: Vaisala radiosondes (the most used
type here in Europe, see www.vaisala.com) include half GPS receiver
on it and the other half is in the ground tracking program. The
balloons go up to about 30 Km and while the speed is very low this
height is above the
In my haste to post I forgot to delete the 00:00:00 UTC string from that
list. The rollovers happen at 00:00:00 GPS time, which differs from UTC by a
number of seconds.
/tvb (iPhone4)
On Jun 7, 2012, at 12:53 PM, Tom Van Baak t...@leapsecond.com wrote:
GPS week number roll-overs happen
Most GPS receivers base their rollover point from their data of
manufacture/firmware creation/etc. The week rolls over 1024 weeks after that.
They tend to not be dependent upon when the actual GPS week rolls over.
Better receivers have ways of inferring the actual week after a rollover
Hello,
There was a competitor, long ago, AIR (Atmospheric Instrumentation
Research Inc.) that produced something similar. As usual, Vaisala bought
that company in order to make it dissapear, like a lot others, but this
is another history.
I never had the details of how it worked (it was
Not true. GPS week is imbedded in the GPS data.
David
On 6/7/12 4:39 PM, Mark Sims wrote:
Most GPS receivers base their rollover point from their data of
manufacture/firmware creation/etc. The week rolls over 1024 weeks after that.
They tend to not be dependent upon when the actual GPS
I got in a couple of those Nortel GPSDO modules (marked 45000-00-B8 GPSTM).
These are the single board version of the NTGS50AA modules that have a separate
small front panel board.They are hardware and software compatible (mostly).
Some immediate differences popped up. The 45000 board
Is too true! The GPS signal sends the week number as a 10 bit integer number.
That number rolls over every 1024 weeks (call it 20 years). There is no
data sent that indicates which 1024 week cycle it is (some have been proposed,
but I don't think anything was ever implemented).
Mark
I don't get it.
20 years is just about the time we time-nuts get the good rcvrs. Whats with
these manufacturers not serving the important people?
Regards
Paul
On Thu, Jun 7, 2012 at 5:11 PM, Mark Sims hol...@hotmail.com wrote:
Is too true! The GPS signal sends the week number as a 10
So we must find a way to upload a new firmware for the TBolt before the
2017... that is download the actual firmware (3.00) correct the bias and
upload the corrected one.
On Thu, Jun 7, 2012 at 10:48 PM, David McGaw n1...@alum.dartmouth.orgwrote:
Not true. GPS week is imbedded in the GPS data.
HI
The TBolt does not directly display any date or time data. All it really puts
out are PPS and 10 MHz. The rest of the stuff needs a chunk of software to make
any sense at all out of. What you *really* need is a friend writing the
software who is willing to drop in a auto correct routine
Interesting to see
On Thu, Jun 7, 2012 at 6:34 PM, Azelio Boriani azelio.bori...@screen.itwrote:
So we must find a way to upload a new firmware for the TBolt before the
2017... that is download the actual firmware (3.00) correct the bias and
upload the corrected one.
On Thu, Jun 7, 2012 at
OK, I can write software but the TBolt has the TSIP protocol in addition to
the 10MHz and PPS. LadyHeather is usually used by TimeNuts as TBolt monitor
so the modification must be done in LH. Moreover I think that there is a
TSIP packet with time and date...
On Fri, Jun 8, 2012 at 12:42 AM, Bob
Hi
Anything that Lady Heather displays does indeed come from the TBolt and is then
interpreted by the software. My point is that none of us really use the TBolt
serial output directly. It's not like an IRIG or SMTPE box.
Bob
On Jun 7, 2012, at 6:52 PM, Azelio Boriani wrote:
OK, I can
When / how the Thunderbolt responds to a rollover event (either raw sat signal
week number or internally biased week number based upon a fixed offset or date
of manufacture) is not known. The Trimble manual suggests that it adds a
fixed bias to the transmitted week number and evil things
Good morning from Japan,
The Neutrino 2012 Conference is being held in Kyoto, Japan, this week. This
morning's session is scheduled for 3 talks on neutrino velocity--one from the
OPERA Experiment that initially reported the anomalous effect, one discussing
other experiments at the Italian Gran
Hi
One could put in a routine that looks at the date the software was written and
fix any date that shows up as being in the past. Simply *assume* it's a
rollover error and move it up modulo the magic offset number. That way any
particular rev of the software would be good for 20 years.
Bob
Hi Magnus;
I hope you have survived the 13 hours of todays seminars. If you are not
exhausted I imagine the Time-Nuts would be interested your thoughts or in any
highlights.
Feel free to call or stop by as time permits.
Best wishes;
Thomas Knox
Ascent Concepts and Technology
4475 Whitney
On 6/7/2012 8:02 PM, Bob Camp wrote:
One could put in a routine that looks at the date the software was
written and fix any date that shows up as being in the past.
After all the issues seen after the last rollover, I'd think receivers
would have been made robust against this.
One obvious
Hi
I suspect that it's one of those - I'll be gone before then sort of firmware
issues. Some fix it others ignore it unless it's on the marketing tick list.
The marketing guys may or may not have been born when the last roll over
occurred ….
Bob
On Jun 7, 2012, at 8:50 PM, Mike S wrote:
On
Mike,
The problem with your solution is that the receiver can get an error in
calculating the year value and if it writes a number greater than it
actually is into eeprom, the next time it powers on it will be forced to go
forward 19 years in time. And since it is not allowed to go
Good morning,
The Neutrino Velocity session at Neutrino 2012 in Kyoto, Japan, is now
finished. Six experiments now report no measurable difference between the
velocity of neutrinos and the velocity of light.
The first talk was from the OPERA Experiment at the Gran Sasso Laboratory, the
28 matches
Mail list logo
