|
|
Post by Noel WI4B on Mar 28, 2023 22:05:57 GMT
I get these decodes quite often with CALL<......> with a signal report or RR73 and no country, I believe them to be F/H messages but no call or country is decoded. The bell rings like it's a country that I need. Can anyone tell me why I'm not decoding these messages properly?
|
|
|
|
Post by w9mdb on Mar 28, 2023 22:11:37 GMT
The <....> indicates the callsign is "hashed" which means you need to decode them at least once in the clear.
You are probably seeing them as the 1st caller -- in other words somebody else is calling them and you have never decoded them.
e.g.
<.....> W9MDB -13
This goes hand-in-hand with all the people blind calling dxpeditions that they've never decoded as though they think it will work by magic somehow.
|
|
|
|
Post by Noel WI4B on Mar 28, 2023 23:26:41 GMT
What I'm seeing is example: W1XX <...> -04 __________W2XX <...> RR73_________W3XX <...> -08 ________
This goes on a long time and I never print the senders call sign or country  |
|
|
|
Post by w9mdb on Mar 29, 2023 3:17:16 GMT
So that's the flip case....
Some places almost never use TX1 which you need to see the true callsign.
So W1XX would have decoded them and sent a reply where the "other" callsign has to be hashed in order to fit in the message.
There's really nothing you can do about it except keep listening for TX1 which will contain the unhashed callsign.
|
|
|
|
Post by Arvo ES1JA on Mar 29, 2023 6:12:06 GMT
Usually callsign is most called callsign in opposite period. Or callsign called in 1799, 1849 freq. Mike give correct answer from technical aspect.
|
|
|
|
Post by Noel WI4B on Mar 29, 2023 13:43:52 GMT
OK, thank you. It sure is annoying!
|
|
