Only NOAA demodulated - never CW or anything else. Observation 1658792: XW-2E (40909)

SatNOGS Software
1

Regarding Observation 1658792 …

I’m new here!

I’m starting to think I have an issue. NOAA APT demods and decodes fine every time - but nothing else is being demodulated.

Am I doing something wrong?

Here’s log for the mentioned observation:
Feb 07 06:24:09 raspberrypi satnogs-client[297]: 2020-02-07 06:24:09,061 - satnogsclient.observer.commsocket - ERROR - Cannot connect to socket 127.0.0.1:4533
Feb 07 06:24:09 raspberrypi satnogs-client[297]: 2020-02-07 06:24:09,064 - satnogsclient.observer.commsocket - ERROR - Cannot connect to socket 127.0.0.1:4533
Feb 07 06:24:09 raspberrypi satnogs-client[297]: 2020-02-07 06:24:09,065 - satnogsclient.observer.commsocket - ERROR - Cannot send to socket 127.0.0.1:4533
Feb 07 06:24:09 raspberrypi satnogs-client[297]: Exception in thread Thread-9:
Feb 07 06:24:09 raspberrypi satnogs-client[297]: Traceback (most recent call last):
Feb 07 06:24:09 raspberrypi satnogs-client[297]: File “/usr/lib/python2.7/threading.py”, line 801, in __bootstrap_inner
Feb 07 06:24:09 raspberrypi satnogs-client[297]: self.run()
Feb 07 06:24:09 raspberrypi satnogs-client[297]: File “/usr/lib/python2.7/threading.py”, line 754, in run
Feb 07 06:24:09 raspberrypi satnogs-client[297]: self.__target(*self.__args, **self.__kwargs)
Feb 07 06:24:09 raspberrypi satnogs-client[297]: File “/var/lib/satnogs/local/lib/python2.7/site-packages/satnogsclient/observer/worker.py”, line 112, in _communicate_tracking_info
Feb 07 06:24:09 raspberrypi satnogs-client[297]: self.send_to_socket(pin, sock)
Feb 07 06:24:09 raspberrypi satnogs-client[297]: File “/var/lib/satnogs/local/lib/python2.7/site-packages/satnogsclient/observer/worker.py”, line 198, in send_to_socket
Feb 07 06:24:09 raspberrypi satnogs-client[297]: position = sock.send(“p\n”).split(’\n’)
Feb 07 06:24:09 raspberrypi satnogs-client[297]: File “/var/lib/satnogs/local/lib/python2.7/site-packages/satnogsclient/observer/commsocket.py”, line 81, in send
Feb 07 06:24:09 raspberrypi satnogs-client[297]: response = self.sock.recv(self._tasks_buffer_size).decode(‘ascii’)
Feb 07 06:24:09 raspberrypi satnogs-client[297]: error: [Errno 107] Transport endpoint is not connected
Feb 07 06:24:11 raspberrypi satnogs-client[297]: [WARNING] /usr/src/packages/BUILD/lib/cw_to_symbol_impl.cc:112: Dot symbol samples: 654
Feb 07 06:24:11 raspberrypi satnogs-client[297]: [WARNING] /usr/src/packages/BUILD/lib/cw_to_symbol_impl.cc:113: Window size: 109
Feb 07 06:24:11 raspberrypi satnogs-client[297]: gr-osmosdr 0.1.4 (0.1.4) gnuradio 3.7.13.4
Feb 07 06:24:11 raspberrypi satnogs-client[297]: built-in source types: file osmosdr fcd rtl rtl_tcp uhd miri hackrf bladerf rfspace airspy airspyhf soapy redpitaya freesrp
Feb 07 06:24:11 raspberrypi satnogs-client[297]: Using device #0 Realtek RTL2838UHIDIR SN: 00000001
Feb 07 06:24:11 raspberrypi satnogs-client[297]: Using 32 buffers of size 16384.
Feb 07 06:24:11 raspberrypi satnogs-client[297]: Found Rafael Micro R820T tuner
Feb 07 06:24:12 raspberrypi satnogs-client[297]: [R82XX] PLL not locked!
Feb 07 06:24:12 raspberrypi satnogs-client[297]: Exact sample rate is: 1000000.026491 Hz
Feb 07 06:24:12 raspberrypi satnogs-client[297]: [R82XX] PLL not locked!
Feb 07 06:24:12 raspberrypi satnogs-client[297]: Allocating 32 zero-copy buffers

