Re: [wsjt-devel] QSO 15 meters FT8 F/H not logged!

[Marco Calistri via wsjt-devel]

Amazing explanation of an "historical" and already well identified issue Grant!

Most likely I did read that post when Bill wrote it, but as you know things are differently digested when they affect you directly.

Regarding the "Fox file" you are right! I had found it but it contains some text may be I produced myself when I tried to be the Fox(?).
I think it is there just for the Fox usage and not for the Hounds.

-----------------FoxQSO.txt------------------------------
2021-09-24 21:01:50  0.000  0  0  0 NSlots 5
2021-09-24 21:01:50  0.000  0  0  0 Max_dB 70
2021-09-24 21:04:30  0.000  0  0  0 NSlots 5
2021-09-24 21:04:30  0.000  0  0  0 Max_dB 70
2021-09-25 14:00:09  0.000  0  0  0 NSlots 5
2021-09-25 14:00:09  0.000  0  0  0 Max_dB 70
2021-09-26 14:02:01  0.000  0  0  0 NSlots 5
2021-09-26 14:02:01  0.000  0  0  0 Max_dB 70
---

The searched strings (ZV8L, 3X2021) have been collected regularly into ALL.TXT, it was just a little mistake on the command issued to extract them.

---
73 de Marco, PY1ZRJ (former IK5BCU)



Il 19/02/22 18:51, Grant VK5GR via wsjt-devel ha scritto:

Folks,

 

Bill Somerville (sk) responded to a similar question that came up during the 3DA0RU expedition in October last year.

 

In summary:

 

1.       3X2021 does not fit the standard callsign pattern and so must use the “Hash Code” call way of processing a callsign and  QSO sequence  – where the <HASH>is a coded form of the callsign that shortens them to fit insite the number of bits available in the FT8 protocol, and which is then that is translated back to a full call by the receiving station once the receiving station sees a particular sequence transmitted.

 

2.       Back in October, Bill reported that the developers had identified a bug with WSJT where  if you use it in FOX mode and are running a non standard callsign that the sequencing will fail. I can’t find reference so far that they released a fox for that issue?

 

So this leaves the expedition with the problem what software to use where they want to run multi-stream to improve efficiency and QSO rate. This leads to the use of MSHV/WSJT-Z use.

 

As for how to ID exactly what mode they are running, you used to be able to tell when you at least knew the dial frequency the expedition station was on and could see their transmissions above 1000Hz on the waterfall – then it isn’t Fox Mode but MHSV multi-stream. Now however some of the other WSJT “variants”  appear to place their muti-streams at the bottom of the channel like WSJT-X fox mode so it makes the problem harder to identify. The fact that these variants don’t follow the full FOX protocol leads to more confusion too.

 

There are various solutions I suspect – but they require either a formal agreement between all of the variant developers to either follow the proper WSJT-X protocol for multi-stream OR to start broadcasting free text periodically with dial freq + software version automatically to give the hounds half a chance at working out what is going on.

 

Regards,

Grant VK5GR

 

P.S. with ALL.TXT – I am not sure in HOUND MODE, but I know in FOX mode that ALL.TXT does not capture every string. There is a separate FOX.TXT file I think it was called where the FOX/Hound QSO data is written – but it doesn’t capture all details either. (I had this issue when working through log issues on one of my previous expeditions (A35JT Tonga)).

 

 

 

From: Kari Sillanmäki via wsjt-devel [mailto:wsjt-devel@lists.sourceforge.net]
Sent: Sunday, 20 February 2022 1:14 AM
To: Marco Calistri via wsjt-devel
Cc: Kari Sillanmäki
Subject: Re: [wsjt-devel] QSO 15 meters FT8 F/H not logged!

 

Hi Marco,

AFAIK WSJT-X records everything it hears and sends to ALL.TXT file and there is no option to disable that.
So you should see youre QSO in ALL.TXT

Perhaps you are using configurations?
In that case the ALL.TXT wil be in directory
~/.local/share/WSJT-X - <your config name>

73's de Kari, oh2gqc

 

On 19.2.2022 14.27, Marco Calistri via wsjt-devel wrote:

Hi Saku!

Good command! But as I wrote, there is not any registry of the QSO in the ALL.TXT file simply because WSJT-X has not registered it!

Best regards,

---
73 de Marco, PY1ZRJ (former IK5BCU)


Il 19/02/22 05:01, Saku via wsjt-devel ha scritto:

Hi I
Think you were using linux. Then open command console and:

cd ~/.local/share/WSJT-X
grep -ni HisCall ALL.TXT | grep -i YourCall

Shows qso in fast and easy way (with line numbers of ALL.TXT).
Just replace the callsigns in command.

Jim Shorney via wsjt-devel kirjoitti 19.2.2022 klo 6.57:

You should be able to find this in your all.txt file.

73

-Jim
NU0C

On Sat, 19 Feb 2022 01:46:13 -0300
Marco Calistri via wsjt-devel <wsjt-devel@lists.sourceforge.net> wrote:

I asked to the DX station's QSL manager if he can send me the details of the QSO (Time and RST) registered by the Fox station on his ClubLog, so hopefully I could manually include the QSO also into my log.

_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel