time-nuts@lists.febo.com

Discussion of precise time and frequency measurement

View all threads

LORAN-C demise

KH
ken hartman
Sat, Nov 28, 2009 7:09 PM

Given the confusing and seemingly ambiguous infomation on the .gov site, a
clearer picture is given by this announcement:

http://www.gpsworld.com/gnss-system/news/coast-guard-jettisons-loran-9178

excerpted below:

Coast Guard Jettisons Loran
November 25, 2009

The U.S. Coast Guard Commandant has formally certified that termination of
the Loran-C signal will not adversely impact maritime navigation, signing a
document to that effect on November 20 and forwarding it to the Secretary of
Homeland Security Janet Napolitano. The first of the two criteria for
terminating the Loran-C signal has thus been met.

Anticipated next steps include a Coast Guard ALCOAST Internet message
release on this topic, the release of the Programmatic Environmental Impact
Statement Record of Decision, and a Federal Register Notice, all measures en
route to executing the termination of the Loran-C signal.

Actual termination depends upon a final determination by DHS Secretary
Napolitano that the Loran-C infrastructure is not required as a backup to
GPS. Until then, the Coast Guard will continue  moving towards termination
while operating the system. If/when that determination is made, actual
termination will take place.
For a recent GPS World blog and readers' comments on this subject, see Wide
Awake with No Back-Uphttp://www.gpsworld.com/gnss-system/wide-awake/wide-awake-with-no-back-9168
.

Inevitable , but still a misguided shame.

Given the confusing and seemingly ambiguous infomation on the .gov site, a clearer picture is given by this announcement: http://www.gpsworld.com/gnss-system/news/coast-guard-jettisons-loran-9178 excerpted below: Coast Guard Jettisons Loran November 25, 2009 ------------------------------ The U.S. Coast Guard Commandant has formally certified that termination of the Loran-C signal will not adversely impact maritime navigation, signing a document to that effect on November 20 and forwarding it to the Secretary of Homeland Security Janet Napolitano. The first of the two criteria for terminating the Loran-C signal has thus been met. Anticipated next steps include a Coast Guard ALCOAST Internet message release on this topic, the release of the Programmatic Environmental Impact Statement Record of Decision, and a Federal Register Notice, all measures en route to executing the termination of the Loran-C signal. Actual termination depends upon a final determination by DHS Secretary Napolitano that the Loran-C infrastructure is not required as a backup to GPS. Until then, the Coast Guard will continue moving towards termination while operating the system. If/when that determination is made, actual termination will take place. For a recent *GPS World* blog and readers' comments on this subject, see Wide Awake with No Back-Up<http://www.gpsworld.com/gnss-system/wide-awake/wide-awake-with-no-back-9168> . Inevitable , but still a misguided shame.
JF
J. Forster
Sat, Nov 28, 2009 7:43 PM

There are on-line petition sites where people can sign on to support a
particular cause. Has anyone started such a petition to save LORAN?

I've not seen one.

Best,
-John

==============

Given the confusing and seemingly ambiguous infomation on the .gov site, a
clearer picture is given by this announcement:

http://www.gpsworld.com/gnss-system/news/coast-guard-jettisons-loran-9178

excerpted below:

Coast Guard Jettisons Loran
November 25, 2009

The U.S. Coast Guard Commandant has formally certified that termination of
the Loran-C signal will not adversely impact maritime navigation, signing
a
document to that effect on November 20 and forwarding it to the Secretary
of
Homeland Security Janet Napolitano. The first of the two criteria for
terminating the Loran-C signal has thus been met.

Anticipated next steps include a Coast Guard ALCOAST Internet message
release on this topic, the release of the Programmatic Environmental
Impact
Statement Record of Decision, and a Federal Register Notice, all measures
en
route to executing the termination of the Loran-C signal.

Actual termination depends upon a final determination by DHS Secretary
Napolitano that the Loran-C infrastructure is not required as a backup to
GPS. Until then, the Coast Guard will continue  moving towards termination
while operating the system. If/when that determination is made, actual
termination will take place.
For a recent GPS World blog and readers' comments on this subject, see
Wide
Awake with No
Back-Uphttp://www.gpsworld.com/gnss-system/wide-awake/wide-awake-with-no-back-9168
.

Inevitable , but still a misguided shame.


time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.

There are on-line petition sites where people can sign on to support a particular cause. Has anyone started such a petition to save LORAN? I've not seen one. Best, -John ============== > Given the confusing and seemingly ambiguous infomation on the .gov site, a > clearer picture is given by this announcement: > > http://www.gpsworld.com/gnss-system/news/coast-guard-jettisons-loran-9178 > > excerpted below: > > Coast Guard Jettisons Loran > November 25, 2009 > ------------------------------ > > The U.S. Coast Guard Commandant has formally certified that termination of > the Loran-C signal will not adversely impact maritime navigation, signing > a > document to that effect on November 20 and forwarding it to the Secretary > of > Homeland Security Janet Napolitano. The first of the two criteria for > terminating the Loran-C signal has thus been met. > > Anticipated next steps include a Coast Guard ALCOAST Internet message > release on this topic, the release of the Programmatic Environmental > Impact > Statement Record of Decision, and a Federal Register Notice, all measures > en > route to executing the termination of the Loran-C signal. > > Actual termination depends upon a final determination by DHS Secretary > Napolitano that the Loran-C infrastructure is not required as a backup to > GPS. Until then, the Coast Guard will continue moving towards termination > while operating the system. If/when that determination is made, actual > termination will take place. > For a recent *GPS World* blog and readers' comments on this subject, see > Wide > Awake with No > Back-Up<http://www.gpsworld.com/gnss-system/wide-awake/wide-awake-with-no-back-9168> > . > > Inevitable , but still a misguided shame. > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. > >
CH
Chuck Harris
Sat, Nov 28, 2009 8:36 PM

Time and frequency measurement people were specifically
exclude from the polls I have seen to determine whether
or not Loran should continue.  They only wanted navigation
users input... and I guess there weren't any.

-Chuck

J. Forster wrote:

There are on-line petition sites where people can sign on to support a
particular cause. Has anyone started such a petition to save LORAN?

I've not seen one.

Best,
-John

==============

Given the confusing and seemingly ambiguous infomation on the .gov site, a
clearer picture is given by this announcement:

http://www.gpsworld.com/gnss-system/news/coast-guard-jettisons-loran-9178

excerpted below:

Coast Guard Jettisons Loran
November 25, 2009

The U.S. Coast Guard Commandant has formally certified that termination of
the Loran-C signal will not adversely impact maritime navigation, signing
a
document to that effect on November 20 and forwarding it to the Secretary
of
Homeland Security Janet Napolitano. The first of the two criteria for
terminating the Loran-C signal has thus been met.

Anticipated next steps include a Coast Guard ALCOAST Internet message
release on this topic, the release of the Programmatic Environmental
Impact
Statement Record of Decision, and a Federal Register Notice, all measures
en
route to executing the termination of the Loran-C signal.

Actual termination depends upon a final determination by DHS Secretary
Napolitano that the Loran-C infrastructure is not required as a backup to
GPS. Until then, the Coast Guard will continue  moving towards termination
while operating the system. If/when that determination is made, actual
termination will take place.
For a recent GPS World blog and readers' comments on this subject, see
Wide
Awake with No
Back-Uphttp://www.gpsworld.com/gnss-system/wide-awake/wide-awake-with-no-back-9168
.

Inevitable , but still a misguided shame.


time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.


time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.

Time and frequency measurement people were specifically exclude from the polls I have seen to determine whether or not Loran should continue. They only wanted navigation users input... and I guess there weren't any. -Chuck J. Forster wrote: > There are on-line petition sites where people can sign on to support a > particular cause. Has anyone started such a petition to save LORAN? > > I've not seen one. > > Best, > -John > > ============== > > > >> Given the confusing and seemingly ambiguous infomation on the .gov site, a >> clearer picture is given by this announcement: >> >> http://www.gpsworld.com/gnss-system/news/coast-guard-jettisons-loran-9178 >> >> excerpted below: >> >> Coast Guard Jettisons Loran >> November 25, 2009 >> ------------------------------ >> >> The U.S. Coast Guard Commandant has formally certified that termination of >> the Loran-C signal will not adversely impact maritime navigation, signing >> a >> document to that effect on November 20 and forwarding it to the Secretary >> of >> Homeland Security Janet Napolitano. The first of the two criteria for >> terminating the Loran-C signal has thus been met. >> >> Anticipated next steps include a Coast Guard ALCOAST Internet message >> release on this topic, the release of the Programmatic Environmental >> Impact >> Statement Record of Decision, and a Federal Register Notice, all measures >> en >> route to executing the termination of the Loran-C signal. >> >> Actual termination depends upon a final determination by DHS Secretary >> Napolitano that the Loran-C infrastructure is not required as a backup to >> GPS. Until then, the Coast Guard will continue moving towards termination >> while operating the system. If/when that determination is made, actual >> termination will take place. >> For a recent *GPS World* blog and readers' comments on this subject, see >> Wide >> Awake with No >> Back-Up<http://www.gpsworld.com/gnss-system/wide-awake/wide-awake-with-no-back-9168> >> . >> >> Inevitable , but still a misguided shame. >> _______________________________________________ >> time-nuts mailing list -- time-nuts@febo.com >> To unsubscribe, go to >> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts >> and follow the instructions there. >> >> > > > > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. >
KH
ken hartman
Sat, Nov 28, 2009 9:04 PM

My impression is that significant stake-holders (e.g. Telecom service
providers, ILECs, AOPA, National Laboratories, FAA, NIST, DHS, CG, and
others) were unwilling  - at an institutional level - to embrace or own any
aspect of LORAN preservation and unable - at an individual level - to
influence "policy" decisions with any consideration for technical
viability or necessity.
Stated  differently  - this nations  NTP policy is totally driven  by
political considerations without regard to demonstrable critical
infrastructure technical evaluation.
Standard disclaimer: My opinions only
khartman

On Sat, Nov 28, 2009 at 2:36 PM, Chuck Harris cfharris@erols.com wrote:

Time and frequency measurement people were specifically
exclude from the polls I have seen to determine whether
or not Loran should continue.  They only wanted navigation
users input... and I guess there weren't any.

-Chuck

J. Forster wrote:

There are on-line petition sites where people can sign on to support a
particular cause. Has anyone started such a petition to save LORAN?

I've not seen one.

Best,
-John

==============

Given the confusing and seemingly ambiguous infomation on the .gov site,

