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

Re: [wsjt-devel] WSJT-X 2.5.4 Dependency Issue Raspberry Pi 4 Bullseye

> > If the binary package is not compatible with your Linux distribution or > version, you must build the application from sources. To resolve the dependencies, download the latest version of the wsjtx sources from SourceForge and

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

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

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

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

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

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

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 –

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

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

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

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

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

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

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

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

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

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,

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

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

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: