I put this post here, because I don’t know where I have to post it.
If it disturbs I will delete it.
My question is the following:
I am a new SatNOGS user. And since the beginning of I built it.
In every record I did with the SatNOGS software I never send the data on the network.
Like today, three times I tried to do an observations but no data was send.
The last message with the access to the ground-station " IP:5000 " is :
" [INFO]: Tracking stopped. " or " [ERROR]: No waterfall data file found. "
Did I miss configure something or forget something to do ?
Thank you in advance for your advice and comments.
Yes, the groundstation is in the list in Orange #125 “CSU test station v0”.
And I check the API, it is correct.
Yes, I can click on the “Schedule” button and after on the “Calculate” button too.
To every pass I watch it by the IP:5000 to understand the global process and the different step. But I don’t understand, and this is why I create this topic. Maybe I misconfigure something or I forgot something, I don’t know why but the data are never sent to the network.
OK …It looks like you are scheduling passes, but all of your tests are failing. Are you marking them failed? Or are they not running?
Start with scheduling the satellites with the most signal and schedule only passes that are directly overhead. Schedule those that are green all the way across.
What I want to see next is if your RTL-SDR’s gain was properly set.
I poked around a bit today and remembered what the problem is with fcd: the sample rates are too low and fixed at a rate that is not compatible with our gnuradio scripts (in the way they are written today). The original funcube dongle is 96kHz and the pro+ is 192kHz… Our first decimation calculation divides the incoming sample_rate by 250k.
So… the funcube dongle is feasible but only after refactoring all of our gnuradio scripts and filters, which I can’t quite estimate when such a task would be done (or by whom).
I think you’re mixing things up:
Our first stages decimates the input signal to match an output sampling rate of 250 k samples per second - with an rtlsdr sampling at 1 MHz the first stage decimation is set to 4.
I could offer you to make a testing script using an arbitrary resampler to resample the output of the fcd to match 250 k sps also.
This might be an easy way to enable them, but it is highly experimental and needs some testing.
P.S.: I don’t have an fcd so there’s limited debug capabilities…