Taiwan PARUS-T1A 3U CubeSat ready to go!

BV2DQ · December 15, 2024, 10:57am

Dear Libre Space Development Team,
Hi there; this is from Develop Team of PARUS-T1A
We are writing to request your support for the upcoming launch of the PARUS-T1A 3U CubeSat. This CubeSat is scheduled to be launched from Japan on a SpaceOne rocket in the next few days.

Satellite Details:
Call Sign:BN0TIT-11
TLE:
PARUS-T1A
1 99999U 24349.12075232 .00000000 00000-0 00000-0 0 00002
2 99999 097.3302 066.1302 0009155 254.6453 086.7753 15.22849958000018

Frequency List:
* Telemetry: 437.850 MHz AFSK 1200bps, AX.25
* APRS Digipeater: 145.825 MHz
* Voice Repeater:
* Uplink: 145.980 MHz (Tone 67Hz)
* Downlink: 435.250 MHz

Data Packet Frame Format:
T1A_housekeeping.pdf (139.9 KB)

We kindly request your assistance in developing a dashboard to visualize the raw data received from the PARUS-T1A CubeSat. This dashboard should be able to interpret the data packet frame format and display the information in a clear and concise manner.

Additionally, we would appreciate it if you could setup it for observation system. We have attached the IARU frequency coordination document for the amateur radio payload, which can be used as a reference.

We believe that your expertise and resources can significantly contribute to the success of this mission.

Again; we appreciate for your help and contribution

Thank you for your time and consideration.

Sincerely,
The Team of PARUS-T1A

Vy 73!
Randson Huang
BV2DQ /WJ2I

dl7ndr · December 15, 2024, 3:31pm

… says

(Please refer to T1A_housekeeping.exe for detailed telemetry.)

We need detailed telemetry information, but not in .exe format.

BV2DQ · December 15, 2024, 3:47pm

The Excel file have telemetry format explanation, is okay?

deckbsd · December 15, 2024, 4:18pm

Hello

Nice to see you here.

I checked the files and i have some questions.

First you are saying that telemetry is going to be AX.25, so is it safe to assume that frame format in the files are going to be the payload part of an AX.25 one ? if so what is going to be the used type of AX25 frame ? (ui frame ? i frame ?)

Also are housekeeping and telemetry the same frames ? or is it two separated types of packets ? if it is separated ones, what is the format inside Data (unfixed lenght) by data sequence ?

Second, there are missing informations in the excel file for us to be able to work on a decoder. In the T1A_tlm.xlsx file there are no indications of sizes (is one ligne equal to 1 byte ?). Also there is a subsystem ID field but despite for EPS,ADCS, GPS and TT&C part, the other IDs are missing (What about Ohter, EPS_PV ? GPSR ? or are these part included in refered subsystem ?). If telemetry format is the same as housekeeping, how the data sequence are divided in this structure.

Usually what we need to be able to do a decoder is a precise description of the different types of frame (fields + length + possible values of fields that describes the frame, like susbsystem ID, data sequence , formulas if the value of the field needs some calculations,…). And also if possible some bin files (preferably one by type of frame that will be sent) on which we can test the decoder behavior.

For giving you the big picture of the decoding process on SatNOGS, once the signal is demodulated by the satnogs-client/flowgraph part, the raw data are then interpreted by satnogs-decoder using a kaitai file that describe the data format (you can find all the files here . This can give you an idea of what we need in order to create this file for PARUS-T1A ). These decoded data are then saved into an influxDB database and can be used to produce a dashboard on SatNOGS dashboard.

BV2DQ · December 15, 2024, 7:05pm

Hi Julien…
It’s same as APRS UI Frame.
I will ask team engineer for more detail.

PE0SAT · December 15, 2024, 7:51pm

Up front I wish you and the team a successful mission.

Is it possible to share an IQ recording from transmission made with the satellite so that we can check and test the demodulation and frames produced.

Unfortunately we have seen in the past that demodulation and frames produces were not as expected.

fredy · December 15, 2024, 8:37pm

Satellite is added with the temporary NORAD ID 98732
https://db.satnogs.org/satellite/BFPS-7251-1020-2290-1029

@BV2DQ are there other cubesats that will be deployed on the same launch?

PE0SAT · December 15, 2024, 8:39pm

Thanks @fredy converted the TLE to the temporary object ID

PARUS-T1A
1 98732U          24349.12075232  .00000000  00000-0  00000-0 0 00006
2 98732 097.3302 066.1302 0009155 254.6453 086.7753 15.22849958000012

This TLE has an epoch time of:

Sat Dec 14 2024 02:53:53 UTC d=9115.12075232 ep=24349.12075232

We will use that epoch to create new set if it is clear when the new launch will take place, the latest information regarding Space One KAIROS LV second launch is mentioning that tomorrow the 16th there will be more information shared.

Satellites part of this launch are:

TATARA-1 (micro satellite)
SC-Sat1 (3u)
PARUS-T1A (3u)
ISHIKI (3u)
One unknown

If all protocol standards are met, the following PARUS-T1A yaml file should work with gr-satellites.

name: PARUS-T1A
norad: 98732
data:
  &tlm Telemetry:
    telemetry: ax25
transmitters:
  1k2 AFSK downlink:
    frequency: 437.850e+6
    modulation: AFSK
    baudrate: 1200
    af_carrier: 1700
    deviation: 500
    framing: AX.25
    data:
    - *tlm

BV2DQ · December 16, 2024, 3:29am

Dear Jan, very thanks for your help. I will give a IQ file link for testing. Also kindly to forward to DK3WN decoder web site…
The SpaceOne payload reference site…
SpaceOne KAIROS Payload

BV2DQ · December 16, 2024, 6:13am

This is telemetry IQ file.
PARUS-T1A IQ FILE

Please let me know if any question you have.
Thank you.

Randson Huang
BV2DQ/WJ2I

PE0SAT · December 16, 2024, 7:59am

Decoding the IQ files, all seems to be fine.

@deckbsd @dl7ndr @oldbug shall I forward the data to the db for dashboard development?

gr_satellites PARUS-T1A.yml --samp_rate 48e3 --audio

-> 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 = 11
                    extension = False
            Container: 
                callsign = u'WIDE1' (total 5)
                ssid = Container: 
                    ch = False
                    ssid = 1
                    extension = True
        control = 0x03
        pid = 0xF0
    info = b'>PARUS:01030005000300000000050000000000000700030000000007000300000000D6\r\n' (total 73)
-> 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 = 11
                    extension = False
            Container: 
                callsign = u'WIDE1' (total 5)
                ssid = Container: 
                    ch = False
                    ssid = 1
                    extension = True
        control = 0x03
        pid = 0xF0
    info = b'>PARUS:01040007000000000000070' (total 30)
-> 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 = 11
                    extension = False
            Container: 
                callsign = u'WIDE1' (total 5)
                ssid = Container: 
                    ch = False
                    ssid = 1
                    extension = True
        control = 0x03
        pid = 0xF0
    info = b'>PARUS:010201EB006F014501EB000101EB01E700020038030102EAFFBF1450B6\r\n' (total 67)

gr_satellites PARUS-T1A.yml --samp_rate 48e3 --audio --hexdump

***** VERBOSE PDU DEBUG PRINT ******
((transmitter . 1k2 AFSK downlink))
pdu length =         96 bytes
pdu vector contents = 
0000: 82 a0 b0 62 a6 40 60 84 9c 60 a8 92 a8 f6 ae 92 
0010: 88 8a 62 40 63 03 f0 3e 50 41 52 55 53 3a 30 31 
0020: 30 33 30 30 30 35 30 30 30 33 30 30 30 30 30 30 
0030: 30 30 30 35 30 30 30 30 30 30 30 30 30 30 30 30 
0040: 30 37 30 30 30 33 30 30 30 30 30 30 30 30 30 37 
0050: 30 30 30 33 30 30 30 30 30 30 30 30 44 36 0d 0a 
************************************
***** VERBOSE PDU DEBUG PRINT ******
((transmitter . 1k2 AFSK downlink))
pdu length =         53 bytes
pdu vector contents = 
0000: 82 a0 b0 62 a6 40 60 84 9c 60 a8 92 a8 f6 ae 92 
0010: 88 8a 62 40 63 03 f0 3e 50 41 52 55 53 3a 30 31 
0020: 30 34 30 30 30 37 30 30 30 30 30 30 30 30 30 30 
0030: 30 30 30 37 30 
************************************
***** VERBOSE PDU DEBUG PRINT ******
((transmitter . 1k2 AFSK downlink))
pdu length =         90 bytes
pdu vector contents = 
0000: 82 a0 b0 62 a6 40 60 84 9c 60 a8 92 a8 f6 ae 92 
0010: 88 8a 62 40 63 03 f0 3e 50 41 52 55 53 3a 30 31 
0020: 30 32 30 31 45 42 30 30 36 46 30 31 34 35 30 31 
0030: 45 42 30 30 30 31 30 31 45 42 30 31 45 37 30 30 
0040: 30 32 30 30 33 38 30 33 30 31 30 32 45 41 46 46 
0050: 42 46 31 34 35 30 42 36 0d 0a 
************************************
***** VERBOSE PDU DEBUG PRINT ******
((transmitter . 1k2 AFSK downlink))
pdu length =         94 bytes
pdu vector contents = 
0000: 82 a0 b0 62 a6 40 60 84 9c 60 a8 92 a8 f6 ae 92 
0010: 88 8a 62 40 63 03 f0 3e 50 41 52 55 53 3a 30 31 
0020: 30 31 30 30 30 31 30 30 30 30 30 32 30 30 30 38 
0030: 46 37 30 39 32 35 30 30 30 32 30 30 30 42 30 30 
0040: 32 44 30 30 30 34 30 30 30 30 30 30 42 30 30 31 
0050: 45 45 30 30 30 30 30 30 30 30 30 39 0d 0a 
************************************

fredy · December 16, 2024, 8:12am

