Signal vetting gone wrong

Why are my observations being vetted as failed when there is signal in the waterfall and when there is data present? Has something been broken in the programming?

@nigel if the difference of audio duration and scheduled duration is more than 1min then the observation is automatically change to failed as probably something went wrong. If you see signal in waterfall then you can vet the waterfall as “has signal” and the status of the observation will change to good.

Check also this recent thread about vetting.

1 Like

Hi Nigel,

I had a similar issue this morning and I changed parameter ‘SATNOGS_RX_SAMP_RATE’ and decreased value from 2.048e6 to 1.024e6 and problem was solved !

Best 73’s Benoit ON3ZZT