sdrtrunk icon indicating copy to clipboard operation
sdrtrunk copied to clipboard

Allow RTL-SDR Tuner via TCP

Open HoracioDos opened this issue 7 years ago • 16 comments

Hello! Would you please consider to allow connecting RTL-SDR Tuner via TCP with RTL_TCP command or AirSpy Server. Thanks!

HoracioDos avatar Oct 21 '17 15:10 HoracioDos

Wouldn't that only work for fixed frequencies?
Wouldn't code be required to remotely retune the tuner on the fly?

chudgoo avatar Oct 26 '17 23:10 chudgoo

Probably wouldn't be able problem for the control channel.

W8AWT avatar Oct 27 '17 02:10 W8AWT

@chudgoo No, GQRX changes frequencies and other settings (e.g. LNA) on the fly. The client → server link is used to remotely control the dongle.

This would be super useful. As it is, I have to run SDRTrunk by X11 or VNC to get around this, and even over a gigabit Ethernet link, X11 is ... not ideal. That's to say nothing of the problem of audio forwarding over the network. The latency of X11 is probably the fault of AWT and not SDRTrunk, but supporting remote SDR protocols would be very nice.

ghost avatar Dec 01 '17 19:12 ghost

@classicfm What is the typical network bandwidth used for a remote RTL-SDR sending IQ data over the network? So if let's say tcp port 3333 is being used to send data, how does the tuning config actually change? I've only ever used rtl_tcp for one freq at a time.

chudgoo avatar Dec 02 '17 02:12 chudgoo

@chudgoo It varies on sampling rate but it's no different than PCM audio. Instead of 16 bit samples the high eight bits are amplitude and the low are phase. Obviously sampling rates are higher than PCM audio but I would say it's about two to three times more bandwidth than CD quality audio.

It easily works over a WiFi link and it even works, albeit rather shakily, over a VPN from my home network (5-6 Mbps upload). In that case it tends to fail because most SDR applications are intolerant of latency changes.

The control commands are sent over the TCP link. The sample data comes down one side of the bidirectional duplex link, and any configuration commands are sent on the 'reverse' link. I don't know how the application handles e.g. a change in frequency as a consequence of setting it at runtime, I assume it is via internal state tracking.

ghost avatar Dec 02 '17 17:12 ghost

@DSheirer Is there any chance to add RTL-SDR TCP support?

skawikk avatar Mar 22 '20 21:03 skawikk

There is a chance, but right now I have so many other features in the queue that I have to get done first.

DSheirer avatar Mar 23 '20 08:03 DSheirer

@DSheirer Hi;) You're doing awesome job!! Can You post any update in this topic? M.

skawikk avatar Jul 20 '20 12:07 skawikk

Any update?

Vedeneb avatar Jun 11 '21 13:06 Vedeneb

I'd still really like to see squelch for NFM, that would be great. At the present time in ver 0.6 there is no way to use non-constant carrier NFM frequencies due to the program having a lack of squelch.

Brad-git-man avatar Jun 12 '21 07:06 Brad-git-man

+1 to this, another use case of having my dongles all plugged into my PI near the window and using the horsepower of my desktop to run SDRTrunk.

ge0metrix avatar Aug 13 '22 22:08 ge0metrix

I'm also really hoping to see this!

sofakng avatar Sep 27 '22 19:09 sofakng

Likewise, my rtl-sdr dongle is connected to a remote headless pi in a different building running rtl_tcp. Bit of a deal breaker not being able to access it remotely.

ArrEssJay avatar Jun 20 '23 11:06 ArrEssJay

Like others I have my SDRs plugged into a Raspberry Pi that's remote. I'm able to use trunk-recorder today to record trunked systems, but it would be nice to take advantage of some of the advanced features that SDRTrunk has.

theficus avatar Aug 05 '23 18:08 theficus

Any Update ? this should be priority must have feature.

Or at least recommend some workaround...

Peterkal2112 avatar Nov 22 '23 15:11 Peterkal2112