1 Like
2

I don’t know if this is related but I’m getting a bunch of 403’s with error log level “INFO”.

Feb 07 13:27:23 raspberrypi satnogs-client[12224]: 2020-02-07 13:27:23,209 - apscheduler.scheduler - INFO - Added job “spawn_observer” to job store “default”
Feb 07 13:27:23 raspberrypi satnogs-client[12224]: 2020-02-07 13:27:23,214 - satnogsclient.scheduler.tasks - INFO - Adding new job: 1660334
Feb 07 13:27:23 raspberrypi satnogs-client[12224]: 2020-02-07 13:27:23,218 - apscheduler.scheduler - INFO - Added job “spawn_observer” to job store “default”
Feb 07 13:27:23 raspberrypi satnogs-client[12224]: 2020-02-07 13:27:23,223 - satnogsclient.scheduler.tasks - INFO - Adding new job: 1660338
Feb 07 13:27:23 raspberrypi satnogs-client[12224]: 2020-02-07 13:27:23,228 - apscheduler.scheduler - INFO - Added job “spawn_observer” to job store “default”
Feb 07 13:27:23 raspberrypi satnogs-client[12224]: 2020-02-07 13:27:23,230 - apscheduler.executors.default - INFO - Job “get_jobs (trigger: interval[0:01:00], next run at: 2020-02-07 13:28:22 UTC)” executed successfully
Feb 07 13:27:23 raspberrypi satnogs-client[12224]: 2020-02-07 13:27:23,712 - satnogsclient.scheduler.tasks - ERROR - Bad status code: 403
Feb 07 13:27:23 raspberrypi satnogs-client[12224]: 2020-02-07 13:27:23,713 - satnogsclient.scheduler.tasks - INFO - Trying to PUT observation data for id: 1660332
Feb 07 13:27:27 raspberrypi satnogs-client[12224]: 2020-02-07 13:27:27,143 - satnogsclient.scheduler.tasks - ERROR - Bad status code: 403
Feb 07 13:27:27 raspberrypi satnogs-client[12224]: 2020-02-07 13:27:27,144 - satnogsclient.scheduler.tasks - INFO - Trying to PUT observation data for id: 1660269
Feb 07 13:27:28 raspberrypi satnogs-client[12224]: 2020-02-07 13:27:28,260 - satnogsclient.scheduler.tasks - ERROR - Bad status code: 403
Feb 07 13:27:28 raspberrypi satnogs-client[12224]: 2020-02-07 13:27:28,264 - satnogsclient.scheduler.tasks - INFO - Trying to PUT observation data for id: 1660269
Feb 07 13:27:32 raspberrypi satnogs-client[12224]: 2020-02-07 13:27:32,584 - satnogsclient.scheduler.tasks - ERROR - Bad status code: 403
Feb 07 13:27:32 raspberrypi satnogs-client[12224]: 2020-02-07 13:27:32,589 - satnogsclient.scheduler.tasks - INFO - Trying to PUT observation data for id: 1660331
Feb 07 13:27:33 raspberrypi satnogs-client[12224]: 2020-02-07 13:27:33,568 - satnogsclient.scheduler.tasks - ERROR - Bad status code: 403
Feb 07 13:27:33 raspberrypi satnogs-client[12224]: 2020-02-07 13:27:33,573 - satnogsclient.scheduler.tasks - INFO - Trying to PUT observation data for id: 1660331
Feb 07 13:27:35 raspberrypi satnogs-client[12224]: 2020-02-07 13:27:35,533 - satnogsclient.scheduler.tasks - ERROR - Bad status code: 403
Feb 07 13:27:35 raspberrypi satnogs-client[12224]: 2020-02-07 13:27:35,540 - satnogsclient.scheduler.tasks - INFO - Trying to PUT observation data for id: 1660270
Feb 07 13:27:39 raspberrypi satnogs-client[12224]: 2020-02-07 13:27:39,205 - satnogsclient.scheduler.tasks - ERROR - Bad status code: 403
Feb 07 13:27:39 raspberrypi satnogs-client[12224]: 2020-02-07 13:27:39,210 - satnogsclient.scheduler.tasks - INFO - Trying to PUT observation data for id: 1660337
Feb 07 13:27:40 raspberrypi satnogs-client[12224]: 2020-02-07 13:27:40,763 - satnogsclient.scheduler.tasks - ERROR - Bad status code: 403
Feb 07 13:27:40 raspberrypi satnogs-client[12224]: 2020-02-07 13:27:40,768 - satnogsclient.scheduler.tasks - INFO - Trying to PUT observation data for id: 1660330
Feb 07 13:27:42 raspberrypi satnogs-client[12224]: 2020-02-07 13:27:42,861 - satnogsclient.scheduler.tasks - ERROR - Bad status code: 403
Feb 07 13:27:42 raspberrypi satnogs-client[12224]: 2020-02-07 13:27:42,867 - satnogsclient.scheduler.tasks - INFO - Trying to PUT observation data for id: 1660332
Feb 07 13:27:43 raspberrypi satnogs-client[12224]: 2020-02-07 13:27:43,927 - satnogsclient.scheduler.tasks - ERROR - Bad status code: 403
Feb 07 13:27:43 raspberrypi satnogs-client[12224]: 2020-02-07 13:27:43,931 - satnogsclient.scheduler.tasks - INFO - Trying to PUT observation data for id: 1660337
Feb 07 13:27:45 raspberrypi satnogs-client[12224]: 2020-02-07 13:27:45,185 - satnogsclient.scheduler.tasks - ERROR - Bad status code: 403
Feb 07 13:27:45 raspberrypi satnogs-client[12224]: 2020-02-07 13:27:45,189 - satnogsclient.scheduler.tasks - INFO - Trying to PUT observation data for id: 1660330
Feb 07 13:27:46 raspberrypi satnogs-client[12224]: 2020-02-07 13:27:46,327 - satnogsclient.scheduler.tasks - ERROR - Bad status code: 403
Feb 07 13:27:46 raspberrypi satnogs-client[12224]: 2020-02-07 13:27:46,345 - apscheduler.executors.default - INFO - Job “post_data (trigger: interval[0:02:00], next run at: 2020-02-07 13:29:22 UTC)” executed successfully
Feb 07 13:28:22 raspberrypi satnogs-client[12224]: 2020-02-07 13:28:22,753 - apscheduler.executors.default - INFO - Running job “get_jobs (trigger: interval[0:01:00], next run at: 2020-02-07 13:29:22 UTC)” (scheduled at 2020-02-07 13:28:22.750445+00:00)
Feb 07 13:28:22 raspberrypi satnogs-client[12224]: 2020-02-07 13:28:22,754 - satnogsclient.scheduler.tasks - INFO - Get jobs started
Feb 07 13:28:22 raspberrypi satnogs-client[12224]: 2020-02-07 13:28:22,755 - satnogsclient.scheduler.tasks - INFO - Trying to GET observation jobs from the network
Feb 07 13:28:23 raspberrypi satnogs-client[12224]: 2020-02-07 13:28:23,154 - satnogsclient.scheduler.tasks - INFO - Adding new job: 1660553
Feb 07 13:28:23 raspberrypi satnogs-client[12224]: 2020-02-07 13:28:23,157 - apscheduler.scheduler - INFO - Added job “spawn_observer” to job store “default”
Feb 07 13:28:23 raspberrypi satnogs-client[12224]: 2020-02-07 13:28:23,161 - satnogsclient.scheduler.tasks - INFO - Adding new job: 1660552
Feb 07 13:28:23 raspberrypi satnogs-client[12224]: 2020-02-07 13:28:23,164 - apscheduler.scheduler - INFO - Added job “spawn_observer” to job store “default”
Feb 07 13:28:23 raspberrypi satnogs-client[12224]: 2020-02-07 13:28:23,167 - satnogsclient.scheduler.tasks - INFO - Adding new job: 1660550
Feb 07 13:28:23 raspberrypi satnogs-client[12224]: 2020-02-07 13:28:23,170 - apscheduler.scheduler - INFO - Added job “spawn_observer” to job store “default”
Feb 07 13:28:23 raspberrypi satnogs-client[12224]: 2020-02-07 13:28:23,174 - satnogsclient.scheduler.tasks - INFO - Adding new job: 1660549
Feb 07 13:28:23 raspberrypi satnogs-client[12224]: 2020-02-07 13:28:23,178 - apscheduler.scheduler - INFO - Added job “spawn_observer” to job store “default”
Feb 07 13:28:23 raspberrypi satnogs-client[12224]: 2020-02-07 13:28:23,182 - satnogsclient.scheduler.tasks - INFO - Adding new job: 1660334
Feb 07 13:28:23 raspberrypi satnogs-client[12224]: 2020-02-07 13:28:23,186 - apscheduler.scheduler - INFO - Added job “spawn_observer” to job store “default”
Feb 07 13:28:23 raspberrypi satnogs-client[12224]: 2020-02-07 13:28:23,190 - satnogsclient.scheduler.tasks - INFO - Adding new job: 1660338
Feb 07 13:28:23 raspberrypi satnogs-client[12224]: 2020-02-07 13:28:23,194 - apscheduler.scheduler - INFO - Added job “spawn_observer” to job store “default”
Feb 07 13:28:23 raspberrypi satnogs-client[12224]: 2020-02-07 13:28:23,196 - apscheduler.executors.default - INFO - Job “get_jobs (trigger: interval[0:01:00], next run at: 2020-02-07 13:29:22 UTC)” executed successfully

