Updated INNOCube TLE
INNOCUBE
1 98709U 25017.43692333 .00000000 00000-0 -67803-3 0 02
2 98709 97.4389 100.1866 0007295 359.8410 130.2626 15.16264502 02
ikhnos -t ~/satnogs/strf/98709_4801.tle -f .8 -r 29.0 10928576
Please share your experience with this TLE set.
AMSAT-EA has been informed that its Hades-R satellite will be deployed from D-Orbit ION SVC-016 OTV the next 22th of january
We have also been informed that at the moment, ION SVC-016 is orbiting in good shape
Hi David,
Thanks for this information.
To my knowledge, Hades-R is not only within D-Orbit’s ION SVC-016 but additionally within Alba Orbital’s Albapod.
Is AMSAT-EA also informed from Alba Orbital about when they will deploy Hades-R into free space?
Daniel
Hi Daniel. The Hades-R above mentioned information came for Alba Orbital. So we expect Hades-R orbiting free on the mentioned 22th of january.
Thank you!
We have used this TLE for the last pass, it has worked pretty well. It is slightly too early based on my observations. The last TLE we had was around 500-600 Hz late for the morning / lunch passes, now this set was around 100 Hz too early. However it worked fine.
I will turn the transmitter on in the next pass as well. 2108-2120 UTC.
We will also be sending the beacon semi regularly in the next time, until we fully understand the status of the satellite.
Good pass from ION SVC-014
https://network.satnogs.org/observations/10936681/
Hi folks, I am reporting in here from the team supporting ELEVATION-1. I have noticed some oddities in the DB I wanted to report, so hopefully we can help shed some extra light on this large batch of satellites launched from T-12.
The satellite with ID FOYA-6887-7497-4856-0981 in the DB currently labeled “ELEVATION-1 (98688)” does not have the correct transceiver configuration. The ELEVATION-1 satellites uses a UHF downlink frequency of 400.200Mhz. The ground track reported in the DB appears to be close to what I believe is correct, but not spot on. Here is a TLE provided by our ops team that is currently being used to track the spacecraft. It is still being refined, mind you:
!!1 00000U 00000AAA 25019.99285517 .00000000 00000-0 14837-2 0 01
2 00000 97.4422 102.5930 0005782 344.6296 52.4695 15.16642116 00
The UHF transmitter onboard is operating at 7.41577kbps using 2-FSK modulation. It uses the openlst protocol, which would be awesome to integrate for general use on the Satnogs network. We can open a side conversation on that topic if it would be of interest. Some resources:
Thanks!
Brian
Thanks for all the info, Brian!
By chance do you have a GNU Radio flowgraph or other tool that can be shared for decoding those openlst downlinks?
Also, if you have an audio or I/Q file that provides high-quality examples of your downlink, please share it if possible. Thanks!
Scott,
Give this a try:
name: ELEVATION-1
norad: 98688
data:
&tlm Telemetry:
unknown
transmitters:
7k4 FSK downlink:
frequency: 400.200e+6
modulation: FSK
baudrate: 7415.77
framing: OpenLST
data:
- *tlm
Thanks so much! Just installed the OpenLST blocks on my GRC 3.10 machine, so now I’m just lacking a test file. SatNogs usually comes to the rescue when I don’t have any of my own recordings for an object, but they will need to switch over to 400.200 MHz before any observations might catch some of these ELEVATION-1 downlinks.
And as always, your .yml file templates are MUCH appreciated and very helpful!!
This could be ELEVATION-1 at 400.200
And that gives the following TLE:
ELEVATION-1
1 98688U 25019.55071759 .00000000 00000-0 13711-2 0 03
2 98688 97.4407 102.5595 0006135 342.3926 117.8359 14.92734270 06
I misunderstood, I thought you already had a test file.
Just now, @fredy is changing the transmitter and then we will create some obs to see if we can record some data and test the OpenLST framing. (Have a look for DORA, that was one of the first with this framing)
We do have and challenge with the TLE, looking at the latest T12 Celestrak data that was +/- 4 minutes of.
I proposed my TLE to see if these will fit better and to make things even more confusing, look at the image.
We have another satellite some 20 KHz higher
There is even an UZ7HO Windows version for OpenLST
If it helps, here is a quick flowgraph that just shows how to plumb the downlink together @K4KDR gr-openlst/examples/openlst_downlink.grc at main · antaris-inc/gr-openlst · GitHub
@bcwaldon do you use GRAF1N as callsign?
Pardon my ignorance… this is a commercial satellite, so no callsign. Not an amateur radio station. Do I understand the question correctly?
@bcwaldon I’m asking as we have an unknown satellite at 400.200 MHz, so I’m trying to find out if this is ELEVATION-1.
You can see some frames of that unknown satellite in SatNOGS Network - Observation 10947185 like this:
8E A4 82 8C 62 9C 00 8E A4 82 8C 62 9C 01 00 21 31 3F 03 00 00 00 00 00 09 00 00 00 EE 1A 41 21 85 B0 33 06 64 66 6C 16 84 15 D2 DE 61 37 1B 23 D8 03 D9 4F B1 AB 18 A0 C0 82 BE 78 BD F0 18 63 0D F0 2F E5 7A 8D 80 37 17 B2 60 34 C9 B5 29 69 B2 FB 6E 00 F8 E3 23 27 75 CC 15 5C 6D DD 52 BF 69 CE 0F 47 D3 01 55 CB 39 90 55 B3 61 84 5D 8C E0 A5 B3 43 55 79 69 25 6A 48 61 68 CD 1C EF 86 EC 44 2A 6E E1 F7 9E F4 3E 39 47 C0 B0 E9 74 96 61 6F 42 E6 08 72 2C 2D 11 3F 87 A6 61 17 14 62 33 A5 A5 5B CA 53 47 48 50 A1 6C DA B1 A0 92 0C 95 CD 9A D8 6F 50 68 AF F0 A9 DB 8E CB AC 08 BD 2D D9 87 BF 7D AC BC C0 42 C5 12 6E 83 E8 CC E4 A5 E8 45 A8 33 B9 38 68 FC 21 9B 9D 62 A7 31 A9 EB 57 BC 7C F3 FA 43 B0 49 B6 33 21 8D 45 3F 7C 6E F0 A8 1B 07 36 C0 68 25 E7 DB 96 1E 54 7E 3E
So, if we decode it with the AX.25 decoder we get this:
Source Callsign GRAF1N
Destination Callsign GRAF1N
Source SSID 0
Destination SSID 0
Ctl 0
Pid 33
Monitor 1? �A!��3dfl���a7e#��O������x��c �/�z��7�`4ɵ)i��n��#'u lie�\m�R�i�G�U�9�U�a�]�ॳCUyi%jHah� ��D*n����>9G���t�aoB�r,-?��ab3��[�SGHP�lڱ�� �͚�oPh��ێˬ�-ه�}���B�n�����E�3�8h�!��b�1��W�|��C�I�3!�E?|n�ea6�h%�ۖ T~>
@bcwaldon After some quick analysis it seems that the unknown satellite isn’t ELEVATION-1 as the AX.25 doesn’t fit what you described and also the TLE followed for the ELEVATION-1 and the unknown satellite give very different positions for the satellites.
By the way the one that @PE0SAT analyzed in this post Transporter-12 Rideshare : VSFB SLC-4E : NET 14 January 2025 1849Z-1946Z - #72 by PE0SAT is actually the unknown satellite and not related with the ELEVATION-1.
So, we’ve updated the entry in DB and the TLE and we now have observations scheduled to observe ELEVATION-1. Let’s see if we get something.
So the TLE we have are these:
Unknown T12 satellite 1
1 98659U 25019.55071759 .00000000 00000-0 13711-2 0 01
2 98659 97.4407 102.5595 0006135 342.3926 117.8359 14.92734270 04
ELEVATION-1
1 98688U 00000AAA 25019.99285517 .00000000 00000-0 14837-2 0 00
2 98688 97.4422 102.5930 0005782 344.6296 52.4695 15.16642116 09
Thanks again for the OpenLST repository link + the recently added example GRC file.
I was not able to get past that version of the OpenLST deframer requiring a ‘satcom’ python module, but fortunately there is an OpenLST deframer in gr-satellites that works very well w/ sample files from a previous satellite.
… so, now the wait is on for an example of the ELEVATION-1 downlink to test (either from your team or from a SatNogs recording).
@K4KDR The “satcom” dependency is here: GitHub - antaris-inc/python-satcom. We have simply refactored the openlst frame handling code out of the original gr-openlst repo for testability and reuse elsewhere. You can just clone that git repo and pip install it locally (sorry we are not distributing it on pypy yet!).
