There is a new TLE set from space-track.org:
0 TBA - TO BE ASSIGNED
1 88780U 25241B 26076.16756657 .00008123 00000-0 35927-3 0 9992
2 88780 51.6328 37.2941 0004522 180.4379 179.6594 15.22522171 884
Changed to use temporary NORAD ID in DB:
Ten-Koh 2
1 98542U 25241B 26076.16756657 .00008123 00000-0 35927-3 0 9999
2 98542 51.6328 37.2941 0004522 180.4379 179.6594 15.22522171 881
With the help of @tammojan and @cgbsat we managed to get our first CW signals from the Dwingeloo telescoop station:
The TLE is very good, so as soon as the object gets assigned we can move forward with identification.
It is clear that the satellite has some transmission issues, maybe due to not deployed antennas or something else.
Also note the fading of the signal in the 5th transmission, which is hard to see in station 384 which has the horizontal polarization, but easier to see in station 2338, which is vertical
Replaying the observation and decoding CW
JS1YKI:28FA380ED3163517FF18C18D0
JS1YKI:28FA3793D6263677FF18C18E0
JS1YKI:28FA382BD2063717FF18D1900
JS1YKI:28FA37EDD4063577FF18F1910
Using the TEN-KOH 2 CW Decoder we get the following results.
[INFO] AppConfig
{
"targetString": "JS1YKI",
"ReferencedFilePath": "C:\\path",
"ReferencedFolderPath": "C:\\path",
"extractedDataLength": 25
}
[INFO] App Directory: C:\Temp
[INFO] Decode Data
{
"Callsign": "JS1YKI",
"Input": "28FA380ED3163517FF18C18D0",
"TimeStamp": "2026/03/17 20:17:56",
"GPIOExpander": "True",
"BatteryCurrent": 0.09,
"BatteryStatus": "Discharging",
"BatteryVoltage": 4.12,
"BatteryTemperature": 12.1,
"WDUTemperature": 9.5,
"MCUTemperature": 10.21,
"OperationMode": "Nominal Mode",
"EPSControllerStatus": "Invalid",
"SubsystemInterfaceStatusBits": {
"SystemCheck": "Subsystem Interface Error Detected",
"_I2C_RTC": "FAULT",
"_I2C_MEM": "STABLE",
"_I2C_EPSC": "STABLE",
"_I2C_COM": "STABLE",
"_I2C_ANT": "STABLE",
"_I2C_IFPV": "STABLE",
"_I2C_ADCS": "STABLE",
"_I2C_CAM": "STABLE",
"_I2C__MATLIU": "STABLE",
"_I2C_NU": "STABLE",
"_UART_JAMSAT": "STABLE"
},
"StatusBits": {
"_5V_CAM": "OFF",
"_5V_PL": "OFF",
"_5V_NUM": "OFF",
"_3V3_JAMSAT": "OFF",
"_3V3_ADCS": "OFF",
"_5V_OBC": "ON",
"_5V_ADCS": "OFF",
"_5V_COM": "ON",
"_12V_ADCS": "OFF",
"_12V_LIU": "OFF"
},
"JamsatStatusBits": null,
"JamsatTelemetry": null
}
[INFO] App Directory: C:\Temp
[INFO] Decode Data
{
"Callsign": "JS1YKI",
"Input": "28FA3793D6263677FF18C18E0",
"TimeStamp": "2026/03/17 20:21:17",
"GPIOExpander": "True",
"BatteryCurrent": -0.67,
"BatteryStatus": "Charging",
"BatteryVoltage": 4.18,
"BatteryTemperature": 12.28,
"WDUTemperature": 9.5,
"MCUTemperature": 10.93,
"OperationMode": "Nominal Mode",
"EPSControllerStatus": "Invalid",
"SubsystemInterfaceStatusBits": {
"SystemCheck": "Subsystem Interface Error Detected",
"_I2C_RTC": "FAULT",
"_I2C_MEM": "STABLE",
"_I2C_EPSC": "STABLE",
"_I2C_COM": "STABLE",
"_I2C_ANT": "STABLE",
"_I2C_IFPV": "STABLE",
"_I2C_ADCS": "STABLE",
"_I2C_CAM": "STABLE",
"_I2C__MATLIU": "STABLE",
"_I2C_NU": "STABLE",
"_UART_JAMSAT": "STABLE"
},
"StatusBits": {
"_5V_CAM": "OFF",
"_5V_PL": "OFF",
"_5V_NUM": "OFF",
"_3V3_JAMSAT": "OFF",
"_3V3_ADCS": "OFF",
"_5V_OBC": "ON",
"_5V_ADCS": "OFF",
"_5V_COM": "ON",
"_12V_ADCS": "OFF",
"_12V_LIU": "OFF"
},
"JamsatStatusBits": null,
"JamsatTelemetry": null
}
[INFO] App Directory: C:\Temp
[INFO] Decode Data
{
"Callsign": "JS1YKI",
"Input": "28FA382BD2063717FF18D1900",
"TimeStamp": "2026/03/17 20:21:54",
"GPIOExpander": "True",
"BatteryCurrent": 0.26,
"BatteryStatus": "Discharging",
"BatteryVoltage": 4.1,
"BatteryTemperature": 12.46,
"WDUTemperature": 10.21,
"MCUTemperature": 12.35,
"OperationMode": "Nominal Mode",
"EPSControllerStatus": "Invalid",
"SubsystemInterfaceStatusBits": {
"SystemCheck": "Subsystem Interface Error Detected",
"_I2C_RTC": "FAULT",
"_I2C_MEM": "STABLE",
"_I2C_EPSC": "STABLE",
"_I2C_COM": "STABLE",
"_I2C_ANT": "STABLE",
"_I2C_IFPV": "STABLE",
"_I2C_ADCS": "STABLE",
"_I2C_CAM": "STABLE",
"_I2C__MATLIU": "STABLE",
"_I2C_NU": "STABLE",
"_UART_JAMSAT": "STABLE"
},
"StatusBits": {
"_5V_CAM": "OFF",
"_5V_PL": "OFF",
"_5V_NUM": "OFF",
"_3V3_JAMSAT": "OFF",
"_3V3_ADCS": "OFF",
"_5V_OBC": "ON",
"_5V_ADCS": "OFF",
"_5V_COM": "ON",
"_12V_ADCS": "OFF",
"_12V_LIU": "OFF"
},
"JamsatStatusBits": null,
"JamsatTelemetry": null
}
[INFO] App Directory: C:\Temp
[INFO] Decode Data
{
"Callsign": "JS1YKI",
"Input": "28FA37EDD4063577FF18F1910",
"TimeStamp": "2026/03/17 20:22:22",
"GPIOExpander": "True",
"BatteryCurrent": -0.12,
"BatteryStatus": "Charging",
"BatteryVoltage": 4.14,
"BatteryTemperature": 12.1,
"WDUTemperature": 11.64,
"MCUTemperature": 13.07,
"OperationMode": "Nominal Mode",
"EPSControllerStatus": "Invalid",
"SubsystemInterfaceStatusBits": {
"SystemCheck": "Subsystem Interface Error Detected",
"_I2C_RTC": "FAULT",
"_I2C_MEM": "STABLE",
"_I2C_EPSC": "STABLE",
"_I2C_COM": "STABLE",
"_I2C_ANT": "STABLE",
"_I2C_IFPV": "STABLE",
"_I2C_ADCS": "STABLE",
"_I2C_CAM": "STABLE",
"_I2C__MATLIU": "STABLE",
"_I2C_NU": "STABLE",
"_UART_JAMSAT": "STABLE"
},
"StatusBits": {
"_5V_CAM": "OFF",
"_5V_PL": "OFF",
"_5V_NUM": "OFF",
"_3V3_JAMSAT": "OFF",
"_3V3_ADCS": "OFF",
"_5V_OBC": "ON",
"_5V_ADCS": "OFF",
"_5V_COM": "ON",
"_12V_ADCS": "OFF",
"_12V_LIU": "OFF"
},
"JamsatStatusBits": null,
"JamsatTelemetry": null
}
Jan | PE0SAT
Is the CW beacon on by default for passes over Europe?
Stefan/OE6ISP
It seems to be, we did not coordinate yesterdayâs observation.
⌠itâs because I could not see anything on my high-gain antenna during the last 23:23z pass. Do you think the signal is the same strength RSP-03 was? On your observation for me it seems to be weaker.
This is a plot of the signal strength in the Dwingeloo observations 13607473 and 13607474. The signal strengths 20-25dB are comparable to those of RSP-03.
There is a nice pattern in the signal strength, but I donât see an obvious tumbling pattern.
One more TLE update from space-track.org:
0 TBA - TO BE ASSIGNED
1 88780U 25241B 26076.88958285 .00007258 00000-0 32249-3 0 9994
2 88780 51.6333 33.8625 0004506 183.0830 177.0120 15.22532704 996
and the changed one to follow the temporary NORAD ID in DB:
Ten-Koh 2
1 98542U 25241B 26076.88958285 .00007258 00000-0 32249-3 0 9991
2 98542 51.6333 33.8625 0004506 183.0830 177.0120 15.22532704 993
Interesting diagram indeed! This doesnât match the scheme of a rotating linear pol antenna, as we could see with the RSP-03 showing 2 sine-waves for h and v, but according to my experience with measuring spin with satellites with known attitude and spin, the sudden deep drops in signal strength come from obstruction of (parts) of the antenna by the spacecraft. This usually happens, when the antenna is not facing toward earth. This leads me to the speculation, that the antenna might be in a vertical plane, rotating mainly around the vector of orbital movement of the spacecraft.
Here it is during 16:30z-pass in JN77pa. Very weak, not even as strong as the sun@435MHz,
3-4dB above cold sky on the 42-ele LHCP. Starting at 16:31z in https://network.satnogs.org/observations/13609701/
Stefan/OE6ISP
We have a TLE outside the analyst list from space-track.org, still not assigned but now we can set DB to follow it:
0 TBA - TO BE ASSIGNED
1 68261U 25241B 26077.87414291 .00007938 00000-0 35116-3 0 9991
2 68261 51.6342 29.1833 0004488 186.7062 173.3856 15.22548355 1145
Beacon from pass at 16:03z in JN77pa, 6dB above noise
JS1YKI: 28FA3757D5A63577FF18A18B0
[INFO] Decode Data
{
âCallsignâ: âJS1YKIâ,
âInputâ: â28FA3757D5A63577FF18A18B0â,
âTimeStampâ: â2026.03.19 17:59:42â,
âGPIOExpanderâ: âTrueâ,
âBatteryCurrentâ: -1.03,
âBatteryStatusâ: âChargingâ,
âBatteryVoltageâ: 4.17,
âBatteryTemperatureâ: 12.1,
âWDUTemperatureâ: 8.07,
âMCUTemperatureâ: 8.78,
âOperationModeâ: âNominal Modeâ,
âEPSControllerStatusâ: âInvalidâ,
âSubsystemInterfaceStatusBitsâ: {
âSystemCheckâ: âSubsystem Interface Error Detectedâ,
â_I2C_RTCâ: âFAULTâ,
â_I2C_MEMâ: âSTABLEâ,
â_I2C_EPSCâ: âSTABLEâ,
â_I2C_COMâ: âSTABLEâ,
â_I2C_ANTâ: âSTABLEâ,
â_I2C_IFPVâ: âSTABLEâ,
â_I2C_ADCSâ: âSTABLEâ,
â_I2C_CAMâ: âSTABLEâ,
â_I2C__MATLIUâ: âSTABLEâ,
â_I2C_NUâ: âSTABLEâ,
â_UART_JAMSATâ: âSTABLEâ
},
âStatusBitsâ: {
â_5V_CAMâ: âOFFâ,
â_5V_PLâ: âOFFâ,
â_5V_NUMâ: âOFFâ,
â_3V3_JAMSATâ: âOFFâ,
â_3V3_ADCSâ: âOFFâ,
â_5V_OBCâ: âONâ,
â_5V_ADCSâ: âOFFâ,
â_5V_COMâ: âONâ,
â_12V_ADCSâ: âOFFâ,
â_12V_LIUâ: âOFFâ
},
âJamsatStatusBitsâ: null,
âJamsatTelemetryâ: null
}
Stefan/OE6ISP
wow. incredible
âŚ. pretty the same as the sun@432MHz for SFU=35
Since it takes a 20m dish to receive Ten-Koh 2, thereâs no way that I saw this much of a CW signal from it on a 2.5-turn helical omni tonight, right?
Could not make out any real CW patterns either visually or on replay over the speaker.
Looks like it is the CW telemetry indeed, which is possible even with this antenna and the bird in favourable position. The problem is, that you need at least 6db above noise for 30 seconds without qrm and qsb to decode the whole dataset. This is of course easier with the 25m dish. I was only lucky once so far with the eme-tower to get the complete data, even though I can see a signal with cw-fragments during many passes. Stefan/oe6isp
Another Dwingeloo observation of Ten-Koh 2: 13635374 / 13635375. Signal strength is comparable to the previous observation. In fading, we now saw a null in the first and second CW beacon on horizontal polarization.
Replay the 2026-03-21 15:19:32 PI9RD observation.
JS1YKI:28FA3780D4363677FF18A18B0
JS1YKI:28FA37D9D1463677FF18A18C0
JS1YKI:28FA3774D4363677FF18B18C0
JS1YKI:28FA3755D5363577FF18B18C0
JS1YKI:28FA3838CEF63777FF18C18D0