Closed nxugget closed 3 months ago
if you run satdump live
when the satellite is overhead can you produce a waveform?
note that a V-dipole should be facing the direction of the pass ( |< when sat going -->) and ( >| when sat going <--- )
example of a run from today on my device:
/usr/bin/satdump live noaa_apt . --source rtlsdr --samplerate 1.024e6 --frequency 137.6200e6 --satellite_number 15 --source_id 0 --gain 31.0 --start_timestamp 1714223568 --sdrpp_noise_reduction --http_server 0.0.0.0:8081 --timeout 923 >> /var/log/raspberry-noaa-v2/output.log 2>&1
of course this needs to be adjusted to your own test, these are now numbers in the past.
I don't really know how satdump works. But the issue is not here. Because even with WXtoIMG, I have nothing, only noise.
Furthermore, the spectrogram doesn't show anything.
I don't know if there is a link but when I use the test_reception.sh
, I don't heard anything when I'm connect with ncat
.
My antenna seems totally correct. I didn't touch it and before it worked. I test it and it has SWR of 1.3, and impedance of 43Ω. I really don't know what I did... :(
Also, I checked prediction pass on AMSAT and I see the next pass in UTC for my location is at 19:51.
But, on the Raspberry, in UTC+2, I see the pass at 20:10 when it should be 21:51:
Knowing that I have this empty spectrogram, maybe the capture doesn't start at the right time.
ya, that would confirm that at a minimum you aren't configured correctly somewhere. possibly raspi-config
to check localisation options? I would guess you have a 30 minute offset
note that an additional 10 minute difference can also come up based on the minimum sat angle you're assuming, the higher the cutoff the later in the pass you're scheduled for (vs the AMSAT lookup).
if you've mis-assigned your location, double check your lat / long in the settings.yml
then re-run the install_update
script.
I wouldn't expect the TLEs to be a problem, but its odd that gpredict would act up. perhaps run that directly in the terminal as well against a NOAA TLE?
(in schedule_captures
you can see the CLI usage ` predict_start=$($PREDICT -t $TLE_FILE -p "${OBJ_NAME}" "${next_predict}" | head -1)'.
that aside, if you're having trouble with the timing we can at least confirm your antenna + line-of-sight-to-sky + other implementation details with the prior suggested solution of running satdump directly (or satdump-ui
if you have a monitor to click around in)
Ok, I try with predict
:
user@noaa:~ $ predict -t /home/user/.config/satdump/satdump_tles.txt -p "NOAA 19" | head -1
1714589415 Wed 01May24 18:50:15 0 110 231 31 330 3387 78481 * 0.000000
Results correlate with AMSAT :
But, on the server with UTC+2 :
I checked lat / long on settings.yml
and it's good.
I'm waiting for the next pass to try with SatDump.
Hi, Captures don't work or if they work, I only have noise. I checked
output.log
and I got this :Server information
I don't understand because it used to be working before... I precise that I use a V-dipole antenna with a SWR of 1.3, and impedance of 43Ω without LNA Thanks in advance for your help :)