a
clearer picture is given by this announcement:

http://www.gpsworld.com/gnss-system/news/coast-guard-jettisons-loran-9178

excerpted below:

Coast Guard Jettisons Loran
November 25, 2009

The U.S. Coast Guard Commandant has formally certified that termination
of
the Loran-C signal will not adversely impact maritime navigation, signing
a
document to that effect on November 20 and forwarding it to the Secretary
of
Homeland Security Janet Napolitano. The first of the two criteria for
terminating the Loran-C signal has thus been met.

Anticipated next steps include a Coast Guard ALCOAST Internet message
release on this topic, the release of the Programmatic Environmental
Impact
Statement Record of Decision, and a Federal Register Notice, all measures
en
route to executing the termination of the Loran-C signal.

Actual termination depends upon a final determination by DHS Secretary
Napolitano that the Loran-C infrastructure is not required as a backup to
GPS. Until then, the Coast Guard will continue  moving towards
termination
while operating the system. If/when that determination is made, actual
termination will take place.
For a recent GPS World blog and readers' comments on this subject, see
Wide
Awake with No
Back-Up<
http://www.gpsworld.com/gnss-system/wide-awake/wide-awake-with-no-back-9168

.

Inevitable , but still a misguided shame.


time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.


time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.


time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.

My impression is that significant stake-holders (e.g. Telecom service providers, ILECs, AOPA, National Laboratories, FAA, NIST, DHS, CG, and others) were unwilling - at an institutional level - to embrace or own any aspect of LORAN preservation and unable - at an individual level - to influence "policy" decisions with *any* consideration for technical viability or necessity. Stated differently - this nations NTP policy is totally driven by political considerations without regard to demonstrable critical infrastructure technical evaluation. Standard disclaimer: My opinions only khartman On Sat, Nov 28, 2009 at 2:36 PM, Chuck Harris <cfharris@erols.com> wrote: > Time and frequency measurement people were specifically > exclude from the polls I have seen to determine whether > or not Loran should continue. They only wanted navigation > users input... and I guess there weren't any. > > -Chuck > > > J. Forster wrote: > >> There are on-line petition sites where people can sign on to support a >> particular cause. Has anyone started such a petition to save LORAN? >> >> I've not seen one. >> >> Best, >> -John >> >> ============== >> >> >> >> Given the confusing and seemingly ambiguous infomation on the .gov site, >>> a >>> clearer picture is given by this announcement: >>> >>> http://www.gpsworld.com/gnss-system/news/coast-guard-jettisons-loran-9178 >>> >>> excerpted below: >>> >>> Coast Guard Jettisons Loran >>> November 25, 2009 >>> ------------------------------ >>> >>> The U.S. Coast Guard Commandant has formally certified that termination >>> of >>> the Loran-C signal will not adversely impact maritime navigation, signing >>> a >>> document to that effect on November 20 and forwarding it to the Secretary >>> of >>> Homeland Security Janet Napolitano. The first of the two criteria for >>> terminating the Loran-C signal has thus been met. >>> >>> Anticipated next steps include a Coast Guard ALCOAST Internet message >>> release on this topic, the release of the Programmatic Environmental >>> Impact >>> Statement Record of Decision, and a Federal Register Notice, all measures >>> en >>> route to executing the termination of the Loran-C signal. >>> >>> Actual termination depends upon a final determination by DHS Secretary >>> Napolitano that the Loran-C infrastructure is not required as a backup to >>> GPS. Until then, the Coast Guard will continue moving towards >>> termination >>> while operating the system. If/when that determination is made, actual >>> termination will take place. >>> For a recent *GPS World* blog and readers' comments on this subject, see >>> Wide >>> Awake with No >>> Back-Up< >>> http://www.gpsworld.com/gnss-system/wide-awake/wide-awake-with-no-back-9168 >>> > >>> . >>> >>> Inevitable , but still a misguided shame. >>> _______________________________________________ >>> time-nuts mailing list -- time-nuts@febo.com >>> To unsubscribe, go to >>> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts >>> and follow the instructions there. >>> >>> >>> >> >> >> _______________________________________________ >> time-nuts mailing list -- time-nuts@febo.com >> To unsubscribe, go to >> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts >> and follow the instructions there. >> >> > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. >
BC
Bob Camp
Sat, Nov 28, 2009 10:47 PM

Hi

Some of us have been trying to get the telcom OEM's to embrace a backup for GPS. There are a number of possible things they could do at various points in their networks. Different companies have pushed different approaches for many years. In all cases the response has been "the carriers don't want it". If you go to the carriers it's "the regulations don't require it".  I suspect if you go to the regulators they have their answer as well.

The net result is that something like 99+% of the GPS based stuff out there has no real backup (other than holdover) built into it. Without a backup already built into the gear, keeping Loran up or not has very little impact. Without a regulatory change none of the alternatives are going to get built in. They don't all depend on Loran's unclear future. None of them will go in unless there's a requirement to do so ...

That's true worldwide. It's not an issue with one country or another. It's not an issue with one system or the other. It's not an issue of a level of system or quality of carrier. It's not even an issue of military versus commercial. They just plain don't do it. Backup for timing simply isn't on anybody's list.

Sad but very true.

Bob

On Nov 28, 2009, at 4:04 PM, ken hartman wrote:

My impression is that significant stake-holders (e.g. Telecom service
providers, ILECs, AOPA, National Laboratories, FAA, NIST, DHS, CG, and
others) were unwilling  - at an institutional level - to embrace or own any
aspect of LORAN preservation and unable - at an individual level - to
influence "policy" decisions with any consideration for technical
viability or necessity.
Stated  differently  - this nations  NTP policy is totally driven  by
political considerations without regard to demonstrable critical
infrastructure technical evaluation.
Standard disclaimer: My opinions only
khartman

On Sat, Nov 28, 2009 at 2:36 PM, Chuck Harris cfharris@erols.com wrote:

Time and frequency measurement people were specifically
exclude from the polls I have seen to determine whether
or not Loran should continue.  They only wanted navigation
users input... and I guess there weren't any.

-Chuck

J. Forster wrote:

There are on-line petition sites where people can sign on to support a
particular cause. Has anyone started such a petition to save LORAN?

I've not seen one.

Best,
-John

==============

Given the confusing and seemingly ambiguous infomation on the .gov site,

a
clearer picture is given by this announcement:

http://www.gpsworld.com/gnss-system/news/coast-guard-jettisons-loran-9178

excerpted below:

Coast Guard Jettisons Loran
November 25, 2009

The U.S. Coast Guard Commandant has formally certified that termination
of
the Loran-C signal will not adversely impact maritime navigation, signing
a
document to that effect on November 20 and forwarding it to the Secretary
of
Homeland Security Janet Napolitano. The first of the two criteria for
terminating the Loran-C signal has thus been met.

Anticipated next steps include a Coast Guard ALCOAST Internet message
release on this topic, the release of the Programmatic Environmental
Impact
Statement Record of Decision, and a Federal Register Notice, all measures
en
route to executing the termination of the Loran-C signal.

Actual termination depends upon a final determination by DHS Secretary
Napolitano that the Loran-C infrastructure is not required as a backup to
GPS. Until then, the Coast Guard will continue  moving towards
termination
while operating the system. If/when that determination is made, actual
termination will take place.
For a recent GPS World blog and readers' comments on this subject, see
Wide
Awake with No
Back-Up<
http://www.gpsworld.com/gnss-system/wide-awake/wide-awake-with-no-back-9168

.

Inevitable , but still a misguided shame.


time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.


time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.


time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.


time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.

Hi Some of us have been trying to get the telcom OEM's to embrace a backup for GPS. There are a number of possible things they could do at various points in their networks. Different companies have pushed different approaches for many years. In all cases the response has been "the carriers don't want it". If you go to the carriers it's "the regulations don't require it". I suspect if you go to the regulators they have their answer as well. The net result is that something like 99+% of the GPS based stuff out there has no real backup (other than holdover) built into it. Without a backup already built into the gear, keeping Loran up or not has very little impact. Without a regulatory change none of the alternatives are going to get built in. They don't all depend on Loran's unclear future. None of them will go in unless there's a requirement to do so ... That's true worldwide. It's not an issue with one country or another. It's not an issue with one system or the other. It's not an issue of a level of system or quality of carrier. It's not even an issue of military versus commercial. They just plain don't do it. Backup for timing simply isn't on anybody's list. Sad but very true. Bob On Nov 28, 2009, at 4:04 PM, ken hartman wrote: > My impression is that significant stake-holders (e.g. Telecom service > providers, ILECs, AOPA, National Laboratories, FAA, NIST, DHS, CG, and > others) were unwilling - at an institutional level - to embrace or own any > aspect of LORAN preservation and unable - at an individual level - to > influence "policy" decisions with *any* consideration for technical > viability or necessity. > Stated differently - this nations NTP policy is totally driven by > political considerations without regard to demonstrable critical > infrastructure technical evaluation. > Standard disclaimer: My opinions only > khartman > > > On Sat, Nov 28, 2009 at 2:36 PM, Chuck Harris <cfharris@erols.com> wrote: > >> Time and frequency measurement people were specifically >> exclude from the polls I have seen to determine whether >> or not Loran should continue. They only wanted navigation >> users input... and I guess there weren't any. >> >> -Chuck >> >> >> J. Forster wrote: >> >>> There are on-line petition sites where people can sign on to support a >>> particular cause. Has anyone started such a petition to save LORAN? >>> >>> I've not seen one. >>> >>> Best, >>> -John >>> >>> ============== >>> >>> >>> >>> Given the confusing and seemingly ambiguous infomation on the .gov site, >>>> a >>>> clearer picture is given by this announcement: >>>> >>>> http://www.gpsworld.com/gnss-system/news/coast-guard-jettisons-loran-9178 >>>> >>>> excerpted below: >>>> >>>> Coast Guard Jettisons Loran >>>> November 25, 2009 >>>> ------------------------------ >>>> >>>> The U.S. Coast Guard Commandant has formally certified that termination >>>> of >>>> the Loran-C signal will not adversely impact maritime navigation, signing >>>> a >>>> document to that effect on November 20 and forwarding it to the Secretary >>>> of >>>> Homeland Security Janet Napolitano. The first of the two criteria for >>>> terminating the Loran-C signal has thus been met. >>>> >>>> Anticipated next steps include a Coast Guard ALCOAST Internet message >>>> release on this topic, the release of the Programmatic Environmental >>>> Impact >>>> Statement Record of Decision, and a Federal Register Notice, all measures >>>> en >>>> route to executing the termination of the Loran-C signal. >>>> >>>> Actual termination depends upon a final determination by DHS Secretary >>>> Napolitano that the Loran-C infrastructure is not required as a backup to >>>> GPS. Until then, the Coast Guard will continue moving towards >>>> termination >>>> while operating the system. If/when that determination is made, actual >>>> termination will take place. >>>> For a recent *GPS World* blog and readers' comments on this subject, see >>>> Wide >>>> Awake with No >>>> Back-Up< >>>> http://www.gpsworld.com/gnss-system/wide-awake/wide-awake-with-no-back-9168 >>>>> >>>> . >>>> >>>> Inevitable , but still a misguided shame. >>>> _______________________________________________ >>>> time-nuts mailing list -- time-nuts@febo.com >>>> To unsubscribe, go to >>>> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts >>>> and follow the instructions there. >>>> >>>> >>>> >>> >>> >>> _______________________________________________ >>> time-nuts mailing list -- time-nuts@febo.com >>> To unsubscribe, go to >>> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts >>> and follow the instructions there. >>> >>> >> _______________________________________________ >> time-nuts mailing list -- time-nuts@febo.com >> To unsubscribe, go to >> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts >> and follow the instructions there. >> > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. >
PS
paul swed
Sun, Nov 29, 2009 12:58 AM

