-
Notifications
You must be signed in to change notification settings - Fork 452
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
BUGS: SDRangel RPI server using SDRplay RSP1A #1827
Comments
Yes, I noticed something odd with this the other day, so needs looking at.
What does the signal look like? Does it help to use the channel gain setting?
Yes, and probably wont be implemented. It's too complicated to support every different option for every SDR in the one client.
You should be able to use the new Plugin Presets to set your own defaults. |
Decimation setting isn't being set on remote at startup, due to a race condition, which is probably the cause of the initial buffering problem. |
The SDRplay doesn't support sample rates lower then 2MS/s, so if you try to adjust the remote device sample rate to 1MS/s, it will quite possibly go wrong. To reduce the rate lower than this, you need to use decimation. |
The SDRangel client (RemoteTCPInput) allows me to set the "SR (remote device sample rate)" to "1,000,000 S/s". I just did a test. The SDRangel client (RemoteTCPInput) allows a sample rate from "00,000,000 S/s" to "99,999,999 S/s". |
Correct. edit: Have just written something basic. |
SDRplay API has an index setting, rather than gain in dB, so this would need to be changed. |
Do you have the AGC button pressed? If not, what IF gain setting are you using? |
"Do you have the AGC button pressed? If not, what IF gain setting are you using?" |
Ok, press AGC of set IF to -50ish, as you would if using it directly. At 0, the ADC will be overloaded, if it's anything like the Duo. You may need to experiment, but easiest just to enable AGC. (Note this maps to IF AGC for SDRplay) |
"Ok, press AGC of set IF to -50ish, as you would if using it directly. At 0, the ADC will be overloaded, if it's anything like the Duo. You may need to experiment, but easiest just to enable AGC. (Note this maps to IF AGC for SDRplay)" AGC=ON. IF=0.0dB. Test: Increasing Ch Gain from 0dB to 100dB. AGC=OFF. IF=-50.0dB. Test: Increasing Ch Gain from 0dB to 100dB. NOTES: |
To clarify, keep "channel gain" fixed at 0, and eperiment with IF gain setting To find the correct setting, it's probably better to do this with the SDRplay device connected localy, not via Remote TCP. |
"To clarify, keep "channel gain" fixed at 0, and eperiment with IF gain setting" "To find the correct setting, it's probably better to do this with the SDRplay device connected localy, not via Remote TCP." |
SYSTEM:
The SDRangel Raspberry Pi server has several bugs/issues when using the SDRplay RSP1A device.
If I'm doing something wrong, please let me know.
BUGS/ISSUES:
if the "Remote device sample rate":
a) is DECREASED from "2,000,000 S/s" to "1,000,000 S/s",
then the audio playback pitch drops an octave (audio playback speed likely cut in half).
Playback pitch is restored by returning to "2,000,000 S/s".
b) is INCREASED from "2,000,000 S/s" to "3,000,000 S/s",
then the audio playback PERMANENTLY stops.
It is NOT recovered by returning to "2,000,000 S/s".
To recover audio playback, the server must be stopped and restarted.
the "IQ Sample bit depth" must be set to "24 bits" to get clear stable audio.
"8 bits" has static.
"16 bits" has less static.
"24 bits" is clear and stable.
"32 bits" is clear, but has occasional stuttering.
Prefer that it default to "1" for clearer audio.
(Also, WORK-AROUND below requires setting it to "1").
Prefer that it default to "0.1 second" so that setting changes are observed more quickly.
The most severe bug is getting the client to connect reliably to the server.
To reproduce this bug, first determine the local IP address of the Raspberry Pi server.
In the example below, it is "192.168.0.123".
Next, start the SDRangel server on the Raspberry Pi with the following commands:
Finally, start a "RemoteTCPInput Rx device" on the X86_64 Debian client:
FAIL:
The waterfall never starts.
The pre-fill buffer takes ~40 seconds to completely fill, empties, then repeats.
I've found a fix/work-around.
WORK-AROUND:
Start a RemoteTCPInput Rx device on the X86_64 client:
SUCCESS:
The waterfall starts.
The pre-fill buffer completely fills in 1 second and stays full.
Please let me know if I'm doing something wrong.
Also, please let me know if I can help with anymore info or testing.
The text was updated successfully, but these errors were encountered: