British Forum > OGN-R PilotAware
New ATOM Ground station SDR Detection Issues
kevkdg:
Hi,
PWUKFUF/UKRUF is a new ATOM ground station, previously only an OGN station.
Having a few issues with detecting SDR's as pasted below and being looked into by the PAW Team (Keith/Chris/Lee).
However, are there any useful commands that can be run without the need to run config every time. For example to reboot the Pi, check the SDR status's?
Regards
Kevin
Config From 19th Dec (First time running after setting up ground station hardware and interestingly the FLARM antenna was NOT plugged into USB Bottom Right but into the Top Left):
(15:32:36) FILESYS : Mount RW
Stopping Services
Do not plug in or remove any SDR dongles whilst this configuration script is running.
It is strongly advised to have the SDR's plugged in and then reboot the Pi before running this configuration script.
Found 2 SDR's:
USB Port Top Left : SDR detected ID=1 currently unallocated
USB Port Bottom Left : no SDR detected
USB Port Top Right : no SDR detected
USB Port Bottom Right: SDR detected ID=0 currently allocated to OGN/FLARM reception on 868Mhz
One SDR is currently configured for OGN and you have an unallocated SDR which could be used for ADS-B reception.
Config From 20th Dec (Picked up both dongles and assigned correct ID’s as per the Instruction Manual – ID=1 to OGN/FLARM and ID=0 to ADSB AFTER initially complaining of conflicting SDR serial numbers and following a couple of reboots):
(19:47:31) FILESYS : Mount RW
Stopping Services
Do not plug in or remove any SDR dongles whilst this configuration script is running.
It is strongly advised to have the SDR's plugged in and then reboot the Pi before running this configuration script.
Found 2 SDR's:
USB Port Top Left : SDR detected ID=1 currently allocated to OGN/FLARM reception on 868Mhz
USB Port Bottom Left : no SDR detected
USB Port Top Right : no SDR detected
USB Port Bottom Right: SDR detected ID=0 currently allocated to ADS-B reception on 1090Mhz
One SDR is currently configured for OGN and the other is configured for ADS-B reception.
No tinkering post the above config.... until today (27th) as noticed FLARM was not working:
Config Attempt 1 (27th Dec following FLARM dropout) – Issue appears to be the same serial numbers allocated to both SDR’s – How can this happen given nobody has done anything on the Pi since the above config run on 20th?:
(11:40:57) FILESYS : Mount RW
Stopping Services
Do not plug in or remove any SDR dongles whilst this configuration script is running.
It is strongly advised to have the SDR's plugged in and then reboot the Pi before running this configuration script.
Found 2 SDR's:
WARNING: Either an SDR has no serial number or two or more SDR's have identical serial numbers.
The configuration can only continue once all SDR's have unique serial numbers assighned.
The SDR's will now have their serial numbers changed to randomly assigned values and a reboot will be required.
If any of the SDR's are plugged into a powered USB hub then the hub will also need to be powered down at the same time.
Proceed with updating the serial numbers and reboot [Y/n]: y
SDRs renamed - rebooting in 10 seconds
Please rerun config afterwards
Config Attempt 2 (Following Re-Boot) Picked up ADSB/1090 in correct USB Port:
(11:45:53) FILESYS : Mount RW
Stopping Services
Do not plug in or remove any SDR dongles whilst this configuration script is running.
It is strongly advised to have the SDR's plugged in and then reboot the Pi before running this configuration script.
Found 1 SDR:
USB Port Top Left : no SDR detected
USB Port Bottom Left : no SDR detected
USB Port Top Right : no SDR detected
USB Port Bottom Right: SDR detected ID=0 currently allocated to ADS-B reception on 1090Mhz
SDR's serial changed to 868
Do you want to set a Password (recommended first time) [y/N]:
Config Attempt 3 (Now only picks up FLARM in correct USB Port but is assigning ID=0 which was the ADSB assigned number) - Not sure why ADSB/1090 SDR is no longer being detected as it was only a few minutes ago:
(11:47:12) FILESYS : Mount RW
Stopping Services
Do not plug in or remove any SDR dongles whilst this configuration script is running.
It is strongly advised to have the SDR's plugged in and then reboot the Pi before running this configuration script.
Found 1 SDR:
USB Port Top Left : SDR detected ID=0 currently allocated to OGN/FLARM reception on 868Mhz
USB Port Bottom Left : no SDR detected
USB Port Top Right : no SDR detected
USB Port Bottom Right: no SDR detected
Config Attempt 4:
(11:48:16) FILESYS : Mount RW
Stopping Services
Do not plug in or remove any SDR dongles whilst this configuration script is running.
It is strongly advised to have the SDR's plugged in and then reboot the Pi before running this configuration script.
Found 1 SDR:
USB Port Top Left : SDR detected ID=0 currently allocated to OGN/FLARM reception on 868Mhz
USB Port Bottom Left : no SDR detected
USB Port Top Right : no SDR detected
USB Port Bottom Right: no SDR detected
steveu:
The important thing is NOT to mess with the software on it...
The only command I can suggest is lsusb. All it does is ask the question, what's happening in USB land on this Pi?
--- Code: ---pi@ognpaw:~ $ lsusb
Bus 001 Device 006: ID 1a2c:2124 China Resource Semico Co., Ltd
Bus 001 Device 005: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
Bus 001 Device 004: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pi@ognpaw:~ $
--- End code ---
Here you can see the question has been asked and the Pi says there are two SDRs connected, and gives the device ID and the manufacturer.
There is also a keyboard connected, as I am a terminal based dinosaur.
If this list only gave you one SDR, then you know there is an issue.
My suggestion, not endorsed by PilotAware - I used short USB extension leads so the weight and bending action of the heavy SDR would not damage the motherboard. If the USB connector flexes, this may cause an issue. I could be wrong and clueless though.
kevkdg:
I ran the lsusb query and then did a sudo reboot and ran config various times, as even when it correctly picked up both SDR's it didn't tune the FLARM, so it looks like it lost it again.
Ended up back where I started with only FLARM up and running, except it seems to one minute locate FLARM SDR in the correct USB socket (Top Left) but then another timein the Bottom Right USB which is where the 1090 antenna SDR is connected. however it seems to tune FLARM OK even when i thinks it is connected to the 1090 USB Port which I don't think it would be able to do using the 1090 antenna!
I am wondering whether it might be a power supply issue??
pi@ognpaw:~ $ lsusb
Bus 001 Device 005: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
sudo roboot
Now it picks up 2 SDR's:
(18:32:09) FILESYS : Mount RW
Stopping Services
Do not plug in or remove any SDR dongles whilst this configuration script is running.
It is strongly advised to have the SDR's plugged in and then reboot the Pi before running this configuration script.
Found 2 SDR's:
WARNING: Either an SDR has no serial number or two or more SDR's have identical serial numbers.
The configuration can only continue once all SDR's have unique serial numbers assighned.
The SDR's will now have their serial numbers changed to randomly assigned values and a reboot will be required.
If any of the SDR's are plugged into a powered USB hub then the hub will also need to be powered down at the same time.
Proceed with updating the serial numbers and reboot [Y/n]:
(18:36:08) FILESYS : Mount RW
Stopping Services
Do not plug in or remove any SDR dongles whilst this configuration script is running.
It is strongly advised to have the SDR's plugged in and then reboot the Pi before running this configuration script.
Found 2 SDR's:
WARNING: Either an SDR has no serial number or two or more SDR's have identical serial numbers.
The configuration can only continue once all SDR's have unique serial numbers assighned.
The SDR's will now have their serial numbers changed to randomly assigned values and a reboot will be required.
If any of the SDR's are plugged into a powered USB hub then the hub will also need to be powered down at the same time.
pi@ognpaw:~ $ lsusb
Bus 001 Device 005: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
Bus 001 Device 004: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Now it has assigned them correctly:
(18:46:20) FILESYS : Mount RW
Stopping Services
Do not plug in or remove any SDR dongles whilst this configuration script is running.
It is strongly advised to have the SDR's plugged in and then reboot the Pi before running this configuration script.
Found 2 SDR's:
USB Port Top Left : SDR detected ID=1 currently allocated to OGN/FLARM reception on 868Mhz
USB Port Bottom Left : no SDR detected
USB Port Top Right : no SDR detected
USB Port Bottom Right: SDR detected ID=0 currently allocated to ADS-B reception on 1090Mhz
One SDR is currently configured for OGN and the other is configured for ADS-B reception.
Test tuning however does not pick up the FLARMM
...
Test tuning of rtl-sdr device=1
Testing --ppm=0 --gain=0
Not enough data was collected
Testing --ppm=0 --gain=5
Not enough data was collected
Testing --ppm=0 --gain=10
Testing --ppm=0 --gain=15
Testing --ppm=0 --gain=20
Testing --ppm=0 --gain=25
Testing --ppm=0 --gain=30
Testing --ppm=0 --gain=35
Testing --ppm=0 --gain=40
Testing --ppm=0 --gain=45
Testing --ppm=0 --gain=50
Not a valid number: _UNDEF_ for option ppm
So re-ran config and back to picking up only 1 SDR (ADSB in the correct Bottom Right USB):
Starting Services
(18:48:45) FILESYS : Mount RW
Stopping Services
Do not plug in or remove any SDR dongles whilst this configuration script is running.
It is strongly advised to have the SDR's plugged in and then reboot the Pi before running this configuration script.
Found 1 SDR:
USB Port Top Left : no SDR detected
USB Port Bottom Left : no SDR detected
USB Port Top Right : no SDR detected
USB Port Bottom Right: SDR detected ID=0 currently allocated to ADS-B reception on 1090Mhz
SDR's serial changed to 868
So re-ran config again still picking up 1 SDR BUT this time OGN/FLARM in correct Top Left USB and correctly tunes it:
(18:49:55) FILESYS : Mount RW
Stopping Services
Do not plug in or remove any SDR dongles whilst this configuration script is running.
It is strongly advised to have the SDR's plugged in and then reboot the Pi before running this configuration script.
Found 1 SDR:
USB Port Top Left : SDR detected ID=0 currently allocated to OGN/FLARM reception on 868Mhz
USB Port Bottom Left : no SDR detected
USB Port Top Right : no SDR detected
USB Port Bottom Right: no SDR detected
...
Testing --ppm=-0 --gain=40
Capture @5ppm inrange=43 outrange=0
Frequency Capture Improvement = 42 -> 43
Receiver Xtal correction = 0-0.474 = -0.474 (0.379) ppm [102]
setting APRS_SDR_PPM=-0
setting APRS_SDR_GAIN=40
So, re-ran config again still picking up 1 SDR OGN/FLARM but now thinks it is positioned in the USB in the Bottom Right instead of Top Left but seems to tune it OK (Bottom Right is 1090):
(18:59:00) FILESYS : Mount RW
Stopping Services
Do not plug in or remove any SDR dongles whilst this configuration script is running.
It is strongly advised to have the SDR's plugged in and then reboot the Pi before running this configuration script.
Found 1 SDR:
USB Port Top Left : no SDR detected
USB Port Bottom Left : no SDR detected
USB Port Top Right : no SDR detected
USB Port Bottom Right: SDR detected ID=0 currently allocated to OGN/FLARM reception on 868Mhz
...
Testing --ppm=-0 --gain=40
Capture @5ppm inrange=43 outrange=0
Frequency Capture Improvement = 41 -> 43
Receiver Xtal correction = 0-0.466 = -0.466 (0.369) ppm [102]
setting APRS_SDR_PPM=-0
setting APRS_SDR_GAIN=40
pi@ognpaw:~ $ lsusb
Bus 001 Device 005: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
steveu:
All I can suggest is that you have intermittent connections to the SDRs, or they are about to croak.
The only thing to double check is that the frequency of the aerial is the correct one in the config program.
You could test the USB sockets by moving to different ones. You need to check the config program has the right SDR + aerial for the socket. If not, the procedure will not receive the signal because of a mismatch, AIUI, between the tuning procedure and the aerial using the wrong aerial to try and tune to a set of frequencies it wasn't designed for.
Check all connections. Check SDR USB into Pi is not strained...
kevkdg:
Thanks, will check.
Navigation
[0] Message Index
[#] Next page
Go to full version