Adjust websdr URLs to decode CW activations #45

Merged

kwesthaus merged 1 commit from feat/websdr-cw into master

2025-03-22 08:48:57 +00:00

kwesthaus commented

2025-03-07 19:25:26 +00:00

(Migrated from github.com)

Tested by overwriting function definitions in my browser.
Tested with http://websdr1.kfsdr.com:8901/ and http://websdr.k3fef.com:8901/.

This could be extended to USB/LSB, but as that will require some more testing, I am leaving that for a separate feature.

Tested by overwriting function definitions in my browser. Tested with http://websdr1.kfsdr.com:8901/ and http://websdr.k3fef.com:8901/. This could be extended to USB/LSB, but as that will require some more testing, I am leaving that for a separate feature.

ianrenton commented

2025-03-08 09:10:58 +00:00

(Migrated from github.com)

This is a real weird one! I confess I haven't tried URL parameters on WebSDRs before, and now I have, I'm actually seeing five different behaviours. All screenshots below using a URL parameter of tune=14064CW without your 750Hz adjustment:

University of Twente (http://websdr.ewi.utwente.nl:8901/?tune=14064CW): Sets dial 750Hz higher, "LSB" mode, results in centre of passband being at 14064 and CW therefore being audible
RAF Hack Green (http://hackgreensdr.org:8901/?tune=14064CW): Sets dial on frequency, "USB" mode, results in centre of passband being at 14064.75 and CW not audible
Your two examples (http://websdr.k3fef.com:8901/?tune=14064CW and http://websdr1.kfsdr.com:8901/?tune=14064CW): Sets dial 1500Hz higher, "LSB" mode, results in centre of passband also being at 14064.75 and CW would not be audible. Weirdly neither the dial frequency or the centre of the passband is at 14064kHz, but the effective behaviour is the same as Hack Green.
Maasbree (http://sdr.websdrmaasbree.nl:8901/?tune=14064CW): Sets dial on frequency, passband directly around dial frequency, CW would be audible
Bordeaux (http://ham.websdrbordeaux.fr:8000/?tune=14064CW): "tune" parameter not supported at all.

Based on these and a few more I've tried, it looks like the WebSDRs that require a 750Hz down shift are slightly more common, but not by much. So I think I would prefer if there was an option in the UI to toggle this on or off (which would then get saved to and restored from localstorage for the user).

If you're happy to make that change under your branch, please do - if not, let me know, I'm happy to merge your PR here and then add the toggle myself.

Thanks for pointing this issue out and thanks for contributing to Field Spotter!

This is a real weird one! I confess I haven't tried URL parameters on WebSDRs before, and now I have, I'm actually seeing *five different behaviours*. All screenshots below using a URL parameter of `tune=14064CW` *without* your 750Hz adjustment: 1. University of Twente (http://websdr.ewi.utwente.nl:8901/?tune=14064CW): Sets dial 750Hz higher, "LSB" mode, results in centre of passband being at 14064 and CW therefore being audible ![image](https://github.com/user-attachments/assets/70b49fa8-36ff-40a9-aaf6-9cdc9a54beb1) 2. RAF Hack Green (http://hackgreensdr.org:8901/?tune=14064CW): Sets dial on frequency, "USB" mode, results in centre of passband being at 14064.75 and CW not audible ![image](https://github.com/user-attachments/assets/628ba75b-efa6-4dd4-a2b5-e03457c0aba8) 3. Your two examples (http://websdr.k3fef.com:8901/?tune=14064CW and http://websdr1.kfsdr.com:8901/?tune=14064CW): Sets dial 1500Hz higher, "LSB" mode, results in centre of passband also being at 14064.75 and CW would not be audible. Weirdly *neither* the dial frequency or the centre of the passband is at 14064kHz, but the effective behaviour is the same as Hack Green. ![image](https://github.com/user-attachments/assets/89c04c92-291c-408f-8665-e0b1a4a17c15) 4. Maasbree (http://sdr.websdrmaasbree.nl:8901/?tune=14064CW): Sets dial on frequency, passband directly around dial frequency, CW would be audible ![image](https://github.com/user-attachments/assets/167d2750-8dcf-4405-993e-6089bb353236) 5. Bordeaux (http://ham.websdrbordeaux.fr:8000/?tune=14064CW): "tune" parameter not supported at all. Based on these and a few more I've tried, it looks like the WebSDRs that require a 750Hz down shift are slightly more common, but not by much. So I think I would prefer if there was an option in the UI to toggle this on or off (which would then get saved to and restored from localstorage for the user). If you're happy to make that change under your branch, please do - if not, let me know, I'm happy to merge your PR here and then add the toggle myself. Thanks for pointing this issue out and thanks for contributing to Field Spotter!

kwesthaus commented

2025-03-17 19:43:55 +00:00

(Migrated from github.com)

Weird indeed! Thanks for checking out some more examples. I totally agree if the behavior isn't uniform then it should be behind a UI toggle.

I think you will do a better job integrating the UI/storage functionality, so if you're willing to take care of that part I would be appreciative!

Weird indeed! Thanks for checking out some more examples. I totally agree if the behavior isn't uniform then it should be behind a UI toggle. I think you will do a better job integrating the UI/storage functionality, so if you're willing to take care of that part I would be appreciative!

ianrenton commented

2025-03-22 08:48:54 +00:00

(Migrated from github.com)

OK, no problem. I'll merge this now then include the toggle. Thanks again!