Well that surely is pretty clear.
Now will DHS sign off I suspect yes

On Sat, Nov 28, 2009 at 2:09 PM, ken hartman kdhartman@gmail.com wrote:

Given the confusing and seemingly ambiguous infomation on the .gov site, a
clearer picture is given by this announcement:

http://www.gpsworld.com/gnss-system/news/coast-guard-jettisons-loran-9178

excerpted below:

Coast Guard Jettisons Loran
November 25, 2009

The U.S. Coast Guard Commandant has formally certified that termination of
the Loran-C signal will not adversely impact maritime navigation, signing a
document to that effect on November 20 and forwarding it to the Secretary
of
Homeland Security Janet Napolitano. The first of the two criteria for
terminating the Loran-C signal has thus been met.

Anticipated next steps include a Coast Guard ALCOAST Internet message
release on this topic, the release of the Programmatic Environmental Impact
Statement Record of Decision, and a Federal Register Notice, all measures
en
route to executing the termination of the Loran-C signal.

Actual termination depends upon a final determination by DHS Secretary
Napolitano that the Loran-C infrastructure is not required as a backup to
GPS. Until then, the Coast Guard will continue  moving towards termination
while operating the system. If/when that determination is made, actual
termination will take place.
For a recent GPS World blog and readers' comments on this subject, see
Wide
Awake with No Back-Up<
http://www.gpsworld.com/gnss-system/wide-awake/wide-awake-with-no-back-9168

.

Inevitable , but still a misguided shame.


time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.

Well that surely is pretty clear. Now will DHS sign off I suspect yes On Sat, Nov 28, 2009 at 2:09 PM, ken hartman <kdhartman@gmail.com> wrote: > Given the confusing and seemingly ambiguous infomation on the .gov site, a > clearer picture is given by this announcement: > > http://www.gpsworld.com/gnss-system/news/coast-guard-jettisons-loran-9178 > > excerpted below: > > Coast Guard Jettisons Loran > November 25, 2009 > ------------------------------ > > The U.S. Coast Guard Commandant has formally certified that termination of > the Loran-C signal will not adversely impact maritime navigation, signing a > document to that effect on November 20 and forwarding it to the Secretary > of > Homeland Security Janet Napolitano. The first of the two criteria for > terminating the Loran-C signal has thus been met. > > Anticipated next steps include a Coast Guard ALCOAST Internet message > release on this topic, the release of the Programmatic Environmental Impact > Statement Record of Decision, and a Federal Register Notice, all measures > en > route to executing the termination of the Loran-C signal. > > Actual termination depends upon a final determination by DHS Secretary > Napolitano that the Loran-C infrastructure is not required as a backup to > GPS. Until then, the Coast Guard will continue moving towards termination > while operating the system. If/when that determination is made, actual > termination will take place. > For a recent *GPS World* blog and readers' comments on this subject, see > Wide > Awake with No Back-Up< > http://www.gpsworld.com/gnss-system/wide-awake/wide-awake-with-no-back-9168 > > > . > > Inevitable , but still a misguided shame. > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. >
MS
Mark Spencer
Sun, Nov 29, 2009 4:44 PM

If any one is intersted this doccument provides some insight into the isssues involved in using Loran for "industrial timing"

http://tf.nist.gov/general/pdf/2193.pdf

As a side note in the past I have encountered "Legacy Loran" as a timing source in telecom carrier networks.   The last time I saw this was 7 or 8 years ago IIRC.  

As a side note does any one know how prevalent Cesium Stratum one clocks are in the telcom world these days ?

 
----- Original Message ----
From: Bob Camp lists@cq.nu
To: Discussion of precise time and frequency measurement time-nuts@febo.com
Sent: Sat, November 28, 2009 2:47:55 PM
Subject: Re: [time-nuts] LORAN-C demise

Hi

Some of us have been trying to get the telcom OEM's to embrace a backup for GPS. There are a number of possible things they could do at various points in their networks. Different companies have pushed different approaches for many years. In all cases the response has been "the carriers don't want it". If you go to the carriers it's "the regulations don't require it".  I suspect if you go to the regulators they have their answer as well.

The net result is that something like 99+% of the GPS based stuff out there has no real backup (other than holdover) built into it. Without a backup already built into the gear, keeping Loran up or not has very little impact. Without a regulatory change none of the alternatives are going to get built in. They don't all depend on Loran's unclear future. None of them will go in unless there's a requirement to do so ...

That's true worldwide. It's not an issue with one country or another. It's not an issue with one system or the other. It's not an issue of a level of system or quality of carrier. It's not even an issue of military versus commercial. They just plain don't do it. Backup for timing simply isn't on anybody's list. 

Sad but very true.

Bob

On Nov 28, 2009, at 4:04 PM, ken hartman wrote:

My impression is that significant stake-holders (e.g. Telecom service
providers, ILECs, AOPA, National Laboratories, FAA, NIST, DHS, CG, and
others) were unwilling  - at an institutional level - to embrace or own any
aspect of LORAN preservation and unable - at an individual level - to
influence "policy" decisions with any consideration for technical
viability or necessity.
Stated  differently  - this nations  NTP policy is totally driven  by
political considerations without regard to demonstrable critical
infrastructure technical evaluation.
Standard disclaimer: My opinions only
khartman

On Sat, Nov 28, 2009 at 2:36 PM, Chuck Harris cfharris@erols.com wrote:

Time and frequency measurement people were specifically
exclude from the polls I have seen to determine whether
or not Loran should continue.  They only wanted navigation
users input... and I guess there weren't any.

-Chuck

J. Forster wrote:

There are on-line petition sites where people can sign on to support a
particular cause. Has anyone started such a petition to save LORAN?

I've not seen one.

Best,
-John

==============

Given the confusing and seemingly ambiguous infomation on the .gov site,

a
clearer picture is given by this announcement:

http://www.gpsworld.com/gnss-system/news/coast-guard-jettisons-loran-9178

excerpted below:

Coast Guard Jettisons Loran
November 25, 2009

The U.S. Coast Guard Commandant has formally certified that termination
of
the Loran-C signal will not adversely impact maritime navigation, signing
a
document to that effect on November 20 and forwarding it to the Secretary
of
Homeland Security Janet Napolitano. The first of the two criteria for
terminating the Loran-C signal has thus been met.

Anticipated next steps include a Coast Guard ALCOAST Internet message
release on this topic, the release of the Programmatic Environmental
Impact
Statement Record of Decision, and a Federal Register Notice, all measures
en
route to executing the termination of the Loran-C signal.

Actual termination depends upon a final determination by DHS Secretary
Napolitano that the Loran-C infrastructure is not required as a backup to
GPS. Until then, the Coast Guard will continue  moving towards
termination
while operating the system. If/when that determination is made, actual
termination will take place.
For a recent GPS World blog and readers' comments on this subject, see
Wide
Awake with No
Back-Up<
http://www.gpsworld.com/gnss-system/wide-awake/wide-awake-with-no-back-9168

.

Inevitable , but still a misguided shame.


time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.


time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.


time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.


time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.


time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.

  __________________________________________________________________

Ask a question on any topic and get answers from real people. Go to Yahoo! Answers and share what you know at http://ca.answers.yahoo.com

If any one is intersted this doccument provides some insight into the isssues involved in using Loran for "industrial timing" http://tf.nist.gov/general/pdf/2193.pdf As a side note in the past I have encountered "Legacy Loran" as a timing source in telecom carrier networks.   The last time I saw this was 7 or 8 years ago IIRC.   As a side note does any one know how prevalent Cesium Stratum one clocks are in the telcom world these days ?   ----- Original Message ---- From: Bob Camp <lists@cq.nu> To: Discussion of precise time and frequency measurement <time-nuts@febo.com> Sent: Sat, November 28, 2009 2:47:55 PM Subject: Re: [time-nuts] LORAN-C demise Hi Some of us have been trying to get the telcom OEM's to embrace a backup for GPS. There are a number of possible things they could do at various points in their networks. Different companies have pushed different approaches for many years. In all cases the response has been "the carriers don't want it". If you go to the carriers it's "the regulations don't require it".  I suspect if you go to the regulators they have their answer as well. The net result is that something like 99+% of the GPS based stuff out there has no real backup (other than holdover) built into it. Without a backup already built into the gear, keeping Loran up or not has very little impact. Without a regulatory change none of the alternatives are going to get built in. They don't all depend on Loran's unclear future. None of them will go in unless there's a requirement to do so ... That's true worldwide. It's not an issue with one country or another. It's not an issue with one system or the other. It's not an issue of a level of system or quality of carrier. It's not even an issue of military versus commercial. They just plain don't do it. Backup for timing simply isn't on anybody's list.  Sad but very true. Bob On Nov 28, 2009, at 4:04 PM, ken hartman wrote: > My impression is that significant stake-holders (e.g. Telecom service > providers, ILECs, AOPA, National Laboratories, FAA, NIST, DHS, CG, and > others) were unwilling  - at an institutional level - to embrace or own any > aspect of LORAN preservation and unable - at an individual level - to > influence "policy" decisions with *any* consideration for technical > viability or necessity. > Stated  differently  - this nations  NTP policy is totally driven  by > political considerations without regard to demonstrable critical > infrastructure technical evaluation. > Standard disclaimer: My opinions only > khartman > > > On Sat, Nov 28, 2009 at 2:36 PM, Chuck Harris <cfharris@erols.com> wrote: > >> Time and frequency measurement people were specifically >> exclude from the polls I have seen to determine whether >> or not Loran should continue.  They only wanted navigation >> users input... and I guess there weren't any. >> >> -Chuck >> >> >> J. Forster wrote: >> >>> There are on-line petition sites where people can sign on to support a >>> particular cause. Has anyone started such a petition to save LORAN? >>> >>> I've not seen one. >>> >>> Best, >>> -John >>> >>> ============== >>> >>> >>> >>> Given the confusing and seemingly ambiguous infomation on the .gov site, >>>> a >>>> clearer picture is given by this announcement: >>>> >>>> http://www.gpsworld.com/gnss-system/news/coast-guard-jettisons-loran-9178 >>>> >>>> excerpted below: >>>> >>>> Coast Guard Jettisons Loran >>>> November 25, 2009 >>>> ------------------------------ >>>> >>>> The U.S. Coast Guard Commandant has formally certified that termination >>>> of >>>> the Loran-C signal will not adversely impact maritime navigation, signing >>>> a >>>> document to that effect on November 20 and forwarding it to the Secretary >>>> of >>>> Homeland Security Janet Napolitano. The first of the two criteria for >>>> terminating the Loran-C signal has thus been met. >>>> >>>> Anticipated next steps include a Coast Guard ALCOAST Internet message >>>> release on this topic, the release of the Programmatic Environmental >>>> Impact >>>> Statement Record of Decision, and a Federal Register Notice, all measures >>>> en >>>> route to executing the termination of the Loran-C signal. >>>> >>>> Actual termination depends upon a final determination by DHS Secretary >>>> Napolitano that the Loran-C infrastructure is not required as a backup to >>>> GPS. Until then, the Coast Guard will continue  moving towards >>>> termination >>>> while operating the system. If/when that determination is made, actual >>>> termination will take place. >>>> For a recent *GPS World* blog and readers' comments on this subject, see >>>> Wide >>>> Awake with No >>>> Back-Up< >>>> http://www.gpsworld.com/gnss-system/wide-awake/wide-awake-with-no-back-9168 >>>>> >>>> . >>>> >>>> Inevitable , but still a misguided shame. >>>> _______________________________________________ >>>> time-nuts mailing list -- time-nuts@febo.com >>>> To unsubscribe, go to >>>> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts >>>> and follow the instructions there. >>>> >>>> >>>> >>> >>> >>> _______________________________________________ >>> time-nuts mailing list -- time-nuts@febo.com >>> To unsubscribe, go to >>> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts >>> and follow the instructions there. >>> >>> >> _______________________________________________ >> time-nuts mailing list -- time-nuts@febo.com >> To unsubscribe, go to >> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts >> and follow the instructions there. >> > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. > _______________________________________________ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there. __________________________________________________________________ Ask a question on any topic and get answers from real people. Go to Yahoo! Answers and share what you know at http://ca.answers.yahoo.com
SR
Stanley Reynolds
Sun, Nov 29, 2009 7:03 PM

How about the Volunteer Association of GPS Backup for Timing, VAGBT ?

Propose of the group is to provide backup distribution of timing information for GPS users, via armature radio and cesium clocks. To develop many local transmit stations as possible and low cost receivers with both extended holdover and comparison to GPS to measure backup accuracy. Many low power transmitters would be required as the cost of continuous operation would be lower for each station, and the identification of less accurate stations possible if several in each location was avabile.

Stanley

How about the Volunteer Association of GPS Backup for Timing, VAGBT ? Propose of the group is to provide backup distribution of timing information for GPS users, via armature radio and cesium clocks. To develop many local transmit stations as possible and low cost receivers with both extended holdover and comparison to GPS to measure backup accuracy. Many low power transmitters would be required as the cost of continuous operation would be lower for each station, and the identification of less accurate stations possible if several in each location was avabile. Stanley
MS
Mark Spencer
Sun, Nov 29, 2009 7:40 PM

Any thoughts on how complex a receiver would need to be to produce a 1 pps signal that was locked to the carrier frequency it was receiving ? Lot's of comercial transmitting equipment is designed to use an external frequency standard and if a transmitter at a high altitude site was locked to a cesium source it could serve a typical metroplitan area.  Locking an existing transmiiter to a cesium standard would not require any special signals or wave forms to be transmitted.  To be usefull the receiver would need to produce a standard 1 pps output.

Stanley Reynolds wrote:

How about the Volunteer Association of GPS Backup for Timing, VAGBT ?
Propose of the group is to provide backup distribution of timing information for GPS users, via armature radio and cesium clocks. To develop many local transmit stations as possible and low cost receivers with both extended holdover and comparison to GPS to measure backup accuracy. Many low power transmitters would be required as the cost of continuous operation would be lower for each station, and the identification of less accurate stations possible if several in each location was avabile.
Stanley


time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.

  __________________________________________________________________

Looking for the perfect gift? Give the gift of Flickr!

http://www.flickr.com/gift/

Any thoughts on how complex a receiver would need to be to produce a 1 pps signal that was locked to the carrier frequency it was receiving ? Lot&#39;s of comercial transmitting equipment is designed to use an external frequency standard and if a transmitter at a high altitude site was locked to a cesium source it could serve a typical metroplitan area. Locking an existing transmiiter to a cesium standard would not require any special signals or wave forms to be transmitted. To be usefull the receiver would need to produce a standard 1 pps output. Stanley Reynolds wrote: > How about the Volunteer Association of GPS Backup for Timing, VAGBT ? > Propose of the group is to provide backup distribution of timing information for GPS users, via armature radio and cesium clocks. To develop many local transmit stations as possible and low cost receivers with both extended holdover and comparison to GPS to measure backup accuracy. Many low power transmitters would be required as the cost of continuous operation would be lower for each station, and the identification of less accurate stations possible if several in each location was avabile. > Stanley > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. __________________________________________________________________ Looking for the perfect gift? Give the gift of Flickr! http://www.flickr.com/gift/
RD
Robert Darlington
Sun, Nov 29, 2009 8:02 PM

Hi guys,

Are there any manufacturers that currently produce LORAN receivers?  I
talked to a pilot friend who is very active in my area and he said he is
only aware of one person he knows that has a LORAN receiver in his aircraft
and the guy doesn't use it.  None of my other pilot buddies seem to know of
anybody even having a LORAN receiver in GA.  None of the planes I flew ever
had a LORAN receiver in them.  Between VOR beacons, GPS, street maps and a
compass, I don't see any need for a backup specifically in the scope of
general aviation.  If your visibility degrades to a point where you can't
see the ground, while simultaneously your standard cockpit instruments go
out, you have bigger problems than somebody jamming GPS.

My other buddy who runs a commercial fishing operation does rely on GPS to
an extent.  He basically said it would be an annoyance if it went out but
wouldn't be a show stopper.  He did say it would be pretty hard to find his
fishing spots without it though but navigating in coastal waters that he
knows would not be an issue.

From what I'm reading, Uncle Sam has no need for LORAN for navigation which

is why it's going away.  From talking to my Navy buddy who was one of their
keepers of the time, they don't use LORAN for timing applications as he was
one of the guys that went around synchronizing the Cesium beams.  Is it
really that big of a deal if this system goes away?  I just don't see any
significant reason to keep it around as a backup for a very small minority
of people out there that would wish to continue to use it, especially for
our hobby.

That being said, is there such a thing as an NTP Disciplined Oscillator?
Although, GPS is probably more reliable than my Internet connection!

Thanks,
Bob

On Sun, Nov 29, 2009 at 12:40 PM, Mark Spencer mspencer12345@yahoo.cawrote:

Any thoughts on how complex a receiver would need to be to produce a 1 pps
signal that was locked to the carrier frequency it was receiving ? Lot's
of comercial transmitting equipment is designed to use an external frequency
standard and if a transmitter at a high altitude site was locked to a cesium
source it could serve a typical metroplitan area.  Locking an existing
transmiiter to a cesium standard would not require any special signals or
wave forms to be transmitted.  To be usefull the receiver would need to
produce a standard 1 pps output.

Stanley Reynolds wrote:

How about the Volunteer Association of GPS Backup for Timing, VAGBT ?
Propose of the group is to provide backup distribution of timing

information for GPS users, via armature radio and cesium clocks. To develop
many local transmit stations as possible and low cost receivers with both
extended holdover and comparison to GPS to measure backup accuracy. Many low
power transmitters would be required as the cost of continuous operation
would be lower for each station, and the identification of less accurate
stations possible if several in each location was avabile.

Stanley


time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to

and follow the instructions there.

   __________________________________________________________________

Looking for the perfect gift? Give the gift of Flickr!

http://www.flickr.com/gift/


time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.

Hi guys, Are there any manufacturers that currently produce LORAN receivers? I talked to a pilot friend who is very active in my area and he said he is only aware of one person he knows that has a LORAN receiver in his aircraft and the guy doesn't use it. None of my other pilot buddies seem to know of anybody even having a LORAN receiver in GA. None of the planes I flew ever had a LORAN receiver in them. Between VOR beacons, GPS, street maps and a compass, I don't see any need for a backup specifically in the scope of general aviation. If your visibility degrades to a point where you can't see the ground, while simultaneously your standard cockpit instruments go out, you have bigger problems than somebody jamming GPS. My other buddy who runs a commercial fishing operation does rely on GPS to an extent. He basically said it would be an annoyance if it went out but wouldn't be a show stopper. He did say it would be pretty hard to find his fishing spots without it though but navigating in coastal waters that he knows would not be an issue. >From what I'm reading, Uncle Sam has no need for LORAN for navigation which is why it's going away. From talking to my Navy buddy who was one of their keepers of the time, they don't use LORAN for timing applications as he was one of the guys that went around synchronizing the Cesium beams. Is it really that big of a deal if this system goes away? I just don't see any significant reason to keep it around as a backup for a very small minority of people out there that would wish to continue to use it, especially for our hobby. That being said, is there such a thing as an NTP Disciplined Oscillator? Although, GPS is probably more reliable than my Internet connection! Thanks, Bob On Sun, Nov 29, 2009 at 12:40 PM, Mark Spencer <mspencer12345@yahoo.ca>wrote: > Any thoughts on how complex a receiver would need to be to produce a 1 pps > signal that was locked to the carrier frequency it was receiving ? Lot&#39;s > of comercial transmitting equipment is designed to use an external frequency > standard and if a transmitter at a high altitude site was locked to a cesium > source it could serve a typical metroplitan area. Locking an existing > transmiiter to a cesium standard would not require any special signals or > wave forms to be transmitted. To be usefull the receiver would need to > produce a standard 1 pps output. > > Stanley Reynolds wrote: > > How about the Volunteer Association of GPS Backup for Timing, VAGBT ? > > Propose of the group is to provide backup distribution of timing > information for GPS users, via armature radio and cesium clocks. To develop > many local transmit stations as possible and low cost receivers with both > extended holdover and comparison to GPS to measure backup accuracy. Many low > power transmitters would be required as the cost of continuous operation > would be lower for each station, and the identification of less accurate > stations possible if several in each location was avabile. > > Stanley > > _______________________________________________ > > time-nuts mailing list -- time-nuts@febo.com > > To unsubscribe, go to > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > > and follow the instructions there. > > > > __________________________________________________________________ > Looking for the perfect gift? Give the gift of Flickr! > > http://www.flickr.com/gift/ > > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. >
LJ
Lux, Jim (337C)
Sun, Nov 29, 2009 8:10 PM

On 11/29/09 11:40 AM, "Mark Spencer" mspencer12345@yahoo.ca wrote:

Any thoughts on how complex a receiver would need to be to produce a 1 pps
signal that was locked to the carrier frequency it was receiving ? Lot's
of comercial transmitting equipment is designed to use an external frequency
standard and if a transmitter at a high altitude site was locked to a cesium
source it could serve a typical metroplitan area.  Locking an existing
transmiiter to a cesium standard would not require any special signals or wave
forms to be transmitted.  To be usefull the receiver would need to produce a
standard 1 pps output.

Stanley Reynolds wrote:

How about the Volunteer Association of GPS Backup for Timing, VAGBT ?
Propose of the group is to provide backup distribution of timing information
for GPS users, via armature radio and cesium clocks. To develop many local
transmit stations as possible and low cost receivers with both extended
holdover and comparison to GPS to measure backup accuracy. Many low power
transmitters would be required as the cost of continuous operation would be
lower for each station, and the identification of less accurate stations
possible if several in each location was avabile.

And how is this is different from time stations like WWV or WWVB?  They're
driven by cesium clocks (or an ensemble of clocks).  The atmospheric
propagation uncertainty means that the received instantaneous frequency
might be off by 1E-7 or so (for HF WWV, at least), but I would imagine that
averaged over a long time, it's quite a bit better (one NIST doc says 1E-9),
but apparently it's tough to do straight averaging. The station clocks at
WWV is is good to something like 1E-13  (adev of 1E-13 at tau of 10,000
seconds, down to about 2E-13 at tau of 1E6 seconds)

WWVB at 60kHz is different.. It's from the same master clock, but the NIST
doc says that received phase is stable to 1E-8 at tau of 2 seconds, down to
1E-9 at a tau of 1000 seconds, with a WWVB disciplined oscillator getting
down to around 1E-12 for averaging over a day (which NIST says is about 1
order of mag worse than a GPS disciplined oscillator)

Of course http://tf.nist.gov/general/pdf/1969.pdf says they use common view
GPS to sync the WWV transmitter to the clocks in Boulder. It doesn't use GPS
for time, just as a source visible to both at the same time)  The same
document claims that 0.1 millisecond absolute time uncertainty should be
achievable with the received signals of WWV/WWVH and perhaps <1 microsecond
for WWVB.

One can propose, say, VHF or UHF signals radiated from a high location which
would potentially have better instantaneous frequency stability (because the
propagation is more stable), but at some point, you're still going to have
to deal with things like SNR and propagation.  Granted a lot of those issues
are "solved" in some sense (e.g. You could set up a GPS pseudolite, like
they do for approach/landing navigation experiments)

On 11/29/09 11:40 AM, "Mark Spencer" <mspencer12345@yahoo.ca> wrote: > Any thoughts on how complex a receiver would need to be to produce a 1 pps > signal that was locked to the carrier frequency it was receiving ? Lot&#39;s > of comercial transmitting equipment is designed to use an external frequency > standard and if a transmitter at a high altitude site was locked to a cesium > source it could serve a typical metroplitan area. Locking an existing > transmiiter to a cesium standard would not require any special signals or wave > forms to be transmitted. To be usefull the receiver would need to produce a > standard 1 pps output. > > Stanley Reynolds wrote: >> How about the Volunteer Association of GPS Backup for Timing, VAGBT ? >> Propose of the group is to provide backup distribution of timing information >> for GPS users, via armature radio and cesium clocks. To develop many local >> transmit stations as possible and low cost receivers with both extended >> holdover and comparison to GPS to measure backup accuracy. Many low power >> transmitters would be required as the cost of continuous operation would be >> lower for each station, and the identification of less accurate stations >> possible if several in each location was avabile. And how is this is different from time stations like WWV or WWVB? They're driven by cesium clocks (or an ensemble of clocks). The atmospheric propagation uncertainty means that the received instantaneous frequency might be off by 1E-7 or so (for HF WWV, at least), but I would imagine that averaged over a long time, it's quite a bit better (one NIST doc says 1E-9), but apparently it's tough to do straight averaging. The station clocks at WWV is is good to something like 1E-13 (adev of 1E-13 at tau of 10,000 seconds, down to about 2E-13 at tau of 1E6 seconds) WWVB at 60kHz is different.. It's from the same master clock, but the NIST doc says that received phase is stable to 1E-8 at tau of 2 seconds, down to 1E-9 at a tau of 1000 seconds, with a WWVB disciplined oscillator getting down to around 1E-12 for averaging over a day (which NIST says is about 1 order of mag worse than a GPS disciplined oscillator) Of course http://tf.nist.gov/general/pdf/1969.pdf says they use common view GPS to sync the WWV transmitter to the clocks in Boulder. It doesn't use GPS for time, just as a source visible to both at the same time) The same document claims that 0.1 millisecond absolute time uncertainty should be achievable with the received signals of WWV/WWVH and perhaps <1 microsecond for WWVB. One can propose, say, VHF or UHF signals radiated from a high location which would potentially have better instantaneous frequency stability (because the propagation is more stable), but at some point, you're still going to have to deal with things like SNR and propagation. Granted a lot of those issues are "solved" in some sense (e.g. You could set up a GPS pseudolite, like they do for approach/landing navigation experiments)
MS
Mark Spencer
Sun, Nov 29, 2009 8:25 PM

The main difference is that receiving lf signals is challenging in many areas built up areas and the doppler shift of hf via sky wave reduces the accuracy considerably, while there are already a large number of exisiting high power transmitters that can be locked to an external time base and have line of site paths to many locations in a typical metropolitan area.  If a sutiable receiver existed this might be a feasible means of distributing accurate frequency info and then with a suitable reciever you could generate a 1 pps signal.  That being said a dedicated uhf or shf transmiter that could send accurate 1 pps signals (as well as providing a very accurate carrier frequency) might be an easier solution.  In any event if there was a market for such a system I believe it would have emerged by now.
I imagine you could even design a gps timing receiver that could also receive terristerial signals as a backup, but again it does not seem there is a market for this (:

Lux, Jim (337C) wrote:

On 11/29/09 11:40 AM, "Mark Spencer" mspencer12345@yahoo.ca wrote:

Any thoughts on how complex a receiver would need to be to produce a 1 pps
signal that was locked to the carrier frequency it was receiving ? Lot's
of comercial transmitting equipment is designed to use an external frequency
standard and if a transmitter at a high altitude site was locked to a cesium
source it could serve a typical metroplitan area.  Locking an existing
transmiiter to a cesium standard would not require any special signals or wave
forms to be transmitted.  To be usefull the receiver would need to produce a
standard 1 pps output.

Stanley Reynolds wrote:

How about the Volunteer Association of GPS Backup for Timing, VAGBT ?
Propose of the group is to provide backup distribution of timing information
for GPS users, via armature radio and cesium clocks. To develop many local
transmit stations as possible and low cost receivers with both extended
holdover and comparison to GPS to measure backup accuracy. Many low power
transmitters would be required as the cost of continuous operation would be
lower for each station, and the identification of less accurate stations
possible if several in each location was avabile.

And how is this is different from time stations like WWV or WWVB?  They're
driven by cesium clocks (or an ensemble of clocks).  The atmospheric
propagation uncertainty means that the received instantaneous frequency
might be off by 1E-7 or so (for HF WWV, at least), but I would imagine that
averaged over a long time, it's quite a bit better (one NIST doc says 1E-9),
but apparently it's tough to do straight averaging. The station clocks at
WWV is is good to something like 1E-13  (adev of 1E-13 at tau of 10,000
seconds, down to about 2E-13 at tau of 1E6 seconds)
WWVB at 60kHz is different.. It's from the same master clock, but the NIST
doc says that received phase is stable to 1E-8 at tau of 2 seconds, down to
1E-9 at a tau of 1000 seconds, with a WWVB disciplined oscillator getting
down to around 1E-12 for averaging over a day (which NIST says is about 1
order of mag worse than a GPS disciplined oscillator)
Of course http://tf.nist.gov/general/pdf/1969.pdf says they use common view
GPS to sync the WWV transmitter to the clocks in Boulder. It doesn't use GPS
for time, just as a source visible to both at the same time)  The same
document claims that 0.1 millisecond absolute time uncertainty should be
achievable with the received signals of WWV/WWVH and perhaps <1 microsecond
for WWVB.
One can propose, say, VHF or UHF signals radiated from a high location which
would potentially have better instantaneous frequency stability (because the
propagation is more stable), but at some point, you're still going to have
to deal with things like SNR and propagation.  Granted a lot of those issues
are "solved" in some sense (e.g. You could set up a GPS pseudolite, like
they do for approach/landing navigation experiments)


time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.

  __________________________________________________________________

Looking for the perfect gift? Give the gift of Flickr!

http://www.flickr.com/gift/