1 Like
3

as answered on Riot.im:

On 2m there is not much “demodulatable” activity :slight_smile:

CW demodulation should become better once the new version of gr-satnogs is released more widely on production for stations to deploy (our test stations are reporting good results with it). Also your signals seem kinda weak overall, please check your antenna and/or LNA

Cheers and welcome to SatNOGS!

4

also the first errors you posted are unrelated (and should disappear with an update soon)
As for the second set of errors seems like a mistake on your API key? Can you check?

1 Like
5

Thank you so much for getting back to me! I really appreciate it! I got disconnected on freenode.

I’m just confused as some of the observations have quite strong signals - and others of course not. But out of 100 observations not a single one was demodulated other than NOAA. And they are certainly strong enough that fldigi is able to decode them. Would I get an error if demodulation wasn’t running?

Can I test it manually? I noticed the satnogs_cw_decoder.py script. Can I manually use that with the observation ogg files to test? I can’t seem to figure out if it’s possible or the relevant syntax?

API key correct, so the 403’s make no sense. I also doubt NOAA would demodulate and upload fine if that was the issue.

1 Like
6

My confusion is that an observation like this isn’t demodulated - not even partially: https://network.satnogs.org/observations/1662327/

But this is:
https://network.satnogs.org/observations/1661627/

1 Like
7

Actually both of the are not. The second one is false demodulations.

@surligas has pushed some updates on the CW demodulator and soon those will be in production and you will be able to get results like this:

https://network.satnogs.org/observations/1650780/

1 Like
8

Yeah, absolutely false demodulations. I was just expecting I would at least get a few of those instead of no data at all for anything but NOAA. Also have a bunch of 70cm observations that also look like they would at least get a partial demod. A lot of AAUSAT4 ones that I usually don’t have issues decoding with hs_soundmodem for instance.

I hear you saying that my setup is probably working as intended though, so I will work on improving my reception. … and build a rotator.

Thank you very much!

1 Like
9

I think you are using a dipole +LNA… Where is located the LNA?
Could you try using another antena without LNA?
Or even the dipole without LNA?
Sometimes the LNA is not a help…
Look at my station, is running without LNA, right now with a vertical antenna
https://network.satnogs.org/stations/342/

1 Like
10

The LNA is connected before the coax, running off the RTL-SDR biasT. It’s not giving me much but it is giving me something. It a generic 5V thing but I think I’ll test with a 12v LNA+external biasT soon.
I have a nanoVNA coming - hopefully that can tell me something I don’t know about my antenna.
Also - I’m surrounded by taller buildings so I need pretty good passes.

Maybe my dev-args for enabling the biasT is messing things up without giving any errors but I can’t seem to dig deep enough to figure out if it’s affecting demodulation.

rtl,buffers=32,buflen=16384,bias=1

I really need a house instead of a city apartment :slight_smile:

2 Likes
11

And what about a QFH antenna?

1 Like
12

Absolutely thought about making one but since I’m making a rotator for my yagi it seems superfluous.
Time is so expensive :slight_smile:

2 Likes
13

Yes, of course, if you can yagi+rotator it’s the best option

1 Like
14

I see a cw_to_symbol warning - what does this mean?
Feb 12 08:43:11 raspberrypi satnogs-client[2604]: [WARNING] /usr/src/packages/BUILD/lib/cw_to_symbol_impl.cc:112: Dot symbol samples: 654

In context:

Feb 12 08:43:09 raspberrypi satnogs-client[2604]: Traceback (most recent call last):
Feb 12 08:43:09 raspberrypi satnogs-client[2604]: File “/usr/lib/python2.7/threading.py”, line 801, in __bootstrap_inner
Feb 12 08:43:09 raspberrypi satnogs-client[2604]: self.run()
Feb 12 08:43:09 raspberrypi satnogs-client[2604]: File “/usr/lib/python2.7/threading.py”, line 754, in run
Feb 12 08:43:09 raspberrypi satnogs-client[2604]: self.__target(*self.__args, **self.__kwargs)
Feb 12 08:43:09 raspberrypi satnogs-client[2604]: File “/var/lib/satnogs/local/lib/python2.7/site-packages/satnogsclient/observer/worker.py”, line 112, in _communicate_tracking_info
Feb 12 08:43:09 raspberrypi satnogs-client[2604]: self.send_to_socket(pin, sock)
Feb 12 08:43:09 raspberrypi satnogs-client[2604]: File “/var/lib/satnogs/local/lib/python2.7/site-packages/satnogsclient/observer/worker.py”, line 198, in send_to_socket
Feb 12 08:43:09 raspberrypi satnogs-client[2604]: position = sock.send(“p\n”).split(‘\n’)
Feb 12 08:43:09 raspberrypi satnogs-client[2604]: File “/var/lib/satnogs/local/lib/python2.7/site-packages/satnogsclient/observer/commsocket.py”, line 81, in send
Feb 12 08:43:09 raspberrypi satnogs-client[2604]: response = self.sock.recv(self._tasks_buffer_size).decode(‘ascii’)
Feb 12 08:43:09 raspberrypi satnogs-client[2604]: error: [Errno 107] Transport endpoint is not connected
Feb 12 08:43:11 raspberrypi satnogs-client[2604]: [WARNING] /usr/src/packages/BUILD/lib/cw_to_symbol_impl.cc:112: Dot symbol samples: 654
Feb 12 08:43:11 raspberrypi satnogs-client[2604]: [WARNING] /usr/src/packages/BUILD/lib/cw_to_symbol_impl.cc:113: Window size: 109