You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
good morning,
after installing a fresh jessie lite image on a raspberry pi zero w and running:
apt-get update, upgrade and dist-upgrade and installing WsprryPi I've run the following command:
sudo wspr -s -n mycallsign mylocator 10 20m.
By checking with the scope I see a square wave with a frequency that is the double of the requested frequency! I've tried also to run:
sudo wspr -s -n mycallsign mylocator 10 7100000
but I get a 14.200 Mhz output.
How I can fix this?
The text was updated successfully, but these errors were encountered:
Redoing all the installation on a fresh image, I get after running sudo make:
cc -Wall -c mailbox.c
g++ -D_GLIBCXX_DEBUG -std=c++11 -Wall -Werror -fmax-errors=5 -lm -DRPI1 mailbox.o wspr.cpp -owspr
g++ -D_GLIBCXX_DEBUG -std=c++11 -Wall -Werror -fmax-errors=5 -lm -DRPI1 gpioclk.cpp -ogpioclk
I have this problem on "Raspberry Pi 3 Model B V1.2", but had to divide the frequency by 2.2 to get the correct frequency output on my scope. Even then I didn't get usable WSPR and the frequency was unstable. Edit: tried this card in an original pi, and have the same frequency offset issues, but no frequency jumps. Edit2: switched to a fresh "Raspbian Stretch Lite" OS and my trusty original pi, and it's working correctly. The problem config was on Raspbian/Jesse/noobs/pixel full desktop version.
good morning,
after installing a fresh jessie lite image on a raspberry pi zero w and running:
apt-get update, upgrade and dist-upgrade and installing WsprryPi I've run the following command:
sudo wspr -s -n mycallsign mylocator 10 20m.
By checking with the scope I see a square wave with a frequency that is the double of the requested frequency! I've tried also to run:
sudo wspr -s -n mycallsign mylocator 10 7100000
but I get a 14.200 Mhz output.
How I can fix this?
The text was updated successfully, but these errors were encountered: