forked from DanAnkers/WsprryPi
-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Double frequency. #7
Comments
That's very odd... Can you send me the actual command line you used? James |
Originally:
ExecStart=wspr -r -s -o K1PHA FN42 20 20m
(part of a systemd script)
But then to test
wspr -t 14097100
gave a doubled rate on pin 4 (measured with a HP 5432A frequency
counter to the nearest Hz)
and now I use
# Seems to double the frequency
# so use 20 meter 14097100 / 2 = 7048550
ExecStart=/usr/bin/wspr -r -s -o K1PHA FN42 20 7048550 0 0 0 0
Sucessfully (I added to extra pauses so as not to clutter up the airwaves)
…On Mon, Apr 10, 2017 at 6:18 PM, James Peroulas ***@***.***> wrote:
That's very odd... Can you send me the actual command line you used?
James
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#7 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAD3MfZMzY_4jKpMi6jYWIFQ7VPGmDESks5ruqrTgaJpZM4M3ho8>
.
|
I'm still not seeing this behavior... Can someone else confirm this? Are people receiving your transmissions on the double frequency? JP |
This is a Pi 1B. And yes, my beacon is seen in Belgium Venezuela Texas (from Boston). (This is set at 7MH read at 14MHz=20m). It's a standard Raspbian setup, headless. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I ran on P1 1B I get a frequency on GP4 that is double the specified (and reported frequency). For instance, trying 20m the frequency should be 14097100+- but is actually 28194200.
And my TAPR filter filters it out.
When I specify 7048550 (half the frequency) GP4 actually is at 14097100 and the beacon works at 20m.
The text was updated successfully, but these errors were encountered: