Regarding Observation 13713563 … whats the failure reason?
Hi @lanzo and welcome in the community!
It is marked as failed as the station didn’t upload any artifacts (observation results like waterfall/audio/data). This may caused by satnogs-client crashing or something else.
The best way to debug this is to follow the troubleshooting guide and check the logs to see if there is an error.
Thank you 
hi lanzo, please check your station config
it should be:
look at satnogs_antenna variable, it should be:
SATNOGS_ANTENNA=RX
Thanks bali:) i did that and finally got my first signal. Appreciate it.
2 Likes
DId by any chance you also check the gain ? SatNOGS Network - Observation 13725717 it’s automatically vetted as good cause the system thinks there was some kind of data available, but I notice your gain is (was ?) not set if I read the metadata right ?
Oh yeah, just set it. Thanks!
2 Likes
Looks much better
To disappoint you a bit, the NOAA’s are no longer transmitting APT in 137 MHz for half a year now.
1 Like
Oh my god😭 it’s my first time using satnogs, what do u suggest me to do? Best option atp?
There are no APT satellites left. If you need to receive weather satellite images the best bet would be to check if / how you can decode the Meteor satellites, for which I think 2 are still operational in 137 MHz
ugh none are giving me any signals. could u check my observations? sorry i’m new and its for a project. thanks btw
Looking at the meta data, I am surprised it is working at all
soapy-rx-device: "RTLSDR",
samp-rate-rx: "2.048e+06",
This should be
soapy-rx-device: "driver=rtlsdr",
samp-rate-rx: "2.048e6",
Jan | PE0SAT
thanks boss, trying again:) also which transmiter and satellite would u recommend for my 137MHz
Run this query and you will see successful METEOR M2-4 observations.
These including frequency and mode.
Jan | PE0SAT
for what project my friends ?
I’m an electrical engineering student and taking a communication course
1 Like