so ive been messing around with remote station control for a while now, got a basic setup running at home where i can hit my IC-7300 over the LAN but i want to take it further and actually use RemoteHams to expose it to the internet properly. the SDR side is what im fuzzy on. i have an RTL-SDR dongle sitting on the same machine as my RRC-1258 and im not totally sure how to get that panadapter data streaming out alongside the audio without it turning into a total mess.

the RemoteHams client software supposedly handles all this but every time i try to configure the SDR server piece it either cant find the device or it just hangs on connect. tried reinstalling twice. running windows 10, the dongle shows up fine in SDR# and in SDR Console so its not a driver thing. has anyone actually got the full chain working where you have the rig control, audio and the SDR panadapter all going over a single internet connection? curious how much bandwidth that actually chews through too because im on a 25 up at the shack end.

yeah ive done something close to this. not with an RTL-SDR though, i was using an SDRplay RSP1A and that changes things a bit. the RemoteHams SDR server is kind of finicky about initialization order — you basically have to have the SDR server started and the device open before the main RRC client tries to connect or it just gives up. no real error, just hangs like you said. try launching the SDR server piece first and letting it sit for like 30 seconds before you do anything else. also make sure the sample rate is set conservatively, i had mine trying to push 2 MHz wide and that was just killing the stream. dropped it to 900k and things got way more stable. on 25 up you should be ok for the audio plus a narrow SDR slice but dont expect to run a wide panadapter remotely, it just doesnt work that well unless youre on fiber both ends.

tbh the whole RemoteHams platform has always been a bit temperamental with third party SDR hardware in my experience. i went a totally different direction and just set up an OpenWebRX instance on a separate Pi at the shack and linked that separately, then use the RRC-1258 just for the rig control and audio. more moving parts but each thing is doing one job and its way easier to troubleshoot when something breaks. the bandwidth question really depends on the codec settings, ive seen people run it surprisingly lean but then the latency gets bad and CW becomes unusable. 25 up is plenty if you keep the SDR stream narrow and use one of the compressed audio modes.