Page 1 of 1

Results SDR Use Only - SN #'s?

Posted: Tue Apr 09, 2019 4:01 am
by Flexme
I am only planning/interested in the quad SDR part of the unit.

My results so far:

I chose to use the following for a PSU: ... UTF8&psc=1

Has USBC adapter and seems to be running things well.

I've started up my main use software, and it seems to be chugging along quite nicely, BUT to work with FOUR (4) tuners EACH MUST HAVE A UNIQUE S/N.

Doing an rtl_test I get:

Code: Select all

~$ cat hydrartl_test.txt 
bin$ rtl_test
Found 4 device(s):
  0:  Generic, RTL2832U, SN: 77771111153705700
  1:  Generic, RTL2832U, SN: 77771111153705700
  2:  Generic, RTL2832U, SN: 77771111153705700
  3:  Generic, RTL2832U, SN: 77771111153705700

Using device 0: Generic RTL2832U
Found Rafael Micro R820T tuner
Supported gain values (29): 0.0 0.9 1.4 2.7 3.7 7.7 8.7 12.5 14.4 15.7 16.6 19.7 20.7 22.9 25.4 28.0 29.7 32.8 33.8 36.4 37.2 38.6 40.2 42.1 43.4 43.9 44.5 48.0 49.6 
[R82XX] PLL not locked!
Running the software under its tuner info it shows as SN#3 for all of these.

BEFORE I brick a $100 device, will these units accept the rtl_eeprom -d x -s y commands to set the SN? Where x = device 0-3 and y the new SN.

PPM seems to be pretty stable +/- 2PPM software locked up pretty well right way with out entering a PPM to start.

Re: Results SDR Use Only - SN #'s?

Posted: Tue Apr 09, 2019 1:31 pm
by kb3cs

Re: Results SDR Use Only - SN #'s?

Posted: Tue Apr 09, 2019 7:41 pm
by Corrosive
kb3cs wrote:
Tue Apr 09, 2019 1:31 pm
be careful! see
Yeah be careful for sure, if you're going to proceed anyway I'd suggest doing them one at a time and not having all four turned on at once.

Re: Results SDR Use Only - SN #'s?

Posted: Tue Apr 09, 2019 10:16 pm
by Flexme
kb3cs wrote:
Tue Apr 09, 2019 1:31 pm
be careful! see
Thanks, then I will wait for a while to see if a resolution comes along.

I take it that the HydraSDR needs firmware be compatible with rtl_eeprom?

For now my test case seems to run with 2 tuners, since it needs 2 to cover the spread. It definitely doesn't like V3 or other dongles with the same SN's when it tries to use more than 1 tuner... so I am not sure if its just luck or something else is letting it function for now...

Hopefully this is resolved so I can set SN #'s otherwise I guess it gets relegated to the parts bin.

Great idea 4 SDR's one box...get it to the price level of the fundraiser full time, $99, I can use these v. other dongles...

Couple thoughts:

1) Offer 5V/3A PSU's in your store to get with the units

2) Future runs move to 2.5 Coaxial DC connectors v. USBC

3) Remove the extra board for those that don't need it, ie: SDR users using other software, lower price ie; $99


Re: Results SDR Use Only - SN #'s?

Posted: Wed Apr 10, 2019 9:46 am
by kb3cs
the devices are "compatible" with rtl_eeprom, technically.

the issue is that rtl_eeprom is not designed to keep you from shooting a hole in your foot. and the 'as shipped' contents (lack of contents, actually) of the EEPROM easily leads to foot damage.

DO NOT say 'y' to the ""Write new configuration to device [y/n]?" prompt unless you are absolutely sure EVERYTHING in the formatted configuration report is correct (including the VID:PID). rtl_eeprom will write only those bytes that are changed.

you are well-advised to dump the EEPROM contents into a file first to preserve it and before you do anything to change it. however, some of the possible outcomes of changing EEPROM contents will not be simple to recover.

don't say i didn't warn you. :-/

fyi - i have set my rtlsdrs to serial numbers 1, 2, 3, and 4. the initial USB probe order did not provide a neat left-to-right order, though. almost. btw, a serial number of '0' would be a bad idea.

ps: the unit is called "KerberosSDR" now, okay?

Re: Results SDR Use Only - SN #'s?

Posted: Wed Apr 17, 2019 12:35 am
by Flexme
kb3cs wrote:
Wed Apr 10, 2019 9:46 am
the devices are "compatible" with rtl_eeprom, technically.
I have no intention of using rtl_eeprom until

BOTH HydraSDR and rtl_eeprom are shown to be safe.

That looks unlikely to happen. Sadly.

Coupled with some other results after a couple of days use, and persnickety with USB bus types.