Dear @fredy ,
The TLEs for the satellites launched in the Kakushin Rising mission have recently been updated. However, it appears that the provisional TLE currently registered for KOSEN-2R in the SatNOGS DB does not correspond to any of the currently unidentified objects B, C, or H.
To ensure accurate observations and tracking, I believe it would be preferable to update the TLE in the database. Could you please advise on how we should proceed?
Best regards,
JF6FYI, Kazuki NISHIOKA
Feel free to upload both decodable CW beacons (2 and 3) to the dashboard.
2026-05-11T07:13:59 00730ad0d900
2026-05-11T07:14:40 a8575ead1708eb
Hello @dl7ndr ,
Thank you very much for decoding the CW beacon from my reception data!
I have promptly uploaded it to the dashboard.
Indeed we donât follow any of the objects for KOSEN-2R. Unfortunately Iâm not able to check right now which one could be the best to follow, but here are some steps:
After having an object, you can suggest a satellite change by updating the Followed Norad ID and the citation field linking to either a post here in the forum with an analysis/explanation on the selected object or a link to tinygs if thatâs the case. This suggestion will be reviewed as soon as possible.
Dear @fredy ,
I sincerely apologize for my delayed reply.
Thank you very much for your suggestions regarding the identification of the tracking objects for KOSEN-2R.
At present, even Yonago National College of Technology, the developer of KOSEN-2R, has not yet been able to establish communication with the satellite, and therefore the existence of any signals remains unclear. For this reason, it is currently difficult to infer the correct object based on observations from the SatNOGS or TinyGS networks as proposed in methods 1 and 2.
The third method may be possible as a temporary approach. However, due to the reasons mentioned above, it is still not possible to conclusively identify each object.
Therefore, it may be better to wait until the other two satellites are positively identified.
I will also continue gathering information on our side in an attempt to identify the objects.
Best regards,
Kazuki Nishioka
can the team confirm that the telemetry freq at db.satnogs.org is correct ? is all freq auto activated when the sat deployed? if not what main freq ? btw can the team provide the iq file example ?
Hello Bali,
Understood. I will check to them whether they can provide information regarding the current tracking objects and the transceiver information, as well as sample IQ files.
Please wait for a while.
At around 2026-05-26 07:10 UTC, my SatNOGS GS successfully received the AFSK 1k2 telemetry downlink from OrigamiSat-2.
From a total of 59 received packets, I successfully reconstructed an thumbnail image captured by the onboard camera showing the deployed origami antenna membrane together with the Earth! 
SatNOGS Network - Observation 14154300
Congratulations. Great job. Do we know if such downlinks will occur for other parts of the world or only over Japan?
Thanks,
Bob
N6RFM
ARICA-2 26.05.2026 13:10-13:20 UTC
Best serie of beacons
CQCQ DE JS1YSD ARICA2
8FFE8514E0000024
00D36D9C4800
00D7C0A8D6F0E8
From my observation - https://sonik.space/observations/1360478/
Beacon data was sent via google form to operators
OrigamiSat-2 13:07-13:17 UTC
JS1YRU ORIGAMI2 81 7E 79 2B 84 12 01 80 7E 7A 90 00 00 00 00 83 84 BB 00 6A 18 3E B6 4B 42 48 3E 00
JS1YRU ORIGAMI2 81 7E 78 C2 85 16 01 80 7E 7C 90 00 00 00 00 84 84 BB 00 6A 18 3F 02 4B 42 48 3E 00
thank you je9pel
However, because the Huffman Table is corrupted, standard JPEG
decoders will likely report errors such as:
- âInvalid JPEGâ
- âCorrupted fileâ
- âSOS marker errorâ
- âHuffman table errorâ
that is true. good hack! cool!
i try using the hex data from above obs., select data tab.
then select all, and copy paste into text file. than remove unwanted text and hex,
( like remove first 16 bytes ax25 header - 94 A6 62 B2 9C AA 60 94 A6 62 B2 A4 AA E1 03 F0 ), search the jpeg header FF D8 and footer FF D9
remove space and newline, then the last and important remove the error source , remove the huffman (FFC4 ⌠), remove the crc check (2 bytes at the end every line)
then running
xxd -r -p final.txt final.jpg
and voila result not perfect, buat at least better than other noob. lol
i put the file here, so other noobs can follow:
final.txt (7.8 KB)
origami-obs-jepang-bersih-header-ax.txt (39.5 KB)
origami-obs-jepang-bersih-header-ax2.txt (13.3 KB)
origami-obs-jepang-bersih-header-ax3.txt (12.2 KB)
origami-obs-jepang-bersih-header-ax4.txt (8.1 KB)
origami-obs-jepang-bersih-header-ax5.txt (8.1 KB)
if you have secret sauce to make it perfect, please show your code here
i try again, but without remove the huffman (FFC4)
origami-14154300-01.txt (37.5 KB)
origami-14154300-02.txt (12.6 KB)
origami-14154300-03.txt (11.8 KB)
origami-14154300-04.txt (11.7 KB)
origami-14154300-05.txt (11.6 KB)
origami-14154300-06.txt (7.7 KB)
xxd -r -p origami-14154300-06.txt final-14154300.jpg
and wow⌠cool:
thank you @nishikazu0417 for best obs!
conclusion: try first without remove the huffman. if the result is error like Bogus market length etc, try remove the huffman (FF C4 ..).
FSI-SAT2 02.06.2026 13:30-13:40 UTC
0 JS1YQU FSISAT 03.61V -0.12A 1.04D TTTEEEEEEEEE (ends at 13:32:47 UTC)
0 JS1YQU FSISAT 03.61V -0.13A 1.61D TTTEEEEEEEEE (ends at 13:33:51 UTC)
0 JS1YQU FSISAT 03.61V -0.13A 2.24D TTTEEEEEEEEE (ends at 13:34:55 UTC)
From my observation https://sonik.space/observations/1373653/
I have a question about this satellite - In the description (which is now not used) there was an mentoned ability to transmit photos in SSTV format. When this experiment start? Are there any more information about DTMF signals and the equipment needed? Is it worldwide? I think it i will be an interesting activity and I would like to take part in it.
I have received a reply from Associate Professor Tokumitsu, one of the members of the KOSEN-2R operations team at Yonago National College of Technology.
According to the information provided, the following details have been confirmed:
The object currently being tracked by the KOSEN-2R team is KAKUSHIN RISING OBJECT B (NORAD ID: 68793).
At present, the only planned transmitter mode is:
If communications are successfully established in the future, they may also consider:
Although the spacecraft is capable of transmitting DTMF signals, this mode is not expected to be used due to power consumption considerations.
The frequency 436.750 MHz, which was previously submitted to the IARU, will not be used for any transmissions.
In addition, they informed me that IQ samples of the transmitted signals should be available sometime next week.
Based on this information, I will update the corresponding entries in the SatNOGS Database. Please review the updates when they become available.
73,
Kazuki NISHIOKA, JF6FYI
Dear @fredy ,
I have one question regarding the SatNOGS DB update.
Since the current transmitter entry for KOSEN-2R contains frequency information that differs from the information provided by the KOSEN-2R operations team, would you prefer that I:
I would appreciate your preference before making any changes.
73,
Kazuki NISHIOKA, JF6FYI
For the ones at 465.360 with the non-LoRa transmissions I suggest you create new entries.
If the 436.750 was never planned to be used then I suggest you set as invalid the current entries at this frequency with citation that explain this, if they were planned but not active, I suggest you set them as inactive.
