Thanks very much for the info!
I’m not familiar w/ an IoT/LoRaWAN bandplan “AS-1”… I wonder if that is what is in the documentation currently as “AS923”?
I believe AS923 is another name for the same bandplan, yes. Uplink at 922.1 seems to fit the ITU allocation. This is “channel 9” in that bandplan, 922.1 MHz mode SF7 BW250.
1 Like
Finally I received Kashiwa:
2024-04-21 08:5x utc
kashiwa js1ymx
kashiwa js1ymx a484c76d0fe80001
kashiwa js1ymx a484c76c11e10001
kashiwa js1ymx a484c76b0fe10001
Only CW, no 4k8.
2 Likes
You are right, ENSFNM.
JG6YBW has been recycled several times for satellites from Kyutech (Horyu 2 and 4, Aoba-Velox III and FUTABA) and they also used JG6YMX for TSURU from BIRDS 4 project already.
The CW format might fit to Horyu and FUTABA referred to the length, however the meaning of the values seems different.
And looking at the hex values (4A 47 36 59 42 57 30 4A 47 36 59 4D 58 30 for JG6YBW0JG6YMX0) they forgot to bitshift it (one bit to the left). That’s why it is recognized as “NON-AX25 frame” in Soundmodem.
3 Likes
I wonder if they reassigned the call from Horyu-4 to Kashiwa, given that it’s on the same frequency? It would be a bit odd to transfer it from KyuTech to Chiba, especially if Horyu-4 is still active…
I don’t think so. Yes, it would be very odd. Seems more like a programming error or they missed something to change.