Let’s forward them to db-dev as they are test data, I’ve just created an entry with the same temporary NORAD ID.

PE0SAT · December 16, 2024, 8:49am

I will give it a try, gr-satellites has a fixed URL, so I will use GetKissPlus from DK3WN there I can change the URL.

PE0SAT · December 16, 2024, 9:03am

I used the transport option inside the yaml file to send the data towards the dev environment.

name: PARUS-T1A
norad: 98732
telemetry_servers:
  - SIDS https://db-dev.satnogs.org/api/telemetry/
data:
  &tlm Telemetry:
    telemetry: ax25
transmitters:
  1k2 AFSK downlink:
    frequency: 437.850e+6
    modulation: AFSK
    baudrate: 1200
    af_carrier: 1700
    deviation: 500
    framing: AX.25
    data:
    - *tlm

{
    "next": null,
    "previous": null,
    "results": [
        {
            "sat_id": "VRHL-5090-1914-9567-1438",
            "norad_cat_id": 98732,
            "transmitter": "",
            "app_source": "sids",
            "decoded": "",
            "frame": "82A0B062A64060849C60A892A8F6AE92888A62406303F03E50415255533A303230313030303030303030303030",
            "observer": "PE0SAT-JO21mr",
            "timestamp": "2024-12-16T09:02:08Z",
            "version": "1.6.6",
            "observation_id": null,
            "station_id": null,
            "associated_satellites": []
        },
        {
            "sat_id": "VRHL-5090-1914-9567-1438",
            "norad_cat_id": 98732,
            "transmitter": "",
            "app_source": "sids",
            "decoded": "",
            "frame": "82A0B062A64060849C60A892A8F6AE92888A62406303F03E50415255533A303430313030393630303031303030303031303030303030303030303030303043300D0A",
            "observer": "PE0SAT-JO21mr",
            "timestamp": "2024-12-16T09:02:01Z",
            "version": "1.6.6",
            "observation_id": null,
            "station_id": null,
            "associated_satellites": []
        },
        {
            "sat_id": "VRHL-5090-1914-9567-1438",
            "norad_cat_id": 98732,
            "transmitter": "",
            "app_source": "sids",
            "decoded": "",
            "frame": "82A0B062A64060849C60A892A8F6AE92888A62406303F03E50415255533A30313031303030313030303030323030303846373039323530303032303030423030324430303034303030303030423030314545303030303030303030390D0A",
            "observer": "PE0SAT-JO21mr",
            "timestamp": "2024-12-16T09:01:54Z",
            "version": "1.6.6",
            "observation_id": null,
            "station_id": null,
            "associated_satellites": []
        },
        {
            "sat_id": "VRHL-5090-1914-9567-1438",
            "norad_cat_id": 98732,
            "transmitter": "",
            "app_source": "sids",
            "decoded": "",
            "frame": "82A0B062A64060849C60A892A8F6AE92888A62406303F03E50415255533A303130323031454230303646303134353031454230303031303145423031453730303032303033383033303130324541464642463134353042360D0A",
            "observer": "PE0SAT-JO21mr",
            "timestamp": "2024-12-16T09:01:47Z",
            "version": "1.6.6",
            "observation_id": null,
            "station_id": null,
            "associated_satellites": []
        },

PE0SAT · December 16, 2024, 9:08am

Please explain what you mean by “Also kindly to forward to DK3WN decoder web site”
Are you already in contact with Mike DK3WN and is he expecting the file ?

PE0SAT · December 16, 2024, 9:42am

Launch update:

[Space One 12/16 13:03 announcement]

Scheduled launch date: Wednesday, December 18, 2024

Scheduled launch time (JST): 11:00:00 Launch time slot: 11:00:00 - 11:20:00 (time may be rescheduled within the launch time slot)

Scheduled launch time (UTC): 02:00:00 Launch time slot: 02:00:00 - 02:20:00 (time may be rescheduled within the launch time slot)

Launch backup period: Thursday, December 19, 2024 to Friday, December 27, 2024

PE0SAT · December 16, 2024, 2:18pm

Based upon the same time as shared by the team a new TLE set for the 18th

2024-12-18T02:53:53

PARUS-T1A
1 98732U          24353.12075232  .00000000  00000-0  00000-0 0    01
2 98732  97.3302  70.0728 0009155 254.6453  86.7753 15.22849958    07

dl7ndr · December 16, 2024, 5:25pm

Hi Randson,

According to T1A_housekeeping.pdf, the header is “PARUS:UP” and the subsystem ID is 0x01 for EPS.

This makes 50 41 52 55 53 3A 55 50 01.

The provided IQ file, decoded by Jan, however shows.

By the way, there is also a PARUS-T1 (without A). Can you tell us more about this satellite?

73
Daniel, dl7ndr

K4KDR · December 16, 2024, 7:21pm

Greetings! Great to see another new satellite.

For anyone who might find it easier to test with an AUDIO file, here are a couple of isolated packets from one of the I/Q files kindly provided above:

https://www.qsl.net/k/k4kdr//audio/PARUS-T1A/

Decode with the 1k2 AFSK tools of your choice.