[time-nuts] time-nuts Digest, Vol 118, Issue 35 Message: 3

Alexander Pummer alexpcs at ieee.org
Sat May 17 23:40:00 EDT 2014


Ulrich Rohde has a low noise oscillator circuit perhaps it is patented, 
here is:http://f6csx.free.fr/techni/PLL/Oscillators.pdf
73
Alex

  On 5/17/2014 9:53 AM, Walter Hofstädtler wrote:
> Hi,
>
>> Traced the problem of my FTS 1200 to the first BC109 Transistor on the
>> A2/A3 AGS/Amplifier board. Since it is right after the Oscillator transistor low  noise is critical. This unit is at least 30 years old and my question is, what  transistor will have
>> even lower noise than the than low noise BC 109.
>> Voltage is  6.43 V.
> A BC 549  is a replacement
>
> Walter
>
> -----Ursprüngliche Nachricht-----
> Von: time-nuts-bounces at febo.com [mailto:time-nuts-bounces at febo.com] Im Auftrag von time-nuts-request at febo.com
> Gesendet: Samstag, 17. Mai 2014 18:00
> An: time-nuts at febo.com
> Betreff: time-nuts Digest, Vol 118, Issue 35
>
> Send time-nuts mailing list submissions to
> 	time-nuts at febo.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> or, via email, send a message with subject or body 'help' to
> 	time-nuts-request at febo.com
>
> You can reach the person managing the list at
> 	time-nuts-owner at febo.com
>
> When replying, please edit your Subject line so it is more specific than "Re: Contents of time-nuts digest..."
>
>
> Today's Topics:
>
>     1. Re: Fwd: CGSIC: Known Problem With Certain GPS Devices
>        (Magnus Danielson)
>     2. Re: Fwd: CGSIC: Known Problem With Certain GPS Devices
>        (Brooke Clarke)
>     3. FTS 1200 transistor replacement (EWKehren at aol.com)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 17 May 2014 01:01:50 +0200
> From: Magnus Danielson <magnus at rubidium.dyndns.org>
> To: time-nuts at febo.com
> Subject: Re: [time-nuts] Fwd: CGSIC: Known Problem With Certain GPS
> 	Devices
> Message-ID: <537698DE.2050707 at rubidium.dyndns.org>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> They can't point official fingers. That's why.
>
> Ask you vendor if they need firmware upgrades to comply in this aspect.
>
> Cheers,
> Magnus
>
> On 05/16/2014 12:39 AM, SAIDJACK at aol.com wrote:
>> It would be good to understand which receivers are adversely  affected
>> by this.. the USCG did not list affected vendors/devices..
>>
>>
>> In a message dated 5/15/2014 15:19:51 Pacific Daylight Time,
>> magnus at rubidium.dyndns.org writes:
>>
>> Hi  fellow time-nuts,
>>
>> I think this message is interesting. It shows that  some receiver
>> vendors have been cheating on an important detail, ignoring  the
>> health status and being confused as a  result.
>>
>> Cheers,
>> Magnus
>>
>>
>> -------- Original Message  --------
>> Subject: CGSIC: Known Problem With Certain GPS Devices
>> Date:  Thu, 15 May 2014 21:20:23 +0000
>> From: Civil Global Positioning System  Service Interface Committee
>> (CGSIC)  <cgsic at cgls.uscg.mil>
>> Reply-To: cgsic at cgls.uscg.mil
>> To:  cgsic at cgls.uscg.mil <cgsic at cgls.uscg.mil>
>>
>> All CGSIC:
>>
>> May  15, 2014
>>
>> Recently, many GPS users have reported intermittent GPS  outages in
>> their devices.  After investigating, the U.S. government  has linked
>> the problem to flawed processing of GPS satellite data within  certain
>> GPS receiver chipsets.  The GPS satellite service continues  to
>> function as designed and is fully operational and available  worldwide.
>>
>> The problem affects only user equipment that erroneously  ignores the
>> satellite health status information broadcast from every GPS  satellite.
>> The problem is not related to the April 28, 2014,  activation of civil
>> navigation messages on the GPS L2C and L5  signals.
>>
>> Since March 15, 2014, the Air Force has been conducting  functional
>> checkout on a GPS satellite, designated Space Vehicle Number  (SVN) 64.
>> SVN 64 broadcasts a data message that clearly indicates SVN 64  is
>> unusable for navigation.  Nevertheless, the U.S. government has
>> confirmed that certain GPS receivers are using data from SVN 64, in
>> violation of GPS interface specifications, resulting in outages or
>> corrupted, inaccurate position calculations.
>>
>> The Air Force testing  is scheduled to end in mid-May 2014 at which
>> time SVN 64 will begin normal  operation.  At that point, these problems may
>> stop  occurring.   Meanwhile, the U.S. government urges all GPS device
>> makers to review their products for compliance with the GPS interface
>> specifications, and if necessary, to issue software/firmware updates
>> to users as soon as possible. View specifications
>> http://www.gps.gov/technical/icwg/
>>
>> Users experiencing GPS outages  should check with their device
>> manufacturers for available  software/firmware updates.  In addition,
>> any civil user seeing  unusual behavior in GPS user equipment should
>> report it to the U.S. Coast  Guard Navigation Center (NAVCEN).
>> Aviation users should file reports  consistent with FAA-approved
>> procedures.  Military users seeing  unusual behavior should report it
>> the GPS Operations Center (GPSOC).
>>
>> Please direct any civil user questions to NAVCEN at (703)  313-5900,
>> http://www.navcen.uscg.gov Please direct any military user  questions
>> to the GPSOC at (719) 567-2541, DSN: 560-2541,
>> gpsoperationscenter at us.af.mil https://gps.afspc.af.mil Military
>> alternate: Joint Space Operations Center, (805) 606-3514, DSN:
>> 276-3514,  jspoccombatops at vandenberg.af.mil
>> ----
>> See also:
>> Technical explanation  for device makers (PDF)
>> http://www.navcen.uscg.gov/pdf/gps/GPSOC_PRN  30_Notice.pdf
>>
>> V/R
>> Rick Hamilton
>> CGSIC Executive  Secretariat
>> GPS Information Analysis Team Lead
>> USCG Navigation  Center
>> 703-313-5930
>>
>>
>> _______________________________________________
>> CGSIC  one-way mailing list
>> Unsubscribe:  http://cgls.uscg.mil/mailman/listinfo/cgsic
>>
>> If you would like to report  abuse of the CGLS listserv please send an
>> email to:  CGLSAdmin at uscg.mil
>>
>>
>> _______________________________________________
>> time-nuts  mailing list -- time-nuts at 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 at febo.com To unsubscribe, go to
>> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
>> and follow the instructions there.
>>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 16 May 2014 17:23:19 -0700
> From: Brooke Clarke <brooke at pacific.net>
> To: Discussion of precise time and frequency measurement
> 	<time-nuts at febo.com>
> Subject: Re: [time-nuts] Fwd: CGSIC: Known Problem With Certain GPS
> 	Devices
> Message-ID: <5376ABF7.50601 at pacific.net>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi:
>
> I recently got a CSI LGBX Pro DGPS Receiver and it used to display a list of the satellites it was tracking, but not that function is no longer working.
> But all the other functions seem to work.  CSI made their own LF beacon receivers but in this model they use an Ashtech G-12L for GPS and a Fugro 3000 Receiver for the OmniSTAR correction subscription service which costs $800/year.  I've asked Trimble (who are doing the tech support for Ashtech) if there's a firmware upgrade.
>
> http://www.prc68.com/I/LGBXcsiDGPS.html
>
> Have Fun,
>
> Brooke Clarke
> http://www.PRC68.com
> http://www.end2partygovernment.com/2012Issues.html
>
> Magnus Danielson wrote:
>> They can't point official fingers. That's why.
>>
>> Ask you vendor if they need firmware upgrades to comply in this aspect.
>>
>> Cheers,
>> Magnus
>>
>> On 05/16/2014 12:39 AM, SAIDJACK at aol.com wrote:
>>> It would be good to understand which receivers are adversely
>>> affected by this.. the USCG did not list affected vendors/devices..
>>>
>>>
>>> In a message dated 5/15/2014 15:19:51 Pacific Daylight Time,
>>> magnus at rubidium.dyndns.org writes:
>>>
>>> Hi  fellow time-nuts,
>>>
>>> I think this message is interesting. It shows that  some receiver
>>> vendors have been cheating on an important detail, ignoring  the
>>> health status and being confused as a  result.
>>>
>>> Cheers,
>>> Magnus
>>>
>>>
>>> -------- Original Message  --------
>>> Subject: CGSIC: Known Problem With Certain GPS Devices
>>> Date:  Thu, 15 May 2014 21:20:23 +0000
>>> From: Civil Global Positioning System  Service Interface Committee
>>> (CGSIC)  <cgsic at cgls.uscg.mil>
>>> Reply-To: cgsic at cgls.uscg.mil
>>> To:  cgsic at cgls.uscg.mil <cgsic at cgls.uscg.mil>
>>>
>>> All CGSIC:
>>>
>>> May  15, 2014
>>>
>>> Recently, many GPS users have reported intermittent GPS  outages in
>>> their devices.  After investigating, the U.S. government  has linked
>>> the problem to flawed processing of GPS satellite data within certain
>>> GPS receiver chipsets.  The GPS satellite service continues  to
>>> function as designed and is fully operational and available  worldwide.
>>>
>>> The problem affects only user equipment that erroneously ignores the
>>> satellite health status information broadcast from every GPS satellite.
>>> The problem is not related to the April 28, 2014,  activation of
>>> civil navigation messages on the GPS L2C and L5  signals.
>>>
>>> Since March 15, 2014, the Air Force has been conducting functional
>>> checkout on a GPS satellite, designated Space Vehicle Number (SVN) 64.
>>> SVN 64 broadcasts a data message that clearly indicates SVN 64 is
>>> unusable for navigation.  Nevertheless, the U.S. government has
>>> confirmed that certain GPS receivers are using data from SVN 64, in
>>> violation of GPS interface specifications, resulting in outages or
>>> corrupted, inaccurate position calculations.
>>>
>>> The Air Force testing  is scheduled to end in mid-May 2014 at which
>>> time SVN 64 will begin normal  operation.  At that point, these problems may
>>> stop  occurring.   Meanwhile, the U.S. government urges all GPS device
>>> makers to review their products for compliance with the GPS interface
>>> specifications, and if necessary, to issue software/firmware updates
>>> to users as soon as possible. View specifications
>>> http://www.gps.gov/technical/icwg/
>>>
>>> Users experiencing GPS outages  should check with their device
>>> manufacturers for available  software/firmware updates.  In addition,
>>> any civil user seeing  unusual behavior in GPS user equipment should
>>> report it to the U.S. Coast  Guard Navigation Center (NAVCEN).
>>> Aviation users should file reports  consistent with FAA-approved
>>> procedures. Military users seeing  unusual behavior should report it
>>> the GPS Operations Center (GPSOC).
>>>
>>> Please direct any civil user questions to NAVCEN at (703) 313-5900,
>>> http://www.navcen.uscg.gov Please direct any military user  questions
>>> to the GPSOC at (719) 567-2541, DSN: 560-2541,
>>> gpsoperationscenter at us.af.mil https://gps.afspc.af.mil Military
>>> alternate: Joint Space Operations Center, (805) 606-3514, DSN:
>>> 276-3514,  jspoccombatops at vandenberg.af.mil
>>> ----
>>> See also:
>>> Technical explanation  for device makers (PDF)
>>> http://www.navcen.uscg.gov/pdf/gps/GPSOC_PRN  30_Notice.pdf
>>>
>>> V/R
>>> Rick Hamilton
>>> CGSIC Executive  Secretariat
>>> GPS Information Analysis Team Lead
>>> USCG Navigation  Center
>>> 703-313-5930
>>>
>>>
>>> _______________________________________________
>>> CGSIC  one-way mailing list
>>> Unsubscribe:  http://cgls.uscg.mil/mailman/listinfo/cgsic
>>>
>>> If you would like to report  abuse of the CGLS listserv please send
>>> an email to:  CGLSAdmin at uscg.mil
>>>
>>>
>>> _______________________________________________
>>> time-nuts  mailing list -- time-nuts at 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 at 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 at febo.com To unsubscribe, go to
>> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
>> and follow the instructions there.
>>
>
>
> ------------------------------
>
> Message: 3
> Date: Sat, 17 May 2014 11:37:42 -0400 (EDT)
> From: EWKehren at aol.com
> To: time-nuts at febo.com
> Subject: [time-nuts] FTS 1200 transistor replacement
> Message-ID: <62f98.1c47159b.40a8dc4d at aol.com>
> Content-Type: text/plain; charset="US-ASCII"
>
> Traced the problem of my FTS 1200 to the first BC109 Transistor on the
> A2/A3 AGS/Amplifier board. Since it is right after the Oscillator transistor low  noise is critical. This unit is at least 30 years old and my question is, what  transistor will have even lower noise than the than low noise BC 109.
> Voltage is  6.43 V.
> Thanks  Bert Kehren
>
> ------------------------------
>
> _______________________________________________
> time-nuts mailing list
> time-nuts at febo.com
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
>
> End of time-nuts Digest, Vol 118, Issue 35
> ******************************************
>
> _______________________________________________
> time-nuts mailing list -- time-nuts at febo.com
> To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there.




More information about the time-nuts mailing list