Thanks very much for the link to your ‘satcom’ module for this project!
For anyone interested in using the Team’s GRC blocks, cloning & installing their off-line ‘satcom’ module does indeed allow the ‘OpenLST Deframe+Decode’ block to run without error: (thanks PE0SAT for the DORA flowgraph & sample files).
git clone https://github.com/antaris-inc/python-satcom.git
cd python-satcom/
pip install -e ./
Regarding ELEVATION-1, as of the time of this post there don’t appear to be any likely signals in the SatNogs observations thus far on 400.200.
Additionally, here over the Eastern U.S., N6RFM and myself monitored 2 passes with nothing seen either.
Does ELEVATION-1 transmit 24/7 world-wide? Are you currently seeing packets on 400.200 at your station?
Thanks for any additional info!
Please disregard my question about any downlink from ELEVATION-1 on 400.200; we have contact! (Thank you for the ASCII text in some of your payloads - very helpful!)
@K4KDR Yep, you got it! That would be ELEVATION-1. Thanks for sharing the success here. Could you also share the pass details? Location/timing/etc would be much appreciated.
Thank you for providing enough detail that RX & decode was possible!
Just posted at the link below - please let me know if I can share anything more.
I haven’t seen any obs over Europe, is this as expected ?
Scott,
Do you have an IQ that isn’t Doppler compensated, if so, then we can use it to try and create and TLE set.
An audio replay from this observation SatNOGS Network - Observation 10958143 also confirms that ELEVATION-1 is active.
***** VERBOSE PDU DEBUG PRINT ******
((transmitter . 7k4 FSK downlink))
pdu length = 169 bytes
pdu vector contents =
0000: 40 1e 00 00 00 96 f8 fd 00 a5 aa 40 00 54 6d 38
0010: 23 00 00 00 92 80 00 02 af 03 1f 00 87 00 48 69
0020: 2c 49 20 61 6d 20 45 6c 65 76 61 74 69 6f 6e 00
0030: ff 53 6d 38 00 00 00 00 00 00 00 00 00 00 00 00
0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0070: 00 02 29 00 00 00 0a 00 08 00 00 00 6d f2 72 00
0080: 1d 00 00 05 03 00 18 36 00 00 00 00 00 00 00 00
0090: a0 13 be 79 06 18 06 00 00 00 00 00 00 00 00 20
00a0: fb d3 1a 03 2c b6 ba 0f 00
************************************
cat <frame> | xxd -r -p
@�����@Tm8#����Hi,I am Elevation�Sm8)m�r6��y ��␦,��
Just uploaded a crop of today’s I/Q containing the ELEVATION-1 packets.
32-bit float, Sample-Rate 93750:
https://www.qsl.net/k/k4kdr//iq/elevation-1/
[Update]
… just dawned on me that an I/Q for orbit determination is worthless without a known start time. The file linked to above starts at:
2025-01-21_15:59:30 UTC (center freq = 400.200 MHz)
I had a quick look with Inspectrum, I get the impression it is a Doppler corrected IQ recording, can please confirm.
No, GQRX records without correction.
The packets were close together, so don’t vary much in frequency. The last two perhaps more than the first bunch.
Here is a portion (all that I can fit on one screen) from inspectrum that illustrates the doppler w/ help from the marker lines:
Thanks Scott,
Lets see if we can convert them with the help of rffft, my first attempt failed. Without the bin files I can’t use rfplot and rffit to create a TLE set.
This would be the ideal command:
rffft -P -i gqrx_YYYYMMDD_HHMMSS_97400000_2000000_fc.raw but then I need your help to rename the file.
Sure thing!
So the name of the I/Q file provided at my download URL should be changed to:
gqrx_20250121_155930_400200000_93750_fc.raw
to match that format.
And now I get a segfault 
We have generated a new TLE for Innocube with strf.
This one:
1 98709U 25017.43692333 .00000000 00000-0 -67463-3 0 04
2 98709 97.4389 100.1866 0007295 359.8410 132.1652 15.16264502 02
However, I am unsure how we can update the TLEs in the Database.
Any guidance?
Tag @fredy when you have new TLE data and sharing the information on the Matrix channel is also a good idea.
Unfortunately there isn’t currently a way to suggest or add TLE changes in DB, so this needs to be passed by me. As @PE0SAT noted you can ping me here or in the matrix channel and add the TLE set in DB as soon as possible.
Updated TLE for the two ION deployers and based on these, TLE for the expected to be deployed from those deployers today satellites:
ION SCV-016
1 98668U 25009BY 25021.90669764 .00000000 00000-0 -14212-2 0 06
2 98668 97.4429 104.2661 0003354 352.9277 63.3351 15.17186318 06
ION SCV-014
1 98669U 25009BT 25021.90719310 .00000000 00000-0 -13026-2 0 02
2 98669 97.4432 104.4033 0003136 350.0649 69.5167 15.17207909 09
Sedna-2
1 98661U 25009BY 25021.90669764 .00000000 00000-0 -14212-2 0 09
2 98661 97.4429 104.2661 0003354 352.9277 63.3351 15.17186318 09
HADES-R
1 98710U 25009BY 25021.90669764 .00000000 00000-0 -14212-2 0 04
2 98710 97.4429 104.2661 0003354 352.9277 63.3351 15.17186318 04
POQUITO
1 98706U 25009BY 25021.90669764 .00000000 00000-0 -14212-2 0 09
2 98706 97.4429 104.2661 0003354 352.9277 63.3351 15.17186318 09
PROMETHEUS-1
1 98705U 25009BY 25021.90669764 .00000000 00000-0 -14212-2 0 08
2 98705 97.4429 104.2661 0003354 352.9277 63.3351 15.17186318 08
HYPE
1 98708U 25009BY 25021.90669764 .00000000 00000-0 -14212-2 0 01
2 98708 97.4429 104.2661 0003354 352.9277 63.3351 15.17186318 01
Hi,
HelloSpace has SKYLINK-1 in ALBAPOD-1 and SKYLINK-2 in ALBAPOD-2… I will be happy if you can add those to the list as well…