SDR Trunk and multiple rtlsdr dongles

kb5udf

Member
Premium Subscriber
Joined
Apr 7, 2004
Messages
865
Location
Louisiana
Hi gang, after much hair pulling I managed to get something working and will summarize as follows.
I have 2 rtlsdr v3 (I think) and 1 noo elec dongles that work fine with SDR trunk on a mac; no tweaking required.

For windows, once I installed the driver with zadig, the dongles work fine on SDR#, but were troublesome on
SDRtrunk, due to, I think them all having the same number. However, I could see they were recognized.
Long story short, what worked well to stop me getting no tuner available issue was to set the min and max
to the desired 2.4 mhz interval I want to span/monitor.

Essentially, I'm using, for this instance, 3 dongles to monitor all of the 70cm ham repeaters in my area, all the 2m ham repeaters in my area
and a few GMRS frequencies. I have sufficient bandwidth for each of these three purposes, using one dongle for each. It seemed like at first, SDRtrunk
would start the dongle on some non-useful frequency and then say no tuner available because that frequency was too far away from the desired channel/frequency.
I messed around with editing the center frequency, but ultimately the answer was to set the Min and Max. Now I didn't have to mess around with the rtl-eeprom
program, since it is working fine for my purposes.

73'
 

hruskacha

Member
Premium Subscriber
Joined
Nov 9, 2020
Messages
326
Location
Muskegon
In the tuner menu, as long as you don't see tuner errors, you are all set. If you see "tuner unavailable" In the event logs, that's the indication that you don't have enough tuner bandwidth. The errors can be misleading depending on where they are logged, such as the Application logs vs. channel event logs
 

kb5udf

Member
Premium Subscriber
Joined
Apr 7, 2004
Messages
865
Location
Louisiana
I always had enough bandwidth for the 3 frequency spans in question, but since SDRtrunk was sometimes picking inappropriate center frequencies, I was getting tuner unavailable. Setting max/min was a workaround for this.
 
Top