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
Fabian Kurz, DJ1YFK has figured out how to add simple QRSS beacon capability to one of the original WsspryPi forks. This is done with a new "-q" option. His repository is HERE. Unfortunately, his version lacks the newer shutdown button and transmit LED features.
I would love to see QRSS functionality added to your version of WsprryPi. That would make it the ultimate WSPR / QRSS dual mode application for the Pi. Possibly the two modes could be easily integrated into the web console using a toggle to chose between either WSPR or QRSS.
I run Fabian's command line only version using a bash script that first executes a QRSS beacon on the 1's (1 minute after the hour, 11 minutes, 21 minute etc.) followed by a WSPR beacon on the 8's (8 minutes after the hour, 18 minutes, 28 minutes, etc.). This kind of use may be too complicated for the web console.
The text was updated successfully, but these errors were encountered:
Hi Lee,
Fabian Kurz, DJ1YFK has figured out how to add simple QRSS beacon capability to one of the original WsspryPi forks. This is done with a new "-q" option. His repository is HERE. Unfortunately, his version lacks the newer shutdown button and transmit LED features.
I would love to see QRSS functionality added to your version of WsprryPi. That would make it the ultimate WSPR / QRSS dual mode application for the Pi. Possibly the two modes could be easily integrated into the web console using a toggle to chose between either WSPR or QRSS.
I run Fabian's command line only version using a bash script that first executes a QRSS beacon on the 1's (1 minute after the hour, 11 minutes, 21 minute etc.) followed by a WSPR beacon on the 8's (8 minutes after the hour, 18 minutes, 28 minutes, etc.). This kind of use may be too complicated for the web console.
The text was updated successfully, but these errors were encountered: