Re: [wsjt-devel] QSO 15 meters FT8 F/H not logged!
Il 20/02/22 09:50, Saku via wsjt-devel ha scritto: Hi Marco! Reason that you could not get it working with my suggestion below, and needed "-a" is written here: "il file binario corrisponde". Bash thinks ALL.TXT is a binary file. How ever a clean ALL.TXT is pure text file and grep can handle it directly. Maybe your WSJT-X has crashed some day in past during the write of ALL.TXT and there are some "hieroglyphs" written to file that makes grep think it is a binary file. As seen your ALL.TXT size I suggest you move the file. cd ~/.local/share/WSJT-X mv ALL.TXT ALLOLD1.TXT WSJT-X then opens a new ALL.TXT on next start. Then you can make more ALLOLDx files, monthly, or by yearly basis. Depending how much you use WSJT-X. Hi Saku! Any news regarding CQRLOG updates? (answer me directly, if you prefer!). Yes, I could do what you suggested since my bash_history is not data but text type then the issue could be rightly on ALL.TXT file. Best regards! --- 73 de Marco, PY1ZRJ (former IK5BCU) ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] QSO 15 meters FT8 F/H not logged!
Hi Marco! Reason that you could not get it working with my suggestion below, and needed "-a" is written here: "il file binario corrisponde". Bash thinks ALL.TXT is a binary file. How ever a clean ALL.TXT is pure text file and grep can handle it directly. Maybe your WSJT-X has crashed some day in past during the write of ALL.TXT and there are some "hieroglyphs" written to file that makes grep think it is a binary file. As seen your ALL.TXT size I suggest you move the file. cd ~/.local/share/WSJT-X mv ALL.TXT ALLOLD1.TXT WSJT-X then opens a new ALL.TXT on next start. Then you can make more ALLOLDx files, monthly, or by yearly basis. Depending how much you use WSJT-X. -- Saku OH1KH Saku via wsjt-devel kirjoitti 19.2.2022 klo 10.01: i 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. ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] QSO 15 meters FT8 F/H not logged!
grep ALL.TXT -a ZV8L | grep -a PY1ZRJ grep: ZV8L: No such file or directory man grep: grep [OPTIONS] PATTERN [FILE...] So: grep -a ZV8L ALL.TXT | grep -a PY1ZRJ ;) ;) de Kari, oh2gqc On 19.2.2022 22.18, August Treubig via wsjt-devel wrote: Unix lesson. No need for CAT command. grep ALL.TXT -a ZV8L | grep -a PY1ZRJ Aug AG5AT Sent from my iPad On Feb 19, 2022, at 1:48 PM, Marco Calistri via wsjt-devel wrote: Hi again William! Please, be so kind to accept my apologies but you are extremely right! Using the -a switch has pemitted grep tp show the pattern correctly! marco@localhost:~/.local/share/WSJT-X> cat ALL.TXT |grep -a ZV8L|grep -a PY1ZRJ 220218_150746 24.915 Tx FT8 0 0.0 1964 ZV8L PY1ZRJ GG87 220218_150815 24.915 Tx FT8 0 0.0 1964 ZV8L PY1ZRJ GG87 220218_150830 24.915 Rx FT8 5 0.2 1470 PY1ZRJ ZV8L +01 220218_150845 24.915 Tx FT8 0 0.0 1964 ZV8L PY1ZRJ R+05 220218_150900 24.915 Rx FT8 8 0.2 1470 PY1ZRJ ZV8L RRR 220218_150915 24.915 Tx FT8 0 0.0 1964 ZV8L PY1ZRJ 73 220218_150930 24.915 Rx FT8 10 0.2 1469 PY1ZRJ ZV8L 73 And more important that the above, this one: marco@localhost:~/.local/share/WSJT-X> cat ALL.TXT |grep -a 3X2021|grep -a PY1ZRJ|grep RR73 *220218_181600 21.080 Rx FT8 -12 0.2 754 3X2021 RR73** **220218_183200 21.080 Rx FT8 -12 0.2 764 3X2021 RR73* Probably my bash history is causing that issue but it doesn't contains any data inside, just text. Great suggestion! Thanks again William!!! Best regards! Marco --- *73 de Marco, PY1ZRJ (former IK5BCU)* ** Il 19/02/22 14:01, Marco Calistri via wsjt-devel ha scritto: Hi William! This is not a matter of UNIX command syntax, the fact is that such string is not present in the file. Thanks and regards, Marco, PY1ZRJ Il 19/02/22 13:42, William Smith ha scritto: Try -a with grep as per https://unix.stackexchange.com/questions/335716/grep-returns-binary-file-standard-input-matches-when-trying-to-find-a-string 73, Willie N1JBJ On Feb 19, 2022, at 11:35 AM, Marco Calistri via wsjt-devel wrote: il file binario corrisponde ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] QSO 15 meters FT8 F/H not logged!
> On Feb 19, 2022, at 16:08, Jim Brown via wsjt-devel > wrote: > > I also like the faster "turn-around" after a QSO with JTDX that allows me to > call CQ or answer/call another station. It works that way because it > considers my mouse click to log the QSO as human intervention, and defaults > to calling CQ after receiving RRR or RR73 if those are not repeated. I just click on “Enable TX” as kind of a finger macro when I log a QSO and am running. :-) wsjt-x seems to do the right thing if I get a repeat of the RRR/RR73. Admittedly, not having to make an extra click could be nice, but I also drive a manual transmission. The clutch operation keeps me from dying from boredom in a traffic jam. And I remember JT9 as being as exciting as watching paint dry. (I have one JT9 QSO in my log.) 73 Bill AE6JV ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] QSO 15 meters FT8 F/H not logged!
Il 19/02/22 20:06, Jim Brown via wsjt-devel ha scritto: On 2/19/2022 2:23 PM, Marco Calistri via wsjt-devel wrote: Amazing explanation of an "historical" and already well identified issue Grant! Many of the answers to questions asked here are in the manual for WSJT-X. To reduce the load on the guys who provide support here, everyone should STUDY the manual first. 73, Jim K9YC Right! Regards, --- 73 de Marco, PY1ZRJ (former IK5BCU) ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] QSO 15 meters FT8 F/H not logged!
> On Feb 19, 2022, at 14:51, Grant VK5GR via wsjt-devel > wrote: > > As for how to ID exactly what mode they are running…. Let’s be clear. You’re not talking about MODEs here. Logged mode is till FT8. You’re talking about protocol or format. The mode is still FT8. Gary - AG0N ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] QSO 15 meters FT8 F/H not logged!
On 2/19/2022 2:23 PM, Marco Calistri via wsjt-devel wrote: Amazing explanation of an "historical" and already well identified issue Grant! Many of the answers to questions asked here are in the manual for WSJT-X. To reduce the load on the guys who provide support here, everyone should STUDY the manual first. 73, Jim K9YC ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] QSO 15 meters FT8 F/H not logged!
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 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
P
Re: [wsjt-devel] QSO 15 meters FT8 F/H not logged!
Il 19/02/22 18:08, Jim Brown via wsjt-devel ha scritto: On 2/19/2022 4:45 AM, Marco Calistri via wsjt-devel wrote: Very interesting! I was not aware of the MSHV software, IMHO it's not a good behavior to use "not standard" software expecting same results as it should work as per the "standard way". Fox/Hound mode is NOT a "standard way," it is a very special system for DXpeditions developed by the WSJT team, and implemented ONLY in WSJT-X. There are (at least) two other FT8 implementations, both from EU hams, JTDX and MSHV. Each has pluses and minuses. Many of us use JTDX for FT8, because it decodes more weak signals than the other two, but it doesn't do MS, Q65, FST4, or contest mode, so I use WSJT-X for those. MSHV decoding is comparable to WSJT-X, it does multi-stream, but without fox/hound frequency switching of the hound. I also like the faster "turn-around" after a QSO with JTDX that allows me to call CQ or answer/call another station. It works that way because it considers my mouse click to log the QSO as human intervention, and defaults to calling CQ after receiving RRR or RR73 if those are not repeated. 73, Jim K9YC Hu Jim, Good to know! I use only WSJT-X than I was not aware of the working differences among the other derivates. --- 73 de Marco, PY1ZRJ (former IK5BCU) ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] QSO 15 meters FT8 F/H not logged!
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 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 - 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 <mailto: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 ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] QSO 15 meters FT8 F/H not logged!
On 2/19/2022 4:45 AM, Marco Calistri via wsjt-devel wrote: Very interesting! I was not aware of the MSHV software, IMHO it's not a good behavior to use "not standard" software expecting same results as it should work as per the "standard way". Fox/Hound mode is NOT a "standard way," it is a very special system for DXpeditions developed by the WSJT team, and implemented ONLY in WSJT-X. There are (at least) two other FT8 implementations, both from EU hams, JTDX and MSHV. Each has pluses and minuses. Many of us use JTDX for FT8, because it decodes more weak signals than the other two, but it doesn't do MS, Q65, FST4, or contest mode, so I use WSJT-X for those. MSHV decoding is comparable to WSJT-X, it does multi-stream, but without fox/hound frequency switching of the hound. I also like the faster "turn-around" after a QSO with JTDX that allows me to call CQ or answer/call another station. It works that way because it considers my mouse click to log the QSO as human intervention, and defaults to calling CQ after receiving RRR or RR73 if those are not repeated. 73, Jim K9YC ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] QSO 15 meters FT8 F/H not logged!
Unix lesson. No need for CAT command. grep ALL.TXT -a ZV8L | grep -a PY1ZRJ Aug AG5AT Sent from my iPad > On Feb 19, 2022, at 1:48 PM, Marco Calistri via wsjt-devel > wrote: > > > Hi again William! > > Please, be so kind to accept my apologies but you are extremely right! > > Using the -a switch has pemitted grep tp show the pattern correctly! > > marco@localhost:~/.local/share/WSJT-X> cat ALL.TXT |grep -a ZV8L|grep -a > PY1ZRJ > > 220218_15074624.915 Tx FT8 0 0.0 1964 ZV8L PY1ZRJ GG87 > 220218_15081524.915 Tx FT8 0 0.0 1964 ZV8L PY1ZRJ GG87 > 220218_15083024.915 Rx FT8 5 0.2 1470 PY1ZRJ ZV8L +01 > 220218_15084524.915 Tx FT8 0 0.0 1964 ZV8L PY1ZRJ R+05 > 220218_15090024.915 Rx FT8 8 0.2 1470 PY1ZRJ ZV8L RRR > 220218_15091524.915 Tx FT8 0 0.0 1964 ZV8L PY1ZRJ 73 > 220218_15093024.915 Rx FT8 10 0.2 1469 PY1ZRJ ZV8L 73 > > And more important that the above, this one: > > marco@localhost:~/.local/share/WSJT-X> cat ALL.TXT |grep -a 3X2021|grep -a > PY1ZRJ|grep RR73 > > 220218_18160021.080 Rx FT8-12 0.2 754 3X2021 RR73 > 220218_18320021.080 Rx FT8-12 0.2 764 3X2021 RR73 > > Probably my bash history is causing that issue but it doesn't contains any > data inside, just text. > > Great suggestion! Thanks again William!!! > > Best regards! > > Marco > > --- > 73 de Marco, PY1ZRJ (former IK5BCU) > > > Il 19/02/22 14:01, Marco Calistri via wsjt-devel ha scritto: >> Hi William! >> >> This is not a matter of UNIX command syntax, the fact is that such string is >> not present in the file. >> >> Thanks and regards, >> >> Marco, PY1ZRJ >> >> Il 19/02/22 13:42, William Smith ha scritto: >>> Try -a with grep as per >>> >>> https://unix.stackexchange.com/questions/335716/grep-returns-binary-file-standard-input-matches-when-trying-to-find-a-string >>> >>> >>> 73, Willie N1JBJ >>> >>> On Feb 19, 2022, at 11:35 AM, Marco Calistri via wsjt-devel wrote: il file binario corrisponde >> >> >> >> >> ___ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] QSO 15 meters FT8 F/H not logged!
Hi again William! Please, be so kind to accept my apologies but you are extremely right! Using the -a switch has pemitted grep tp show the pattern correctly! marco@localhost:~/.local/share/WSJT-X> cat ALL.TXT |grep -a ZV8L|grep -a PY1ZRJ 220218_150746 24.915 Tx FT8 0 0.0 1964 ZV8L PY1ZRJ GG87 220218_150815 24.915 Tx FT8 0 0.0 1964 ZV8L PY1ZRJ GG87 220218_150830 24.915 Rx FT8 5 0.2 1470 PY1ZRJ ZV8L +01 220218_150845 24.915 Tx FT8 0 0.0 1964 ZV8L PY1ZRJ R+05 220218_150900 24.915 Rx FT8 8 0.2 1470 PY1ZRJ ZV8L RRR 220218_150915 24.915 Tx FT8 0 0.0 1964 ZV8L PY1ZRJ 73 220218_150930 24.915 Rx FT8 10 0.2 1469 PY1ZRJ ZV8L 73 And more important that the above, this one: marco@localhost:~/.local/share/WSJT-X> cat ALL.TXT |grep -a 3X2021|grep -a PY1ZRJ|grep RR73 220218_181600 21.080 Rx FT8 -12 0.2 754 3X2021 RR73 220218_183200 21.080 Rx FT8 -12 0.2 764 3X2021 RR73 Probably my bash history is causing that issue but it doesn't contains any data inside, just text. Great suggestion! Thanks again William!!! Best regards! Marco --- 73 de Marco, PY1ZRJ (former IK5BCU) Il 19/02/22 14:01, Marco Calistri via wsjt-devel ha scritto: Hi William! This is not a matter of UNIX command syntax, the fact is that such string is not present in the file. Thanks and regards, Marco, PY1ZRJ Il 19/02/22 13:42, William Smith ha scritto: Try -a with grep as per https://unix.stackexchange.com/questions/335716/grep-returns-binary-file-standard-input-matches-when-trying-to-find-a-string 73, Willie N1JBJ On Feb 19, 2022, at 11:35 AM, Marco Calistri via wsjt-devel wrote: il file binario corrisponde ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] QSO 15 meters FT8 F/H not logged!
Hi William! This is not a matter of UNIX command syntax, the fact is that such string is not present in the file. Thanks and regards, Marco, PY1ZRJ Il 19/02/22 13:42, William Smith ha scritto: Try -a with grep as per https://unix.stackexchange.com/questions/335716/grep-returns-binary-file-standard-input-matches-when-trying-to-find-a-string 73, Willie N1JBJ On Feb 19, 2022, at 11:35 AM, Marco Calistri via wsjt-devel wrote: il file binario corrisponde ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] QSO 15 meters FT8 F/H not logged!
Try -a with grep as per https://unix.stackexchange.com/questions/335716/grep-returns-binary-file-standard-input-matches-when-trying-to-find-a-string 73, Willie N1JBJ > > On Feb 19, 2022, at 11:35 AM, Marco Calistri via wsjt-devel > wrote: > > il file binario corrisponde ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
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 - 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 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 ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] QSO 15 meters FT8 F/H not logged!
If you were using WSJT-x, the QSO and everything ever sent or decoded is in ALL.TXT Logged QSOs are in the .adi(f?) file. Please note that when using grep, the calls must be ALLCAPS (or use grep -i) or you will not get a result. 73, Willie N1JBJ > > On Feb 19, 2022, at 7:45 AM, 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 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 >> > > > > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] QSO 15 meters FT8 F/H not logged!
Using my default shell (/bin/bash) the suggested grep command doesn't works. In any case I had opened the ALL.TXT file yesterday using a text editor and I've not found any trace of the 3X2021 data inside. Best regards! --- *73 de Marco, PY1ZRJ (former IK5BCU)* ** Il 19/02/22 11:12, William Smith ha scritto: If you were using WSJT-x, the QSO and everything ever sent or decoded is in ALL.TXT Logged QSOs are in the .adi(f?) file. Please note that when using grep, the calls must be ALLCAPS (or use grep -i) or you will not get a result. 73, Willie N1JBJ On Feb 19, 2022, at 7:45 AM, 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 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
Re: [wsjt-devel] QSO 15 meters FT8 F/H not logged!
Hi Reino! Also you sent a very interesting response!... Sure the best way to indicate a multislot normal operation is the use of the ODD timeslot to indicate that they are NOT using FT8 DX mode. BUT, as you said, most users don’t know that feature of the FT8 DX mode and even less the Spmsg meaning. I confess that I don't know what Spmsg is and I would like to understand it. Regarding the F/H specific management of the frequencies and timing, I have a better idea how it works and I know that this process is governed internally by the WSJT-X software. Best regards, --- 73 de Marco, PY1ZRJ (former IK5BCU) Il 19/02/22 07:33, Reino Talarmo via wsjt-devel ha scritto: Hi Michael, Marco and all I know that this is not a wsjt-x development issue at all and should not be discussed on this list, but may I present my observations. I got the opportunity to work 3X2021 with my contest call ov9a. And as you can see at the picture I worked him in WSJTX Normal mode beacuse there not TX'ed any Spmsg from him at any time. And it all worked as surpposedt. The Spmsg as such may or may not affect to wsjt-x normal mode auto sequencer behavior and an operator may need manually log the QSO. By the was way the TU5PCT Dxpedition was not using WSJT-X but MSHV software in FOX Look a Like Mode and what I call a Pseudo FOX Mode. I would not call it as a “Pseudo FOX Mode” at all as there is no “Hound” related frequency jumping behavior assumed or needed. It is simply a multislot transmission. The Z22O team are also using the MSHV software. In the beginning of the DXpedition they was TX'ing ODD (15/45) with spmsg ON and that made WSJT-X going bananas because people thought it was a FOX due to the Spmsg and then put their WSJT-X in Hound Mode. But when WSJT-X is in Hound Mode it will only TX ODD (15/45). So all the WSJT-X users were TX'ing on the same timeslot as Z22O. What a mess. Lately they are only TX'ing EVEN (00/30) as a normal FOX but sometimes they don't have Spmsg ON and then it ain't a FOX or Pseudo FOX. Sure the best way to indicate a multislot normal operation is the use of the ODD timeslot to indicate that they are NOT using FT8 DX mode. BUT, as you said, most users don’t know that feature of the FT8 DX mode and even less the Spmsg meaning. I wish people would use 4-5 minuttes looking at their screen B4 hitting the TX and make a Spot on the DX-Cluster... Agreed! There could be another “protocol” for a multislot operation, where the DX station uses audio frequencies above say 2000 Hz and listens only below that. That would also minimize possible intermodulation signal above their transmission, when a TX filter is used as normally in most SSB rigs. Even the Spmsg, could be used, if normal FT8 supports it. Of course this will be a new mess before operators learn how the DX station is using split. For sure that needs clearly stated beforehand, hi! On the other hand most unintended interference will be above the DX station. Well, it may not prevent wrong spottings as spotters will report a 2k higher frequency. My 2 cents. 73, Reino OH3mA ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] QSO 15 meters FT8 F/H not logged!
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 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 ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] QSO 15 meters FT8 F/H not logged!
Il 19/02/22 01:57, Jim Shorney via wsjt-devel ha scritto: No, There is not any registry of such QSO in that file! Best regards! --- 73 de Marco, PY1ZRJ (former IK5BCU) 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 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
Re: [wsjt-devel] QSO 15 meters FT8 F/H not logged!
Hi Michael, Marco and all I know that this is not a wsjt-x development issue at all and should not be discussed on this list, but may I present my observations. I got the opportunity to work 3X2021 with my contest call ov9a. And as you can see at the picture I worked him in WSJTX Normal mode beacuse there not TX'ed any Spmsg from him at any time. And it all worked as surpposedt. The Spmsg as such may or may not affect to wsjt-x normal mode auto sequencer behavior and an operator may need manually log the QSO. By the was way the TU5PCT Dxpedition was not using WSJT-X but MSHV software in FOX Look a Like Mode and what I call a Pseudo FOX Mode. I would not call it as a “Pseudo FOX Mode” at all as there is no “Hound” related frequency jumping behavior assumed or needed. It is simply a multislot transmission. The Z22O team are also using the MSHV software. In the beginning of the DXpedition they was TX'ing ODD (15/45) with spmsg ON and that made WSJT-X going bananas because people thought it was a FOX due to the Spmsg and then put their WSJT-X in Hound Mode. But when WSJT-X is in Hound Mode it will only TX ODD (15/45). So all the WSJT-X users were TX'ing on the same timeslot as Z22O. What a mess. Lately they are only TX'ing EVEN (00/30) as a normal FOX but sometimes they don't have Spmsg ON and then it ain't a FOX or Pseudo FOX. Sure the best way to indicate a multislot normal operation is the use of the ODD timeslot to indicate that they are NOT using FT8 DX mode. BUT, as you said, most users don’t know that feature of the FT8 DX mode and even less the Spmsg meaning. I wish people would use 4-5 minuttes looking at their screen B4 hitting the TX and make a Spot on the DX-Cluster... Agreed! There could be another “protocol” for a multislot operation, where the DX station uses audio frequencies above say 2000 Hz and listens only below that. That would also minimize possible intermodulation signal above their transmission, when a TX filter is used as normally in most SSB rigs. Even the Spmsg, could be used, if normal FT8 supports it. Of course this will be a new mess before operators learn how the DX station is using split. For sure that needs clearly stated beforehand, hi! On the other hand most unintended interference will be above the DX station. Well, it may not prevent wrong spottings as spotters will report a 2k higher frequency. My 2 cents. 73, Reino OH3mA ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] QSO 15 meters FT8 F/H not logged!
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 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 -- Saku OH1KH ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] QSO 15 meters FT8 F/H not logged!
The solution would be to switch out of hound mode and send manually. Which is appropriate especially if the station was operating MSHV, but you do not need to be in Hound mode to work a Fox. I stand by what I wrote. 73 -Jim NU0C On Fri, 18 Feb 2022 20:49:53 -0700 Star Light wrote: > Hi Jim, > > Your admonition isn’t appropriate in this case. WSJT-X actually greyed out > the relevant messages so they couldn’t be selected. > > Thanks, > Russ KR6W > > > > On Feb 18, 2022, at 8:29 PM, Jim Shorney via wsjt-devel > > wrote: > > > > > > Auto sequencing is not perfect and will fail eveyone sooner or later. In > > circumstances where the auto sequencing fails it is the responsibility of > > the operator to manually select the correct message to send, and to > > manually click the Log QSO button if necessary. > > > > 73 > > > > -Jim > > NU0C > > > >> On Fri, 18 Feb 2022 22:54:04 -0300 > >> Marco Calistri via wsjt-devel wrote: > >> > >> Hello, > >> > >> Today I tried to make a QSO with the Guinea station: 3X2021 on 15 meters > >> using F/H mode. > >> > >> Despite the Fox has sent to me the RR73 message for three times, due the > >> fact I repeated my CQ attempts because I was not getting back the log > >> message, my WSJT-X has not logged the QSO! > >> > >> Despite this weird occurrence, I verified that the Fox station has logged > >> regularly our QSO on Clublog! > >> > >> For which possible reason this fact has could happen? > >> > >> --- > >> 73 de Marco, PY1ZRJ (former IK5BCU) > >> > > > > > > > > ___ > > wsjt-devel mailing list > > wsjt-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] QSO 15 meters FT8 F/H not logged!
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 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
Re: [wsjt-devel] QSO 15 meters FT8 F/H not logged!
Dears, Very interesting answers, including any eventual "admonitions" I was not aware about the fact explained by Michael, 5p1kzx regarding the pseudo Fox/Hound mode using a different FT8 application. This has been the first time in my experience with WSJT-X wherein a QSO in F/H has not been logged! In any case the observation of Russ, KR6W is exact! I tried three times in a row to double-click on the RR73 reply from the Fox station but the Tx"n" buttons on the WSJT-X were greyed-out and it just was restarting from the first Tx1 "CQ" sequence, instead to log the QSO. 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. Many thanks to all for your really appreciated answers! Best regards, --- 73 de Marco, PY1ZRJ (former IK5BCU) Il 19/02/22 00:49, Star Light via wsjt-devel ha scritto: Hi Jim, Your admonition isn’t appropriate in this case. WSJT-X actually greyed out the relevant messages so they couldn’t be selected. Thanks, Russ KR6W On Feb 18, 2022, at 8:29 PM, Jim Shorney via wsjt-devel wrote: Auto sequencing is not perfect and will fail eveyone sooner or later. In circumstances where the auto sequencing fails it is the responsibility of the operator to manually select the correct message to send, and to manually click the Log QSO button if necessary. 73 -Jim NU0C On Fri, 18 Feb 2022 22:54:04 -0300 Marco Calistri via wsjt-devel wrote: Hello, Today I tried to make a QSO with the Guinea station: 3X2021 on 15 meters using F/H mode. Despite the Fox has sent to me the RR73 message for three times, due the fact I repeated my CQ attempts because I was not getting back the log message, my WSJT-X has not logged the QSO! Despite this weird occurrence, I verified that the Fox station has logged regularly our QSO on Clublog! For which possible reason this fact has could happen? --- 73 de Marco, PY1ZRJ (former IK5BCU) ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] QSO 15 meters FT8 F/H not logged!
I had the same weirdness. So I stepped thru manually to complete QSO. Maybe he wasnt using WSJTX or really wasnt in Fox mode. I had worked him on another band when he was first on with no issues. Aug AG5AT Sent from my iPad > On Feb 18, 2022, at 9:00 PM, Ravella Russ via wsjt-devel > wrote: > > Very weird - I had exactly the same thing happen today with the same station > also on 15M ! I assumed I’d inadvertently screwed something up somewhere ! > I had to perform the log and subsequent uploads manually. > > Russ KR6W > > > >> On Feb 18, 2022, at 6:54 PM, Marco Calistri via wsjt-devel >> wrote: >> >> Hello, >> >> Today I tried to make a QSO with the Guinea station: 3X2021 on 15 meters >> using F/H mode. >> >> Despite the Fox has sent to me the RR73 message for three times, due the >> fact I repeated my CQ attempts because I was not getting back the log >> message, my WSJT-X has not logged the QSO! >> >> Despite this weird occurrence, I verified that the Fox station has logged >> regularly our QSO on Clublog! >> >> For which possible reason this fact has could happen? >> >> >> --- >> 73 de Marco, PY1ZRJ (former IK5BCU) >> >> ___ >> wsjt-devel mailing list >> wsjt-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] QSO 15 meters FT8 F/H not logged!
Hi Jim, Your admonition isn’t appropriate in this case. WSJT-X actually greyed out the relevant messages so they couldn’t be selected. Thanks, Russ KR6W > On Feb 18, 2022, at 8:29 PM, Jim Shorney via wsjt-devel > wrote: > > > Auto sequencing is not perfect and will fail eveyone sooner or later. In > circumstances where the auto sequencing fails it is the responsibility of the > operator to manually select the correct message to send, and to manually > click the Log QSO button if necessary. > > 73 > > -Jim > NU0C > >> On Fri, 18 Feb 2022 22:54:04 -0300 >> Marco Calistri via wsjt-devel wrote: >> >> Hello, >> >> Today I tried to make a QSO with the Guinea station: 3X2021 on 15 meters >> using F/H mode. >> >> Despite the Fox has sent to me the RR73 message for three times, due the >> fact I repeated my CQ attempts because I was not getting back the log >> message, my WSJT-X has not logged the QSO! >> >> Despite this weird occurrence, I verified that the Fox station has logged >> regularly our QSO on Clublog! >> >> For which possible reason this fact has could happen? >> >> --- >> 73 de Marco, PY1ZRJ (former IK5BCU) >> > > > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] QSO 15 meters FT8 F/H not logged!
Auto sequencing is not perfect and will fail eveyone sooner or later. In circumstances where the auto sequencing fails it is the responsibility of the operator to manually select the correct message to send, and to manually click the Log QSO button if necessary. 73 -Jim NU0C On Fri, 18 Feb 2022 22:54:04 -0300 Marco Calistri via wsjt-devel wrote: > Hello, > > Today I tried to make a QSO with the Guinea station: 3X2021 on 15 meters > using F/H mode. > > Despite the Fox has sent to me the RR73 message for three times, due the fact > I repeated my CQ attempts because I was not getting back the log message, my > WSJT-X has not logged the QSO! > > Despite this weird occurrence, I verified that the Fox station has logged > regularly our QSO on Clublog! > > For which possible reason this fact has could happen? > > --- > 73 de Marco, PY1ZRJ (former IK5BCU) > ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
Re: [wsjt-devel] QSO 15 meters FT8 F/H not logged!
Very weird - I had exactly the same thing happen today with the same station also on 15M ! I assumed I’d inadvertently screwed something up somewhere ! I had to perform the log and subsequent uploads manually. Russ KR6W > On Feb 18, 2022, at 6:54 PM, Marco Calistri via wsjt-devel > wrote: > > Hello, > > Today I tried to make a QSO with the Guinea station: 3X2021 on 15 meters > using F/H mode. > > Despite the Fox has sent to me the RR73 message for three times, due the fact > I repeated my CQ attempts because I was not getting back the log message, my > WSJT-X has not logged the QSO! > > Despite this weird occurrence, I verified that the Fox station has logged > regularly our QSO on Clublog! > > For which possible reason this fact has could happen? > > > --- > 73 de Marco, PY1ZRJ (former IK5BCU) > > ___ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
