[GPS_Standard] GPS_Standard Digest, Vol 30, Issue 3

Thu Jul 16 15:51:30 EDT 2009

I have tested the VE2ZAZ programme with 40 MHz ( of course by adapting the 
hex-value in the assembler source).
regards
Arie
----- Original Message ----- 
From: <gps_standard-request at mailman.qth.net>
To: <gps_standard at mailman.qth.net>
Sent: Thursday, July 16, 2009 6:00 PM
Subject: GPS_Standard Digest, Vol 30, Issue 3


> Send GPS_Standard mailing list submissions to
> gps_standard at mailman.qth.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://mailman.qth.net/mailman/listinfo/gps_standard
> or, via email, send a message with subject or body 'help' to
> gps_standard-request at mailman.qth.net
>
> You can reach the person managing the list at
> gps_standard-owner at mailman.qth.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of GPS_Standard digest..."
>
>
> Today's Topics:
>
>   1. Re: Custom PIC Chip to Regulate 20 MHz VCO (Stanley Reynolds)
>   2. Re: Custom PIC Chip to Regulate 20 MHz VCO (Stanley Reynolds)
>   3. Re: 20 MHz Disciplined Osc (wbr/wf4r)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 15 Jul 2009 09:07:17 -0700 (PDT)
> From: Stanley Reynolds <stanley_reynolds at yahoo.com>
> Subject: Re: [GPS_Standard] Custom PIC Chip to Regulate 20 MHz VCO
> To: gps_standard at mailman.qth.net
> Message-ID: <861226.89000.qm at web30303.mail.mud.yahoo.com>
> Content-Type: text/plain; charset=iso-8859-1
>
>
>
>
> You would need to adjust the code as well.
> Reduce the gate time from 16 sec to 8 sec would produce the same 6800 hex 
> pulse count or change 6800 to D000 for 20 Mhz.
> I have not considered the adjustments to the PC monitor program.
> You may want to look at the 5 to 10 Mhz adjustments in the curent code:
>
> ccp_160mhz_h??????????????? EQU 0x68??????????????? ;when frequency 
> counted is exactly 160MHz, OLD_CCPR1 reads 26624, or 0x6800
> ccp_160mhz_l??????????????? EQU 0x00??????????????? ; "
> ccp_80mhz_h???????????????? EQU 0xB4??????????????? ;when frequency 
> counted is exactly 80MHz, OLD_CCPR1 reads 46080, or 0xB400
> ccp_80mhz_l???????????????? EQU 0x00??????????????? ; "
> .
> . <snip>
> .
> ??????? BTFSS PORTB,bootup_freq_test??????????????? ;Is the frequency 
> selection pin for 10MHz OCXO?
> ??????? BRA INIT_5MHz?????????????????????????????? ;No, go initialize for 
> 5MHz OCXO
> INIT_10MHz????????????????????????????????????????? ;Yes, initialize for 
> 10MHz OCXO
> ??????? MOVLW ccp_160mhz_h????????????????????????? ;Load nominal value H 
> to compare to measured frequency
> ??????? MOVWF NOMINAL_FREQ_VAL_H??????????????????? ; "
> ??????? MOVLW ccp_160mhz_l????????????????????????? ;Load nominal value L 
> to compare to measured frequency
> ??????? MOVWF NOMINAL_FREQ_VAL_L??????????????????? ; "
> ??????? BRA INIT_FREQ_COMPLETED???????????????????? ;Go continue 
> initialization
> INIT_5MHz?????????????????????????????????????????? ;initialize for 5MHz 
> OCXO
> ??????? MOVLW ccp_80mhz_h?????????????????????????? ;Load nominal value H 
> to compare to measured frequency
> ??????? MOVWF NOMINAL_FREQ_VAL_H??????????????????? ; "
> ??????? MOVLW ccp_80mhz_l?????????????????????????? ;Load nominal value L 
> to compare to measured frequency
> ??????? MOVWF NOMINAL_FREQ_VAL_L??????????????????? ; "
>
> This would point to the pluse count method :
>
> or
> ccp_320mhz_h??????????????EQU 0xD0?????????? ;when frequency counted is 
> exactly 320MHz, OLD_CCPR1 reads 53248, or 0xD000
> ccp_320Mhz_l????????????????EQU 0x00
> ...
>
> INIT_20MHz????????????????????????????????????????? ;Yes, initialize for 
> 20MHz OCXO
> ??????? MOVLW ccp_320mhz_h????????????????????????? ;Load nominal value H 
> to compare to measured frequency
> ??????? MOVWF NOMINAL_FREQ_VAL_H??????????????????? ; "
> ??????? MOVLW ccp_320mhz_l????????????????????????? ;Load nominal value L 
> to compare to measured frequency
> ??????? MOVWF NOMINAL_FREQ_VAL_L??????????????????? ; "
> ??????? BRA INIT_FREQ_COMPLETED???????????????????? ;Go continue 
> initialization
>
> If you wanted to force 20Mhz just use the code INIT_20MHz instead of the 
> current code starting with BIFSS or better yet in place of the 5MHz case 
> so the i/o pin would select 10 or 20 MHz.
>
>
> Stanley
>
> ?
> ----- Original Message ----
> From: Arie Dogterom <pa0ez at amsat.org>
> To: gps_standard at mailman.qth.net
> Sent: Tuesday, July 14, 2009 12:16:37 PM
> Subject: Re: [GPS_Standard] GPS_Standard Digest, Vol 30, Issue 1
>
> The chip will go to 50 MHz
> Arie
>
> ----- Original Message ----- 
> From: <gps_standard-request at mailman.qth.net>
> To: <gps_standard at mailman.qth.net>
> Sent: Tuesday, July 14, 2009 6:00 PM
> Subject: GPS_Standard Digest, Vol 30, Issue 1
>
>
>> Send GPS_Standard mailing list submissions to
>> gps_standard at mailman.qth.net
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> http://mailman.qth.net/mailman/listinfo/gps_standard
>> or, via email, send a message with subject or body 'help' to
>> gps_standard-request at mailman.qth.net
>>
>> You can reach the person managing the list at
>> gps_standard-owner at mailman.qth.net
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of GPS_Standard digest..."
>>
>>
>> Today's Topics:
>>
>>? 1. Custom PIC Chip to Regulate 20 MHz VCO (P M Gant)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Tue, 14 Jul 2009 12:01:27 +0200
>> From: P M Gant <ha5rxz at gmail.com>
>> Subject: [GPS_Standard] Custom PIC Chip to Regulate 20 MHz VCO
>> To: gps_standard at mailman.qth.net
>> Message-ID:
>> <f2226b090907140301r14bd4f1avba0c7ee79b67e37f at mail.gmail.com>
>> Content-Type: text/plain; charset=ISO-8859-1
>>
>> Is it possible to prepare a custom version of the PIC to regulate a 20
>> MHz oscillator or is this frequency too high?
>>
>> HA5RXZ
>>
>>
>> ------------------------------
>>
>> _______________________________________________
>> GPS_Standard mailing list
>> GPS_Standard at mailman.qth.net
>> http://mailman.qth.net/mailman/listinfo/gps_standard
>>
>>
>> End of GPS_Standard Digest, Vol 30, Issue 1
>> *******************************************
>>
> ______________________________________________________________
> GPS_Standard mailing list
> Home: http://mailman.qth.net/mailman/listinfo/gps_standard
> Help: http://mailman.qth.net/mmfaq.htm
> Post: mailto:GPS_Standard at mailman.qth.net
>
> This list hosted by: http://www.qsl.net
> Please help support this email list: http://www.qsl.net/donate.html
>
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 15 Jul 2009 09:47:59 -0700 (PDT)
> From: Stanley Reynolds <stanley_reynolds at yahoo.com>
> Subject: Re: [GPS_Standard] Custom PIC Chip to Regulate 20 MHz VCO
> To: gps_standard at mailman.qth.net
> Message-ID: <593092.66360.qm at web30307.mail.mud.yahoo.com>
> Content-Type: text/plain; charset=us-ascii
>
>
>
> Of course you could divide the clock by two with a flip-flop and feed the 
> controller 10MHz. U2 has an extra ripple counter you could use and U3 has 
> an extra output if you want to have 20 MHz,10 MHz, 5 MHz and 1MHz depends 
> how much you modify the board. Stacking IC's is another possible way to 
> expand the board but I would add heat sink between and on top of the stack 
> of output chips.
>
> Stanley
>
>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 15 Jul 2009 19:29:41 -0500 (CDT)
> From: wbr/wf4r <wbr at verizon.net>
> Subject: Re: [GPS_Standard] 20 MHz Disciplined Osc
> To: gps_standard at mailman.qth.net
> Cc: gps_standard at mailman.qth.net
> Message-ID:
> <19129237.32181.1247704181507.JavaMail.root at vms061.mailsrvcs.net>
> Content-Type: text/plain; charset="UTF-8"
>
>
>
> ------------------------------
>
> _______________________________________________
> GPS_Standard mailing list
> GPS_Standard at mailman.qth.net
> http://mailman.qth.net/mailman/listinfo/gps_standard
>
>
> End of GPS_Standard Digest, Vol 30, Issue 3
> *******************************************
>