FT8 - hashed callsigns - my callsign

[Sanny Sanoff]

Hello dear SparkSDR author. 

I'm currently traveling. My callsign has prefix. When using FT8 mode, SparkSDR behaves like my prefix is short, and sending the following (wrong) messages. At least it shows so:

CQ P1/AB1CDE MN45             

   - must send CQ P1/AB1CDE  because locator does not fit in the message.

   - ideally, sending DE <P1/AB1CDE> MN45 after the CQ, and repeat.

when i click the DX's CQ , it sends:

DX1XYZ P1/AB1CDE MN45

   - must send <DX1XYZ> P1/AB1CDE 

And also hashed callsigns are not decoded in the left list. I suspect this is all linked together, but there's real use of it ;)

Thanks a lot!

Alex.

[ahop...@googlemail.com]

Hi Alex,

I'll look into the encoding of of that message.  I'm aware there is an issue with hashed callsigns on decode levels 1,2,and 3, these use the wsjtx decoder and it does not pass enough info to display the hash. The inbuilt level 0 decoder should display received hashed callsigns correctly.

Thanks for the report, it is the first time anyone has mentioned hashed calls.

73 Alan M0NNB

[Thomas Beiderwieden]

Hi Alan,

still no luck with hashed calls. They are decoded, however a qso does not work, as SparkSDR will not see / accept the reply. Am I doing something wrong?

It is V 2.0.922

vy 73 de Thomas, DL3EL