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.
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
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
> 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
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
> 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
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
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,
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
@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
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
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
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
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
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
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
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
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
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
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,
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
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
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:
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
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
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
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
>
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
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
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
>
30 matches
Mail list logo
