Hi Eric,
Thanks for the details.
Do you also know when the digipeater will be switched on and what to do to get a QSL card?
73
Daniel
1 Like
@fredy Yes, I understand. However, I noticed that the TLE of the ERMIS-2 satellite has been assigned to both ERMIS-2 and VEGAFLY-1. Could you please assign a more appropriate TLE that is closest to our satellite for VEGAFLY-1 on SatNOGS?
Thank you very much for your support.
Unfortunately due to other tasks I didn’t have the chance to take a deeper look, any suggestion from your analysis? Which one we should follow?
Probably I’ll be able to continue my analysis tomorrow.
Hi @N6RFM , @dl7ndr , and everyone in the community,
The EPS telemetry decoder for PARUS-6U1 is now available.
We have released a GNU Radio Out-Of-Tree (OOT) module specifically for decoding our EPS data. You can access the repository here: https://github.com/ntut-rf/PARUS_6U1.git
Additionally, we are providing eQSL cards. If you have successfully received our signals, please send your reception reports to t114369009@ntut.org.tw, and we will send you an eQSL card.
Thank you for tracking PARUS-6U1 and sharing your data.
10 Likes
Thanks Eric!!
Bob
N6RFM
So a SoundModem (gaspacs 4800) will not work properly for Parus 6U1?
can you share the satyml file for gr_satellites ?
i used this but not work:
name: PARUS-6U1
norad: 68456
data:
&endurosat Endurosat Telemetry:
unknown
transmitters:
9k6 FSK Endurosat downlink:
frequency: 437.195e+6
modulation: FSK
baudrate: 9600
deviation: 2600
framing: Endurosat
data:
- *endurosat
or this:
name: PARUS-6U1
norad: 68456
data:
&tlm Telemetry:
telemetry: ax25
transmitters:
9k6 FSK downlink:
frequency: 437.195e+6
modulation: FSK
baudrate: 9600
deviation: 2400
framing: AX.25 G3RUH
data:
- *tlm
late join.
i try using gr_satellites
and
PARUS-6U1.yml
name: PARUS-6U1
norad: 68456
data:
&endurosat Endurosat Telemetry:
unknown
transmitters:
9k6 FSK Endurosat downlink:
frequency: 437.195e+6
modulation: FSK
baudrate: 9600
deviation: 2600
framing: Endurosat
data:
- *endurosat
gr_satellites PARUS-6U1.yml --iq --rawfile p1.iq --samp_rate 50000 --hexdump
result:
result
correlate_access_code_tag_bb :debug: Access code: aa7e
correlate_access_code_tag_bb :debug: Mask: ffff
correlate_access_code_tag_bb :debug: writing tag at sample 9410
***** VERBOSE PDU DEBUG PRINT ******
((transmitter . 9k6 FSK Endurosat downlink))
pdu length = 90 bytes
pdu vector contents =
0000: 59 84 9c 60 a8 92 a8 7e 7e 7e d6 05 f0 0b 5f e7
0010: fe 20 f2 47 d4 28 4c 90 85 a8 83 6b 3e 0a d6 8b
0020: 0e ea bd 0a f1 fa 4d 2a 3f a6 1d 96 94 76 24 aa
0030: ea fc d3 d5 dd 77 8b 5f c6 d7 f1 b3 b7 1f d0 33
0040: 19 f4 75 b6 8c a7 63 75 d5 0b 69 a4 8a 24 06 63
0050: 15 52 7c 89 2b 47 1f b4 0f f1
************************************
correlate_access_code_tag_bb :debug: writing tag at sample 11726
correlate_access_code_tag_bb :debug: writing tag at sample 13432
***** VERBOSE PDU DEBUG PRINT ******
((transmitter . 9k6 FSK Endurosat downlink))
pdu length = 90 bytes
pdu vector contents =
0000: 59 84 9c 60 a8 92 a8 7e 7e 7e 17 67 5f 38 3b c3
0010: 70 8a 46 58 46 36 81 7c d3 1f 5b 8e d2 0f 51 f0
0020: b8 7a da 52 b8 df 8b 02 3f f5 2d 35 c7 0a 46 75
0030: d8 6f 85 9a 85 6d 9e 3a bd ab c0 5c 26 df fa 1e
0040: 9e dc f3 85 b8 83 48 8f 21 b0 fd be 70 76 d3 1a
0050: ef c6 73 e6 64 68 2c 09 cd 95
************************************
correlate_access_code_tag_bb :debug: writing tag at sample 15254
correlate_access_code_tag_bb :debug: writing tag at sample 17235
correlate_access_code_tag_bb :debug: writing tag at sample 19196
crc_check :debug: CRC fail
***** VERBOSE PDU DEBUG PRINT ******
((transmitter . 9k6 FSK Endurosat downlink))
pdu length = 114 bytes
pdu vector contents =
0000: 71 84 9c 60 a8 92 a8 7e 7e 7e 41 7b 37 81 7c ca
0010: 13 a8 a6 10 08 43 49 13 a7 77 35 b8 e9 eb 6d 09
0020: 4d c2 b2 a8 ee bb 63 4c 01 8c 42 0f 71 0e 05 4c
0030: ca 3c 58 fa 15 ab 9a fc fc 36 96 0e c5 4d 56 ff
0040: 59 61 a6 a4 06 23 89 16 7a 8c 33 20 b0 be 4c 73
0050: 1f 62 82 a7 29 93 00 6c b9 ce d7 a4 5f 74 a1 bc
0060: 26 07 6a 54 8d f7 b2 70 e7 b3 35 4f 04 b1 c2 24
0070: 52 9b
************************************
***** VERBOSE PDU DEBUG PRINT ******
((transmitter . 9k6 FSK Endurosat downlink))
pdu length = 101 bytes
pdu vector contents =
0000: 64 84 9c 60 a8 92 a8 7e 7e 7e b2 aa cf af 60 55
0010: d7 df 53 82 82 2c cd 89 06 7b bd 21 61 51 d4 b1
0020: b5 38 e0 06 ae ed 86 e3 35 99 f8 bb 4e 9c 59 a1
0030: a6 28 c7 22 a2 67 3e 2d af a8 d4 15 cc ea 34 6b
0040: e6 b0 c2 0a 11 05 73 ea 78 5a 56 2d 43 68 02 f6
0050: 64 23 c0 b7 95 7e ce 13 d9 9a a7 3d 37 27 f7 d9
0060: d2 27 9a a5 fe
************************************
***** VERBOSE PDU DEBUG PRINT ******
((transmitter . 9k6 FSK Endurosat downlink))
pdu length = 113 bytes
pdu vector contents =
0000: 70 84 9c 60 a8 92 a8 7e 7e 7e 34 62 4a 62 b4 82
0010: 0f fd cf c8 df 21 1c 4c 35 80 d7 b5 3e 4c 83 ac
0020: c1 8b 7f 0f 1f e4 bd 16 f0 4e 4e cb 19 ab 39 97
0030: b7 d7 af 69 3f 2e 27 2e eb 29 08 b1 0b d3 65 fb
0040: 43 ad 92 4f dc 5b 05 e0 0a 6e f5 88 65 49 5d b0
0050: 40 1c 73 09 71 46 8d 58 92 94 6d f0 dd 3f 46 05
0060: ba 3d 90 2f dd 12 75 a0 ce bc 60 61 28 61 d1 96
0070: 7f
************************************
generate kiss file:
gr_satellites ~/Documents/SATYML/PARUS-6U1.yml --iq --rawfile p1.iq --samp_rate 50000 --hexdump --kiss_out parus.kiss
create grc flowgraph using gnuradio-companion:
contoh.grc.txt (2.1 KB)
run & wow it work (but i think still complicated for noobs)
EPS Beacon
DATETIME: 1776504612
MODE: 3 | Sat_mode: 0 | LVLH: 0
Energy: 53.529000 Wh | Vol: 15.233 V | Cur: -247 mA | Temp: 5.407 C
Outputs Mask: 65313
12V : 0.0 V / 0 mA / 0 mW
5V_1 : 5.07 V / 100 mA / 512 mW
5V_2 : 5.064 V / 295 mA / 1869 mW
3V3_1 : 3.368 V / 257 mA / 875 mW
3V3_2 : 3.396 V / 132 mA / 262 mW
Callsign:
Repeat Counter: 2
[Beacon] packet_count = 2, len = 90
EPS Beacon
DATETIME: 1776504612
MODE: 3 | Sat_mode: 0 | LVLH: 0
Energy: 53.529000 Wh | Vol: 15.233 V | Cur: -247 mA | Temp: 5.407 C
Outputs Mask: 65313
12V : 0.0 V / 0 mA / 0 mW
5V_1 : 5.07 V / 100 mA / 512 mW
5V_2 : 5.064 V / 295 mA / 1869 mW
3V3_1 : 3.368 V / 257 mA / 875 mW
3V3_2 : 3.396 V / 132 mA / 262 mW
Callsign:
Repeat Counter: 2
The Unix timestamp 1776504612 converts to:
April 12, 2026, 10:45:00 UTC
5 Likes
Excellent results!!
1 Like
Today… but you keep showing your work and us noobs won’t be that for long!
(THANK YOU for showing your work… I’m planning on innovating something soon, and then I get to show MY work! bwa ha ha!!)
2 Likes
Thanks for the information, I created the following GNURadio flow graph
Producing:
>>> Classification: [ Unknown Beacon ] (Func ID: 4)
EPS Beacon
DATETIME: 1776434722
MODE: 3 | Sat_mode: 0 | LVLH: 0
Energy: 30.564000 Wh | Vol: 14.47 V | Cur: -38 mA | Temp: 2.133 C
Outputs Mask: 65313
12V : 0.0 V / -1 mA / 0 mW
5V_1 : 5.067 V / 98 mA / 487 mW
5V_2 : 5.079 V / 117 mA / 746 mW
3V3_1 : 3.367 V / 265 mA / 875 mW
3V3_2 : 3.397 V / 75 mA / 262 mW
Callsign:
Repeat Counter: 2
[Warning] Ignoring CRC error (calculated:0xfcb3 received:0x771b)
EPS Beacon
DATETIME: 1776434675
MODE: 3 | Sat_mode: 0 | LVLH: 0
Energy: 31.069000 Wh | Vol: 14.463 V | Cur: -77 mA | Temp: 1.962 C
Outputs Mask: 65313
12V : 0.0 V / 0 mA / 0 mW
5V_1 : 5.067 V / 102 mA / 512 mW
5V_2 : 5.079 V / 117 mA / 746 mW
3V3_1 : 3.366 V / 264 mA / 875 mW
3V3_2 : 3.397 V / 80 mA / 250 mW
Callsign:
Repeat Counter: 2
[Warning] Ignoring CRC error (calculated:0xd87d received:0x2675)
Jan | PE0SAT
8 Likes
This is super cool !!
It REALLY encourages operators to pay more attention to their satellite 
Thanks for the eQSL card !!
3 Likes
Is it possible to use an audio file or an audio stream, playing via mediaplayer?
I got few packets from Parus-6U1 from my ground station (soniks) but I doubt that they were processed correctly. Every packet has a sequence “84 9C 60 A8 92 A8” but the rest seems to be scrambled as it was mentioned in the earlier posts. So I doubt that this data will be accepted for eQSL
yes of course..
just run this command:
gr_satellites PARUS-6U1.yml --wavfile your_audio_file.wav --hexdump --kiss_out parus.kiss
if you get the .kiss file, the next step is just follow the above step after..
2 Likes
Hi @fredy,
Could you please help verify and update TLE for VEGAFLY-1 in the SatNOGS database?
Link: Find Vegafly-1 — Live Satellite Tracking
TLE:
1 68434U 26067U 26123.97251461 .00004781 00000-0 23634-3 0 9996
2 68434 97.4561 83.1225 0003430 108.6521 251.5086 15.18305363 5235
Thank you very much for your support!
I’ve changed for Vegafly-1 to follow 68434, I’ll schedule later some observations and will check the results for verification.
Unfortunately I still haven’t finished my analysis on the T16 launch objects as other tasks get in the middle, I’ll try to take a look this week but I don’t promise anything. Until then if there is any other suggestion we could try let me know here.
2 Likes
I understand, and we truly appreciate your support. Thank you very much.
1 Like
Hi @fredy,
We believe we have identified EMISAR as Object M (68427, 2026-067M). I’m not sure if there’s something needed on your side too, as we have contacted Space-Track Office to claim the object as EMISAR.
Thank you!
2 Likes