Trying to schedule observation -- "PLL not Locked"

SatNOGS
1

Hello,

We are trying to finally test our setup. We scheduled an observation, and journalctl was listening, and caught the event (the messages in the terminal showed some activity from the regular checking for events), but some messages popped up about “PLL not locked” and nothing else happened (it didn’t move or try to point at its position or anything). It just goes back to listening for more events.

Below are the messages we got from the observation:
raspberrypi satnogs-client[538]: 2019-07-26 17:20:49,019 - apscheduler.executors.default - INFO - Running job “spawn_observer (trigger: date[2019-07-27 00:20:49 UTC], next run at: 2019-07-27 00:20:49 UTC)” (scheduled at 2019-07-27 00:20:49+00:00)
Jul 26 17:20:49 raspberrypi satnogs-client[538]: Exception in thread Thread-9:
Jul 26 17:20:49 raspberrypi satnogs-client[538]: Traceback (most recent call last):
Jul 26 17:20:49 raspberrypi satnogs-client[538]: File “/usr/lib/python2.7/threading.py”, line 801, in __bootstrap_inner
Jul 26 17:20:49 raspberrypi satnogs-client[538]: self.run()
Jul 26 17:20:49 raspberrypi satnogs-client[538]: File “/usr/lib/python2.7/threading.py”, line 754, in run
Jul 26 17:20:49 raspberrypi satnogs-client[538]: self.__target(*self.__args, **self.__kwargs)
Jul 26 17:20:49 raspberrypi satnogs-client[538]: File “/var/lib/satnogs/local/lib/python2.7/site-packages/satnogsclient/observer/worker.py”, line 142, in _status_interface
Jul 26 17:20:49 raspberrypi satnogs-client[538]: sock.bind()
Jul 26 17:20:49 raspberrypi satnogs-client[538]: File “/var/lib/satnogs/local/lib/python2.7/site-packages/satnogsclient/observer/commsocket.py”, line 104, in bind
Jul 26 17:20:49 raspberrypi satnogs-client[538]: self.s.bind((self._TCP_IP, self._TCP_PORT))
Jul 26 17:20:49 raspberrypi satnogs-client[538]: File “/usr/lib/python2.7/socket.py”, line 228, in meth
Jul 26 17:20:49 raspberrypi satnogs-client[538]: return getattr(self._sock,name)(*args)
Jul 26 17:20:49 raspberrypi satnogs-client[538]: error: [Errno 98] Address already in use
Jul 26 17:20:49 raspberrypi satnogs-client[538]: linux; GNU C++ version 6.2.0 20161010; Boost_106100; UHD_003.009.005-0-unknown
Jul 26 17:20:49 raspberrypi satnogs-client[538]: linux; GNU C++ version 6.2.0 20161010; Boost_106100; UHD_003.009.005-0-unknown
Jul 26 17:20:50 raspberrypi satnogs-client[538]: [WARNING] /tmp/dpkg/gr-satnogs/lib/cw_to_symbol_impl.cc:106: Dot symbol samples: 720
Jul 26 17:20:50 raspberrypi satnogs-client[538]: [WARNING] /tmp/dpkg/gr-satnogs/lib/cw_to_symbol_impl.cc:107: Window size: 60
Jul 26 17:20:50 raspberrypi satnogs-client[538]: gr-osmosdr 0.1.4 (0.1.4) gnuradio 3.7.10
Jul 26 17:20:50 raspberrypi satnogs-client[538]: built-in source types: file osmosdr fcd rtl rtl_tcp uhd miri hackrf bladerf rfspace airspy soapy redpitaya
Jul 26 17:20:50 raspberrypi satnogs-client[538]: Using device #0 Realtek RTL2838UHIDIR SN: 00000001
Jul 26 17:20:50 raspberrypi satnogs-client[538]: Using 32 buffers of size 16384.
Jul 26 17:20:50 raspberrypi satnogs-client[538]: Found Rafael Micro R820T tuner
Jul 26 17:20:51 raspberrypi satnogs-client[538]: [R82XX] PLL not locked!
Jul 26 17:20:51 raspberrypi satnogs-client[538]: Exact sample rate is: 1000000.026491 Hz
Jul 26 17:20:51 raspberrypi satnogs-client[538]: [R82XX] PLL not locked!

We’re fairly inexperienced with this stuff, so we don’t know what the issue is exactly. Any ideas?

2

Hello!

Are you using the latest version from the master branch? The error message of interest here is the “Jul 26 17:20:49 raspberrypi satnogs-client[538]: error: [Errno 98] Address already in use” which means that some socket is trying to bind to a port that is already being used by someone else.

3

This ‘error’ seems to be fairly common when starting up the R820T/T2 tuner SDRs. It doesn’t seem to affect performance or operation in any way. Your other error is probably the issue!

4

Actually there’s no error that will stop a station from working. The address all ready in use is also pretty common with Satnogs.

5

Hm. Do you have any ideas for why I’m not seeing expected behavior then?

By the way am I right in assuming that what should happen at the observation time is that the rotator should point to the path of the satellite and follow it during its window?

6

You are right on that. Could you copy paste your current settings in satnogs-setup (Don’t forget to hide the API KEY).

7

Is this what you need?

8

PLL not Locked
Most likely USB cable