Transporter-15 Rideshare: VSFB SLC-4E : 28 November 2025 - 18:44:30 UTC

tron_satellite · December 9, 2025, 2:19pm

Hello again,

We have a new TLE for TMICROSAT-1 as below

TMICROSAT-1
1 98515C 25276Y   25343.10484381 +.00007837 +00000+0 +38628-3 0 00137
2 98515  97.4376  54.9439 0001913 102.7368 257.4080 15.18207560001575

Could you please help us to update it in the SatNOGS DB? Thank you very much!

PE0SAT · December 9, 2025, 2:20pm

@therman89 Is this mission also supporting remote telemetry BMEWS server ?

If not we can remove this configuration.

telemetry_servers:
  - BMEWS

Jan | PE0SAT

N6RFM · December 9, 2025, 3:12pm

Hi @szlldm Thanks for the additional details above.

Now trying to upload packets to the local webpage display as instructed

Monitor packets received by smogcli2 locally (index.html for telemetry viewer)( hunity.pkts with relative or absolute path)
python3 hunity_upload_from_file.py --tail hunity.pkts --port 8765
Then open index.html in browser and connect to python websocket server running locally via Ws settings->Local telemetry

However, I get the error below

bob@bob:~/smogcli2/scripts/hunity$ python3 hunity_upload_from_file.py --tail h1.pkts --port 8765
usage: hunity_upload_from_file.py [-h] [-q QTH] [filenames …]
hunity_upload_from_file.py: error: unrecognized arguments: --tail --port 8765
bob@bob:~/smogcli2/scripts/hunity$

Am I using the correct method to see the frames on the local webpage?

Thanks,

Bob

K4KDR · December 9, 2025, 4:55pm

Please disregard my previous post regarding an error when attempting to use the FORESAIL-1.yml file from gr-satellites to decode this satellite.

It was a version issue; the error was in GRC 3.8… the standard ‘satellite decoder’ flowgraph runs fine in GRC 3.10.

szlldm · December 9, 2025, 6:54pm

Hi, i think you need to use hunity_local_telemetry.py, instead of hunity_upload_from_file.py, but i’m not absolutely sure.

N6RFM · December 9, 2025, 11:25pm

Thanks, tried that also. Will investigate further.

EA4GPZ · December 10, 2025, 7:49am

The FS1 Skylink Protocol Specification is giving a 404 error: https://foresail.github.io/docs/FS1_Skylink_protocol_Specification.pdf

therman89 · December 10, 2025, 8:34am

Hi,

I suggest you just watch the telemetry from the terminal.

tail -f decoded.pkts

The README file needs some updates.

tjanos · December 10, 2025, 8:50am

Try this:

Or from here, on the google drive:

Foresail-1 Skylink Protocol Specification

dl7ndr · December 10, 2025, 11:01am

Foresail-1 prime

2025-12-10 10:5x UTC decoded strong beacon signals using UZ7HO’s soundmodem just 1 kHz below the regular frequency.

[10:56:00R]
[len:43 FEC_err:0 RS_err:0]
66 4F 48 32 46 31 53 09 3A 7C 05 44 00 FA 00 F1 0B 34 0B 34 00 11 10 03 06 69 39 51 BE 00 00 04 00 0F 00 00 00 00 00 39 99 26 82

[10:56:29R]
[len:71 FEC_err:0 RS_err:0]
66 4F 48 32 46 31 53 09 3A 7D 05 44 00 FA 00 0E 0B 34 0B 34 00 2D 10 03 02 69 39 51 DB 00 00 00 00 01 1F 44 65 01 00 62 00 C2 0E D1 64 35 01 03 00 1C 00 01 00 01 00 00 00 00 00 04 00 05 00 06 00 06 20 F1 77 06 EE

[10:56:30R]
[len:112 FEC_err:0 RS_err:0]
66 4F 48 32 46 31 53 09 3A 7E 05 44 00 FA 00 FA 0B 34 0B 34 00 56 10 03 05 69 39 51 DB 00 00 75 5B 6E 47 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80 00 08 80 0C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 F4 01 09 00 64 00 09 00 07 F0 4C 87 83 EB 00 00 00 00 00 00 00 00 00 00 00 00 A6 50 E1 38

[10:56:30R]
[len:89 FEC_err:0 RS_err:0]
66 4F 48 32 46 31 53 09 3A 7F 05 44 00 FA 00 6B 0B 34 0B 34 00 3F 10 03 04 69 39 51 DB D1 62 01 00 02 00 00 00 00 00 00 00 00 41 26 00 00 9E 00 00 00 00 00 00 00 00 00 00 00 48 00 49 00 01 01 01 FA 00 00 00 FA 00 00 00 1A 00 2D 00 BA 00 14 02 C4 00 24 FE 2B CB 2B 67

[10:56:31R]
[len:143 FEC_err:0 RS_err:0]
66 4F 48 32 46 31 53 09 3A 80 05 44 00 FA 00 F7 0B 34 0B 34 00 75 10 03 03 69 39 51 DB 4A 65 01 00 02 02 91 E8 00 00 83 00 9B 00 DC 00 0E 00 D1 4B 79 46 B1 01 68 49 0E 00 A8 48 B9 1F C9 0F 83 0E 77 0E 5B 0E 2E 00 57 00 32 00 77 00 44 00 E8 FF A3 FF A4 00 7D 00 6D 00 86 00 00 00 00 00 00 00 7E 00 00 00 56 00 30 00 0D 00 00 00 00 00 00 00 7D 00 00 00 55 00 2F 00 0D 00 00 00 00 00 00 00 7F 00 00 00 5B 00 8E 03 0E 00 17 AF 7A 84

