2024-08-29 09:20 UTC and 11:00 UTC: ISS Cubesat Deployment (JAXA) J-SSOD#31 - [CosmoGirl-Sat, SaganSat0, SAKURA, Wisseed Sat, Binar-2, -3, -4]

[fredy]

I’ve updated the first post with the frequencies table.

Please double check that the entries of satellites and transmitters are right.

I’ve set as inactive the digipeaters as usually they are not initially active and to avoid confusion with ISS APRS digipeater. If there is any information that they will be active directly after deployment please let me know.

The satellites will be available for scheduling in Network ~30min before deployment in order to have the right ISS TLE set to follow initially.

To station owners

1. I’m going to schedule massively for the next days until identification but feel free to change (delete and re-schedule) observations.
2. Please given that the satellites will follow the ISS orbit in the first days, make sure if scheduling to leave some empty spots for ISS observations.

[vk6drd]

CW and OQPSK aren’t going to be used this time around. The filing was put in for this mission and the next (B567), so we are hoping to implement this then.

Yes we have a research license around 441.25MHz, we will only be using this over Perth. 1621.25 is for the Iridium network. All three satellites have an Iridium 9603 transceiver on them. There is also an S-band transmitter on all three satellites which we will be testing. However, only over Perth, Australia, and Darmstadt, Germany.

Only 9k6 for now, we may try out 19k2 later. Unfortunately, we could never get 1k2 working on the ground so I doubt we will try it.

[pe2bz]

I am close enough to Germany

[pu4elt]

Sakura is alive!! Observation #10136219

[yd9ckh]

is there any new TLE for new Satellite?

[chillyphilly]

This looks like some Binar’s are alive
https://network.satnogs.org/observations/10135909/
If so congrats to the team!

[pu4elt]

CosmoGirl-Sat also!!

https://network.satnogs.org/observations/10136654/

[PE0SAT]

They are deployed from ISS, so for now use the ISS TLE

[PY4ZBZ]

[pu4elt]

Received here too Roland !!!

Parabéns pela sua recepção

[vk6tpw]

Binar 2 3 4 on the waterfall plot.

[PE0SAT]

Preliminary TLE created and can found via this link, for the creation I used the last ISS TLE.

[fredy]

@vk6tpw is there an interval for the binar transmissions?

[PY4ZBZ]

[PY4ZBZ]

[dl7ndr]

Regarding SAKURA:

JS1YMY, that’s interesting.

Looking at the call for listen for CW beacon poster the callsign should be JS1YNI.

Looking also on the first decodeable 4k8 beacon on network (thanks @PE0SAT) it prints

  000:  4a 53 31 59 4d 59 30 4a 53 31 59 4e 49 30 3e f0  JS1YMY0JS1YNI0>.                                            
  010:  53 11 ff 00 00 01 00 04 00 00 00 05 00 00 00 06  S...............                                            
  020:  00 38 00 08 10 80 03 f1 02 40 04 1a 02 40 05 b0  .8.......@...@..                                            
  030:  10 00 05 b2 00 00 05 b5 00 00 05 b6 10 00 05 eb  ................
  040:  a0 00 06 21 30 00 06 40 e0 00 06 9a 10 00 00 00  ...!0..@........
  050:  00 45 01 00 00 ff                                .E....

Besides it does not comply with AX.25 protocol (as Kashiwa missed also) since the callsigns are not bitshifted, it states JS1YNI as the sender callsign.
JS1YMY is at the position for the destination callsign.

SAKURA’s website reveals it:
Initially right after deploy, the CW callsign is “sixxxx” (x as a variable value).

" but it will later be changed to the actual callsign."

Seems they just not changed it to JS1YNI yet.

The format is:

SAKURA JS1YMY JS1YNI DATA
SAKURA GROUND SATELLITE DATA

[dl7ndr]

Since there are no reports from SaganSat 0 yet and the observations from network are also bad, please have a look on 437.050 for a CW beacon starting by:

SAGAN0 JG6YPC

The interval is 80 seconds.

If you receive the beacon, please send it to jaxaga-highschool@yumeginga.jp.

The responsible operator Akinori Ito JF6BYD (according to IARU coordination) provided me also the CW beacon format.

SaganSat 0 - CW beacon format (interval 80 seconds).pdf (114.7 KB)

[vk6drd]

Binar-2, and 3 have a 5 second interval, and Binar-4 has a 10 second interval.

[vk6tpw]

Hey, just a quick note, a beacon would look like this

aa aa aa aa d3 91 d3 91 cb ff 01 01 11 11 42 49 44 3a 20 42 69 6e 61 72 51 4d 4f 70 20 4d 6f
64 65 3a 20 41 4d 56 4b 36 42 53 50 20 42 69 6e 61 72 32 33 34 2d 43 6f 6e 74 61 63 74 20
62 69 6e 61 72 73 70 61 63 65 2e 63 6f 6d c0 c0 c0 bb 07 02 10 02 0b 01 01 11 0f 1a b7 19 f7
18 08 18 c0 19 d9 18 4f 19 17 1b 01 14 f0 19 4f 38 87 47 98 32 28 16 15 13 22 18 e7 1c 2c 1f
17 04 2c 1f 17 0d 7e 23 22 15 d0 14 e0 18 2f 3f 61 3d 04 80 db 3c 01 03 8c 3b 1e dc 87 3f 3d
6f 94 3b fb 7a 74 3b 7d 2a 1d 3d a7 d6 b1 36 e7 02 f2 37 30 ad 17 38 15 01 10 0b 01 0f f2 a0
8b 38 c5 68 07 b8 3b aa 85 37 01 01 01 01 01 01 01 01 01 01 01 01 00 02 01 ff ff af 72

aa aa aa aa, preamble
02 01 BLT hardware ID (will be 0x 01 where x is a number from 1 to 9)
d3 91 d3 91 synk words
cb length of beacon

[dl7ndr]

SAKURA has changed its beacon to SAKURA JS1YMY JS1YNI

2024-08-30 04:05:22 UTC
SAKURA JS1YMY JS1YNI A485C37128A10410

2024-08-30 04:09:18 UTC
SAKURA JS1YMY JS1YNI A480C57028A10410