The main difference is that receiving lf signals is challenging in many areas built up areas and the doppler shift of hf via sky wave reduces the accuracy considerably, while there are already a large number of exisiting high power transmitters that can be locked to an external time base and have line of site paths to many locations in a typical metropolitan area. If a sutiable receiver existed this might be a feasible means of distributing accurate frequency info and then with a suitable reciever you could generate a 1 pps signal. That being said a dedicated uhf or shf transmiter that could send accurate 1 pps signals (as well as providing a very accurate carrier frequency) might be an easier solution. In any event if there was a market for such a system I believe it would have emerged by now. I imagine you could even design a gps timing receiver that could also receive terristerial signals as a backup, but again it does not seem there is a market for this (: Lux, Jim (337C) wrote: > On 11/29/09 11:40 AM, "Mark Spencer" <mspencer12345@yahoo.ca> wrote: >> Any thoughts on how complex a receiver would need to be to produce a 1 pps >> signal that was locked to the carrier frequency it was receiving ? Lot&#39;s >> of comercial transmitting equipment is designed to use an external frequency >> standard and if a transmitter at a high altitude site was locked to a cesium >> source it could serve a typical metroplitan area. Locking an existing >> transmiiter to a cesium standard would not require any special signals or wave >> forms to be transmitted. To be usefull the receiver would need to produce a >> standard 1 pps output. >> >> Stanley Reynolds wrote: >>> How about the Volunteer Association of GPS Backup for Timing, VAGBT ? >>> Propose of the group is to provide backup distribution of timing information >>> for GPS users, via armature radio and cesium clocks. To develop many local >>> transmit stations as possible and low cost receivers with both extended >>> holdover and comparison to GPS to measure backup accuracy. Many low power >>> transmitters would be required as the cost of continuous operation would be >>> lower for each station, and the identification of less accurate stations >>> possible if several in each location was avabile. > And how is this is different from time stations like WWV or WWVB? They're > driven by cesium clocks (or an ensemble of clocks). The atmospheric > propagation uncertainty means that the received instantaneous frequency > might be off by 1E-7 or so (for HF WWV, at least), but I would imagine that > averaged over a long time, it's quite a bit better (one NIST doc says 1E-9), > but apparently it's tough to do straight averaging. The station clocks at > WWV is is good to something like 1E-13 (adev of 1E-13 at tau of 10,000 > seconds, down to about 2E-13 at tau of 1E6 seconds) > WWVB at 60kHz is different.. It's from the same master clock, but the NIST > doc says that received phase is stable to 1E-8 at tau of 2 seconds, down to > 1E-9 at a tau of 1000 seconds, with a WWVB disciplined oscillator getting > down to around 1E-12 for averaging over a day (which NIST says is about 1 > order of mag worse than a GPS disciplined oscillator) > Of course http://tf.nist.gov/general/pdf/1969.pdf says they use common view > GPS to sync the WWV transmitter to the clocks in Boulder. It doesn't use GPS > for time, just as a source visible to both at the same time) The same > document claims that 0.1 millisecond absolute time uncertainty should be > achievable with the received signals of WWV/WWVH and perhaps <1 microsecond > for WWVB. > One can propose, say, VHF or UHF signals radiated from a high location which > would potentially have better instantaneous frequency stability (because the > propagation is more stable), but at some point, you're still going to have > to deal with things like SNR and propagation. Granted a lot of those issues > are "solved" in some sense (e.g. You could set up a GPS pseudolite, like > they do for approach/landing navigation experiments) > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. __________________________________________________________________ Looking for the perfect gift? Give the gift of Flickr! http://www.flickr.com/gift/
DI
David I. Emery
Sun, Nov 29, 2009 9:52 PM

On Sun, Nov 29, 2009 at 12:25:06PM -0800, Mark Spencer wrote:

The main difference is that receiving lf signals is challenging in
many areas built up areas and the doppler shift of hf via sky wave
reduces the accuracy considerably, while there are already a large
number of exisiting high power transmitters that can be locked to an
external time base and have line of site paths to many locations in a
typical metropolitan area.  If a sutiable receiver existed this might
be a feasible means of distributing accurate frequency info and then
with a suitable reciever you could generate a 1 pps signal.  That being
said a dedicated uhf or shf transmiter that could send accurate 1 pps
signals (as well as providing a very accurate carrier frequency) might
be an easier solution.  In any event if there was a market for such a
system I believe it would have emerged by now.

As I suggested earlier, I believe that relatively simple tweaks

to a broadcast ATSC transmitter/modulator/mux chain to lock both carrier
frequency, symbol clock, and say PCR clock to a local cesium standard
with time of day based (initially)  on GPS would probably be quite
practical and perhaps even little more than using the 10 Mhz (or 27 MHz
derived from it) from the cesium as clock input for existing plant and
setting some firmware settings correctly.

OBVIOUSLY as others have pointed out someone has to pay for this

even though the actual costs might be very small compared to the other
operating and engineering costs associated with the broadcast
transmitter plant.  It is hard to think of a more powerful signal for
time sync in a metro area...

As for receivers, existing ATSC tuner/demod chip sets and a FPGA could

no doubt supply all the usual timing signals (10 MHz, 1 PPS, time of day
in some  standard format).  One imagines sub microsecond PPS accuracy
(once propagation skew is measured) is quite possible.

One would clearly need to use a GPS based measurement to establish

the propagation based skews...

I imagine you could even design a gps timing receiver that could also
receive terristerial signals as a backup, but again it does not seem
there is a market for this (:

Network effects apply here - if there is no signal to lock to,

then there is no market for a receiver - if there is no receiver even rather
low cost changes to TV plant aren't gonna happen or be justified...

And I suppose the bottom line is that we'd better hope that no

natural (or perish the thought deliberate man made) event takes out
enough of GPS to cause GPS based timing to fail.  And system designers
had better start thinking about very local jamming of GPS timing
receivers at targeted sites that might cause a vital system (say public
safety radio) to degrade or fail.

--
Dave Emery N1PRE/AE, die@dieconsulting.com  DIE Consulting, Weston, Mass 02493
"An empty zombie mind with a forlorn barely readable weatherbeaten
'For Rent' sign still vainly flapping outside on the weed encrusted pole - in
celebration of what could have been, but wasn't and is not to be now either."

On Sun, Nov 29, 2009 at 12:25:06PM -0800, Mark Spencer wrote: > The main difference is that receiving lf signals is challenging in > many areas built up areas and the doppler shift of hf via sky wave > reduces the accuracy considerably, while there are already a large > number of exisiting high power transmitters that can be locked to an > external time base and have line of site paths to many locations in a > typical metropolitan area. If a sutiable receiver existed this might > be a feasible means of distributing accurate frequency info and then > with a suitable reciever you could generate a 1 pps signal. That being > said a dedicated uhf or shf transmiter that could send accurate 1 pps > signals (as well as providing a very accurate carrier frequency) might > be an easier solution. In any event if there was a market for such a > system I believe it would have emerged by now. As I suggested earlier, I believe that relatively simple tweaks to a broadcast ATSC transmitter/modulator/mux chain to lock both carrier frequency, symbol clock, and say PCR clock to a local cesium standard with time of day based (initially) on GPS would probably be quite practical and perhaps even little more than using the 10 Mhz (or 27 MHz derived from it) from the cesium as clock input for existing plant and setting some firmware settings correctly. OBVIOUSLY as others have pointed out someone has to pay for this even though the actual costs might be very small compared to the other operating and engineering costs associated with the broadcast transmitter plant. It is hard to think of a more powerful signal for time sync in a metro area... As for receivers, existing ATSC tuner/demod chip sets and a FPGA could no doubt supply all the usual timing signals (10 MHz, 1 PPS, time of day in some standard format). One imagines sub microsecond PPS accuracy (once propagation skew is measured) is quite possible. One would clearly need to use a GPS based measurement to establish the propagation based skews... > I imagine you could even design a gps timing receiver that could also > receive terristerial signals as a backup, but again it does not seem > there is a market for this (: Network effects apply here - if there is no signal to lock to, then there is no market for a receiver - if there is no receiver even rather low cost changes to TV plant aren't gonna happen or be justified... And I suppose the bottom line is that we'd better hope that no natural (or perish the thought deliberate man made) event takes out enough of GPS to cause GPS based timing to fail. And system designers had better start thinking about very local jamming of GPS timing receivers at targeted sites that might cause a vital system (say public safety radio) to degrade or fail. -- Dave Emery N1PRE/AE, die@dieconsulting.com DIE Consulting, Weston, Mass 02493 "An empty zombie mind with a forlorn barely readable weatherbeaten 'For Rent' sign still vainly flapping outside on the weed encrusted pole - in celebration of what could have been, but wasn't and is not to be now either."
B
bg@lysator.liu.se
Sun, Nov 29, 2009 10:19 PM

Hi,

Well, most of this discussion is about GPS backup. The GLONASS system has
received global coverage (again) for navigation. Timing is less demanding
if we consider the static and known position case. In some years we will
have Galileo (Euro) and Compass (China). Perhaps also regional Japanese
and Indian (global?) systems. These are systemwise independant of GPS.
Looking at spectral redundancy - we have L2C available on some GPS SVs, L5
will come. The other coming systems are also multi carrier frequency. One
could argue that a jammer on the whole of the 1GHz to 2GHz will take all
services. But such a wide band jammer is very much less efficient than a
narrowband L1 carrier version.

How about using SBAS (WAAS, EGNOS, MSAS) for single satellite timing use?
That should be possible? The SBAS do provide a ranging signal if running
in the right mode, and that should be usable for a timing receiver. Having
a GEO signal, there should be no problem in using a high gain (parabol)
pointing directly to the GEO. This will steal many dB from the jammer
power budget.

Perhaps the way to redundancy is getting GNSS receivers using multiple
carrier frequencies and multiple constellations. Even though it is sad
Loran-C seems to go away soon.

--

Björn

On Sun, Nov 29, 2009 at 12:25:06PM -0800, Mark Spencer wrote:

The main difference is that receiving lf signals is challenging in
many areas built up areas and the doppler shift of hf via sky wave
reduces the accuracy considerably, while there are already a large
number of exisiting high power transmitters that can be locked to an
external time base and have line of site paths to many locations in a
typical metropolitan area.  If a sutiable receiver existed this might
be a feasible means of distributing accurate frequency info and then
with a suitable reciever you could generate a 1 pps signal.  That being
said a dedicated uhf or shf transmiter that could send accurate 1 pps
signals (as well as providing a very accurate carrier frequency) might
be an easier solution.  In any event if there was a market for such a
system I believe it would have emerged by now.

As I suggested earlier, I believe that relatively simple tweaks

to a broadcast ATSC transmitter/modulator/mux chain to lock both carrier
frequency, symbol clock, and say PCR clock to a local cesium standard
with time of day based (initially)  on GPS would probably be quite
practical and perhaps even little more than using the 10 Mhz (or 27 MHz
derived from it) from the cesium as clock input for existing plant and
setting some firmware settings correctly.

OBVIOUSLY as others have pointed out someone has to pay for this

even though the actual costs might be very small compared to the other
operating and engineering costs associated with the broadcast
transmitter plant.  It is hard to think of a more powerful signal for
time sync in a metro area...

As for receivers, existing ATSC tuner/demod chip sets and a FPGA could

no doubt supply all the usual timing signals (10 MHz, 1 PPS, time of day
in some  standard format).  One imagines sub microsecond PPS accuracy
(once propagation skew is measured) is quite possible.

One would clearly need to use a GPS based measurement to establish

the propagation based skews...

I imagine you could even design a gps timing receiver that could also
receive terristerial signals as a backup, but again it does not seem
there is a market for this (:

Network effects apply here - if there is no signal to lock to,

then there is no market for a receiver - if there is no receiver even
rather
low cost changes to TV plant aren't gonna happen or be justified...

And I suppose the bottom line is that we'd better hope that no

natural (or perish the thought deliberate man made) event takes out
enough of GPS to cause GPS based timing to fail.  And system designers
had better start thinking about very local jamming of GPS timing
receivers at targeted sites that might cause a vital system (say public
safety radio) to degrade or fail.

--
Dave Emery N1PRE/AE, die@dieconsulting.com  DIE Consulting, Weston, Mass
02493
"An empty zombie mind with a forlorn barely readable weatherbeaten
'For Rent' sign still vainly flapping outside on the weed encrusted pole -
in
celebration of what could have been, but wasn't and is not to be now
either."


time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to
https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.

Hi, Well, most of this discussion is about GPS backup. The GLONASS system has received global coverage (again) for navigation. Timing is less demanding if we consider the static and known position case. In some years we will have Galileo (Euro) and Compass (China). Perhaps also regional Japanese and Indian (global?) systems. These are systemwise independant of GPS. Looking at spectral redundancy - we have L2C available on some GPS SVs, L5 will come. The other coming systems are also multi carrier frequency. One could argue that a jammer on the whole of the 1GHz to 2GHz will take all services. But such a wide band jammer is very much less efficient than a narrowband L1 carrier version. How about using SBAS (WAAS, EGNOS, MSAS) for single satellite timing use? That should be possible? The SBAS do provide a ranging signal if running in the right mode, and that should be usable for a timing receiver. Having a GEO signal, there should be no problem in using a high gain (parabol) pointing directly to the GEO. This will steal many dB from the jammer power budget. Perhaps the way to redundancy is getting GNSS receivers using multiple carrier frequencies and multiple constellations. Even though it is sad Loran-C seems to go away soon. -- Björn > On Sun, Nov 29, 2009 at 12:25:06PM -0800, Mark Spencer wrote: > >> The main difference is that receiving lf signals is challenging in >> many areas built up areas and the doppler shift of hf via sky wave >> reduces the accuracy considerably, while there are already a large >> number of exisiting high power transmitters that can be locked to an >> external time base and have line of site paths to many locations in a >> typical metropolitan area. If a sutiable receiver existed this might >> be a feasible means of distributing accurate frequency info and then >> with a suitable reciever you could generate a 1 pps signal. That being >> said a dedicated uhf or shf transmiter that could send accurate 1 pps >> signals (as well as providing a very accurate carrier frequency) might >> be an easier solution. In any event if there was a market for such a >> system I believe it would have emerged by now. > > As I suggested earlier, I believe that relatively simple tweaks > to a broadcast ATSC transmitter/modulator/mux chain to lock both carrier > frequency, symbol clock, and say PCR clock to a local cesium standard > with time of day based (initially) on GPS would probably be quite > practical and perhaps even little more than using the 10 Mhz (or 27 MHz > derived from it) from the cesium as clock input for existing plant and > setting some firmware settings correctly. > > OBVIOUSLY as others have pointed out someone has to pay for this > even though the actual costs might be very small compared to the other > operating and engineering costs associated with the broadcast > transmitter plant. It is hard to think of a more powerful signal for > time sync in a metro area... > > As for receivers, existing ATSC tuner/demod chip sets and a FPGA could > no doubt supply all the usual timing signals (10 MHz, 1 PPS, time of day > in some standard format). One imagines sub microsecond PPS accuracy > (once propagation skew is measured) is quite possible. > > One would clearly need to use a GPS based measurement to establish > the propagation based skews... > >> I imagine you could even design a gps timing receiver that could also >> receive terristerial signals as a backup, but again it does not seem >> there is a market for this (: > > Network effects apply here - if there is no signal to lock to, > then there is no market for a receiver - if there is no receiver even > rather > low cost changes to TV plant aren't gonna happen or be justified... > > And I suppose the bottom line is that we'd better hope that no > natural (or perish the thought deliberate man made) event takes out > enough of GPS to cause GPS based timing to fail. And system designers > had better start thinking about very local jamming of GPS timing > receivers at targeted sites that might cause a vital system (say public > safety radio) to degrade or fail. > > -- > Dave Emery N1PRE/AE, die@dieconsulting.com DIE Consulting, Weston, Mass > 02493 > "An empty zombie mind with a forlorn barely readable weatherbeaten > 'For Rent' sign still vainly flapping outside on the weed encrusted pole - > in > celebration of what could have been, but wasn't and is not to be now > either." > > > _______________________________________________ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to > https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. >
MD
Magnus Danielson
Sun, Nov 29, 2009 10:51 PM

David I. Emery wrote:

On Sun, Nov 29, 2009 at 12:25:06PM -0800, Mark Spencer wrote:

The main difference is that receiving lf signals is challenging in
many areas built up areas and the doppler shift of hf via sky wave
reduces the accuracy considerably, while there are already a large
number of exisiting high power transmitters that can be locked to an
external time base and have line of site paths to many locations in a
typical metropolitan area.  If a sutiable receiver existed this might
be a feasible means of distributing accurate frequency info and then
with a suitable reciever you could generate a 1 pps signal.  That being
said a dedicated uhf or shf transmiter that could send accurate 1 pps
signals (as well as providing a very accurate carrier frequency) might
be an easier solution.  In any event if there was a market for such a
system I believe it would have emerged by now.

As I suggested earlier, I believe that relatively simple tweaks

to a broadcast ATSC transmitter/modulator/mux chain to lock both carrier
frequency, symbol clock, and say PCR clock to a local cesium standard
with time of day based (initially)  on GPS would probably be quite
practical and perhaps even little more than using the 10 Mhz (or 27 MHz
derived from it) from the cesium as clock input for existing plant and
setting some firmware settings correctly.

There's a standard for ATSC SFN configuration.

OBVIOUSLY as others have pointed out someone has to pay for this

even though the actual costs might be very small compared to the other
operating and engineering costs associated with the broadcast
transmitter plant.  It is hard to think of a more powerful signal for
time sync in a metro area...

Unless SFN operation is applied, it is fairly unreasnoble to expect that
it would happend.

As for receivers, existing ATSC tuner/demod chip sets and a FPGA could

no doubt supply all the usual timing signals (10 MHz, 1 PPS, time of day
in some  standard format).  One imagines sub microsecond PPS accuracy
(once propagation skew is measured) is quite possible.

The propagation delay from the transmitter tower and any delay-offsets
of the tower would add up.

One would clearly need to use a GPS based measurement to establish

the propagation based skews...

Certainly.

I imagine you could even design a gps timing receiver that could also
receive terristerial signals as a backup, but again it does not seem
there is a market for this (:

Network effects apply here - if there is no signal to lock to,

then there is no market for a receiver - if there is no receiver even rather
low cost changes to TV plant aren't gonna happen or be justified...

Only within SFN regions the receivers would be usefull.

And I suppose the bottom line is that we'd better hope that no

natural (or perish the thought deliberate man made) event takes out
enough of GPS to cause GPS based timing to fail.  And system designers
had better start thinking about very local jamming of GPS timing
receivers at targeted sites that might cause a vital system (say public
safety radio) to degrade or fail.

There are several man-made things which may cause loss of signal,
including firmware errors, bad antenna connections, water in antenna
(actually happend to me) etc. etc. There are many reasons for the full
function to fluke out.

Cheers,
Magnus

David I. Emery wrote: > On Sun, Nov 29, 2009 at 12:25:06PM -0800, Mark Spencer wrote: > >> The main difference is that receiving lf signals is challenging in >> many areas built up areas and the doppler shift of hf via sky wave >> reduces the accuracy considerably, while there are already a large >> number of exisiting high power transmitters that can be locked to an >> external time base and have line of site paths to many locations in a >> typical metropolitan area. If a sutiable receiver existed this might >> be a feasible means of distributing accurate frequency info and then >> with a suitable reciever you could generate a 1 pps signal. That being >> said a dedicated uhf or shf transmiter that could send accurate 1 pps >> signals (as well as providing a very accurate carrier frequency) might >> be an easier solution. In any event if there was a market for such a >> system I believe it would have emerged by now. > > As I suggested earlier, I believe that relatively simple tweaks > to a broadcast ATSC transmitter/modulator/mux chain to lock both carrier > frequency, symbol clock, and say PCR clock to a local cesium standard > with time of day based (initially) on GPS would probably be quite > practical and perhaps even little more than using the 10 Mhz (or 27 MHz > derived from it) from the cesium as clock input for existing plant and > setting some firmware settings correctly. There's a standard for ATSC SFN configuration. > OBVIOUSLY as others have pointed out someone has to pay for this > even though the actual costs might be very small compared to the other > operating and engineering costs associated with the broadcast > transmitter plant. It is hard to think of a more powerful signal for > time sync in a metro area... Unless SFN operation is applied, it is fairly unreasnoble to expect that it would happend. > As for receivers, existing ATSC tuner/demod chip sets and a FPGA could > no doubt supply all the usual timing signals (10 MHz, 1 PPS, time of day > in some standard format). One imagines sub microsecond PPS accuracy > (once propagation skew is measured) is quite possible. The propagation delay from the transmitter tower and any delay-offsets of the tower would add up. > One would clearly need to use a GPS based measurement to establish > the propagation based skews... Certainly. >> I imagine you could even design a gps timing receiver that could also >> receive terristerial signals as a backup, but again it does not seem >> there is a market for this (: > > Network effects apply here - if there is no signal to lock to, > then there is no market for a receiver - if there is no receiver even rather > low cost changes to TV plant aren't gonna happen or be justified... Only within SFN regions the receivers would be usefull. > And I suppose the bottom line is that we'd better hope that no > natural (or perish the thought deliberate man made) event takes out > enough of GPS to cause GPS based timing to fail. And system designers > had better start thinking about very local jamming of GPS timing > receivers at targeted sites that might cause a vital system (say public > safety radio) to degrade or fail. > There are several man-made things which may cause loss of signal, including firmware errors, bad antenna connections, water in antenna (actually happend to me) etc. etc. There are many reasons for the full function to fluke out. Cheers, Magnus
MD
Magnus Danielson
Sun, Nov 29, 2009 11:14 PM

Hi,

Well, most of this discussion is about GPS backup. The GLONASS system has
received global coverage (again) for navigation. Timing is less demanding
if we consider the static and known position case. In some years we will
have Galileo (Euro) and Compass (China). Perhaps also regional Japanese
and Indian (global?) systems. These are systemwise independant of GPS.
Looking at spectral redundancy - we have L2C available on some GPS SVs, L5
will come. The other coming systems are also multi carrier frequency. One
could argue that a jammer on the whole of the 1GHz to 2GHz will take all
services. But such a wide band jammer is very much less efficient than a
narrowband L1 carrier version.

L1, L2, L3, L4 and L5 jammers is off the shelf. Not particular
efficient, not to speak of L3 and L4 being of no significant use.

Spectral diversity of the signal, system diversity and coding diversity
helps for some of the failure modes, but you have common aspects such as
receivers, antennas and distance to the sats.

How about using SBAS (WAAS, EGNOS, MSAS) for single satellite timing use?
That should be possible? The SBAS do provide a ranging signal if running
in the right mode, and that should be usable for a timing receiver. Having
a GEO signal, there should be no problem in using a high gain (parabol)
pointing directly to the GEO. This will steal many dB from the jammer
power budget.

The GEO orbit is given and the time of the systems is fairly well kept,
at least so that it would suit many, but not all, needs. Parabol or
hexical antennas could be used. Linear array is another possibility,
althought a simplified approach could be used since it could be oriented
towards the target just as a parabol. For fixed locations elaborate
antennas is possible regardless.

Perhaps the way to redundancy is getting GNSS receivers using multiple
carrier frequencies and multiple constellations. Even though it is sad
Loran-C seems to go away soon.

I still wait for L2C receivers to become commonplace enought.

Cheers,
Magnus

bg@lysator.liu.se wrote: > Hi, > > Well, most of this discussion is about GPS backup. The GLONASS system has > received global coverage (again) for navigation. Timing is less demanding > if we consider the static and known position case. In some years we will > have Galileo (Euro) and Compass (China). Perhaps also regional Japanese > and Indian (global?) systems. These are systemwise independant of GPS. > Looking at spectral redundancy - we have L2C available on some GPS SVs, L5 > will come. The other coming systems are also multi carrier frequency. One > could argue that a jammer on the whole of the 1GHz to 2GHz will take all > services. But such a wide band jammer is very much less efficient than a > narrowband L1 carrier version. L1, L2, L3, L4 and L5 jammers is off the shelf. Not particular efficient, not to speak of L3 and L4 being of no significant use. Spectral diversity of the signal, system diversity and coding diversity helps for some of the failure modes, but you have common aspects such as receivers, antennas and distance to the sats. > How about using SBAS (WAAS, EGNOS, MSAS) for single satellite timing use? > That should be possible? The SBAS do provide a ranging signal if running > in the right mode, and that should be usable for a timing receiver. Having > a GEO signal, there should be no problem in using a high gain (parabol) > pointing directly to the GEO. This will steal many dB from the jammer > power budget. The GEO orbit is given and the time of the systems is fairly well kept, at least so that it would suit many, but not all, needs. Parabol or hexical antennas could be used. Linear array is another possibility, althought a simplified approach could be used since it could be oriented towards the target just as a parabol. For fixed locations elaborate antennas is possible regardless. > Perhaps the way to redundancy is getting GNSS receivers using multiple > carrier frequencies and multiple constellations. Even though it is sad > Loran-C seems to go away soon. I still wait for L2C receivers to become commonplace enought. Cheers, Magnus
PK
Poul-Henning Kamp
Sun, Nov 29, 2009 11:35 PM

In message 4B130050.1050002@rubidium.dyndns.org, Magnus Danielson writes:

L1, L2, L3, L4 and L5 jammers is off the shelf. Not particular
efficient, not to speak of L3 and L4 being of no significant use.

Not to mention the fact that there is a good probability that
GPS and Galileo will jam each other, degrading both signals more
than the benefit of having twice as many birds will be able to
compensate for...

--
Poul-Henning Kamp      | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG        | TCP/IP since RFC 956
FreeBSD committer      | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.

In message <4B130050.1050002@rubidium.dyndns.org>, Magnus Danielson writes: >bg@lysator.liu.se wrote: >L1, L2, L3, L4 and L5 jammers is off the shelf. Not particular >efficient, not to speak of L3 and L4 being of no significant use. Not to mention the fact that there is a good probability that GPS and Galileo will jam each other, degrading both signals more than the benefit of having twice as many birds will be able to compensate for... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
MD
Magnus Danielson
Mon, Nov 30, 2009 12:13 AM

Poul-Henning Kamp wrote:

In message 4B130050.1050002@rubidium.dyndns.org, Magnus Danielson writes:

L1, L2, L3, L4 and L5 jammers is off the shelf. Not particular
efficient, not to speak of L3 and L4 being of no significant use.

Not to mention the fact that there is a good probability that
GPS and Galileo will jam each other, degrading both signals more
than the benefit of having twice as many birds will be able to
compensate for...

That particular aspect have been in deep investigation, and so has the
M-codes. Their similarity in strength and code separation make the
effect less than the gain you get. The BOC code aids to insert signal in
the null of the L1 code which causes additional spectral/code division.

Cheers,
Magnus

Poul-Henning Kamp wrote: > In message <4B130050.1050002@rubidium.dyndns.org>, Magnus Danielson writes: >> bg@lysator.liu.se wrote: > >> L1, L2, L3, L4 and L5 jammers is off the shelf. Not particular >> efficient, not to speak of L3 and L4 being of no significant use. > > Not to mention the fact that there is a good probability that > GPS and Galileo will jam each other, degrading both signals more > than the benefit of having twice as many birds will be able to > compensate for... > That particular aspect have been in deep investigation, and so has the M-codes. Their similarity in strength and code separation make the effect less than the gain you get. The BOC code aids to insert signal in the null of the L1 code which causes additional spectral/code division. Cheers, Magnus
B
bg@lysator.liu.se
Mon, Nov 30, 2009 12:16 AM

In message 4B130050.1050002@rubidium.dyndns.org, Magnus Danielson
writes:

L1, L2, L3, L4 and L5 jammers is off the shelf. Not particular
efficient, not to speak of L3 and L4 being of no significant use.

Not to mention the fact that there is a good probability that
GPS and Galileo will jam each other, degrading both signals more
than the benefit of having twice as many birds will be able to
compensate for...

There has been rather elaborate studies conducted on Galileo signals
disturbing GPS and vice versa. The chosen/negotiated signals give minimal
interference to others.

There has been bilateral agreements reached between all (?) future global
GNSS-systems. I think unintentional jamming between the systems are
unlikely.

An unintentional mishap like the recent GPS-L5 debacle is ofcause a
possibility.

--

Björn

> In message <4B130050.1050002@rubidium.dyndns.org>, Magnus Danielson > writes: >>bg@lysator.liu.se wrote: > >>L1, L2, L3, L4 and L5 jammers is off the shelf. Not particular >>efficient, not to speak of L3 and L4 being of no significant use. > > Not to mention the fact that there is a good probability that > GPS and Galileo will jam each other, degrading both signals more > than the benefit of having twice as many birds will be able to > compensate for... > There has been rather elaborate studies conducted on Galileo signals disturbing GPS and vice versa. The chosen/negotiated signals give minimal interference to others. There has been bilateral agreements reached between all (?) future global GNSS-systems. I think unintentional jamming between the systems are unlikely. An unintentional mishap like the recent GPS-L5 debacle is ofcause a possibility. -- Björn
MD
Magnus Danielson
Mon, Nov 30, 2009 12:27 AM

In message 4B130050.1050002@rubidium.dyndns.org, Magnus Danielson
writes:

bg@lysator.liu.se wrote:
L1, L2, L3, L4 and L5 jammers is off the shelf. Not particular
efficient, not to speak of L3 and L4 being of no significant use.

Not to mention the fact that there is a good probability that
GPS and Galileo will jam each other, degrading both signals more
than the benefit of having twice as many birds will be able to
compensate for...

There has been rather elaborate studies conducted on Galileo signals
disturbing GPS and vice versa. The chosen/negotiated signals give minimal
interference to others.

The BOC signal approach has been agreed upon.

There has been bilateral agreements reached between all (?) future global
GNSS-systems. I think unintentional jamming between the systems are
unlikely.

Besides, considering similar signal strength, the VCA would not be
significantly affected if at all while the coding gain would reduce the
other signals. Also consider that dopplers isn't make perfect matches
and that BOC signals and C/A does not correlate while BOC signals can
have better coding gain.

An unintentional mishap like the recent GPS-L5 debacle is ofcause a
possibility.

I think they learned the hard way from that bird. Then again, it does
one of its intended missions, preserve the L5 allocation with ITU, so
that part of the mission is good. Javad says they can overcome the bias
error.

Cheers,
Magnus

bg@lysator.liu.se wrote: >> In message <4B130050.1050002@rubidium.dyndns.org>, Magnus Danielson >> writes: >>> bg@lysator.liu.se wrote: >>> L1, L2, L3, L4 and L5 jammers is off the shelf. Not particular >>> efficient, not to speak of L3 and L4 being of no significant use. >> Not to mention the fact that there is a good probability that >> GPS and Galileo will jam each other, degrading both signals more >> than the benefit of having twice as many birds will be able to >> compensate for... >> > > There has been rather elaborate studies conducted on Galileo signals > disturbing GPS and vice versa. The chosen/negotiated signals give minimal > interference to others. The BOC signal approach has been agreed upon. > There has been bilateral agreements reached between all (?) future global > GNSS-systems. I think unintentional jamming between the systems are > unlikely. Besides, considering similar signal strength, the VCA would not be significantly affected if at all while the coding gain would reduce the other signals. Also consider that dopplers isn't make perfect matches and that BOC signals and C/A does not correlate while BOC signals can have better coding gain. > An unintentional mishap like the recent GPS-L5 debacle is ofcause a > possibility. I think they learned the hard way from that bird. Then again, it does one of its intended missions, preserve the L5 allocation with ITU, so that part of the mission is good. Javad says they can overcome the bias error. Cheers, Magnus