From JAXA site: 「きぼう」から超小型衛星3機を2024年4月11日(木)に放出する予定です | 「きぼう」利用のご案内 | JAXA 有人宇宙技術部門
KASHIWA info from JAMSAT-BB
- Callsign: JS1YMX
- UHF downlink(CW, GMSK:4800bps AX.25, FM): 437.375MHz
- APRS digipeater(AFSK): 145.825MHz
6 Likes
KASHIWA TLE from CHIBA INSTITUTE OF TECHNOLOGY.
KASHIWA
1 99999U 99999A 24102.44119213 0.00000000 00000-0 00000-0 0 9994
2 99999 51.6536 286.3632 0017326 70.1835 307.5241 15.48932041 05
2 Likes
All satellites from this deployment have been added in DB and scheduled in Network for the next 48h.
@JH4XSY thanks for the info
The TLE set is added in DB too but changed to use the temporary NORAD ID we use for KASHIWA in DB:
KASHIWA
1 99197U 99999A 24102.44119213 0.00000000 00000-0 00000-0 0 9994
2 99197 51.6536 286.3632 0017326 70.1835 307.5241 15.48932041 05
2 Likes
MicroOrbiter-1 is alive… CW only for the moment. (https://twitter.com/scott23192/status/1778427473207628252
5 Likes
Oh my - I didn’t realize that CURTIS was also on 400.960. I hope that actually was MicroOrbiter-1 that I saw.
The entire CW transmission was not clear, so I didn’t try to decode it. However, I did see “M O 1” at one spot, so hopefully that’s an indication that it was MicroOrbiter-1.
Time will tell - thanks for the additional info!!
2 Likes
Just in case, the 400.960 MHz was for both satellites in ITU entries, tbh without a clear decoding I’m not sure if those signals belong to these satellites. However the signal curve on waterfall increases a lot the chances.
As you said, let’s keep watching.
2 Likes
Still only CW from the newly deployed sats, but my own as well as SatNogs observations make it clear that there are signals from at least 2 different objects. This morning’s pass had a clear " C U R T I S " decode in one of them. Now the wait is on to see what other modes show up!
3 Likes
there is 2 CW signal when ISS pass. The right one is CURTIS. Still don’t know the other one.
this is CW decode : O O R A M O S A T A 1 8 4 C 1 0 0 0 0 8
Im upload the video IQWAV recorded
https://drive.google.com/file/d/1Y5iSt0hnw7WVE2J2Gndc2O3YVOUnkQRq/view?usp=sharing
4 Likes
We have 3 TLE sets from space-track.org:
0 OBJECT A
1 59483U 98067WF 24103.92013684 .00060617 00000-0 10269-2 0 9992
2 59483 51.6372 279.0122 0003914 98.7836 261.3597 15.50943166 302
0 OBJECT B
1 59507U 98067WG 24104.04885101 .00048537 00000-0 82192-3 0 9996
2 59507 51.6374 278.3723 0003426 110.1548 249.9810 15.51052407 330
0 OBJECT C
1 59508U 98067WH 24103.98454405 .00061205 00000-0 10354-2 0 9995
2 59508 51.6371 278.6926 0003950 102.0756 258.0676 15.50978607 327
From Network observations and ikhnos:
OBJECT WG (B) is further from the other two and also fits CURTIS
OBJECT WH(C) seems to be MicroOrbiter-1 but needs some more observations to verify it
So, it remains OBJECT WF (A) for KASHIWA.
I’ve changed all the satellite entries to follow the above NORAD IDs until we finally identify them. It is interesting that the naming doesn’t follow as usually the naming in the first line, also interesting that the NORAD IDs are not sequential. I think we should wait a little more before any identification.
5 Likes
Looks like CelesTrak has firmed up the assignment of TLEs for KASHIWA, CURTIS, & MicroOrbiter-1… has KASHIWA been heard?
CURTIS
1 59483U 98067WF 24108.62260807 .00102996 00000+0 16754-2 0 9996
2 59483 51.6363 255.6673 0003055 100.7931 259.3403 15.51845702 1031
MICROORBITER-1
1 59507U 98067WG 24109.00877043 .00096884 00000+0 15768-2 0 9994
2 59507 51.6366 253.7459 0002437 115.0485 245.0758 15.51862054 1100
KASHIWA
1 59508U 98067WH 24108.62251705 .00111523 00000+0 18103-2 0 9997
2 59508 51.6361 255.6673 0002988 102.1489 257.9835 15.51864588 1042
1 Like
Not as far as I know, we went over multiple obs but no signals found, not on VHF nor on UHF
2 Likes
About KASHIWA I agree that it is 59508, not because it is heard (tbh I haven’t checked the latest observations) but because we have fit for the other two.
For the other two I think we have a mis-identification from celestrak, however I’m going to schedule more observations to verify before finalizing our identification.
Here are the data that show mis-identification, below are the results of ikhnos on observation 9371357, the signal at the middle and left is Microorbiter-1 (its signal is in lower frequency than CURTIS) and it has a curve to the left as the used TLE was the one of KASHIWA(59508) for this observation. The signal at the middle and right, as well as the signal at the bottom are from CURTIS, the singal at the middle has a curve going to the right.
With the red line you see the expected curve for each object of the three by following the TLE sets. As you can see the OBJECT WF (59483) fits the left curved signal of MicroOrbiter-1 while the OBJECT WG (59507) fits the right curved signal of CURTIS. OBJECT WH (59508) is straight as this was the one used for this observation, and it doesn’t fit any of the signal as both are curved.
OBJECT WF - center frequency at 400.9611 MHz (the one of MicroOrbiter-1)
OBJECT WG - center frequency 400.9639 (the one of CURTIS)
OBJECT WH - center frequency at 400.9611 MHz
Similar results we have also if we use ikhnos on SatNOGS Network - Observation 9369496
3 Likes
Since Kashiwa’s beacons were received by pi9cam’s 25m dish, probably the antenna has not (yet) deployed.
I had no luck on nine passes so far.
The received data (CW and 4k8) doesn’t fit the published format.
3 Likes
If anyone other than me has been watching for downlinks other than CW on 400.960 from MicroOrbiter-1, I got word that at least for now, it’s only downlinking the IoT/LoRaWAN packets over Japan.
It wasn’t stated or implied, but hopefully that might change at some point later in the mission.
3 Likes
The original approval used LoRa bandplan “AS-1” which isn’t compatible with bandplans in most other countries, though perhaps uplinks in other countries could work as long as they are still within the local ISM band there.
1 Like
Upon further review, the decode above from JE9PL has the callsign “JG6YBW” which matches with Horyu-4 (41340) from KyuTech. This was previously used by Horyu-2 (38340) as well. It is worth noting this is also on the same frequency as Kashiwa, 437.375. It is a bit odd that the doppler matches perfectly in the PI9CAM observation. This also might help explain the discrepancy in format mentioned above by @dl7ndr.
2 Likes