search

willblades / sdrtrunk

Automatically exported from code.google.com/p/sdrtrunk
0 stars 1 forks source link

Not good signal at R820T #13

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. r820t
2. tune to 466mhz / comparing to gqrx - see images. No strong signal spikes 
there

What is the expected output? What do you see instead?
See signal, not only hum noise

What version of the product are you using? On what operating system?
r133

Please provide any additional information below.

root@t61:~/sdr/sdrtrunk/product# ./run_sdrtrunk_linux 
root@t61:~/sdr/sdrtrunk/product# SystemProperties - loaded 
[/root/SDRTrunk/SDRTrunk.properties]
SDRTrunk Multi-Channel Trunking Decoder Application Log
Log - application logging started 
[/root/SDRTrunk/logs/20140607_125153_SDRTrunk_application.log]
********** User Environment **********
OS:         Linux
OS Version:     3.14-kali1-amd64
OS Arch:        amd64
Java Vendor:        Oracle Corporation
Java Vendor URL:    http://java.oracle.com/
Java Version:       1.7.0_55
User:           root
User Home:      /root
User Directory:     /root/sdr/sdrtrunk/product
********** Java Class Path **********
SDRTrunk.jar:libs/usb-api-1.0.2.jar:libs/usb4java-javax-1.2.0.jar:libs/libusb4ja
va-1.2.0-linux-arm.jar:libs/libusb4java-1.2.0-osx-x86.jar:libs/libusb4java-1.2.0
-windows-x86.jar:libs/jide-oss-3.5.15.jar:libs/commons-lang3-3.2.1.jar:libs/libu
sb4java-1.2.0-osx-x86_64.jar:libs/libusb4java-1.2.0-linux-x86.jar:libs/jsr80-1.0
.1.jar:libs/libusb4java-1.2.0-windows-x86_64.jar:libs/miglayout-4.0-swing.jar:li
bs/usb4java-1.2.0.jar:libs/jtransforms-2.4.jar:libs/libusb4java-1.2.0-linux-x86_
64.jar
SystemProperties - application properties loaded 
[/root/SDRTrunk/SDRTrunk.properties]
SettingsManager - loading settings file [/root/SDRTrunk/settings/settings.xml]
PlaylistManager - loading playlist file [/root/SDRTrunk/playlist/playlist.xml]
********** USB Device Discovery **********
TunerManager - discovered [8] attached usb devices
    [NOT RECOGNIZED]    Bus 003 Device 001: ID 1d6b:0001
    [NOT RECOGNIZED]    Bus 005 Device 001: ID 1d6b:0002
    [NOT RECOGNIZED]    Bus 007 Device 001: ID 1d6b:0002
    [RECOGNIZED]        Bus 007 Device 002: ID 0bda:2838 RTL2832 SDR
    [NOT RECOGNIZED]    Bus 001 Device 001: ID 1d6b:0001
    [NOT RECOGNIZED]    Bus 006 Device 001: ID 1d6b:0001
    [NOT RECOGNIZED]    Bus 002 Device 001: ID 1d6b:0001
    [NOT RECOGNIZED]    Bus 004 Device 001: ID 1d6b:0001

********** Configuring USB Tuners **********
Tuner Manager - discovered [1] USB tuner devices
    [LOADED]    0BDA:2838 RTL2832 SDR/R820T #00000008

could not load 'loading.png'
DEBUG: RTL2832TunerController [00000008] - starting sample fetch thread
Starting the main gui
ERROR: R820T Tuner Controller - error setting frequency [461100000] - 
R820TTunerController - exception while setting frequency [461100000] - R820T 
Tuner Controller - couldn't achieve PLL lock on frequency [461100000]
ERROR: R820T Tuner Controller - error setting frequency [462100000] - 
R820TTunerController - exception while setting frequency [462100000] - R820T 
Tuner Controller - couldn't achieve PLL lock on frequency [462100000]
ERROR: R820T Tuner Controller - error setting frequency [463100000] - 
R820TTunerController - exception while setting frequency [463100000] - R820T 
Tuner Controller - couldn't achieve PLL lock on frequency [463100000]
ERROR: R820T Tuner Controller - error setting frequency [464100000] - 
R820TTunerController - exception while setting frequency [464100000] - R820T 
Tuner Controller - couldn't achieve PLL lock on frequency [464100000]
20140607 125256 RTL-2832 [00000008] Sample Rate - current: 1,238,630.4  average: 
1,238,630.4 count:1
20140607 125356 RTL-2832 [00000008] Sample Rate - current: 1,312,358.4  average: 
1,275,494.4 count:2

Original issue reported on code.google.com by pschonm...@gmail.com on 7 Jun 2014 at 10:56

Attachments:

GoogleCodeExporter commented 9 years ago 
Confirmed that the R133 revision does not achieve PLL lock for frequencies in 
the range of 460.8 MHz - ~468.0 MHz.  I suspect that the error is in register 
0x14 (PLL register).

Will confirm with wireshark captures between sdrtrunk and gqrx.

Original comment by dennis.s...@gmail.com on 11 Jun 2014 at 1:20

GoogleCodeExporter commented 9 years ago 
This issue was closed by revision r134.

Original comment by dennis.s...@gmail.com on 14 Jun 2014 at 2:37