Hold on.
You wrote:
So we both don’t talk about KNACKSAT-2’s transmissions, but those test transmissions from Bangkok ground station.
And I don’t believe that a station 600 km apart is able to pick that up.
So, are you sure the station in Chiang Mai is capable of that?
No, the reception in Chiang Mai wasn’t a direct link from Bangkok.
The path looked like this:
KMUTNB (Bangkok) → KNACKSAT-2 → Chiang Mai
Now understood.
I took your “directly” as I used it.
But you mean via KNACKSAT-2.
Thanks for clarification.
2026-04-08 09:37 ~ 09:43 UTC on a almost zenith pass:
no signals and response from KNACKSAT-2’s digipeater.
E25YUS read/ack my messages and will answer the questions at community soon.
You don’t see it in this example, because there is no digipeater callsign.
The hbit is the most significant bit in the digipeaters SSID byte.
Since my gr-satellites UPloader only uploads if this hbit is set, I’ve prepared another GNU Radio flowgraph to check just for HS0K in the digipeater field (without hbit set) to upload the packet.
Please enter your callsign or station name along with your coordinates into the Telemetry Forwarder block before use.
SatNOGS_uploader_for_KNACKSAT_2_digipeater.grc.zip (1.4 KB)
2026-04-08 12:5x UTC zenith pass: no signal or response from KNACKSAT-2’s digipeater.
I just saw the beacon telemetry, and it looks like the repeater is turned off right now. I will figure out what’s going on and turn it back on during the next pass over the KMUTNB gs.
The repeater module is scheduled to be turned on at 16:00 Thailand time (09:00 UTC). I will try to enable it and update everyone once it’s on
Will be able to try again on Saturday.
DO1AM was able to digipeat 3 times via KNACKSAT-2 on 2026-04-09 at 10:02:08, 10:04:37 and 10:04:43 UTC and uploaded it.
The digipeater callsign was however not HS0K but 0x61 0x48 0x77 0x64 0x3b 0xd4 (aHwd; ).
Something broken?
Almost sounds like the received (digipeated) packet had CRC errors?
The CRC is not uploaded.
But had there been any CRC errors, the packet would have been discarded.
The repeater module is currently powered off after a normal power cycle. My ground station is experiencing some issues at the moment. I expect to turn it back on around April 13, 09:00 UTC. Sorry for the inconvenience. Thank you all for your support of KNACKSAT-2.
Do you read that from a value?
How long last a normal power cycle?
The next time after the 13th I could give the digipeater a try would be the 15th.
I’ve added KNACKSAT-2 to the digipeater dashboard.
Daniel
Update: The repeater module is now back online.
There is some data in the beacon that can be read, and I can provide more information. A normal power cycle typically lasts around 24 hours, and I will try to turn it on again each day.
Thank you for your patience and support
Please, go ahead.
DO1AM was again digipeated.
On 2026-04-13 at 10:06:48 and 10:07:16 UTC.
And this time the digipeater callsign was correct HS0K!
However something seems to be not working correctly with the dashboard database.
@gkc , could you try to turn on again the digipeater for tomorrow?
I’ve tried it half an hour ago at a 30° pass without success.
Daniel
