The PARUS-T1 is APRS signal received and analysis for where is good propagation on VHF band. “T1” no Voice repeater and “T1A” meaning support “Audio voice Repeater”.
Taiwan PARUS-T1 3U CubeSat ready to go on 17th, Jan via Falcon 9.
PARUS-T1
1 99999U 25006.66666667 .00000190 00000-0 78946-5 0 00009
2 99999 097.4317 088.6023 0086891 020.2959 173.4876 15.20401651000016
The telemetry almost same as PARUS-T1A, I wil provide wave file for analysis.
7 Likes
Hi Randson,
Thank your for informing us about that.
Please keep in mind, that we are still not able to build a decoder.
T1A_tlm.xls is not meaningful enough.
We need the exact byte length of every value. .wav files are not sufficient.
And for Subsystem EPS we also need the format of all the four data sequences as well as for ADCS all two.
Daniel
1 Like
There is no PARUS-T1 entry in the database, please make a proposal in the SatNOGS database.
If there is more information made available, then add this in this community Transporter 12 launch post.
Please confirm the launch date and time, all information I could find is mentioning 14 January 2025
2 Likes
Satellite PARUS-T1 is added with temporary
NORAD ID: 98707 / SatNOGS Satellite ID: UCZO-3697-9016-2037-7134
Feel free to add transmitter suggestions or share telemetry format information. Also let us know if the format is similar or even the same as for the previous PARUS-T1A mission. Best of luck with this mission!
4 Likes
Dear Daniel.
Please see the cloud file(wave and telemetry explanation) for the PARUS-T1.
PARUS-T1 Telemetry and wave file.
I appreciate if anyone have question.
Thank you.
1 Like
I appreciate if you can help to update for the TLE.
1 99999U 25014.82277280 .00000000 00000-0 00000-0 0 00006
2 99999 097.3135 069.7122 0003715 073.9632 271.3052 15.19732673000013
Thank you.
1 Like
Thanks very much for the sample file!
Since that file is so large, if anyone would like a smaller sample to test with, here is an AUDIO file containing -5- good 1k2 AFSK decodes from the I/Q file provided:
4 Likes
That looks good. Thank you very much. Will work on a decoder.
1 Like
Hi Randson,
I took a look at the telemetry definition for EPS and Data Sequence 0x01 in your provided Excel file and compared it with a corresponding example packet from your audio file.
The packets mainly contain zeros and ones, represented in ASCII, where 0 is 30 and 1 is 31.
82 A0 B0 62 A6 40 60 84 9C 60 A8 92 A8 F6 AE 92
88 8A 62 40 63 03 F0 3E 50 41 52 55 53 3A 30 31
30 31 30 30 30 31 30 30 30 30 30 31 30 30 30 38
46 37 30 38 45 34 30 30 30 30 30 30 31 31 30 30
30 42 30 30 31 43 30 30 30 30 30 30 46 30 30 31
45 43 31 34 0D 0A
According to the telemetry definition, the individual values are supposed to be signed and unsigned integers with lengths of 1, 2 or 4 bytes.
One could represent the maximum 2-byte unsigned integer 0xffff in ASCII as 66 66 66 66 (with ‘f’ as a lowercase letter) or as 46 46 46 46 in uppercase.
Smaller values would need to be padded to 4 bytes in ASCII to maintain a constant length. For example, 0x01 would be represented in ASCII as 30 30 30 31.
However, determining the value from an ASCII representation for signed integers would certainly not be straightforward.
Regardless, in the above example, if the trailer is 0x0D0A and CRC-8 stands for 1 byte CRC, there are still 5 bytes left that I cannot assign.
In short: The length of the data parts of the packets exceed the specified length in the telemetry definition.
Therefore, I cannot build a decoder that reads the telemetry and makes it available for the database for a dashboard.
Daniel
1 Like
Thank you; will update you today.
By the way;I appreciate if can help to update for the photo of PARUS-T1 on DB.
PARUS-T1 Photo
1 Like
I’ve moved posts about PARUS-T1 to a new thread to be separated from the PARUS-T1A.
@BV2DQ will the APRS transceiver be active from the beginning, after deployment, or it will be activated later?
3 Likes
30 mins after deployed. UHF TT&C and VHF APRS Digipeater will start to active.
4 Likes
Hi Daniel…
The wave files and telemetry structure already update.
PARUS-T1 Files.
Please let me know if effect to Dashboard design or any else.
We PARUS Team are very thanks for your support!
Vy 73!
1 Like
Is possible to build dashboard for PARUS-T1?
So far how to setup scheduling for it?
The PARUS-T1 3U CubeSat, which carries a GNSS receiver for TT&C telemetry beacon and an APRS digipeater.
We believe that the onboard GNSS receiver data can significantly improve the accuracy of orbit determination and tracking for PARUS-T1. We would like to request your assistance in utilizing this GNSS location data to refine the predicted orbit position of the satellite.
I checked again and interpreted the data differently.
I now understand it, even if it’s a pretty unusal format.
Will try to build a decoder, hang on.
1 Like
Replay obs SatNOGS Network - Observation 10927397
and decoding with gr_satellites.
-> Packet from 1k2 AFSK downlink
Container:
header = Container:
addresses = ListContainer:
Container:
callsign = u'APX1S' (total 5)
ssid = Container:
ch = False
ssid = 0
extension = False
Container:
callsign = u'BN0TIT' (total 6)
ssid = Container:
ch = True
ssid = 6
extension = False
Container:
callsign = u'WIDE1' (total 5)
ssid = Container:
ch = False
ssid = 1
extension = True
control = 0x03
pid = 0xF0
info = b">R00.7VT00.7VC 21.0-\\'v'/ FORMOSA PARUS-T1 VHF DIGI! \\'v'/" (total 58)
5 Likes
PARUS-T1 satellite SWL report. 14-January-25 23:30 UTC. Orbit number 3. After IQ playback, four frames were received and decoded in Madrid Spain in 436.850MHz NFM. Strong signal. Good luck for your mission. 73 de David EA4SG
1:Fm BN0TIT-11 To APX1S Via WIDE1-1 [00:52:44R] [+++]
PARUS:0201000000000000000000000000000000000000000000000039D1B71735
1:Fm BN0TIT-11 To APX1S Via WIDE1-1 [00:52:51R] [+++]
PARUS:03010000000000000000000000000000000006600060FFADFE71001F005B02780012009DFC079B
1:Fm BN0TIT-11 To APX1S Via WIDE1-1 [00:52:58R] [±-]
PARUS:0401004B000000010100F000010101010000000000000000000000000000001E4B
1:Fm BN0TIT-11 To APX1S Via WIDE1-1 [00:53:02R] [+++]
R05.0VT04.8VC 17.5-'v’/ FORMOSA PARUS-T1 UHF 'v’/
5 Likes