[10:56:31R]
[len:43 FEC_err:0 RS_err:0]
66 4F 48 32 46 31 53 09 3A 81 05 44 00 FA 00 4D 0B 34 0B 34 00 11 10 03 06 69 39 51 DC 00 00 04 00 0F 00 00 00 00 00 C6 9E A3 4F

hodlemil · December 10, 2025, 11:53am

Yes the smogcli2/scripts/hunity/README.txt has copy paste bug. I will be fix it.

python3 hunity_upload_from_file.py -q qthfile.txt hunity.pkts first point in readme is correct
python3 hunity_upload_continous.py -q qthfile.txt --tail hunity.pkts
python3 hunity_local_telemetry.py --tail hunity.pkts --port 8765

The different arguments process is minimal protection the wrong usage

qth content something that:

HA5MRC
47.4775326N
19.055378E
120
username
password

I now writing user guide to this scripts and local telemetry html. If you would like see the telemetry locally use that python3 hunity_local_telemetry.py --tail hunity.pkts --port 8765 after or smogcli2 before open local_html/index.html in browser. This index.html can process smogcli2 pkts format or minimal json fields data and code_type. If you write some data to hunity.pkts it will be processed by local_html/index.html javascript function.

Emil

fredy · December 10, 2025, 3:50pm

The Network’s stations use the gr-satnogs and satnogs-flowgraphs for demodulating the satellite data.
Currently the flowgraphs/demodulators are not very configurable, so they go with some defaults, for example with the entry in DB for HUNITY according to this code it will run the fsk_ax25.grc flowgraph, with 12k5 baudrate and at HUNITY frequency and the rest parameters will be set to the default ones.

I checked some obs from MRC-100 which uses the same type of frame and I see demodulated frames only from customized stations that use in parallel gr-satellites. So, my guess is that the used flowgraph doesn’t work for HUNITY’s signals.

We are working on the radio part in order to make available more parameters and create dynamically the flowgraphs based on them in order to have better results. However this may take some time to be completed. Until then, unfortunately from Network, there will be demodulated frames from the stations that use gr-satellites.

For helping us, if you can, please provide (if not already, I haven’t checked) IQ from observation(s), that will help the flowgraph developers to test their changes.

N6RFM · December 10, 2025, 5:10pm

Thanks Emil! Much appreciated.

Bob

PE0SAT · December 11, 2025, 11:03am

Today I was able to create an IQ with some good FORESAIL-1P SNR frames.

I had a look at the documentation but wasn’t able to create a working gr-satellites decoder, I guess we need some help from @EA4GPZ for SkyLink protocol support.

Jan | PE0SAT

K4KDR · December 11, 2025, 11:41am

Morning, Jan!

Are your frames of a different type than those decoded w/ the FORESAIL-1P.yml file Dani posted this morning. That decodes the packets from https://network.satnogs.org/observations/12925621/

-Scott

K4KDR · December 11, 2025, 12:03pm

Downloaded the most recent 57600 I/Q file from your link and that decodes w/ the new .yml file as well.

tron_satellite · December 11, 2025, 12:52pm

Hello,

We have a new TLE for TMICROSAT-1:

TMICROSAT-1
1 98515U 25276Y   25344.95028125 +.00009986 +00000+0 +49073-3 0 00178
2 98515  97.4375  56.7578 0001968 101.3003 258.8452 15.18241603001854

Could you please help us to update it in the SatNOGS DB? Thanks!

PE0SAT · December 11, 2025, 1:33pm

I missed that post and will first update my gr-satellites.

Wonder if these will also work on my “old” 3.8 environment.

~~I guess not, it has specific framing.~~ Correction, also 3.8 has FORESAIL-1 framing.

name: FORESAIL-1P
norad: 98467
data:
  &tlm Telemetry:
    unknown
transmitters:
  9k6 FSK downlink:
    frequency: 437.125e+6
    modulation: FSK
    baudrate: 9600
    framing: FORESAIL-1
    data:
    - *tlm

Jan | PE0SAT

hubert-nuspace · December 12, 2025, 1:05am

Hi all,

We have a new TLE for Black-Kite-1 generated based off the previous TLE and verified using ikhnos.

BLACK-KITE-1
1 98527U 14900A   25345.89404986 +.00017352 +00000-0 +88676-3 0    01
2 98527  97.4484  57.6809 0005079 312.6247  95.6249 15.16943229    07

Could this be loaded into Satnogs for the upcoming scheduled observations? Thank you all again for your hard work!

yurimdias · December 12, 2025, 1:04pm

Hello,

We have generated a GNSS-based new TLE for MICE-1:

1 72001U 25276Z   25345.50761227  .00000000  00000-0  85911-3 0 00001
2 72001  97.4491  57.2978 0004401 288.2412 177.0173 15.17054724 01823

I haven’t updated it to use your temporary ID yet, but if you can please update the tracking for it, that’d be great.