The second one is better!
Keijo EA5/OG55W
From: DG2YCB, Uwe
Sent: Thursday, January 24, 2019 7:43 AM
To: wsjt-devel@lists.sourceforge.net
Subject: [wsjt-devel] Layout different when "Menus" enabled/disabled
Hi,
One minor issue: The layout for the various fields in WSJT-X v2.0.0 is somewhat
d
Hi,
One minor issue: The layout for the various fields in WSJT-X v2.0.0 is
somewhat different when "Menus" is enabled or disabled. (My preferred layout
is that when menus are enabled, but usually I like the menus disabled.). Not
a big deal, but maybe it can be corrected for the next release.
L
Hi, I got this address from the WSJT website. I am new to this group
and not sure of the protocols. I tried emailing yesterday but am unsure if this
was received.
I am operating as VK2/G3NJV. After upgrading to v2.0.0 I found reports of my
transmissions almost disappeared from PSK Repo
I just worked then with one call -- they have multiple signals a bit apart
from each other, but working them is not difficult. Just use normal FT8
protocols.
73 -- Larry -- W1DYJ
[in Maine]
-Original Message-
From: Gary McDuffie
Sent: Wednesday, January 23, 2019 18:25
To: WSJT soft
Hi John,
I hope I’m not over-simplifying your question, but I worked them on 15M this
morning in normal FT8 mode. As I recall, I was about 500 Hz above them.
Good luck!
Joe/WB0CDY
From: John Zantek
Reply-To: WSJT software development
Date: Wednesday, January 23, 2019 at 2:57 PM
To: 'WSJT sof
Once I saw what they were doing, I ignored them 100%. But so many don't
realize they are defeating the purpose of FT8 and an unwritten "Code of
Conduct" like a certain Belize station does all the time.
George - WB5JJJ
On Wed, Jan 23, 2019 at 5:29 PM Gary McDuffie wrote:
>
>
> > On Jan 23, 2019
> On Jan 23, 2019, at 13:34, John Zantek wrote:
>
> Has anyone observed the FT8 operation of the PJ4P expedition team? Maybe I’m
> missing something obvious, but….
>
> It LOOKS they’re operating as a Fox, but on the conventional FT8 frequencies.
Saw the same thing this afternoon. I think i
I see them on 20M this afternoon, strange they are transmitting on
1100-1200 & up every 60 Hz.
Thought FOX was transmitting below 1K??
Special version of the software?
73;
Bill W2PKY
On Wed, Jan 23, 2019 at 5:36 PM Fred Price wrote:
>
>
> On Jan 23, 2019 3:34 PM, John Zantek wrote:
>
> Has any
Hi John,
Quick followup…I just worked them on 20M using standard FT8 again. Their reply
looks like F/H, or as Fred mentioned, “multi thread”, as their final Tx was
“WB0CDY RR73; ON5CD -08”.
Best regards,
Joe/WB0CDY
From: John Zantek
Reply-To: WSJT software development
Date: Wednesday, Janu
On Jan 23, 2019 3:34 PM, John Zantek wrote:
Has anyone observed the FT8 operation of the PJ4P expedition team? Maybe I’m
missing something obvious, but….
It LOOKS they’re operating as a Fox, but on the conventional FT8 frequencies.
They’re transmitting on ODD, not EVEN, so I can’t engag
Hi Mike
Thanks again for your rapid reply, and for the information ..I suspected this
would be corrected in the next release.
Take care
Lorin
> On Jan 23, 2019, at 12:11 PM, Black Michael via wsjt-devel
> wrote:
>
> It's a bug in the 2.0.0 version where the "Retain" checkbox is not being
They are on 20M FT8 now73 wa4mit Morris
On Wednesday, January 23, 2019, 4:15:42 PM CST, Hasan al-Basri
wrote:
I worked them in the normal mode calling them about 100 Hz above where they
were tx'ing.73, N0ANHasan
On Wed, Jan 23, 2019 at 4:00 PM John Zantek wrote:
Has anyone observe
I worked them in the normal mode calling them about 100 Hz above where they
were tx'ing.
73, N0AN
Hasan
On Wed, Jan 23, 2019 at 4:00 PM John Zantek wrote:
> Has anyone observed the FT8 operation of the PJ4P expedition team? Maybe
> I’m missing something obvious, but….
>
>
>
> It LOOKS they’re
Has anyone observed the FT8 operation of the PJ4P expedition team? Maybe
I'm missing something obvious, but..
It LOOKS they're operating as a Fox, but on the conventional FT8
frequencies.
They're transmitting on ODD, not EVEN, so I can't engage them as a Hound
with WSJT-X 2.0.
Their tr
It's a bug in the 2.0.0 version where the "Retain" checkbox is not being
honored.
It's been fixed for the next version.
de Mike W9MDB
On Wednesday, January 23, 2019, 2:07:38 PM CST, Lorin Hollander
wrote:
Hi Bill, Mike and the others who kindly answered my question and addressed
t
On 23/01/2019 20:02, Lorin Hollander wrote:
Please, can you help me address the other issue? It is about the
empty Comment and Power fields in the "Log QSO” pop-up window,
Although the windows is now configured differently in vs/ 2.0., is
thee a way to autofill these two fields, fields that
Hi Bill, Mike and the others who kindly answered my question and addressed
this issues so well. Thank you all for your time and care, it means a lot.
I have returned to the practice of sending CQ DX WA1PGB CM88, and that is
working fine. Thank you again.
Please, can you help me address th
On 23/01/2019 16:24, Lorin Hollander wrote:
When sending a CQ DX from the drop down entry box No 5 where I have
previously entered my call in F2 “Settings “, as the compound WA1PGB/6
Hi Lorin, sorry clicked "Send" prematurely. Let's try again:
the way non-standard callsigns are handled in WSJ
On 23/01/2019 16:24, Lorin Hollander wrote:
When sending a CQ DX from the drop down entry box No 5 where I have
previously entered my call in F2 “Settings “, as the compound WA1PGB/6
Hi Lorin,
the way non-standard callsigns are handled in WSJT-X for the new 77-bit
FT8 and MSK144 modes has co
On 1/21/19 5:51 PM, Andreas Gille wrote:
Hi Andy & all,
We could send you a log excerpt (not the entire 4000 QSOs) or a more
precise description of the discrepancies.
I would be happy to see a little extract of the FoxLog and ADIF files,
showing the occurring problem. You can post such littl
On 1/23/19 5:46 PM, Roy Gould wrote:
Hi Roy & all,
This happens to me once in a while. I don't know what call sign was
supposed to be there so I delete the whole record and save the file and
then everything seems to be OK.
When you reread an ADIF file, it should not contain obvious errors, o
I can confirm "CQ DX WA1PGB/6" works in 1.9.1 but not 2.0.0...you're solution
right now is to drop the "DX" and the grid. The grid doesn't work either and
drops the suffix. In 1.9.1 it dropped the grid and kept the suffix.
C:\WSJT\wsjtx\bin>ft8code.exe "CQ WA1PGB/6 EM49" Message
This happens to me once in a while. I don't know what call sign was
supposed to be there so I delete the whole record and save the file and
then everything seems to be OK.
On Wed, Jan 23, 2019 at 9:40 AM Black Michael via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
> It appears that was
It appears that was just one record where you didn't have the callsign in the
"DX Call" box in WSJT-X.
That first field is your QSO partner's callsign.
Mike
On Wednesday, January 23, 2019, 10:31:26 AM CST, Lorin Hollander
wrote:
Many thanks Mike for this information and advice.
And a
Many thanks Mike for this information and advice.
And as to where I should enter station snd personal information so that this
will be included as autofill in the Log Window fields? Where do I enter that
data?
Thanks again
Lorin
Sent from my iPhone
> On Jan 23, 2019, at 7:45 AM, Black Mic
Hello,
I have been successfully using FT-8 in vs 1.9 for several months with no
problems or issues. I have now been using vs. 2.0 in the latest iteration, I
believe, and have run into what seems like a bug, although I cannot be sure.
I am running WSJT-X 2.0 on a MacBook Pro with OS X High Si
The error tells you -- that record has no call sign. Edit the log file and
remove the record.
The ADIF parsing has been relaxed for the next version but not sure what it
will do a record like this.
Perhaps Bill knows.
de Mike W9MDB
On Wednesday, January 23, 2019, 9:40:35 AM CST, Lorin Ho
Hello,
I am a new member of this group.
I receive the following error (see screenshot below) when starting WSJT-X FT8
vs 2.0 in Windows 10.What is the process to correct this. Also, the
previous versions always autofilled most of the fields in the Log Contact
window (Power - etc.) and no
28 matches
Mail list logo
