Re: [wsjt-devel] WSJT-X: Summary of issues with v2.0.0 RC5 in RTTY Roundup mode

[Saku]

Hi!

Please consider UDP messages that follow ADIF 3.0.4 tag specification:

RST_RCVD
RST_SENT
These are ok now, just the rst either dB or 5xx format as leagacy rst 
UDP string


GridSquare
This is also ok now. If contest message includes locator it should be 
sent to companion program using leagacy locator UDP message


SRX
STX
Contest qso number sent and received , *NO other* message data, as new 
UDP string


SRX_STRING
STX_STRING
Contest message information sent and received , *NOT including* serial 
number or locator, as new UDP string



That way companion program can easily construct it's own database in way 
what it wants.


--
Saku
OH1KH



Bill Somerville kirjoitti 3.12.2018 klo 1.37:

On 02/12/2018 21:19, Laurie, VK3AMA wrote:

On 3/12/2018 12:05 am, Bill Somerville wrote:


The WSJT-X UDP protocol logging message will have the contest 
exchange fields added for the next release of WSJT-X and cooperating 
applications will be able to extract the required information.



Bill,

Good to hear.

Please give some serious consideration to adding additional UDP 
status data. Currently, there is no way to know what operating mode 
(not TX mode) WSJT-X is currently using, Fox, Hound or which Contest 
enabled. It would be very helpful if the UDP protocol provided a 
field within the Status packet for these modes of operation.


de Laurie VK3AMA


Hi Laurie,

I am not really certain that knowing which mode WSJT-X is in will 
necessarily help a great deal. Part of the point of the new FT8 77-bit 
messages is that WSJT-X does not need to know which type it is set to 
to decode any message. the messages contain all the information with 
exception of the ones with a hash code where some information is 
recalled from prior decodes. OTOH it is likely that each mode of 
operation will be separated by time or frequency or both so I suppose 
there is some value but there is no guarantee that when in one of the 
contest modes it will only decode messages deigned for that contest mode.


Anyway, I have made the changes. Here is the diff of the 
NetworkMessage.hpp file:


$ git diff wsjtx-2.0.0-rc5 -- NetworkMessage.hpp
diff --git a/NetworkMessage.hpp b/NetworkMessage.hpp
index ffd0ff288..a4d9ba0d5 100644
--- a/NetworkMessage.hpp
+++ b/NetworkMessage.hpp
@@ -124,6 +124,7 @@
  * Tx Watchdog    bool
  * Sub-mode   utf8
  * Fast mode  bool
+ * Special operation mode quint8
  *
  *    WSJT-X  sends this  status message  when various internal state
  *    changes to allow the server to  track the relevant state of each
@@ -142,10 +143,22 @@
  *  At the start and end of decoding,
  *  When the Rx DF changes,
  *  When the Tx DF changes,
- *  When the DE call or grid changes (currently when settings are 
exited),

+ *  When settings are exited,
  *  When the DX call or grid changes,
  *  When the Tx watchdog is set or reset.
  *
+ *    The Special operation mode is  an enumeration that indicates the
+ *    setting  selected  in  the  WSJT-X "Settings->Advanced->Special
+ *    operating activity" panel. The values are as follows:
+ *
+ *   0 -> NONE
+ *   1 -> NA VHF
+ *   2 -> EU VHF
+ *   3 -> FIELD DAY
+ *   4 -> RTTY RU
+ *   5 -> FOX
+ *   6 -> HOUND
+ *
  *
  * Decode    Out   2  quint32
  * Id (unique key)    utf8
@@ -240,6 +253,8 @@
  * Operator call  utf8
  * My call    utf8
  * My grid    utf8
+ * Exchange sent  utf8
+ * Exchange received  utf8
  *
  *  The  QSO logged  message is  sent  to the  server(s) when  the
  *  WSJT-X user accepts the "Log  QSO" dialog by clicking the "OK"

I will send you a preview Windows installer direct.

73
Bill
G4WJS.



___
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] FW: [rttydigital] FT8 Roundup Logs Received Page

[Tom Ramberg via wsjt-devel]

 Our log from OH2K was saved as a .cbr file, not a.LOG file. So not sure what 
to do about it. I'm going to send both, and hope that the log will be accepted 
one way or the other.
73 de Tom OH6VDA

On Monday, December 3, 2018, 6:47:57 AM GMT+2, Ed Muns  
wrote:  
 
 FYI ...

-Original Message-
From: rttydigi...@groups.io [mailto:rttydigi...@groups.io] On Behalf Of Don
Hill AA5AU
Sent: 02 December, 2018 19:57
To: rttydigi...@groups.io
Subject: [rttydigital] FT8 Roundup Logs Received Page

Here...

https://www.rttycontesting.com/ft8-roundup/2018-results/logs-received/

73, Don AA5AU


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.

View/Reply Online (#151): https://groups.io/g/rttydigital/message/151
Mute This Topic: https://groups.io/mt/28568285/757327
Group Owner: rttydigital+ow...@groups.io
Unsubscribe: https://groups.io/g/rttydigital/leave/3491911/856418499/xyzzy
[e...@w0yk.com]
-=-=-=-=-=-=-=-=-=-=-=-



___
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] RU and callers outside the contest

[Tom Ramberg via wsjt-devel]

Great experience last night. Only thing that got me off the track for a second 
was when a station called us outside the contest and the programme refused to 
log. I realised that he'd given us a standard dB report and no serial number. I 
took a quick and dirty solution and logged my received report as 549 0001, but 
will make a remark of that when uploading the log. But shouldn't the other 
operator see a warning at least when he receives non standard report like 549 
0026 instead of a dB report?

73 the Tom OH6VDA



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

Re: [wsjt-devel] AK & HI accepted in Exch: box when it shouldn't be

[Don Hill AA5AU]

I missed HI... HI

Stations will not be penalized for either sending or accepting HI or AK
reports in the FT8 Roundup.

Don AA5AU

-Original Message-
From: Jim Jennings [mailto:w...@comcast.net] 
Sent: Sunday, December 2, 2018 11:00 PM
To: WSJT software development
Subject: Re: [wsjt-devel] AK & HI accepted in Exch: box when it shouldn't be

Wondered about that, Don.  Worked one AH6 in the Roundup and received HI in 
the exchange.  73,

Jim, W7XZ

-Original Message- 
From: Don Hill AA5AU
Sent: Sunday, December 02, 2018 18:33
To: 'WSJT software development'
Subject: Re: [wsjt-devel] AK & HI accepted in Exch: box when it shouldn't be

I am hearing now that perhaps this is not correct. Please QRX or someone who
really knows please clarify.

Don AA5AU

-Original Message-
From: Don Hill AA5AU [mailto:aa...@bellsouth.net]
Sent: Sunday, December 2, 2018 8:06 PM
To: 'WSJT software development'
Subject: [wsjt-devel] AK & HI accepted in Exch: box when it shouldn't be

It's been brought to my attention, that if you enter either AK or HI into
the Exch: box under the "Special operating activity" section of the Advanced
tab screen in Settings, it is accepted. It shouldn't be. Alaska and Hawaii
are considered DX in both the FT8 Roundup and ARRL RTTY Roundup.

I just tested it and you can input either AK and HI and it's accepted. AK
and HI stations should enter DX here.

Don AA5AU



___
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] AK & HI accepted in Exch: box when it shouldn't be

[Don Hill AA5AU]

After looking at past years of ARRL RTTY Roundup logs, I have concluded that
my original post is correct. Stations in Alaska and Hawaii should enter DX
in the "Exch:" box on the Advanced Page and . AK and HI should not be legal
input into that box. Furthermore, they have to send serial numbers since
they are DX.

73, Don AA5AU

-Original Message-
From: Thomas Webb [mailto:tmw...@cox.net] 
Sent: Sunday, December 2, 2018 8:42 PM
To: 'WSJT software development'
Subject: Re: [wsjt-devel] AK & HI accepted in Exch: box when it shouldn't be

Don,
 Here is the last sentence in the 'Multipliers' paragraph from the 2018
RU rules "KH6 and
KL7 count only as separate DXCC entities."

Thomas Webb
WA9AFM/5
ASM
Oklahoma Section

-Original Message-
From: Don Hill AA5AU [mailto:aa...@bellsouth.net] 
Sent: Sunday, December 02, 2018 8:34 PM
To: 'WSJT software development'
Subject: Re: [wsjt-devel] AK & HI accepted in Exch: box when it shouldn't be

I am hearing now that perhaps this is not correct. Please QRX or someone who
really knows please
clarify.

Don AA5AU

-Original Message-
From: Don Hill AA5AU [mailto:aa...@bellsouth.net]
Sent: Sunday, December 2, 2018 8:06 PM
To: 'WSJT software development'
Subject: [wsjt-devel] AK & HI accepted in Exch: box when it shouldn't be

It's been brought to my attention, that if you enter either AK or HI into
the Exch: box under the
"Special operating activity" section of the Advanced tab screen in Settings,
it is accepted. It
shouldn't be. Alaska and Hawaii are considered DX in both the FT8 Roundup
and ARRL RTTY Roundup.

I just tested it and you can input either AK and HI and it's accepted. AK
and HI stations should
enter DX here.

Don AA5AU



___
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] AK & HI accepted in Exch: box when it shouldn't be

[Jim Jennings]

Wondered about that, Don.  Worked one AH6 in the Roundup and received HI in 
the exchange.  73,


Jim, W7XZ

-Original Message- 
From: Don Hill AA5AU

Sent: Sunday, December 02, 2018 18:33
To: 'WSJT software development'
Subject: Re: [wsjt-devel] AK & HI accepted in Exch: box when it shouldn't be

I am hearing now that perhaps this is not correct. Please QRX or someone who
really knows please clarify.

Don AA5AU

-Original Message-
From: Don Hill AA5AU [mailto:aa...@bellsouth.net]
Sent: Sunday, December 2, 2018 8:06 PM
To: 'WSJT software development'
Subject: [wsjt-devel] AK & HI accepted in Exch: box when it shouldn't be

It's been brought to my attention, that if you enter either AK or HI into
the Exch: box under the "Special operating activity" section of the Advanced
tab screen in Settings, it is accepted. It shouldn't be. Alaska and Hawaii
are considered DX in both the FT8 Roundup and ARRL RTTY Roundup.

I just tested it and you can input either AK and HI and it's accepted. AK
and HI stations should enter DX here.

Don AA5AU



___
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] Feedback: Contest Log and Colors

[Greg Beam]

Hello All,

 

First, well done to Joe and all the WSJT-X developers!! I've not made any
QSO's for several months (summer 2018) and was able to get up and running in
no time (v2 RC5 Win32) by reading the docs. Made some rookie mistakes with
QSO's, but, was able to make a few Q's to test things out. Overall, I had
very little trouble getting things working properly once I made a couple
Q's.

 

Couple Suggestions / Comments:


These may be covered elsewhere, but, I've not had a chance to review the
archive. As for my setup, I was only using WSJT-X an JT-Alerts. I've no Idea
if / how N1MM ties into things, if at all.

 

-Contest Log Order: Currently, the log is sorted by first in and the user
must use the scroll bar to get to the bottom of the log to see (last-in). I
was wondering if we could get a sorting option that would allow First-In /
Last-In for the log. It's not critical, but for me, I prefer to see the last
Q logged at the top. 

 

-Use Contest Log for WSJT-X/JT-Alerts: I noticed, during the contest, both
WSJT-X and JT-Alerts were using their normal log objects. In the case of
JT-Alerts it was my DXLab DB, and WSJT-X was using its local default log. In
contest mode, I'm not really concerned about contacts I've made, or not, in
my main logging application(s), rather, only what multipliers that I need
for the given contest. It seems to me that all the alerts, colors, and
highlighting should be the result of what is in the Contest Log, not my
normal logging applications. In JT Alerts I had/saw manty B4 calls appearing
even though I had not worked them in the contest. I updated to the latest
JT-Alerts today before running a few Q's; there may be options I'm not up to
speed on at this point.

 

-Colors During Contests: I'm sure colors has been beaten seven ways to
Sunday, however, during a contest I am only concerned with Q's during the
contest; is the station(s) a new band / multi or not? A CQ-ing station in
Green is a distraction if I've already worked them for a given band/mode
combination. It would be helpful, at least for me, if we could have the
color scheme's (in the Band Activity / Rx Frequency Windows) match that of
contest loggers (N1MM, WriteLog, etc). Maybe this is already possible, and I
am behind the 8-ball here, but, it's certainly helpful in the wee-hours of
the morning when the ops are not always in top-mental condition.

 

-Contest/Non-Contest QSO's: I had a few callers using the standard FT8
exchange(s). I need to read the Docs a bit more, but, is there a way to
quickly switch the from contest:   R 599 MT to normal 
 RST just for that one exchange?

 

Anyway, it was good fun for the time I was able to put in. I look forward to
seeing how things progress with the contest modes.

 

73's

Greg, KI7MT

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

[wsjt-devel] FW: [rttydigital] FT8 Roundup Logs Received Page

[Ed Muns]

FYI ...

-Original Message-
From: rttydigi...@groups.io [mailto:rttydigi...@groups.io] On Behalf Of Don
Hill AA5AU
Sent: 02 December, 2018 19:57
To: rttydigi...@groups.io
Subject: [rttydigital] FT8 Roundup Logs Received Page

Here...

https://www.rttycontesting.com/ft8-roundup/2018-results/logs-received/

73, Don AA5AU


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.

View/Reply Online (#151): https://groups.io/g/rttydigital/message/151
Mute This Topic: https://groups.io/mt/28568285/757327
Group Owner: rttydigital+ow...@groups.io
Unsubscribe: https://groups.io/g/rttydigital/leave/3491911/856418499/xyzzy
[e...@w0yk.com]
-=-=-=-=-=-=-=-=-=-=-=-



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

Re: [wsjt-devel] FT8 Roundup Log Submittal

[Ed Muns]

Either one will work, but we recommend *.log.

 

Ed W0YK

 

  _  

From: Carey Fisher [mailto:careyfis...@gmail.com] 
Sent: 02 December, 2018 19:49
To: e...@w0yk.com; WSJT software development
Cc: rttydigi...@groups.io
Subject: Re: [wsjt-devel] FT8 Roundup Log Submittal

 

The SAVE Cabrillo log function saves the log as a whateveryoutype.cbr. But
your instructions say it saves it as callsign.log. Which is correct? I sent
my log with both filename extensions but neither shows up in the list of
received logs.

Carey WB4HXE

 

On Sun, Dec 2, 2018 at 10:36 PM Ed Muns  wrote:

The log submittal robot failed to send confirmation emails to the early log
submittals.  That has been fixed, but if you didn't receive the normal
confirmation email, please check the Logs Received web page on the FT8
Roundup website.  We have your log if your call is listed there.

 

Over 400 logs have already been received.  Deadline is next Sunday, but the
sooner the better.  We expect to publish results a week or two after that.

 

Ed W0YK

Don AA5AU

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




 

-- 

Carey Fisher

careyfis...@gmail.com

 

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

[wsjt-devel] Contest log clock, overall RU impressions

[mail]

Hi all!My contest log showed the times as 12 hour AM/PM based on UTC time, so it neither matched the clock on my PC or WSJT-X. I had read the reports and realized that the actual log would be correct UTC times, so I ignored the contest log times.Overall it was a great RU contest, lots of new stations to work, much better than struggling to find decodes during rc4 testing.I had not used tab 2 in so long that I had to open WSJT-X after reading the reports just to see what they were talking about, I had forgotten it was there, haven't used it since auto seq became standard.Many thanks to the whole WSJT-X team who made it possible for a ham with a vertical antenna on a small city lot to work serious DX with low power! This is great fun!73 de kv4zy

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

[wsjt-devel] UTC time in contest log page

[Rich Zwirko - K1HTV]

I noticed during the FT8 RU that the log page, although in UTC, is not in
the 24 hour format but uses the 12 hour plus AM or PM. Who uses UTC in 12
AM/PM format? Almost all Ham logs are in 24 hour format, right?

73,
Rich - K1HTV
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FT8 Roundup Log Submittal

[Don Hill AA5AU]

It should be .log as in WB4HXE.LOG.

 

Don AA5AU

 

From: Carey Fisher [mailto:careyfis...@gmail.com] 
Sent: Sunday, December 2, 2018 9:49 PM
To: e...@w0yk.com; WSJT software development
Cc: rttydigi...@groups.io
Subject: Re: [wsjt-devel] FT8 Roundup Log Submittal

 

The SAVE Cabrillo log function saves the log as a whateveryoutype.cbr. But your 
instructions say it saves it as callsign.log. Which is correct? I sent my log 
with both filename extensions but neither shows up in the list of received logs.

Carey WB4HXE

 

On Sun, Dec 2, 2018 at 10:36 PM Ed Muns mailto:e...@w0yk.com> > 
wrote:

The log submittal robot failed to send confirmation emails to the early log 
submittals.  That has been fixed, but if you didn’t receive the normal 
confirmation email, please check the Logs Received web page on the FT8 Roundup 
website.  We have your log if your call is listed there.

 

Over 400 logs have already been received.  Deadline is next Sunday, but the 
sooner the better.  We expect to publish results a week or two after that.

 

Ed W0YK

Don AA5AU

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




 

-- 

Carey Fisher

careyfis...@gmail.com

 

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

[wsjt-devel] Contest Log Window - snaps to 256

[Drew White]

First, let me say that WSJT-X RC5 worked extraordinarily well for me 
this weekend!  I was simply amazed to see how well RC5 was able to 
recover stations transmitting in the same time slot with reported 
separations of only a few Hz.  I have nothing but respect and admiration 
for the skill and talent of K1JT, K9AN and the entire FT8 development 
team.  Thank you!


I experienced one minor issue with the contest log window.  In addition 
to the contest log window not displaying the last QSO as others have 
reported, I discovered that the log window always ends with entry #256 
when the QSO total exceeds 256.  You can manually scroll the log down to 
see entries beyond #256, but when a new contact is logged, the bottom of 
the log window always returns to #256.


Drew K9CW

On 12/2/2018 11:25 AM, Steven Franke via wsjt-devel wrote:
Try expanding the log window, vertically, so that it takes up at least 
2/3 of your screen. If I do that, I can always see the last line.

Steve k9an

On Dec 2, 2018, at 11:07 AM, Bill Pence > wrote:


Same here. Last qso is just off the bottom on the contest log window. 
A new Q scolls to see the previous last, but then the newest is still 
out of view unless I scroll manually...






--
**
* K9CW   DXCC: 363/340  CW: 351/339 (need P5!)
*

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

Re: [wsjt-devel] FT8 Roundup Log Submittal

[Carey Fisher]

The SAVE Cabrillo log function saves the log as a whateveryoutype.cbr. But
your instructions say it saves it as callsign.log. Which is correct? I sent
my log with both filename extensions but neither shows up in the list of
received logs.
Carey WB4HXE

On Sun, Dec 2, 2018 at 10:36 PM Ed Muns  wrote:

> The log submittal robot failed to send confirmation emails to the early
> log submittals.  That has been fixed, but if you didn’t receive the normal
> confirmation email, please check the Logs Received web page on the FT8
> Roundup website.  We have your log if your call is listed there.
>
>
>
> Over 400 logs have already been received.  Deadline is next Sunday, but
> the sooner the better.  We expect to publish results a week or two after
> that.
>
>
>
> Ed W0YK
>
> Don AA5AU
> ___
> wsjt-devel mailing list
> wsjt-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>


-- 
Carey Fisher
careyfis...@gmail.com
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] 100% success for me

[WB5JJJ]

Joe and list:

I was only able to devote a hour or so here and there on Saturday, and on
Sunday I was out of town all day.  I was able to log 63 stations, many of
which were 1st timers for me, so v2 and the contest brought lots of new
calls to the air, at least for the contest.  So many signals in the WF that
it looked like normal 20m, except they were all running v2 RC5 this time.

I had absolutely no problems with WSJTX RC5, JTAlert and HRD LB.  The
Contest Log was a perfect performer.  Times were in UTC and correct in all
respects.  All exchanges were handed off from WSJTX to HRD Logbook without
error.  HRD LB of course did a QRZ lookup and found all personal data and
the listed Grid Square.  And, of course, I was using TAB 1 which give the
most detail of system operations.

Looking forward to v2 GA and increased users.

-- 
George Cotton, WB5JJJ
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] TX not moving on double-clcik

[Paul Kube]

Me three :).

Well described by Charlie and Jim.

73, Paul K6PO

On Sun, Dec 2, 2018 at 4:48 PM Jim Shorney  wrote:

>
> Thanks Charlie! Nice to know it isn't just me...  :)
>
> 73
>
> -Jim
> NU0C
>
>
> On Sun, 2 Dec 2018 21:20:39 -
> char...@sucklingfamily.free-online.co.uk wrote:
>
> > Hi Jim
> >
> > Yes, we experienced the same behaviour where clicking an earlier message
> > when bailing on a QSO ended up splitting the TX and RX frequencies.
> >
> > We also found it labour intensive to have to select TX4 and enable TX
> > manually when the calling station sent R report again, clearly not having
> > received our initial RR73 message.  On some occasions we needed to do
> this
> > several times during more difficult QSOs.
> >
> > 73
> >
> > Charlie G3WDG
> > >
> > > I have noticed a specific scenario that has happened several times
> during
> > > the contest. This happens when I have called a CQing station two or
> three
> > > times with no reply and I bail and go call another. Then I see the
> first
> > > station replying to me with TX3 while I am calling the new one. So I
> bail
> > > on that call and try to go back to work the first station with a
> > > double-click on the message. This moves the RX back to the first
> station's
> > > frequency, but not the TX. It is acting like Hold TX is on, but it is
> not.
> > > I tried toggling Hold TX. and shift-doubleclick, but the TX refuses to
> > > move until I use one those "confusing" arrows. (j/k, I'm not confused
> -
> > > much).
> > >
> > > Maybe I'm just a bad op. I know we are supposed to offset our signals
> and
> > > call split, but that doesn't seem to be happening. At any rate, it
> seems
> > > like the TX should move in this scenario, otherwise I end up QRMing the
> > > second op until I remember where I am.
> > >
> > > While I am at it, it would be nice if, when calling running station,
> Tx4
> > > could me made sticky until the final 73 is received. Leave TX disable
> > > alone, just let Tx4 stay selected in case it needs to be re-sent. One
> less
> > > thing to have to scramble for when things don't go as planned.
> > >
> > > Anyway, 70 contacts so far before I needed to take a break.
> > >
> > > 73
> > >
> > > -Jim
> > > NU0C
> > >
> > >
> > > --
> > > The universe we're in will reach absolute zero in three hours. Safe is
> > > relative. - Idris, "The Doctor's Wife"
>
>
> ___
> 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] AK & HI accepted in Exch: box when it shouldn't be

[Thomas Webb]

Don,
 Here is the last sentence in the 'Multipliers' paragraph from the 2018 RU 
rules "KH6 and
KL7 count only as separate DXCC entities."

Thomas Webb
WA9AFM/5
ASM
Oklahoma Section

-Original Message-
From: Don Hill AA5AU [mailto:aa...@bellsouth.net] 
Sent: Sunday, December 02, 2018 8:34 PM
To: 'WSJT software development'
Subject: Re: [wsjt-devel] AK & HI accepted in Exch: box when it shouldn't be

I am hearing now that perhaps this is not correct. Please QRX or someone who 
really knows please
clarify.

Don AA5AU

-Original Message-
From: Don Hill AA5AU [mailto:aa...@bellsouth.net]
Sent: Sunday, December 2, 2018 8:06 PM
To: 'WSJT software development'
Subject: [wsjt-devel] AK & HI accepted in Exch: box when it shouldn't be

It's been brought to my attention, that if you enter either AK or HI into the 
Exch: box under the
"Special operating activity" section of the Advanced tab screen in Settings, it 
is accepted. It
shouldn't be. Alaska and Hawaii are considered DX in both the FT8 Roundup and 
ARRL RTTY Roundup.

I just tested it and you can input either AK and HI and it's accepted. AK and 
HI stations should
enter DX here.

Don AA5AU



___
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] AK & HI accepted in Exch: box when it shouldn't be

[Don Hill AA5AU]

I am hearing now that perhaps this is not correct. Please QRX or someone who
really knows please clarify.

Don AA5AU

-Original Message-
From: Don Hill AA5AU [mailto:aa...@bellsouth.net] 
Sent: Sunday, December 2, 2018 8:06 PM
To: 'WSJT software development'
Subject: [wsjt-devel] AK & HI accepted in Exch: box when it shouldn't be

It's been brought to my attention, that if you enter either AK or HI into
the Exch: box under the "Special operating activity" section of the Advanced
tab screen in Settings, it is accepted. It shouldn't be. Alaska and Hawaii
are considered DX in both the FT8 Roundup and ARRL RTTY Roundup.

I just tested it and you can input either AK and HI and it's accepted. AK
and HI stations should enter DX here.

Don AA5AU



___
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] AK & HI accepted in Exch: box when it shouldn't be

[Don Hill AA5AU]

It's been brought to my attention, that if you enter either AK or HI into
the Exch: box under the "Special operating activity" section of the Advanced
tab screen in Settings, it is accepted. It shouldn't be. Alaska and Hawaii
are considered DX in both the FT8 Roundup and ARRL RTTY Roundup.

I just tested it and you can input either AK and HI and it's accepted. AK
and HI stations should enter DX here.

Don AA5AU



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

Re: [wsjt-devel] Frequency Management in Contest Mode.

[Grant Willis]

Ill do some more checking and try to reproduce. I didn’t have enough time this 
morning to explore further.

Regards,
Grant Willis

> On 3 Dec 2018, at 8:19 am, Bill Somerville  wrote:
> 
>> On 02/12/2018 21:22, Grant VK5GR wrote:
>> I double clicked on his call in the Band Activity window and then wondered 
>> why he disappeared. After about 90 seconds I glanced over at my SDR and 
>> realised my signal was in the lower cluster of signals – looked at the rig 
>> and realised it had jumped back to 7074.
> 
> Hi Grant,
> 
> that's not supposed to happen. Was it the double-clicking of a call that 
> caused it to skip to a preset frequency or something else? Is it reproducible?
> 
> 73
> Bill
> G4WJS.
> 
> 
> 
> ___
> 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] TX not moving on double-clcik

[Jim Shorney]

Thanks Charlie! Nice to know it isn't just me...  :)

73

-Jim
NU0C


On Sun, 2 Dec 2018 21:20:39 -
char...@sucklingfamily.free-online.co.uk wrote:

> Hi Jim
> 
> Yes, we experienced the same behaviour where clicking an earlier message
> when bailing on a QSO ended up splitting the TX and RX frequencies.
> 
> We also found it labour intensive to have to select TX4 and enable TX
> manually when the calling station sent R report again, clearly not having
> received our initial RR73 message.  On some occasions we needed to do this
> several times during more difficult QSOs.
> 
> 73
> 
> Charlie G3WDG
> >
> > I have noticed a specific scenario that has happened several times during
> > the contest. This happens when I have called a CQing station two or three
> > times with no reply and I bail and go call another. Then I see the first
> > station replying to me with TX3 while I am calling the new one. So I bail
> > on that call and try to go back to work the first station with a
> > double-click on the message. This moves the RX back to the first station's
> > frequency, but not the TX. It is acting like Hold TX is on, but it is not.
> > I tried toggling Hold TX. and shift-doubleclick, but the TX refuses to
> > move until I use one those "confusing" arrows. (j/k, I'm not confused  -
> > much).
> >
> > Maybe I'm just a bad op. I know we are supposed to offset our signals and
> > call split, but that doesn't seem to be happening. At any rate, it seems
> > like the TX should move in this scenario, otherwise I end up QRMing the
> > second op until I remember where I am.
> >
> > While I am at it, it would be nice if, when calling running station, Tx4
> > could me made sticky until the final 73 is received. Leave TX disable
> > alone, just let Tx4 stay selected in case it needs to be re-sent. One less
> > thing to have to scramble for when things don't go as planned.
> >
> > Anyway, 70 contacts so far before I needed to take a break.
> >
> > 73
> >
> > -Jim
> > NU0C
> >
> >
> > --
> > The universe we're in will reach absolute zero in three hours. Safe is
> > relative. - Idris, "The Doctor's Wife"


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

[wsjt-devel] FT8-RU FB

[Glen Brown]

Fun contest.  No problems at all with the software.  .
WIN10 PRO 64,  K3, Xonar U7

Looking forward to "TU; ..."  feature
73,
Glen W6GJB
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Wide Graph Display Problem

[Thomas Webb]

Which 'palette' are you using?

  _  

From: Chuck Furman [mailto:chuck.fur...@gmail.com] 
Sent: Sunday, December 02, 2018 6:14 PM
To: WSJT software development
Subject: Re: [wsjt-devel] Wide Graph Display Problem


I just noticed that mine was not showing the band either. I switched "N Avg 4" 
to "Nvg 3", and now
it is displaying time and band.

On Sun, 2 Dec 2018 at 17:20, Thomas Webb  wrote:


For whatever reason, the wide graph display on both Ver 1.9 & 2.0 has gone 
goofy.

The lines between 15 second time block is now VERY narrow and the band is no 
longer displayed.

Any suggestions?

Thomas Webb
WA9AFM/5
ASM
Oklahoma Section



___
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] Wide Graph Display Problem

[Thomas Webb]

Thanks for the heads up!  I had to go to Nvg 1, but all is now as it should be.

  _  

From: Chuck Furman [mailto:chuck.fur...@gmail.com] 
Sent: Sunday, December 02, 2018 6:14 PM
To: WSJT software development
Subject: Re: [wsjt-devel] Wide Graph Display Problem


I just noticed that mine was not showing the band either. I switched "N Avg 4" 
to "Nvg 3", and now
it is displaying time and band.

On Sun, 2 Dec 2018 at 17:20, Thomas Webb  wrote:


For whatever reason, the wide graph display on both Ver 1.9 & 2.0 has gone 
goofy.

The lines between 15 second time block is now VERY narrow and the band is no 
longer displayed.

Any suggestions?

Thomas Webb
WA9AFM/5
ASM
Oklahoma Section



___
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] Wide Graph Display Problem

[Chuck Furman]

I just noticed that mine was not showing the band either. I switched "N Avg
4" to "Nvg 3", and now it is displaying time and band.

On Sun, 2 Dec 2018 at 17:20, Thomas Webb  wrote:

> For whatever reason, the wide graph display on both Ver 1.9 & 2.0 has gone
> goofy.
>
> The lines between 15 second time block is now VERY narrow and the band is
> no longer displayed.
>
> Any suggestions?
>
> Thomas Webb
> WA9AFM/5
> ASM
> Oklahoma Section
>
>
>
> ___
> 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] WSJT-X: Summary of issues with v2.0.0 RC5 in RTTY Roundup mode

[Bill Somerville]

On 02/12/2018 21:19, Laurie, VK3AMA wrote:

On 3/12/2018 12:05 am, Bill Somerville wrote:


The WSJT-X UDP protocol logging message will have the contest 
exchange fields added for the next release of WSJT-X and cooperating 
applications will be able to extract the required information.



Bill,

Good to hear.

Please give some serious consideration to adding additional UDP status 
data. Currently, there is no way to know what operating mode (not TX 
mode) WSJT-X is currently using, Fox, Hound or which Contest enabled. 
It would be very helpful if the UDP protocol provided a field within 
the Status packet for these modes of operation.


de Laurie VK3AMA


Hi Laurie,

I am not really certain that knowing which mode WSJT-X is in will 
necessarily help a great deal. Part of the point of the new FT8 77-bit 
messages is that WSJT-X does not need to know which type it is set to to 
decode any message. the messages contain all the information with 
exception of the ones with a hash code where some information is 
recalled from prior decodes. OTOH it is likely that each mode of 
operation will be separated by time or frequency or both so I suppose 
there is some value but there is no guarantee that when in one of the 
contest modes it will only decode messages deigned for that contest mode.


Anyway, I have made the changes. Here is the diff of the 
NetworkMessage.hpp file:


$ git diff wsjtx-2.0.0-rc5 -- NetworkMessage.hpp
diff --git a/NetworkMessage.hpp b/NetworkMessage.hpp
index ffd0ff288..a4d9ba0d5 100644
--- a/NetworkMessage.hpp
+++ b/NetworkMessage.hpp
@@ -124,6 +124,7 @@
  * Tx Watchdog    bool
  * Sub-mode   utf8
  * Fast mode  bool
+ * Special operation mode quint8
  *
  *    WSJT-X  sends this  status message  when various  internal state
  *    changes to allow the server to  track the relevant state of each
@@ -142,10 +143,22 @@
  *  At the start and end of decoding,
  *  When the Rx DF changes,
  *  When the Tx DF changes,
- *  When the DE call or grid changes (currently when settings are 
exited),

+ *  When settings are exited,
  *  When the DX call or grid changes,
  *  When the Tx watchdog is set or reset.
  *
+ *    The Special operation mode is  an enumeration that indicates the
+ *    setting  selected  in  the  WSJT-X "Settings->Advanced->Special
+ *    operating activity" panel. The values are as follows:
+ *
+ *   0 -> NONE
+ *   1 -> NA VHF
+ *   2 -> EU VHF
+ *   3 -> FIELD DAY
+ *   4 -> RTTY RU
+ *   5 -> FOX
+ *   6 -> HOUND
+ *
  *
  * Decode    Out   2  quint32
  * Id (unique key)    utf8
@@ -240,6 +253,8 @@
  * Operator call  utf8
  * My call    utf8
  * My grid    utf8
+ * Exchange sent  utf8
+ * Exchange received  utf8
  *
  *  The  QSO logged  message is  sent  to the  server(s) when  the
  *  WSJT-X user accepts the "Log  QSO" dialog by clicking the "OK"

I will send you a preview Windows installer direct.

73
Bill
G4WJS.

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

[wsjt-devel] Wide Graph Display Problem

[Thomas Webb]

For whatever reason, the wide graph display on both Ver 1.9 & 2.0 has gone 
goofy.

The lines between 15 second time block is now VERY narrow and the band is no 
longer displayed.

Any suggestions?

Thomas Webb
WA9AFM/5
ASM
Oklahoma Section



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

Re: [wsjt-devel] Running 1.9 and 2.0 Simultaneously

[Frank Kirschner]

Thanks to all. I'll do some experimenting and see what I can do.

73,
Frank
KF6E
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Frequency Management in Contest Mode.

[Bill Somerville]

On 02/12/2018 21:22, Grant VK5GR wrote:
I double clicked on his call in the Band Activity window and then 
wondered why he disappeared. After about 90 seconds I glanced over at 
my SDR and realised my signal was in the lower cluster of signals – 
looked at the rig and realised it had jumped back to 7074.


Hi Grant,

that's not supposed to happen. Was it the double-clicking of a call that 
caused it to skip to a preset frequency or something else? Is it 
reproducible?


73
Bill
G4WJS.



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

[wsjt-devel] Frequency Management in Contest Mode.

[Grant VK5GR]

Joe and team,

 

One issue I also just encountered  - while working you Joe actually - was
that I had only spun the dial onto 7080 I hadn't programmed it into the
frequency list. When I started calling CQ it was fine and I worked my first
station with "hold TX Freq" checked plus Call First and AutoSeq checked. At
the end of the first caller cycle I didn't immediately select enable TX to
have another round, however Joe called me while I was trying to sort out the
logging again - so I double clicked on his call in the Band Activity window
and then wondered why he disappeared. After about 90 seconds I glanced over
at my SDR and realised my signal was in the lower cluster of signals -
looked at the rig and realised it had jumped back to 7074.

 

I can already see there are two blocks of contesters on 40m and so manually
tuning the dial I can see will become more common. It would be good if the
system could be put in a mode where VFO-A (receiver control) can always be
taken from the rig and VFO-B (in split mode) is managed as an offset from
VFO A only. It would be a return to more of the PSK contesting days where
you still tuned the dial to work everyone in your 2-3kHz RX window - then
move on to the next cluster.

 

Regards,

Grant VK5GR

 

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

Re: [wsjt-devel] TX not moving on double-clcik

[charlie]

Hi Jim

Yes, we experienced the same behaviour where clicking an earlier message
when bailing on a QSO ended up splitting the TX and RX frequencies.

We also found it labour intensive to have to select TX4 and enable TX
manually when the calling station sent R report again, clearly not having
received our initial RR73 message.  On some occasions we needed to do this
several times during more difficult QSOs.

73

Charlie G3WDG
>
> I have noticed a specific scenario that has happened several times during
> the contest. This happens when I have called a CQing station two or three
> times with no reply and I bail and go call another. Then I see the first
> station replying to me with TX3 while I am calling the new one. So I bail
> on that call and try to go back to work the first station with a
> double-click on the message. This moves the RX back to the first station's
> frequency, but not the TX. It is acting like Hold TX is on, but it is not.
> I tried toggling Hold TX. and shift-doubleclick, but the TX refuses to
> move until I use one those "confusing" arrows. (j/k, I'm not confused  -
> much).
>
> Maybe I'm just a bad op. I know we are supposed to offset our signals and
> call split, but that doesn't seem to be happening. At any rate, it seems
> like the TX should move in this scenario, otherwise I end up QRMing the
> second op until I remember where I am.
>
> While I am at it, it would be nice if, when calling running station, Tx4
> could me made sticky until the final 73 is received. Leave TX disable
> alone, just let Tx4 stay selected in case it needs to be re-sent. One less
> thing to have to scramble for when things don't go as planned.
>
> Anyway, 70 contacts so far before I needed to take a break.
>
> 73
>
> -Jim
> NU0C
>
>
> --
> The universe we're in will reach absolute zero in three hours. Safe is
> relative. - Idris, "The Doctor's Wife"
>
>
> ___
> 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] WSJT-X: Summary of issues with v2.0.0 RC5 in RTTY Roundup mode

[Laurie, VK3AMA]

On 3/12/2018 12:05 am, Bill Somerville wrote:


The WSJT-X UDP protocol logging message will have the contest exchange 
fields added for the next release of WSJT-X and cooperating 
applications will be able to extract the required information.




Bill,

Good to hear.

Please give some serious consideration to adding additional UDP status 
data. Currently, there is no way to know what operating mode (not TX 
mode) WSJT-X is currently using, Fox, Hound or which Contest enabled. It 
would be very helpful if the UDP protocol provided a field within the 
Status packet for these modes of operation.


de Laurie VK3AMA



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

Re: [wsjt-devel] Running 1.9 and 2.0 Simultaneously

[Black Michael via wsjt-devel]

You can copy the shortcut on your desktop and change the Target to include the 
--rig-name value.
de Mike W9MDB



 

On Sunday, December 2, 2018, 1:54:43 PM CST, Paul Kube 
 wrote:  
 
 Frank -- The only way I know to do this is from the command line.
See http://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main.html#FAQ.

How should I configure WSJT-X to run multiple instances?

Start WSJT-X from a command-prompt window, passing each instance a unique 
identifier as in the following two-instance example. This procedure will 
isolate the Settings file and the writable file location for each instance of 
WSJT-X.
wsjtx --rig-name=TS2000
wsjtx --rig-name=FT847

73, Paul K6PO
On Sun, Dec 2, 2018 at 10:44 AM Frank Kirschner  
wrote:

I'd like to run both versions of WSJT-X simultaneously, linked to two different 
receiver slices. When I try to run the second program, it says it needs a 
different radio name. I don't see anywhere to enter a radio name. I would have 
thought it would be under Settings, Radio, but there is only Rig, which is a 
drop-down, and has to be HRD.
Is there a way to run both versions simultaneously? Any help would be 
appreciated.
Flex 6600/MaestroWin 7 64HRD latest version
Thanks.
73,FrankKF6E
___
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] WSJT-X: Summary of issues with v2.0.0 RC5 in RTTY Roundup mode

[Dana Myers]

On 12/2/2018 5:05 AM, Bill Somerville wrote:


1) Having Tab 2 messages selected on the WSJT-X main window causes contest exchanges not to be transferred to the Log QSO window 
which in turn blocks logging a QSO until the exchange fields are filled in.


Workaround: Select Tab 1 messages.



Historically, I've always used Tab 2, it was easier for me when getting started 
with all
this marvelous new magic that was WSJT-X. So, as a results of using the Tab 1 
work-around,
I realized I personally would not miss Tab 2 - and it helps me avoid 
out-of-sequence
errors I sometimes make.

At the same time, I'm not offended by the presence of Tab 2.

Again, apologies to those trying to make a serious entry in the ARRL RTTY Roundup using FT8 mode if you were hindered. All these 
issues will be fixed for the next release



Fortunately, this isn't the ARRL RTTY Round-Up - that's in January. This is the 
FT8
Round-Up - wonderfully timed to help us all get the kinds sorted-out before the
ARRL RTTY Round-Up.

Thanks for all the hard work on WSJT-X!

73,
Dana  K6JQ



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

Re: [wsjt-devel] Contest Log Window- Autoscroll

[Al Pawlowski]

Me too. When I log, log entries scroll up one, but just logged entry is one 
line below bottom edge. If I have already scrolled the last entry into view 
(bottom line), no entries scroll up on a new log entry - if I remember 
correctly. 

Vertically, my window is open enough to show about 18 entries (no room for 
more).  Windows 10 Home.


Al Pawlowski, K6AVP
Los Osos, CA USA

> Date: Sun, 2 Dec 2018 12:07:00 -0500
> From: Bill Pence mailto:pence.b...@gmail.com>>
> To: marting0...@gmail.com ,  WSJT software 
> development
>>
> Cc: Bill Somerville mailto:b...@classdesign.com>>
> Subject: Re: [wsjt-devel] Contest Log Window- Autoscroll
> 
> Same here. Last qso is just off the bottom on the contest log window. A new
> Q scolls to see the previous last, but then the newest is still out of view
> unless I scroll manually...

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

Re: [wsjt-devel] WSJT-X: Summary of issues with v2.0.0 RC5 in RTTY Roundup mode

[Jörg Hochheimer , DL6ZBN]

Hi all,

I second that. I am much more comfortable with Tab 2 and almost never 
use Tab 1.


Vy 73 de Joe, DL6ZBN

Am 02.12.2018 um 17:24 schrieb Richard Lamont:

On 02/12/2018 13:05, Bill Somerville wrote:

[snip] It might be desirable for the ongoing development of WSJT-X to
remove Tab 2 from the user interface. Please respond if you feel that
Tab 2 messages are essential to your operating enjoyment and that Tab 1
is not suitable for you.

Hi Bill.

I've always used Tab 2. I could no doubt get used to Tab 1 with
sufficient practice, but would prefer not to have to.


73,
Richard G4DYA


___
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] WSJT-X: Summary of issues with v2.0.0 RC5 in RTTY Roundup mode

[Tom Ramberg via wsjt-devel]

Point 3 and 3a: For what it's worth, the contest log and all other logs where 
data is exported to shows UTC (and it's correct). I'm in Finland, and the 
computer clock is set to regional time. OS is Windows 7. In other word, I do 
not see this problem here. 

de Tom OH6VDA (operating OH2K - The radio Club of Kauniainen)

> 2. des. 2018 kl. 19:25 skrev Al Pawlowski :
> 
> My vote is for keeping the tab 2 messages window/layout. I find tab 2 faster 
> for selecting the appropriate message and the “free text” message easier to 
> use - maybe it is the bigger/bolder select buttons, vs the undifferentiated 
> (for tx, rx), smaller selection targets of tab 1.
> 
> Al Pawlowski, K6AVP
> Los Osos, CA USA
> 
> 
> Date: Sun, 2 Dec 2018 13:05:16 +
>> From: Bill Somerville 
>> To: WSJT software development 
>> Subject: [wsjt-devel] WSJT-X: Summary of issues with v2.0.0 RC5 in
>>  RTTY Roundup mode
>> 
>> Hi All,
>> 
>> thanks for the feedback during the contest activity and sorry for those 
>> that have had issues that caused serious problems. Here is a summary of 
>> the main issues with workarounds where available:
> 
>> …..Please respond if you feel that 
>> Tab 2 messages are essential to your operating enjoyment and that Tab 1 
>> is not suitable for you.
> 
> ___
> 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] Running 1.9 and 2.0 Simultaneously

[N1BUG]

I run multiple instances all the time. I have configured separate
desktop shortcuts for each instance I want to run with unique
rig-name parameters on the command line.

At the moment I have only two instances running... one of 1.9.1 and
one of 2.0.0-rc5. But I sometimes have as many as five or six
instances running.

73,
Paul N1BUG


On 12/2/18 2:51 PM, Paul Kube wrote:
> Frank -- The only way I know to do this is from the command line.
> 
> See http://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main.html#FAQ.
> 
> *How should I configure WSJT-X to run multiple instances?*
> 
> Start *WSJT-X* from a command-prompt window, passing each instance a unique
> identifier as in the following two-instance example. This procedure will
> isolate the *Settings* file and the writable file location for each
> instance of *WSJT-X*.
> 
> wsjtx --rig-name=TS2000
> wsjtx --rig-name=FT847
> 
> 
> 
> 73, Paul K6PO
> 
> On Sun, Dec 2, 2018 at 10:44 AM Frank Kirschner 
> wrote:
> 
>> I'd like to run both versions of WSJT-X simultaneously, linked to two
>> different receiver slices. When I try to run the second program, it says it
>> needs a different radio name. I don't see anywhere to enter a radio name. I
>> would have thought it would be under Settings, Radio, but there is only
>> Rig, which is a drop-down, and has to be HRD.
>>
>> Is there a way to run both versions simultaneously? Any help would be
>> appreciated.
>>
>> Flex 6600/Maestro
>> Win 7 64
>> HRD latest version
>>
>> Thanks.
>>
>> 73,
>> Frank
>> KF6E


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

Re: [wsjt-devel] Missing grid square info

[Chuck Furman]

QRZ.com should show the location of the radio, not the operator.

On Sun, Dec 2, 2018 at 1:50 PM AB4IQ  wrote:

> I have a friend who has a remote station just several miles outside of the
> county limits Grid EM57 (Home QTH) and is now EM56 at his remote location.
> However, he has his QRZ Information updated noting that his station is now
> at the remote site in EM56.
>
>
>
> Ed.. AB4IQ
>
>
>
> *From:* Chuck Furman [mailto:chuck.fur...@gmail.com]
> *Sent:* Sunday, December 2, 2018 11:41 AM
> *To:* WSJT software development 
> *Subject:* Re: [wsjt-devel] Missing grid square info
>
>
>
> Bill,
>
>
>
> I’m confused. Why does remote operating affect the grid? I operate
> remotely all the time. I operate from my kitchen, my living room, patio,
> etc. I’ve also operated from China and Dubai. But in all cases, the station
> is in my house in Plano, Texas... in grid EM13oc. The grid square never
> changes. Why does it matter where the operator is located? The only thing
> that is important is the location of the radio.
>
>
>
> On a slightly different topic... I’ve noticed that some people don’t keep
> QRZ.com updated. The grid they give you during the contact doesn’t match
> what’s on QRZ. So filling in missing grids can be risky.
>
>
>
> Chuck
>
> KG6PH
>
> Plano, Texas
>
>
>
>
>
> On Sun, Dec 2, 2018 at 10:45 AM Bill Pence  wrote:
>
> In the round up, grids are only present in the CQ message.  So if someone
> ANSWERS your CQ, you do not get their grid...
>
>
>
> I plan to look these up and add then the the log
>
>
>
> But, at least 1 Q was with someone using a remote station via internet, so
> his grid will remain unknown...
>
>
>
> On Sun, Dec 2, 2018, 11:12 AM Bill Mullin 
> I'm an FT8 newbie - made my first QSO with this mode less than a week
> ago.  The below problem may have been discussed before and I apologize if I
> missed it.  Anyway, I notice that both my LOG and ADI files are randomly
> missing grid squares.  Here's my last 6 QSO's, all made today:
>
> 2018-12-02,13:53:45,2018-12-02,13:54:45,DS4NPL,PM35,7.074300,FT8,+01,-15,,,
> 2018-12-02,14:01:45,2018-12-02,14:03:15,JG1ULT,PM95,7.075050,FT8,-10,-12,,,
> 2018-12-02,14:11:45,2018-12-02,14:12:45,KQ6K,,3.575100,FT8,-03,-03,,,
> 2018-12-02,14:32:15,2018-12-02,14:33:15,JA2ATE,,3.573600,FT8,+02,+02,,,
> 2018-12-02,14:49:15,2018-12-02,14:50:15,HR1LW,,14.075094,FT8,-10,-17,,,
> 2018-12-02,14:51:00,2018-12-02,14:52:00,PJ2DD,FK52,14.075717,FT8,-08,-04,,,
>
> 3 of the 6 grid square information is missing, in spite of the fact that
> it was definitely sent to me.  This group was with 1.9.1.  I also had 16
> QSOs in the Roundup with 2.0.0 RC5 . . . 2 of the QSOs do not have grid
> information in the LOG or ADI file.
>
> Is this a known problem?  Will these missing grids cause me any problems
> in the future?
>
> Tnx & 73,
> Bill  AA4M
>
> ___
> 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] Running 1.9 and 2.0 Simultaneously

[Paul Kube]

Frank -- The only way I know to do this is from the command line.

See http://physics.princeton.edu/pulsar/k1jt/wsjtx-doc/wsjtx-main.html#FAQ.

*How should I configure WSJT-X to run multiple instances?*

Start *WSJT-X* from a command-prompt window, passing each instance a unique
identifier as in the following two-instance example. This procedure will
isolate the *Settings* file and the writable file location for each
instance of *WSJT-X*.

wsjtx --rig-name=TS2000
wsjtx --rig-name=FT847



73, Paul K6PO

On Sun, Dec 2, 2018 at 10:44 AM Frank Kirschner 
wrote:

> I'd like to run both versions of WSJT-X simultaneously, linked to two
> different receiver slices. When I try to run the second program, it says it
> needs a different radio name. I don't see anywhere to enter a radio name. I
> would have thought it would be under Settings, Radio, but there is only
> Rig, which is a drop-down, and has to be HRD.
>
> Is there a way to run both versions simultaneously? Any help would be
> appreciated.
>
> Flex 6600/Maestro
> Win 7 64
> HRD latest version
>
> Thanks.
>
> 73,
> Frank
> KF6E
> ___
> 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] Missing grid square info

[AB4IQ]

I have a friend who has a remote station just several miles outside of the 
county limits Grid EM57 (Home QTH) and is now EM56 at his remote location.  
However, he has his QRZ Information updated noting that his station is now at 
the remote site in EM56.

 

Ed.. AB4IQ

 

From: Chuck Furman [mailto:chuck.fur...@gmail.com] 
Sent: Sunday, December 2, 2018 11:41 AM
To: WSJT software development 
Subject: Re: [wsjt-devel] Missing grid square info

 

Bill,

 

I’m confused. Why does remote operating affect the grid? I operate remotely all 
the time. I operate from my kitchen, my living room, patio, etc. I’ve also 
operated from China and Dubai. But in all cases, the station is in my house in 
Plano, Texas... in grid EM13oc. The grid square never changes. Why does it 
matter where the operator is located? The only thing that is important is the 
location of the radio. 

 

On a slightly different topic... I’ve noticed that some people don’t keep 
QRZ.com updated. The grid they give you during the contact doesn’t match what’s 
on QRZ. So filling in missing grids can be risky. 

 

Chuck 

KG6PH 

Plano, Texas 

 

 

On Sun, Dec 2, 2018 at 10:45 AM Bill Pence mailto:pence.b...@gmail.com> > wrote:

In the round up, grids are only present in the CQ message.  So if someone 
ANSWERS your CQ, you do not get their grid...

 

I plan to look these up and add then the the log

 

But, at least 1 Q was with someone using a remote station via internet, so his 
grid will remain unknown...

 

On Sun, Dec 2, 2018, 11:12 AM Bill Mullin mailto:mrb...@aa4m.com>  wrote:

I'm an FT8 newbie - made my first QSO with this mode less than a week ago.  The 
below problem may have been discussed before and I apologize if I missed it.  
Anyway, I notice that both my LOG and ADI files are randomly missing grid 
squares.  Here's my last 6 QSO's, all made today:

2018-12-02,13:53:45,2018-12-02,13:54:45,DS4NPL,PM35,7.074300,FT8,+01,-15,,,
2018-12-02,14:01:45,2018-12-02,14:03:15,JG1ULT,PM95,7.075050,FT8,-10,-12,,,
2018-12-02,14:11:45,2018-12-02,14:12:45,KQ6K,,3.575100,FT8,-03,-03,,,
2018-12-02,14:32:15,2018-12-02,14:33:15,JA2ATE,,3.573600,FT8,+02,+02,,,
2018-12-02,14:49:15,2018-12-02,14:50:15,HR1LW,,14.075094,FT8,-10,-17,,,
2018-12-02,14:51:00,2018-12-02,14:52:00,PJ2DD,FK52,14.075717,FT8,-08,-04,,,

3 of the 6 grid square information is missing, in spite of the fact that it was 
definitely sent to me.  This group was with 1.9.1.  I also had 16 QSOs in the 
Roundup with 2.0.0 RC5 . . . 2 of the QSOs do not have grid information in the 
LOG or ADI file.

Is this a known problem?  Will these missing grids cause me any problems in the 
future?

Tnx & 73,
Bill  AA4M

___
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] WSJT-X RU logging possible improvements

[Bill Pence]

I had considered the same thing.
I agree that would be nice.  but you're right this is ignoring the code
implications... And I bet they are not small

but yes it would be an awesome feature to have kind of a command " I'm
about to start a contest so start a new contest log but still log
everything to my overall Master log as well.

I suspect that responsibility is for external log program.

On Sun, Dec 2, 2018, 2:26 PM Marco Calistri  Despite my very modest antenna system (HVT-400B on the balcony at 4th
> floor) I'm here on 14.130 KHz attempting to put at least 20 contacts
> into the Cabrillo log... :-(
>
> I was thinking to the requirement to reset the "wsjtx_log.adi" before
> starting a new RU and the possibility to manage it differently by WSJT-X
> next versions.
>
> For example: by using a separate log_adi specifically created for RUs,
> let's say for example a file named "log_RU_.adi" in order the RTTY
> RU Contest could use it instead of the main and very important default
> "wsjtx_log.adi" file.
>
> But I ignore what a similar feature implies in the code of the application.
>
> Regards,
>
> --
>
> 73 de Marco, PY1ZRJ
>
> ___
> 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] Tab 2

[Jim Preston]

Same here.

73,

Jim N6VH


On 12/2/2018 7:51 AM, Gary Rogers wrote:

I also almost always use Tab 2…Please keep it…Thanks Gary KO3f

On Dec 2, 2018, at 10:37 AM, Edfel Rivera > wrote:


Hi All:

Tab 2 is my default operating since using WSJTX (1.6).  Vote to keep 
it as option or better find a fix.  Also, IMO Tab 2 make the program 
more intuitive and UI more appealing.  Particularly when calling CQ.  
It is matter of preferences, at least make option to use and alert 
(through message) users limitation related with QSO logging, if fix is 
not possible.


Thanks Development Team!

73'

Edfel
KP4AJ

On Sun, Dec 2, 2018 at 9:53 AM Gene H > wrote:


To List,

Please keep TAB 2 so it can be an option. I use it all the time
for FT8 contacts since inception.

73 Gene K5PA


On 12/2/2018 8:20 AM, Hasan al-Basri wrote:

I prefer TAB 1, do not use TAB 2, ever.

Hasan


On Sun, Dec 2, 2018 at 8:06 AM WB5JJJ mailto:wb5...@gmail.com>> wrote:

Bill:

As you requested, I have never used Tab 2.  One vote to
remove it.  Tab 1 has all the information as to what is going
on during a contact with no thinking required.

I have NOT had the UTC/Local time stamp issue.  My Contest
Log has the correct 24 hour UTC for every entry and I'm set
to Central Time in my automatic MS time keeping offset.

Enjoyed reading your all-inclusive review of
problems/solutions and fixes in one place, great work putting
that together.  Thanks.

Windows 10 Pro 64 bit here and all aspects of WSJTx-RC5 have
worked perfectly. I for one, have not had a single problem
with the Contest Logger, so never had a reason to "edit" it
for any reason.  Everything is logging to HRD LB directly
without a glitch - and I DO check every entry while waiting
on next contact.

Even though most contacts do not include a Grid Square along
with all other personal information, HRD LB does get the 6
digit GS with the query of QRZ upon adding the entry. Of
course this field is "0" characters in the WSJTX log file. 
This could cause a problem for some that use the adi file as

the import to their logger.  The  size may not
allow the GS to be edited in their logger to a 4 or 6
character count since space was not allocated by the adi file
import.

Bottom Line - the program requires absolutely no interaction
from me for proper logging.  I do edit the HRD LB entry when
some European stations have their Postal Code in front of 
their QTH information, so I do delete that. (Future note to

coders to fix this if possible, could be a problem as there
are several variations being seen).

73's
-- 
George Cotton, WB5JJJ


___
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


-- 
Gene Hinkle

2026 Spyglass Hill, Leander, TX 78641
e-mail to Gene:ghin...@gmail.com  
cell phone or text messaging:  (512) 413-9251
--




___
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

[wsjt-devel] WSJT-X RU logging possible improvements

[Marco Calistri]

Despite my very modest antenna system (HVT-400B on the balcony at 4th
floor) I'm here on 14.130 KHz attempting to put at least 20 contacts
into the Cabrillo log... :-(

I was thinking to the requirement to reset the "wsjtx_log.adi" before
starting a new RU and the possibility to manage it differently by WSJT-X
next versions.

For example: by using a separate log_adi specifically created for RUs,
let's say for example a file named "log_RU_.adi" in order the RTTY
RU Contest could use it instead of the main and very important default
"wsjtx_log.adi" file.

But I ignore what a similar feature implies in the code of the application.

Regards,

-- 

73 de Marco, PY1ZRJ

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

Re: [wsjt-devel] Missing grid square info

[Bill Pence]

Yes lotw uses the other stations grid sq. Not sure about eqsl. I am prolly
doing extra work to add missing grid sq to my logs.


On Sun, Dec 2, 2018, 2:12 PM Mark James  For the Grid Chase, I think ARRL uses the grid set for each station in
> LOTW (multiple QTH profiles can be set. Not sure about VUCC.
> On Sun, Dec 2, 2018 at 2:04 PM Bill Pence  wrote:
>
>> Correct. I had not realized this. As I looked at his qrz.com page he was
>> talking about living deed restricted and using remote radios
>> Dang.
>>
>> And yes, some others might be in accurate as well.
>>
>> On Sun, Dec 2, 2018, 1:28 PM Chuck Furman >
>>> I get it now. You meant he was operating remote, as in “away from his
>>> home station” (actual radio in a different grid). That was exactly my
>>> point... you can’t rely on the qrz.com information to be correct.
>>> Sometimes I try to text them with JTALERT to ask for their grid. But if
>>> they are portable, they may not have an Internet connection.
>>>
>>> On Sun, Dec 2, 2018 at 12:17 Bill Pence  wrote:
>>>
 Because he answered my CQ, so while  I can look up his home grid, that
 was not necessarily his transmitter location. And since he answered my CQ,
 his grid was not exchanged
 The impact of him operating remote is that I am unable to add from
 qrz.com



 On Sun, Dec 2, 2018, 12:44 PM Chuck Furman >>> wrote:

> Bill,
>
> I’m confused. Why does remote operating affect the grid? I operate
> remotely all the time. I operate from my kitchen, my living room, patio,
> etc. I’ve also operated from China and Dubai. But in all cases, the 
> station
> is in my house in Plano, Texas... in grid EM13oc. The grid square never
> changes. Why does it matter where the operator is located? The only thing
> that is important is the location of the radio.
>
> On a slightly different topic... I’ve noticed that some people don’t
> keep QRZ.com updated. The grid they give you during the contact doesn’t
> match what’s on QRZ. So filling in missing grids can be risky.
>
> Chuck
> KG6PH
> Plano, Texas
>
>
> On Sun, Dec 2, 2018 at 10:45 AM Bill Pence 
> wrote:
>
>> In the round up, grids are only present in the CQ message.  So if
>> someone ANSWERS your CQ, you do not get their grid...
>>
>> I plan to look these up and add then the the log
>>
>> But, at least 1 Q was with someone using a remote station via
>> internet, so his grid will remain unknown...
>>
>> On Sun, Dec 2, 2018, 11:12 AM Bill Mullin >
>>> I'm an FT8 newbie - made my first QSO with this mode less than a
>>> week ago.  The below problem may have been discussed before and I 
>>> apologize
>>> if I missed it.  Anyway, I notice that both my LOG and ADI files are
>>> randomly missing grid squares.  Here's my last 6 QSO's, all made today:
>>>
>>>
>>> 2018-12-02,13:53:45,2018-12-02,13:54:45,DS4NPL,PM35,7.074300,FT8,+01,-15,,,
>>>
>>> 2018-12-02,14:01:45,2018-12-02,14:03:15,JG1ULT,PM95,7.075050,FT8,-10,-12,,,
>>> 2018-12-02,14:11:45,2018-12-02,14:12:45,KQ6K,,3.575100,FT8,-03,-03,,,
>>>
>>> 2018-12-02,14:32:15,2018-12-02,14:33:15,JA2ATE,,3.573600,FT8,+02,+02,,,
>>>
>>> 2018-12-02,14:49:15,2018-12-02,14:50:15,HR1LW,,14.075094,FT8,-10,-17,,,
>>>
>>> 2018-12-02,14:51:00,2018-12-02,14:52:00,PJ2DD,FK52,14.075717,FT8,-08,-04,,,
>>>
>>> 3 of the 6 grid square information is missing, in spite of the fact
>>> that it was definitely sent to me.  This group was with 1.9.1.  I also 
>>> had
>>> 16 QSOs in the Roundup with 2.0.0 RC5 . . . 2 of the QSOs do not have 
>>> grid
>>> information in the LOG or ADI file.
>>>
>>> Is this a known problem?  Will these missing grids cause me any
>>> problems in the future?
>>>
>>> Tnx & 73,
>>> Bill  AA4M
>>>
>>> ___
>>> 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
>>
> ___
> 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

Re: [wsjt-devel] Missing grid square info

[Mark James]

For the Grid Chase, I think ARRL uses the grid set for each station in LOTW
(multiple QTH profiles can be set. Not sure about VUCC.
On Sun, Dec 2, 2018 at 2:04 PM Bill Pence  wrote:

> Correct. I had not realized this. As I looked at his qrz.com page he was
> talking about living deed restricted and using remote radios
> Dang.
>
> And yes, some others might be in accurate as well.
>
> On Sun, Dec 2, 2018, 1:28 PM Chuck Furman 
>> I get it now. You meant he was operating remote, as in “away from his
>> home station” (actual radio in a different grid). That was exactly my
>> point... you can’t rely on the qrz.com information to be correct.
>> Sometimes I try to text them with JTALERT to ask for their grid. But if
>> they are portable, they may not have an Internet connection.
>>
>> On Sun, Dec 2, 2018 at 12:17 Bill Pence  wrote:
>>
>>> Because he answered my CQ, so while  I can look up his home grid, that
>>> was not necessarily his transmitter location. And since he answered my CQ,
>>> his grid was not exchanged
>>> The impact of him operating remote is that I am unable to add from
>>> qrz.com
>>>
>>>
>>>
>>> On Sun, Dec 2, 2018, 12:44 PM Chuck Furman >> wrote:
>>>
 Bill,

 I’m confused. Why does remote operating affect the grid? I operate
 remotely all the time. I operate from my kitchen, my living room, patio,
 etc. I’ve also operated from China and Dubai. But in all cases, the station
 is in my house in Plano, Texas... in grid EM13oc. The grid square never
 changes. Why does it matter where the operator is located? The only thing
 that is important is the location of the radio.

 On a slightly different topic... I’ve noticed that some people don’t
 keep QRZ.com updated. The grid they give you during the contact doesn’t
 match what’s on QRZ. So filling in missing grids can be risky.

 Chuck
 KG6PH
 Plano, Texas


 On Sun, Dec 2, 2018 at 10:45 AM Bill Pence 
 wrote:

> In the round up, grids are only present in the CQ message.  So if
> someone ANSWERS your CQ, you do not get their grid...
>
> I plan to look these up and add then the the log
>
> But, at least 1 Q was with someone using a remote station via
> internet, so his grid will remain unknown...
>
> On Sun, Dec 2, 2018, 11:12 AM Bill Mullin 
>> I'm an FT8 newbie - made my first QSO with this mode less than a week
>> ago.  The below problem may have been discussed before and I apologize 
>> if I
>> missed it.  Anyway, I notice that both my LOG and ADI files are randomly
>> missing grid squares.  Here's my last 6 QSO's, all made today:
>>
>>
>> 2018-12-02,13:53:45,2018-12-02,13:54:45,DS4NPL,PM35,7.074300,FT8,+01,-15,,,
>>
>> 2018-12-02,14:01:45,2018-12-02,14:03:15,JG1ULT,PM95,7.075050,FT8,-10,-12,,,
>> 2018-12-02,14:11:45,2018-12-02,14:12:45,KQ6K,,3.575100,FT8,-03,-03,,,
>>
>> 2018-12-02,14:32:15,2018-12-02,14:33:15,JA2ATE,,3.573600,FT8,+02,+02,,,
>>
>> 2018-12-02,14:49:15,2018-12-02,14:50:15,HR1LW,,14.075094,FT8,-10,-17,,,
>>
>> 2018-12-02,14:51:00,2018-12-02,14:52:00,PJ2DD,FK52,14.075717,FT8,-08,-04,,,
>>
>> 3 of the 6 grid square information is missing, in spite of the fact
>> that it was definitely sent to me.  This group was with 1.9.1.  I also 
>> had
>> 16 QSOs in the Roundup with 2.0.0 RC5 . . . 2 of the QSOs do not have 
>> grid
>> information in the LOG or ADI file.
>>
>> Is this a known problem?  Will these missing grids cause me any
>> problems in the future?
>>
>> Tnx & 73,
>> Bill  AA4M
>>
>> ___
>> 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
>
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Missing grid square info

[Bill Pence]

Correct. I had not realized this. As I looked at his qrz.com page he was
talking about living deed restricted and using remote radios
Dang.

And yes, some others might be in accurate as well.

On Sun, Dec 2, 2018, 1:28 PM Chuck Furman  I get it now. You meant he was operating remote, as in “away from his home
> station” (actual radio in a different grid). That was exactly my point...
> you can’t rely on the qrz.com information to be correct. Sometimes I try
> to text them with JTALERT to ask for their grid. But if they are portable,
> they may not have an Internet connection.
>
> On Sun, Dec 2, 2018 at 12:17 Bill Pence  wrote:
>
>> Because he answered my CQ, so while  I can look up his home grid, that
>> was not necessarily his transmitter location. And since he answered my CQ,
>> his grid was not exchanged
>> The impact of him operating remote is that I am unable to add from
>> qrz.com
>>
>>
>>
>> On Sun, Dec 2, 2018, 12:44 PM Chuck Furman >
>>> Bill,
>>>
>>> I’m confused. Why does remote operating affect the grid? I operate
>>> remotely all the time. I operate from my kitchen, my living room, patio,
>>> etc. I’ve also operated from China and Dubai. But in all cases, the station
>>> is in my house in Plano, Texas... in grid EM13oc. The grid square never
>>> changes. Why does it matter where the operator is located? The only thing
>>> that is important is the location of the radio.
>>>
>>> On a slightly different topic... I’ve noticed that some people don’t
>>> keep QRZ.com updated. The grid they give you during the contact doesn’t
>>> match what’s on QRZ. So filling in missing grids can be risky.
>>>
>>> Chuck
>>> KG6PH
>>> Plano, Texas
>>>
>>>
>>> On Sun, Dec 2, 2018 at 10:45 AM Bill Pence  wrote:
>>>
 In the round up, grids are only present in the CQ message.  So if
 someone ANSWERS your CQ, you do not get their grid...

 I plan to look these up and add then the the log

 But, at least 1 Q was with someone using a remote station via internet,
 so his grid will remain unknown...

 On Sun, Dec 2, 2018, 11:12 AM Bill Mullin >>>
> I'm an FT8 newbie - made my first QSO with this mode less than a week
> ago.  The below problem may have been discussed before and I apologize if 
> I
> missed it.  Anyway, I notice that both my LOG and ADI files are randomly
> missing grid squares.  Here's my last 6 QSO's, all made today:
>
>
> 2018-12-02,13:53:45,2018-12-02,13:54:45,DS4NPL,PM35,7.074300,FT8,+01,-15,,,
>
> 2018-12-02,14:01:45,2018-12-02,14:03:15,JG1ULT,PM95,7.075050,FT8,-10,-12,,,
> 2018-12-02,14:11:45,2018-12-02,14:12:45,KQ6K,,3.575100,FT8,-03,-03,,,
> 2018-12-02,14:32:15,2018-12-02,14:33:15,JA2ATE,,3.573600,FT8,+02,+02,,,
> 2018-12-02,14:49:15,2018-12-02,14:50:15,HR1LW,,14.075094,FT8,-10,-17,,,
>
> 2018-12-02,14:51:00,2018-12-02,14:52:00,PJ2DD,FK52,14.075717,FT8,-08,-04,,,
>
> 3 of the 6 grid square information is missing, in spite of the fact
> that it was definitely sent to me.  This group was with 1.9.1.  I also had
> 16 QSOs in the Roundup with 2.0.0 RC5 . . . 2 of the QSOs do not have grid
> information in the LOG or ADI file.
>
> Is this a known problem?  Will these missing grids cause me any
> problems in the future?
>
> Tnx & 73,
> Bill  AA4M
>
> ___
> 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

[wsjt-devel] Running 1.9 and 2.0 Simultaneously

[Frank Kirschner]

I'd like to run both versions of WSJT-X simultaneously, linked to two
different receiver slices. When I try to run the second program, it says it
needs a different radio name. I don't see anywhere to enter a radio name. I
would have thought it would be under Settings, Radio, but there is only
Rig, which is a drop-down, and has to be HRD.

Is there a way to run both versions simultaneously? Any help would be
appreciated.

Flex 6600/Maestro
Win 7 64
HRD latest version

Thanks.

73,
Frank
KF6E
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Missing grid square info

[Chuck Furman]

You can quickly and easily edit your “biography” on  qrz.com. Many people
do this when they operate from different locations. Just put a comment
there showing the dates you will be operating portable, and list the
different grids you will be in. Each time you travel, just add the dates
and grids.



On Sun, Dec 2, 2018 at 12:01 OG55W  wrote:

> FT never gives my grid in my CQ
> And I am operating in Finland from several grids, like KP20, KP13, KP30
> etc.
> in QRZ.com there is a place only for one grid.
>
> In LoTW the grid is OK.
>
> 73 Keijo OG55W
>
> *From:* Chuck Furman
> *Sent:* Sunday, December 2, 2018 7:41 PM
> *To:* WSJT software development
> *Subject:* Re: [wsjt-devel] Missing grid square info
>
> Bill,
>
> I’m confused. Why does remote operating affect the grid? I operate
> remotely all the time. I operate from my kitchen, my living room, patio,
> etc. I’ve also operated from China and Dubai. But in all cases, the station
> is in my house in Plano, Texas... in grid EM13oc. The grid square never
> changes. Why does it matter where the operator is located? The only thing
> that is important is the location of the radio.
>
> On a slightly different topic... I’ve noticed that some people don’t keep
> QRZ.com updated. The grid they give you during the contact doesn’t match
> what’s on QRZ. So filling in missing grids can be risky.
>
> Chuck
> KG6PH
> Plano, Texas
>
>
> On Sun, Dec 2, 2018 at 10:45 AM Bill Pence  wrote:
>
>> In the round up, grids are only present in the CQ message.  So if someone
>> ANSWERS your CQ, you do not get their grid...
>>
>> I plan to look these up and add then the the log
>>
>> But, at least 1 Q was with someone using a remote station via internet,
>> so his grid will remain unknown...
>>
>> On Sun, Dec 2, 2018, 11:12 AM Bill Mullin >
>>> I'm an FT8 newbie - made my first QSO with this mode less than a week
>>> ago.  The below problem may have been discussed before and I apologize if I
>>> missed it.  Anyway, I notice that both my LOG and ADI files are randomly
>>> missing grid squares.  Here's my last 6 QSO's, all made today:
>>>
>>>
>>> 2018-12-02,13:53:45,2018-12-02,13:54:45,DS4NPL,PM35,7.074300,FT8,+01,-15,,,
>>>
>>> 2018-12-02,14:01:45,2018-12-02,14:03:15,JG1ULT,PM95,7.075050,FT8,-10,-12,,,
>>> 2018-12-02,14:11:45,2018-12-02,14:12:45,KQ6K,,3.575100,FT8,-03,-03,,,
>>> 2018-12-02,14:32:15,2018-12-02,14:33:15,JA2ATE,,3.573600,FT8,+02,+02,,,
>>> 2018-12-02,14:49:15,2018-12-02,14:50:15,HR1LW,,14.075094,FT8,-10,-17,,,
>>>
>>> 2018-12-02,14:51:00,2018-12-02,14:52:00,PJ2DD,FK52,14.075717,FT8,-08,-04,,,
>>>
>>> 3 of the 6 grid square information is missing, in spite of the fact that
>>> it was definitely sent to me.  This group was with 1.9.1.  I also had 16
>>> QSOs in the Roundup with 2.0.0 RC5 . . . 2 of the QSOs do not have grid
>>> information in the LOG or ADI file.
>>>
>>> Is this a known problem?  Will these missing grids cause me any problems
>>> in the future?
>>>
>>> Tnx & 73,
>>> Bill  AA4M
>>>
>>> ___
>>> 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] Missing grid square info

[Chuck Furman]

I get it now. You meant he was operating remote, as in “away from his home
station” (actual radio in a different grid). That was exactly my point...
you can’t rely on the qrz.com information to be correct. Sometimes I try to
text them with JTALERT to ask for their grid. But if they are portable,
they may not have an Internet connection.

On Sun, Dec 2, 2018 at 12:17 Bill Pence  wrote:

> Because he answered my CQ, so while  I can look up his home grid, that was
> not necessarily his transmitter location. And since he answered my CQ, his
> grid was not exchanged
> The impact of him operating remote is that I am unable to add from
> qrz.com
>
>
>
> On Sun, Dec 2, 2018, 12:44 PM Chuck Furman 
>> Bill,
>>
>> I’m confused. Why does remote operating affect the grid? I operate
>> remotely all the time. I operate from my kitchen, my living room, patio,
>> etc. I’ve also operated from China and Dubai. But in all cases, the station
>> is in my house in Plano, Texas... in grid EM13oc. The grid square never
>> changes. Why does it matter where the operator is located? The only thing
>> that is important is the location of the radio.
>>
>> On a slightly different topic... I’ve noticed that some people don’t keep
>> QRZ.com updated. The grid they give you during the contact doesn’t match
>> what’s on QRZ. So filling in missing grids can be risky.
>>
>> Chuck
>> KG6PH
>> Plano, Texas
>>
>>
>> On Sun, Dec 2, 2018 at 10:45 AM Bill Pence  wrote:
>>
>>> In the round up, grids are only present in the CQ message.  So if
>>> someone ANSWERS your CQ, you do not get their grid...
>>>
>>> I plan to look these up and add then the the log
>>>
>>> But, at least 1 Q was with someone using a remote station via internet,
>>> so his grid will remain unknown...
>>>
>>> On Sun, Dec 2, 2018, 11:12 AM Bill Mullin >>
 I'm an FT8 newbie - made my first QSO with this mode less than a week
 ago.  The below problem may have been discussed before and I apologize if I
 missed it.  Anyway, I notice that both my LOG and ADI files are randomly
 missing grid squares.  Here's my last 6 QSO's, all made today:


 2018-12-02,13:53:45,2018-12-02,13:54:45,DS4NPL,PM35,7.074300,FT8,+01,-15,,,

 2018-12-02,14:01:45,2018-12-02,14:03:15,JG1ULT,PM95,7.075050,FT8,-10,-12,,,
 2018-12-02,14:11:45,2018-12-02,14:12:45,KQ6K,,3.575100,FT8,-03,-03,,,
 2018-12-02,14:32:15,2018-12-02,14:33:15,JA2ATE,,3.573600,FT8,+02,+02,,,
 2018-12-02,14:49:15,2018-12-02,14:50:15,HR1LW,,14.075094,FT8,-10,-17,,,

 2018-12-02,14:51:00,2018-12-02,14:52:00,PJ2DD,FK52,14.075717,FT8,-08,-04,,,

 3 of the 6 grid square information is missing, in spite of the fact
 that it was definitely sent to me.  This group was with 1.9.1.  I also had
 16 QSOs in the Roundup with 2.0.0 RC5 . . . 2 of the QSOs do not have grid
 information in the LOG or ADI file.

 Is this a known problem?  Will these missing grids cause me any
 problems in the future?

 Tnx & 73,
 Bill  AA4M

 ___
 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] Contest Log Window- Autoscroll

[Bill Pence]

Ok. mine is about half the screen or so.



On Sun, Dec 2, 2018, 12:29 PM Steven Franke via wsjt-devel <
wsjt-devel@lists.sourceforge.net wrote:

> Try expanding the log window, vertically, so that it takes up at least 2/3
> of your screen. If I do that, I can always see the last line.
> Steve k9an
>
> On Dec 2, 2018, at 11:07 AM, Bill Pence  wrote:
>
> Same here. Last qso is just off the bottom on the contest log window. A
> new Q scolls to see the previous last, but then the newest is still out of
> view unless I scroll manually...
>
>
>
> On Sun, Dec 2, 2018, 12:00 PM Martin Davies G0HDB  wrote:
>
>> On 2 Dec 2018 at 12:16, Bill Somerville wrote:
>>
>> > On 02/12/2018 09:41, oe9...@ft8.at wrote:
>> > > Hello from Austria,
>> > >
>> > > RC5 737d2f, Windows 10 Pro, Version 1809 (Build 17763.134)
>> > >
>> > > looking at the Contest Log Windows - is there a "trick" to make it
>> scroll
>> > > down automatically
>> > > all the way to the LAST entry?
>> > >
>> > > Regardless of the window position/size it always shows the last but
>> one log
>> > > line.
>> > >
>> > > Thanks.
>> > >
>> > > 73, Frank
>> > > OE9KFV
>> >
>> > Hi Frank,
>> >
>> > this is the first report of this on MS Windows. There are issues with
>> > the Contest Log window not scrolling to show the last QSO on some Linux
>> > desktops.
>> >
>> > Is the Contest Log window trying to go to the last entry but stopping
>> > short by one row or is it not scrolling at all when you log a QSO?
>> >
>> > 73
>> > Bill
>> > G4WJS.
>>
>> Hi Bill (and all), I can confirm that on my system - 32-bit Win 7 Pro
>> running v2.0.0-rc5 737d2f
>> - the entries in the Contest Log window don't scroll up sufficiently to
>> ensure that a
>> newly-logged entry is fully displayed on the bottom line of the window.
>>
>> When a new QSO is logged the information in the window moves slightly
>> upwards but not by
>> enough to fully display the new QSO.  This happens no matter what size
>> the window is.
>>
>> --
>> 73, Martin G0HDB
>>
>>
>> ---
>> This email has been checked for viruses by Avast antivirus software.
>> https://www.avast.com/antivirus
>>
>>
>>
>> ___
>> 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] Missing grid square info

[Bill Pence]

Because he answered my CQ, so while  I can look up his home grid, that was
not necessarily his transmitter location. And since he answered my CQ, his
grid was not exchanged
The impact of him operating remote is that I am unable to add from
qrz.com



On Sun, Dec 2, 2018, 12:44 PM Chuck Furman  Bill,
>
> I’m confused. Why does remote operating affect the grid? I operate
> remotely all the time. I operate from my kitchen, my living room, patio,
> etc. I’ve also operated from China and Dubai. But in all cases, the station
> is in my house in Plano, Texas... in grid EM13oc. The grid square never
> changes. Why does it matter where the operator is located? The only thing
> that is important is the location of the radio.
>
> On a slightly different topic... I’ve noticed that some people don’t keep
> QRZ.com updated. The grid they give you during the contact doesn’t match
> what’s on QRZ. So filling in missing grids can be risky.
>
> Chuck
> KG6PH
> Plano, Texas
>
>
> On Sun, Dec 2, 2018 at 10:45 AM Bill Pence  wrote:
>
>> In the round up, grids are only present in the CQ message.  So if someone
>> ANSWERS your CQ, you do not get their grid...
>>
>> I plan to look these up and add then the the log
>>
>> But, at least 1 Q was with someone using a remote station via internet,
>> so his grid will remain unknown...
>>
>> On Sun, Dec 2, 2018, 11:12 AM Bill Mullin >
>>> I'm an FT8 newbie - made my first QSO with this mode less than a week
>>> ago.  The below problem may have been discussed before and I apologize if I
>>> missed it.  Anyway, I notice that both my LOG and ADI files are randomly
>>> missing grid squares.  Here's my last 6 QSO's, all made today:
>>>
>>>
>>> 2018-12-02,13:53:45,2018-12-02,13:54:45,DS4NPL,PM35,7.074300,FT8,+01,-15,,,
>>>
>>> 2018-12-02,14:01:45,2018-12-02,14:03:15,JG1ULT,PM95,7.075050,FT8,-10,-12,,,
>>> 2018-12-02,14:11:45,2018-12-02,14:12:45,KQ6K,,3.575100,FT8,-03,-03,,,
>>> 2018-12-02,14:32:15,2018-12-02,14:33:15,JA2ATE,,3.573600,FT8,+02,+02,,,
>>> 2018-12-02,14:49:15,2018-12-02,14:50:15,HR1LW,,14.075094,FT8,-10,-17,,,
>>>
>>> 2018-12-02,14:51:00,2018-12-02,14:52:00,PJ2DD,FK52,14.075717,FT8,-08,-04,,,
>>>
>>> 3 of the 6 grid square information is missing, in spite of the fact that
>>> it was definitely sent to me.  This group was with 1.9.1.  I also had 16
>>> QSOs in the Roundup with 2.0.0 RC5 . . . 2 of the QSOs do not have grid
>>> information in the LOG or ADI file.
>>>
>>> Is this a known problem?  Will these missing grids cause me any problems
>>> in the future?
>>>
>>> Tnx & 73,
>>> Bill  AA4M
>>>
>>> ___
>>> 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] Missing grid square info

[OG55W]

FT never gives my grid in my CQ
And I am operating in Finland from several grids, like KP20, KP13, KP30 etc.
in QRZ.com there is a place only for one grid.

In LoTW the grid is OK.

73 Keijo OG55W

From: Chuck Furman 
Sent: Sunday, December 2, 2018 7:41 PM
To: WSJT software development 
Subject: Re: [wsjt-devel] Missing grid square info

Bill,

I’m confused. Why does remote operating affect the grid? I operate remotely all 
the time. I operate from my kitchen, my living room, patio, etc. I’ve also 
operated from China and Dubai. But in all cases, the station is in my house in 
Plano, Texas... in grid EM13oc. The grid square never changes. Why does it 
matter where the operator is located? The only thing that is important is the 
location of the radio. 

On a slightly different topic... I’ve noticed that some people don’t keep 
QRZ.com updated. The grid they give you during the contact doesn’t match what’s 
on QRZ. So filling in missing grids can be risky. 

Chuck 
KG6PH 
Plano, Texas 


On Sun, Dec 2, 2018 at 10:45 AM Bill Pence  wrote:

  In the round up, grids are only present in the CQ message.  So if someone 
ANSWERS your CQ, you do not get their grid... 

  I plan to look these up and add then the the log

  But, at least 1 Q was with someone using a remote station via internet, so 
his grid will remain unknown...

  On Sun, Dec 2, 2018, 11:12 AM Bill Mullin 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

[wsjt-devel] Tab 2 - never used

[WB5JJJ]

Tab 2 is something I never have used (other than early on testing) and find
it useless in my operation.

With Tab 1, I can see EXACTLY what is about to be transmitted and I have
full control over what is next or what I want to send NOW.  No surprises or
guesswork required, especially with the full TX text always shown right
there.

I'm sure there are users that live and die by Tab 2 because of it's
simplicity and in that light, maybe it should stay for those folks.  But
for me, I find it of no value in normal operation of WSTJX.

-- 
George Cotton, WB5JJJ
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Missing grid square info

[Chuck Furman]

Bill,

I’m confused. Why does remote operating affect the grid? I operate remotely
all the time. I operate from my kitchen, my living room, patio, etc. I’ve
also operated from China and Dubai. But in all cases, the station is in my
house in Plano, Texas... in grid EM13oc. The grid square never changes. Why
does it matter where the operator is located? The only thing that is
important is the location of the radio.

On a slightly different topic... I’ve noticed that some people don’t keep
QRZ.com updated. The grid they give you during the contact doesn’t match
what’s on QRZ. So filling in missing grids can be risky.

Chuck
KG6PH
Plano, Texas


On Sun, Dec 2, 2018 at 10:45 AM Bill Pence  wrote:

> In the round up, grids are only present in the CQ message.  So if someone
> ANSWERS your CQ, you do not get their grid...
>
> I plan to look these up and add then the the log
>
> But, at least 1 Q was with someone using a remote station via internet, so
> his grid will remain unknown...
>
> On Sun, Dec 2, 2018, 11:12 AM Bill Mullin 
>> I'm an FT8 newbie - made my first QSO with this mode less than a week
>> ago.  The below problem may have been discussed before and I apologize if I
>> missed it.  Anyway, I notice that both my LOG and ADI files are randomly
>> missing grid squares.  Here's my last 6 QSO's, all made today:
>>
>>
>> 2018-12-02,13:53:45,2018-12-02,13:54:45,DS4NPL,PM35,7.074300,FT8,+01,-15,,,
>>
>> 2018-12-02,14:01:45,2018-12-02,14:03:15,JG1ULT,PM95,7.075050,FT8,-10,-12,,,
>> 2018-12-02,14:11:45,2018-12-02,14:12:45,KQ6K,,3.575100,FT8,-03,-03,,,
>> 2018-12-02,14:32:15,2018-12-02,14:33:15,JA2ATE,,3.573600,FT8,+02,+02,,,
>> 2018-12-02,14:49:15,2018-12-02,14:50:15,HR1LW,,14.075094,FT8,-10,-17,,,
>>
>> 2018-12-02,14:51:00,2018-12-02,14:52:00,PJ2DD,FK52,14.075717,FT8,-08,-04,,,
>>
>> 3 of the 6 grid square information is missing, in spite of the fact that
>> it was definitely sent to me.  This group was with 1.9.1.  I also had 16
>> QSOs in the Roundup with 2.0.0 RC5 . . . 2 of the QSOs do not have grid
>> information in the LOG or ADI file.
>>
>> Is this a known problem?  Will these missing grids cause me any problems
>> in the future?
>>
>> Tnx & 73,
>> Bill  AA4M
>>
>> ___
>> 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] Contest Log Window- Autoscroll

[Don Hill AA5AU]

Same here. Can't see last entry in the log.

Bob, VE1RSM, has also reported the issue to me.

Don AA5AU

-Original Message-
From: Martin Davies G0HDB [mailto:marting0...@gmail.com] 
Sent: Sunday, December 2, 2018 10:57 AM
To: WSJT software development; Bill Somerville
Subject: Re: [wsjt-devel] Contest Log Window- Autoscroll

On 2 Dec 2018 at 12:16, Bill Somerville wrote:

> On 02/12/2018 09:41, oe9...@ft8.at wrote:
> > Hello from Austria,
> >
> > RC5 737d2f, Windows 10 Pro, Version 1809 (Build 17763.134)
> >
> > looking at the Contest Log Windows - is there a "trick" to make it
scroll
> > down automatically
> > all the way to the LAST entry?
> >
> > Regardless of the window position/size it always shows the last but one
log
> > line.
> >
> > Thanks.
> >
> > 73, Frank
> > OE9KFV
> 
> Hi Frank,
> 
> this is the first report of this on MS Windows. There are issues with 
> the Contest Log window not scrolling to show the last QSO on some Linux 
> desktops.
> 
> Is the Contest Log window trying to go to the last entry but stopping 
> short by one row or is it not scrolling at all when you log a QSO?
> 
> 73
> Bill
> G4WJS.

Hi Bill (and all), I can confirm that on my system - 32-bit Win 7 Pro
running v2.0.0-rc5 737d2f 
- the entries in the Contest Log window don't scroll up sufficiently to
ensure that a 
newly-logged entry is fully displayed on the bottom line of the window.  

When a new QSO is logged the information in the window moves slightly
upwards but not by 
enough to fully display the new QSO.  This happens no matter what size the
window is.

--
73, Martin G0HDB


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus



___
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] Contest Log Window- Autoscroll

[Steven Franke via wsjt-devel]

Try expanding the log window, vertically, so that it takes up at least 2/3 of 
your screen. If I do that, I can always see the last line.
Steve k9an

> On Dec 2, 2018, at 11:07 AM, Bill Pence  wrote:
> 
> Same here. Last qso is just off the bottom on the contest log window. A new Q 
> scolls to see the previous last, but then the newest is still out of view 
> unless I scroll manually...
> 
> 
> 
> On Sun, Dec 2, 2018, 12:00 PM Martin Davies G0HDB   wrote:
> On 2 Dec 2018 at 12:16, Bill Somerville wrote:
> 
> > On 02/12/2018 09:41, oe9...@ft8.at  wrote:
> > > Hello from Austria,
> > >
> > > RC5 737d2f, Windows 10 Pro, Version 1809 (Build 17763.134)
> > >
> > > looking at the Contest Log Windows - is there a "trick" to make it scroll
> > > down automatically
> > > all the way to the LAST entry?
> > >
> > > Regardless of the window position/size it always shows the last but one 
> > > log
> > > line.
> > >
> > > Thanks.
> > >
> > > 73, Frank
> > > OE9KFV
> > 
> > Hi Frank,
> > 
> > this is the first report of this on MS Windows. There are issues with 
> > the Contest Log window not scrolling to show the last QSO on some Linux 
> > desktops.
> > 
> > Is the Contest Log window trying to go to the last entry but stopping 
> > short by one row or is it not scrolling at all when you log a QSO?
> > 
> > 73
> > Bill
> > G4WJS.
> 
> Hi Bill (and all), I can confirm that on my system - 32-bit Win 7 Pro running 
> v2.0.0-rc5 737d2f 
> - the entries in the Contest Log window don't scroll up sufficiently to 
> ensure that a 
> newly-logged entry is fully displayed on the bottom line of the window.  
> 
> When a new QSO is logged the information in the window moves slightly upwards 
> but not by 
> enough to fully display the new QSO.  This happens no matter what size the 
> window is.
> 
> --
> 73, Martin G0HDB
> 
> 
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus 
> 
> 
> 
> ___
> 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] WSJT-X: Summary of issues with v2.0.0 RC5 in RTTY Roundup mode

[Al Pawlowski]

My vote is for keeping the tab 2 messages window/layout. I find tab 2 faster 
for selecting the appropriate message and the “free text” message easier to use 
- maybe it is the bigger/bolder select buttons, vs the undifferentiated (for 
tx, rx), smaller selection targets of tab 1.

Al Pawlowski, K6AVP
Los Osos, CA USA


Date: Sun, 2 Dec 2018 13:05:16 +
> From: Bill Somerville mailto:g4...@classdesign.com>>
> To: WSJT software development  >
> Subject: [wsjt-devel] WSJT-X: Summary of issues with v2.0.0 RC5 in
>   RTTY Roundup mode
> 
> Hi All,
> 
> thanks for the feedback during the contest activity and sorry for those 
> that have had issues that caused serious problems. Here is a summary of 
> the main issues with workarounds where available:

> …..Please respond if you feel that 
> Tab 2 messages are essential to your operating enjoyment and that Tab 1 
> is not suitable for you.

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

Re: [wsjt-devel] RC5 - Possible Bug

[Edfel Rivera]

Bill:

I am testing RC5 in 6m 50.313 and noticed that Windows disrupting is NOT
happening on the 6m band. I activated RTTY Special Operation to have same
configuration when I detected the issue, Windows operation remains normal
(6m band).  Changed to 20m 14.130 to test if problem is still present and
yes it remains.  Yes, strange it NOT happening in the 6m band 50.313.  WIll
test other bands.  Just adding this info.  Seems like isolated issue only
happening here.

73'

Edfel
KP4AJ

On Sat, Dec 1, 2018 at 3:11 PM Bill Somerville 
wrote:

> On 01/12/2018 19:44, Edfel Rivera wrote:
> > One thing I have noticed when PPT is active open windows get input and
> > not respond to OS as should.  OS Windows 10.  Not sure if others have
> > observed this behavior.
>
> Hi Edfel,
>
> that sounds like RFI disrupting your mouse of keyboard connections. A
> test at low power, into a dummy load, a different band, or aerial should
> confirm.
>
> 73
> Bill
> G4WJS.
>
>
>
> ___
> 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] Contest Log Window- Autoscroll

[Bill Pence]

Same here. Last qso is just off the bottom on the contest log window. A new
Q scolls to see the previous last, but then the newest is still out of view
unless I scroll manually...



On Sun, Dec 2, 2018, 12:00 PM Martin Davies G0HDB  On 2 Dec 2018 at 12:16, Bill Somerville wrote:
>
> > On 02/12/2018 09:41, oe9...@ft8.at wrote:
> > > Hello from Austria,
> > >
> > > RC5 737d2f, Windows 10 Pro, Version 1809 (Build 17763.134)
> > >
> > > looking at the Contest Log Windows - is there a "trick" to make it
> scroll
> > > down automatically
> > > all the way to the LAST entry?
> > >
> > > Regardless of the window position/size it always shows the last but
> one log
> > > line.
> > >
> > > Thanks.
> > >
> > > 73, Frank
> > > OE9KFV
> >
> > Hi Frank,
> >
> > this is the first report of this on MS Windows. There are issues with
> > the Contest Log window not scrolling to show the last QSO on some Linux
> > desktops.
> >
> > Is the Contest Log window trying to go to the last entry but stopping
> > short by one row or is it not scrolling at all when you log a QSO?
> >
> > 73
> > Bill
> > G4WJS.
>
> Hi Bill (and all), I can confirm that on my system - 32-bit Win 7 Pro
> running v2.0.0-rc5 737d2f
> - the entries in the Contest Log window don't scroll up sufficiently to
> ensure that a
> newly-logged entry is fully displayed on the bottom line of the window.
>
> When a new QSO is logged the information in the window moves slightly
> upwards but not by
> enough to fully display the new QSO.  This happens no matter what size the
> window is.
>
> --
> 73, Martin G0HDB
>
>
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
>
>
>
> ___
> 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] New stations on RU today

[Scotty W7PSK]

Come up to 15m,  20 is too crowded on 14.130,
It seems like its open but not getting much response on 21.130

-- Original Message --
From: "WB5JJJ" 
To: wsjt-devel@lists.sourceforge.net
Sent: 12/1/2018 11:26:14 AM
Subject: [wsjt-devel] New stations on RU today

A multitude of ANTO's (stateside) on 14.130 for the Round Up.  Looks 
like a lot of guys have made the jump to RC5 at least for this test 
contest.  WF looks better than 14.074 since everybody is v2 here today.


--
George Cotton, WB5JJJ
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] Two RRR no answer back to TXT2

[Edfel Rivera]

Hi All:

Please check attachments. This was using TAB1.  First situation I called
PA0TCA (sequence1)  and got report from Otto.  My station sent RRR twice.
Because propagation, station busy, after not getting a response, WSJTX goes
to TXT2 sending first report again.  I manually changed the message to RRR
but QSO was lost. IMO, this could be a problem with very busy stations when
contesting.  Experience tells me that in some situations difficult QSO
could take 4-5 times to send 'RRR' and yes finally QSO could be achieved.
How many 'RRR' before moving again to sending report tahts the question.
Maybe this have been addressed before.

Example #2, this happend with Joe, K1JT, but he send 73 completing QSO
(sequence2.jpg).

Thanks.

Edfel
KP4AJ
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Contest Log Window- Autoscroll

[Martin Davies G0HDB]

On 2 Dec 2018 at 12:16, Bill Somerville wrote:

> On 02/12/2018 09:41, oe9...@ft8.at wrote:
> > Hello from Austria,
> >
> > RC5 737d2f, Windows 10 Pro, Version 1809 (Build 17763.134)
> >
> > looking at the Contest Log Windows - is there a "trick" to make it scroll
> > down automatically
> > all the way to the LAST entry?
> >
> > Regardless of the window position/size it always shows the last but one log
> > line.
> >
> > Thanks.
> >
> > 73, Frank
> > OE9KFV
> 
> Hi Frank,
> 
> this is the first report of this on MS Windows. There are issues with 
> the Contest Log window not scrolling to show the last QSO on some Linux 
> desktops.
> 
> Is the Contest Log window trying to go to the last entry but stopping 
> short by one row or is it not scrolling at all when you log a QSO?
> 
> 73
> Bill
> G4WJS.

Hi Bill (and all), I can confirm that on my system - 32-bit Win 7 Pro running 
v2.0.0-rc5 737d2f 
- the entries in the Contest Log window don't scroll up sufficiently to ensure 
that a 
newly-logged entry is fully displayed on the bottom line of the window.  

When a new QSO is logged the information in the window moves slightly upwards 
but not by 
enough to fully display the new QSO.  This happens no matter what size the 
window is.

--
73, Martin G0HDB


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus



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

[wsjt-devel] 'Call 1st' remaining active when un-ticked

[Martin Davies G0HDB]

I'm using v2.0.0-rc5 737d2f on a PC running 32-bit Win 7 Pro (with all SPs and 
updates).

I've been having a dabble in the FT8 Roundup - what great fun it is! - and came 
across an 
oddity this morning...

In normal FT8 operation I don't use the 'Call 1st' option and always leave it 
unticked but I 
tried it this morning during the Roundup.  Sure enough and exactly as expected 
the s/ware 
intiated a QSO with the first decode and all was well.  I then unticked 'Call 
1st' and expected 
to be able to return to manually selecting which of the decoded signals to 
start a QSO with, 
but I found that the s/ware was still "doing its own thing" and responding as 
if 'Call 1st' was 
still enabled.  Despite me ticking and then unticking 'Call 1st' several times 
the function 
remained active no matter what state the tick-box was in.

To restore things to normal I had to restart the app; since doing that I 
haven't tried 
re-enabling 'Call 1st' to see if it's still being 'sticky'.

Has anyone else noticed this behaviour?

--
73, Martin G0HDB


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus



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

Re: [wsjt-devel] Problem with Contest Data and N1MM+ feed?

[Bill Somerville]

On 02/12/2018 16:25, David Kaplan via wsjt-devel wrote:

Bill,

According to Don Agro, MLDX author, he uses the N1MMLogger+ UDP feed.

You said "only the direct UDP messages sent to N1MM Logger+ and the WSJT-X ADIF 
log have the contest exchange information.”

If MLDX uses the N1MM feed, shouldn’t it receive the context exchange info? Or 
am I missing something?

David, WA1OUI


Hi David,

if that is so then the ADIF field names are not being correctly 
interpreted. The relevant fields for the ARRL RTTY RU contest are STATE 
which has the received state, VE province code or DC when a US or VE 
station is logged or SRX which contains the received serial number when 
a QSO with a DX category station is logged. For operators in the DX 
category the field STX with the sent serial number will be included. The 
operators own state, VE province, or DC must be set up in the 
destination logger as if it were being used directly to log the contest.


I am not aware of the author(s) of MLDX asking about this, if they had I 
would have strongly recommended that they implement a WSJT-X UDP 
protocol server interface as it contains all this and much more 
information including every decode as it happens.


73
Bill
G4WJS.



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

Re: [wsjt-devel] Problem with Contest Data and N1MM+ feed?

[David Kaplan via wsjt-devel]

Bill,

According to Don Agro, MLDX author, he uses the N1MMLogger+ UDP feed. 

You said "only the direct UDP messages sent to N1MM Logger+ and the WSJT-X ADIF 
log have the contest exchange information.”

If MLDX uses the N1MM feed, shouldn’t it receive the context exchange info? Or 
am I missing something?

David, WA1OUI




On Dec 2, 2018, at 7:12 AM, Bill Somerville  wrote:

On 02/12/2018 04:22, David Kaplan via wsjt-devel wrote:
> I made a few QSOs with RC5 feeding MacLoggerDX the N1MM+ data. The main QSO 
> information came through fine, but there was no exchange data for my log..
> 
> An exchange of 539 NJ from K1JT is apparently built from 539 and 
> NJ,
> and 549 0044 for CE1OEB from 549 and 0044.
> 
> It doesn’t seem as if you send a STX_STRING or SRX_STRING in the N1MM+ data 
> which MacLoggerDX would need to populate my log..
> 
> I can send the full ADIF if you want
> 
> Am I interpreting this correctly?
> 
> Thanks.
> 
> David, WA1OUI

Hi David,

only the direct UDP messages sent to N1MM Logger+ and the WSJT-X ADIF log have 
the contest exchange information. No guarantees were offered for other routes 
like the WSJT-X UDP protocol that programs like JTAlert use. We hope to have 
the extra contest exchange information added to the WSJT-X UDP protocol for the 
WSJT-X v2.0.0 GA release but to make use of it the cooperating applications 
will also have to extract the new fields and allocate them to their logs and 
data feeds.

73
Bill
G4WJS.



___
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] Tab 2

[Jim Shorney]

I have used tab 2 almost exclusively with JT modes. I would hate to see it go.

73
-Jim
NU0C

On Sun, 2 Dec 2018 08:49:03 -0600
Gene H  wrote:

> To List,
> 
> Please keep TAB 2 so it can be an option. I use it all the time for FT8 
> contacts since inception.
> 
> 73 Gene K5PA
> 
> 
> On 12/2/2018 8:20 AM, Hasan al-Basri wrote:
> > I prefer TAB 1, do not use TAB 2, ever.
> >
> > Hasan
> >
> >
> > On Sun, Dec 2, 2018 at 8:06 AM WB5JJJ  > > wrote:
> >
> > Bill:
> >
> > As you requested, I have never used Tab 2.  One vote to remove
> > it.  Tab 1 has all the information as to what is going on during a
> > contact with no thinking required.
> >
> > I have NOT had the UTC/Local time stamp issue.  My Contest Log has
> > the correct 24 hour UTC for every entry and I'm set to Central
> > Time in my automatic MS time keeping offset.
> >
> > Enjoyed reading your all-inclusive review of problems/solutions
> > and fixes in one place, great work putting that together.  Thanks.
> >
> > Windows 10 Pro 64 bit here and all aspects of WSJTx-RC5 have
> > worked perfectly. I for one, have not had a single problem with
> > the Contest Logger, so never had a reason to "edit" it for any
> > reason.  Everything is logging to HRD LB directly without a glitch
> > - and I DO check every entry while waiting on next contact.
> >
> > Even though most contacts do not include a Grid Square along with
> > all other personal information, HRD LB does get the 6 digit GS
> > with the query of QRZ upon adding the entry. Of course this field
> > is "0" characters in the WSJTX log file.  This could cause a
> > problem for some that use the adi file as the import to their
> > logger.  The  size may not allow the GS to be edited
> > in their logger to a 4 or 6 character count since space was not
> > allocated by the adi file import.
> >
> > Bottom Line - the program requires absolutely no interaction from
> > me for proper logging.  I do edit the HRD LB entry when some
> > European stations have their Postal Code in front of  their QTH
> > information, so I do delete that. (Future note to coders to fix
> > this if possible, could be a problem as there are several
> > variations being seen).
> >
> > 73's
> > -- 
> > George Cotton, WB5JJJ
>

--

"Good men don’t need rules. Today is not the day to find out why I have so 
many."  - Doctor Who


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

[wsjt-devel] Missing grid square info

[Bill Mullin]

I'm an FT8 newbie - made my first QSO with this mode less than a week 
ago.  The below problem may have been discussed before and I apologize 
if I missed it.  Anyway, I notice that both my LOG and ADI files are 
randomly missing grid squares. Here's my last 6 QSO's, all made today:


2018-12-02,13:53:45,2018-12-02,13:54:45,DS4NPL,PM35,7.074300,FT8,+01,-15,,,
2018-12-02,14:01:45,2018-12-02,14:03:15,JG1ULT,PM95,7.075050,FT8,-10,-12,,,
2018-12-02,14:11:45,2018-12-02,14:12:45,KQ6K,,3.575100,FT8,-03,-03,,,
2018-12-02,14:32:15,2018-12-02,14:33:15,JA2ATE,,3.573600,FT8,+02,+02,,,
2018-12-02,14:49:15,2018-12-02,14:50:15,HR1LW,,14.075094,FT8,-10,-17,,,
2018-12-02,14:51:00,2018-12-02,14:52:00,PJ2DD,FK52,14.075717,FT8,-08,-04,,,

3 of the 6 grid square information is missing, in spite of the fact that 
it was definitely sent to me.  This group was with 1.9.1.  I also had 16 
QSOs in the Roundup with 2.0.0 RC5 . . . 2 of the QSOs do not have grid 
information in the LOG or ADI file.


Is this a known problem?  Will these missing grids cause me any problems 
in the future?


Tnx & 73,
Bill  AA4M

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

Re: [wsjt-devel] Tab 2

[Gary Rogers]

I also almost always use Tab 2…Please keep it…Thanks Gary KO3f

> On Dec 2, 2018, at 10:37 AM, Edfel Rivera  wrote:
> 
> Hi All:
> 
> Tab 2 is my default operating since using WSJTX (1.6).  Vote to keep it as 
> option or better find a fix.  Also, IMO Tab 2 make the program more intuitive 
> and UI more appealing.  Particularly when calling CQ.  It is matter of 
> preferences, at least make option to use and alert (through message) users 
> limitation related with QSO logging, if fix is not possible.
> 
> Thanks Development Team!
> 
> 73'
> 
> Edfel
> KP4AJ
> 
> On Sun, Dec 2, 2018 at 9:53 AM Gene H  > wrote:
> To List,
> 
> Please keep TAB 2 so it can be an option. I use it all the time for FT8 
> contacts since inception.
> 
> 73 Gene K5PA
> 
> 
> 
> On 12/2/2018 8:20 AM, Hasan al-Basri wrote:
>> I prefer TAB 1, do not use TAB 2, ever.
>> 
>> Hasan
>> 
>> 
>> On Sun, Dec 2, 2018 at 8:06 AM WB5JJJ > > wrote:
>> Bill:
>> 
>> As you requested, I have never used Tab 2.  One vote to remove it.  Tab 1 
>> has all the information as to what is going on during a contact with no 
>> thinking required.  
>> 
>> I have NOT had the UTC/Local time stamp issue.  My Contest Log has the 
>> correct 24 hour UTC for every entry and I'm set to Central Time in my 
>> automatic MS time keeping offset.  
>> 
>> Enjoyed reading your all-inclusive review of problems/solutions and fixes in 
>> one place, great work putting that together.  Thanks.  
>> 
>> Windows 10 Pro 64 bit here and all aspects of WSJTx-RC5 have worked 
>> perfectly. I for one, have not had a single problem with the Contest Logger, 
>> so never had a reason to "edit" it for any reason.  Everything is logging to 
>> HRD LB directly without a glitch - and I DO check every entry while waiting 
>> on next contact. 
>> 
>> Even though most contacts do not include a Grid Square along with all other 
>> personal information, HRD LB does get the 6 digit GS with the query of QRZ 
>> upon adding the entry.  Of course this field is "0" characters in the WSJTX 
>> log file.  This could cause a problem for some that use the adi file as the 
>> import to their logger.  The  size may not allow the GS to be 
>> edited in their logger to a 4 or 6 character count since space was not 
>> allocated by the adi file import.  
>> 
>> Bottom Line - the program requires absolutely no interaction from me for 
>> proper logging.  I do edit the HRD LB entry when some European stations have 
>> their Postal Code in front of  their QTH information, so I do delete that.  
>> (Future note to coders to fix this if possible, could be a problem as there 
>> are several variations being seen).
>> 
>> 73's
>> -- 
>> George Cotton, WB5JJJ
>> 
>> ___
>> 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 
>> 
> -- 
> Gene Hinkle
> 2026 Spyglass Hill, Leander, TX 78641
> e-mail to Gene:  ghin...@gmail.com 
> cell phone or text messaging:  (512) 413-9251
> --
> 
> 
> 
> 
> ___
> 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] Tab 2

[Edfel Rivera]

Hi All:

Tab 2 is my default operating since using WSJTX (1.6).  Vote to keep it as
option or better find a fix.  Also, IMO Tab 2 make the program more
intuitive and UI more appealing.  Particularly when calling CQ.  It is
matter of preferences, at least make option to use and alert (through
message) users limitation related with QSO logging, if fix is not possible.

Thanks Development Team!

73'

Edfel
KP4AJ

On Sun, Dec 2, 2018 at 9:53 AM Gene H  wrote:

> To List,
>
> Please keep TAB 2 so it can be an option. I use it all the time for FT8
> contacts since inception.
>
> 73 Gene K5PA
>
>
> On 12/2/2018 8:20 AM, Hasan al-Basri wrote:
>
> I prefer TAB 1, do not use TAB 2, ever.
>
> Hasan
>
>
> On Sun, Dec 2, 2018 at 8:06 AM WB5JJJ  wrote:
>
>> Bill:
>>
>> As you requested, I have never used Tab 2.  One vote to remove it.  Tab 1
>> has all the information as to what is going on during a contact with no
>> thinking required.
>>
>> I have NOT had the UTC/Local time stamp issue.  My Contest Log has the
>> correct 24 hour UTC for every entry and I'm set to Central Time in my
>> automatic MS time keeping offset.
>>
>> Enjoyed reading your all-inclusive review of problems/solutions and fixes
>> in one place, great work putting that together.  Thanks.
>>
>> Windows 10 Pro 64 bit here and all aspects of WSJTx-RC5 have worked
>> perfectly. I for one, have not had a single problem with the Contest
>> Logger, so never had a reason to "edit" it for any reason.  Everything is
>> logging to HRD LB directly without a glitch - and I DO check every entry
>> while waiting on next contact.
>>
>> Even though most contacts do not include a Grid Square along with all
>> other personal information, HRD LB does get the 6 digit GS with the query
>> of QRZ upon adding the entry.  Of course this field is "0" characters in
>> the WSJTX log file.  This could cause a problem for some that use the adi
>> file as the import to their logger.  The  size may not allow
>> the GS to be edited in their logger to a 4 or 6 character count since space
>> was not allocated by the adi file import.
>>
>> Bottom Line - the program requires absolutely no interaction from me for
>> proper logging.  I do edit the HRD LB entry when some European stations
>> have their Postal Code in front of  their QTH information, so I do delete
>> that.  (Future note to coders to fix this if possible, could be a problem
>> as there are several variations being seen).
>>
>> 73's
>> --
>> George Cotton, WB5JJJ
>>
>> ___
>> wsjt-devel mailing list
>> wsjt-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>
>
>
> ___
> wsjt-devel mailing 
> listwsjt-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/wsjt-devel
>
> --
> Gene Hinkle
> 2026 Spyglass Hill, Leander, TX 78641
> e-mail to Gene:  ghin...@gmail.com
> cell phone or text messaging:  (512) 413-9251
> --
>
>
>
>
>
> ___
> 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] Tab 2

[Gene H]

To List,

Please keep TAB 2 so it can be an option. I use it all the time for FT8 
contacts since inception.


73 Gene K5PA


On 12/2/2018 8:20 AM, Hasan al-Basri wrote:

I prefer TAB 1, do not use TAB 2, ever.

Hasan


On Sun, Dec 2, 2018 at 8:06 AM WB5JJJ > wrote:


Bill:

As you requested, I have never used Tab 2.  One vote to remove
it.  Tab 1 has all the information as to what is going on during a
contact with no thinking required.

I have NOT had the UTC/Local time stamp issue.  My Contest Log has
the correct 24 hour UTC for every entry and I'm set to Central
Time in my automatic MS time keeping offset.

Enjoyed reading your all-inclusive review of problems/solutions
and fixes in one place, great work putting that together.  Thanks.

Windows 10 Pro 64 bit here and all aspects of WSJTx-RC5 have
worked perfectly. I for one, have not had a single problem with
the Contest Logger, so never had a reason to "edit" it for any
reason.  Everything is logging to HRD LB directly without a glitch
- and I DO check every entry while waiting on next contact.

Even though most contacts do not include a Grid Square along with
all other personal information, HRD LB does get the 6 digit GS
with the query of QRZ upon adding the entry. Of course this field
is "0" characters in the WSJTX log file.  This could cause a
problem for some that use the adi file as the import to their
logger.  The  size may not allow the GS to be edited
in their logger to a 4 or 6 character count since space was not
allocated by the adi file import.

Bottom Line - the program requires absolutely no interaction from
me for proper logging.  I do edit the HRD LB entry when some
European stations have their Postal Code in front of  their QTH
information, so I do delete that. (Future note to coders to fix
this if possible, could be a problem as there are several
variations being seen).

73's
-- 
George Cotton, WB5JJJ


___
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


--
Gene Hinkle
2026 Spyglass Hill, Leander, TX 78641
e-mail to Gene:  ghin...@gmail.com
cell phone or text messaging:  (512) 413-9251
--




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

Re: [wsjt-devel] Tab 2

[Hasan al-Basri]

I prefer TAB 1, do not use TAB 2, ever.

Hasan


On Sun, Dec 2, 2018 at 8:06 AM WB5JJJ  wrote:

> Bill:
>
> As you requested, I have never used Tab 2.  One vote to remove it.  Tab 1
> has all the information as to what is going on during a contact with no
> thinking required.
>
> I have NOT had the UTC/Local time stamp issue.  My Contest Log has the
> correct 24 hour UTC for every entry and I'm set to Central Time in my
> automatic MS time keeping offset.
>
> Enjoyed reading your all-inclusive review of problems/solutions and fixes
> in one place, great work putting that together.  Thanks.
>
> Windows 10 Pro 64 bit here and all aspects of WSJTx-RC5 have worked
> perfectly. I for one, have not had a single problem with the Contest
> Logger, so never had a reason to "edit" it for any reason.  Everything is
> logging to HRD LB directly without a glitch - and I DO check every entry
> while waiting on next contact.
>
> Even though most contacts do not include a Grid Square along with all
> other personal information, HRD LB does get the 6 digit GS with the query
> of QRZ upon adding the entry.  Of course this field is "0" characters in
> the WSJTX log file.  This could cause a problem for some that use the adi
> file as the import to their logger.  The  size may not allow
> the GS to be edited in their logger to a 4 or 6 character count since space
> was not allocated by the adi file import.
>
> Bottom Line - the program requires absolutely no interaction from me for
> proper logging.  I do edit the HRD LB entry when some European stations
> have their Postal Code in front of  their QTH information, so I do delete
> that.  (Future note to coders to fix this if possible, could be a problem
> as there are several variations being seen).
>
> 73's
> --
> George Cotton, WB5JJJ
>
> ___
> 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] Tab 2

[WB5JJJ]

Bill:

As you requested, I have never used Tab 2.  One vote to remove it.  Tab 1
has all the information as to what is going on during a contact with no
thinking required.

I have NOT had the UTC/Local time stamp issue.  My Contest Log has the
correct 24 hour UTC for every entry and I'm set to Central Time in my
automatic MS time keeping offset.

Enjoyed reading your all-inclusive review of problems/solutions and fixes
in one place, great work putting that together.  Thanks.

Windows 10 Pro 64 bit here and all aspects of WSJTx-RC5 have worked
perfectly. I for one, have not had a single problem with the Contest
Logger, so never had a reason to "edit" it for any reason.  Everything is
logging to HRD LB directly without a glitch - and I DO check every entry
while waiting on next contact.

Even though most contacts do not include a Grid Square along with all other
personal information, HRD LB does get the 6 digit GS with the query of QRZ
upon adding the entry.  Of course this field is "0" characters in the WSJTX
log file.  This could cause a problem for some that use the adi file as the
import to their logger.  The  size may not allow the GS to be
edited in their logger to a 4 or 6 character count since space was not
allocated by the adi file import.

Bottom Line - the program requires absolutely no interaction from me for
proper logging.  I do edit the HRD LB entry when some European stations
have their Postal Code in front of  their QTH information, so I do delete
that.  (Future note to coders to fix this if possible, could be a problem
as there are several variations being seen).

73's
-- 
George Cotton, WB5JJJ
___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] Candidate release WSJT-X 2.0.0-rc5

[N1BUG]

On 11/26/18 4:54 PM, Joe Taylor wrote:
> Changes in RC5 relative to RC4 include the following:
> 
>   -  Add "No own call decodes" checkbox in WSPR mode

This is EXCELLENT! A real game changer! Thank you very much for
incorporating this feature.

73,
Paul N1BUG


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

[wsjt-devel] WSJT-X: Summary of issues with v2.0.0 RC5 in RTTY Roundup mode

[Bill Somerville]

Hi All,

thanks for the feedback during the contest activity and sorry for those 
that have had issues that caused serious problems. Here is a summary of 
the main issues with workarounds where available:


1) Having Tab 2 messages selected on the WSJT-X main window causes 
contest exchanges not to be transferred to the Log QSO window which in 
turn blocks logging a QSO until the exchange fields are filled in.


Workaround: Select Tab 1 messages.

This issue is due to insufficient testing being done with Tab 2 
selected. It might be desirable for the ongoing development of WSJT-X to 
remove Tab 2 from the user interface. Please respond if you feel that 
Tab 2 messages are essential to your operating enjoyment and that Tab 1 
is not suitable for you.


2) Editing data in the Contest Log window can leave the log table locked 
and being unable to log QSOs. This defect is serious because there is no 
indication to the user that there is a problem, the application simply 
refuses to log what appear to be completely valid QSOs.


Workaround: If you get a message box saying "Invalid QSO data. Check all 
fields" then single-click on a different row in the Contest Log window, 
i.e. different from the last row you edited a field in; then log the 
QSO. If you are not sure which row you edited, and there is no 
indication to help with that, just try clicking on any row until the Log 
QSO can be actioned.


This issue is due to an edit strategy on the Contest Log table's 
contents that requires moving to a different row before changes are 
committed. It will be changed to a commit on any field change strategy 
which will fix this defect.


3) The QSO time field in the Contest Log window is incorrectly displayed 
in local time despite the heading implying it is UTC. This is a cosmetic 
issue as the underlying time is correctly stored in UTC. Unfortunately 
this is compounded if one tries to edit the time as saving the edit 
unexpectedly shifts the time by the local time offset.


Workaround: Don't attempt to edit the QSO time in the Contest Log 
window. If you really think the time needs changing then fix it later in 
the exported Cabrillo entry file.


3a) The QSO time field in the Contest Log window is displayed in the 
regional time format your PC is set with. This format may be using a 
12hr AM/PM time display, in fact that is the default for the "English 
(United States)" region setting for MS Windows.


The next release will correctly show UTC with the time always in 24hr 
format and edits will not unexpectedly shift the time when saved.


4) The band selector offered when editing fields in the Band column of 
the Contest Log table incorrectly disallows selection of bands that have 
been used in other QSOs.


Workaround: Don't edit the Band column in the Contest Log window, the 
field is not currently used anywhere so its value doesn't matter. The 
column will be used in a later versions to implement duplicate contact 
avoidance.


5) The WSJT-X UDP protocol that allows applications like JTAlert to 
interoperate with WSJT-X does not send the contest exchange details when 
a QSO is logged. This means that those using JTAlert (and MacLoggerDX, I 
believe) cannot use their logging application to keep and generate a 
valid contest log.


Workaround: The direct UDP interface to N1MM Logger+ does transfer the 
required exchange information.


If that is not suitable for you then the WSJT-X ADIF log file has all 
the necessary fields and should be useable to generate a contest entry 
file if it can be imported into your favoured logging application or as 
a last resort manually.


The WSJT-X UDP protocol logging message will have the contest exchange 
fields added for the next release of WSJT-X and cooperating applications 
will be able to extract the required information.


6) Mac users who have a proxy connection to the Internet or are using a 
VPN connection suffer a crash when attempting to download the LotW users 
data, this happens automatically at start up if the file is not found in 
the WSJT-X log files directory.


This is due to a defect in the Qt framework we use for cross platform 
implementation. This new RC5 DMG installer has a fix:


https://www.dropbox.com/s/2m72gxalybwydzl/wsjtx-2.0.0-rc5-Darwin-qt5.9.dmg?dl=0

We have not replaced it on the project web site yet as it drops support 
for OS X Mavericks (10.9) but the next release will be restricted to 
10.10 or later unless more 10.9 users put their hands up with a good 
reason why they cannot upgrade to a supported version of macOS.


Again, apologies to those trying to make a serious entry in the ARRL 
RTTY Roundup using FT8 mode if you were hindered. All these issues will 
be fixed for the next release.


73
Bill
G4WJS.

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

Re: [wsjt-devel] Switching the config file

[Black Michael via wsjt-devel]

You will have to reset the colors when switching between them.Other than that 
nobody has reported any problems flipping back and forth.

de Mike W9MDB


 

On Sunday, December 2, 2018, 6:53:25 AM CST, Claude Frantz 
 wrote:  
 
 Hi all,

After having used the RC5 version with the same config as with 1.9.1, is 
it necessary to restore the previously used config used with 1.9.1 when 
returning to 1.9.1 again ?

OK, I known about the --rig-name= option.

Best wishes,
Claude


___
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] Switching the config file

[Claude Frantz]

Hi all,

After having used the RC5 version with the same config as with 1.9.1, is 
it necessary to restore the previously used config used with 1.9.1 when 
returning to 1.9.1 again ?


OK, I known about the --rig-name= option.

Best wishes,
Claude


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

[wsjt-devel] SOLVED - Contest Log Window- Autoscroll

[oe9kfv]

Hello Bill,

you're up early, thanks for the reply!

Problem solved.

You have to manually move the vertical scroll bar down so that the last thin
line separator touches the bottom of the window.

Then, and only then, will the window update correctly.

 73, Frank
OE9KFV
W9LQ



-Ursprüngliche Nachricht-
Von: Bill Somerville  
Gesendet: Sonntag, 2. Dezember 2018 13:16
An: wsjt-devel@lists.sourceforge.net
Betreff: Re: [wsjt-devel] Contest Log Window- Autoscroll

On 02/12/2018 09:41, oe9...@ft8.at wrote:
> Hello from Austria,
>
> RC5 737d2f, Windows 10 Pro, Version 1809 (Build 17763.134)
>
> looking at the Contest Log Windows - is there a "trick" to make it 
> scroll down automatically all the way to the LAST entry?
>
> Regardless of the window position/size it always shows the last but 
> one log line.
>
> Thanks.
>
> 73, Frank
> OE9KFV

Hi Frank,

this is the first report of this on MS Windows. There are issues with the
Contest Log window not scrolling to show the last QSO on some Linux
desktops.

Is the Contest Log window trying to go to the last entry but stopping short
by one row or is it not scrolling at all when you log a QSO?

73
Bill
G4WJS.



___
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] RU frequencies

[Saku]

-Another request is that when I receive MYCALL CALL R RST NR and 
my program sends CALL MYCALL RR73 and pops up log window Std messages 
would NOT be erased AND next TX would STAY at RR73 until OK is pressed 
at logging window. Now if other station did not get RR73 and repeats R 
RST NR it is more difficult to generate RR73 for him again as std msg 
are cleared and next TX is CQ.



Forget this one ! Wrong thinking/remembering...

Unchecking "Clear DX call" in settings/reporting/logging helps. Std 
messages stay after logging and RR73 is easy to send again if needed.



But "answer random up" feature would be nice.

--
Saku
OH1KH

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

[wsjt-devel] RU frequencies

[Saku]

Hi !

It seems that now everyone (=almost all) are using RU rule band 
frequency allocation start as dial value.
This limits the amount of stations. We are still used to have just one 
dial frequency slice.


If allocated band frequency is divided to 2kHz slices we get more room. 
It is not relevant now, but in future if/when amount of contest stations 
grows.
Then we are facing a new problem. Search-and-pounce stations MUST answer 
either from 0 or UP. If they answer from negative frequency (DN) they 
might go to another 2kHz slice and away from run stations receiver.



--That's why it would be handy to have checkbox "answer  random x 
60Hz up (0 - 600Hz)" for search-and-pounce stations.



-Another request is that when I receive MYCALL CALL R RST NR and my 
program sends CALL MYCALL RR73 and pops up log window Std messages would 
NOT be erased AND next TX would STAY at RR73 until OK is pressed at 
logging window. Now if other station did not get RR73 and repeats R RST 
NR it is more difficult to generate RR73 for him again as std msg are 
cleared and next TX is CQ.



--
Saku
OH1KH

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

Re: [wsjt-devel] Contest Log Window- Autoscroll

[Bill Somerville]

On 02/12/2018 09:41, oe9...@ft8.at wrote:

Hello from Austria,

RC5 737d2f, Windows 10 Pro, Version 1809 (Build 17763.134)

looking at the Contest Log Windows - is there a "trick" to make it scroll
down automatically
all the way to the LAST entry?

Regardless of the window position/size it always shows the last but one log
line.

Thanks.

73, Frank
OE9KFV


Hi Frank,

this is the first report of this on MS Windows. There are issues with 
the Contest Log window not scrolling to show the last QSO on some Linux 
desktops.


Is the Contest Log window trying to go to the last entry but stopping 
short by one row or is it not scrolling at all when you log a QSO?


73
Bill
G4WJS.



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

Re: [wsjt-devel] Problem with Contest Data and N1MM+ feed?

[Bill Somerville]

On 02/12/2018 04:22, David Kaplan via wsjt-devel wrote:

I made a few QSOs with RC5 feeding MacLoggerDX the N1MM+ data. The main QSO 
information came through fine, but there was no exchange data for my log..

An exchange of 539 NJ from K1JT is apparently built from 539 and 
NJ,
and 549 0044 for CE1OEB from 549 and 0044.

It doesn’t seem as if you send a STX_STRING or SRX_STRING in the N1MM+ data 
which MacLoggerDX would need to populate my log..

I can send the full ADIF if you want

Am I interpreting this correctly?

Thanks.

David, WA1OUI


Hi David,

only the direct UDP messages sent to N1MM Logger+ and the WSJT-X ADIF 
log have the contest exchange information. No guarantees were offered 
for other routes like the WSJT-X UDP protocol that programs like JTAlert 
use. We hope to have the extra contest exchange information added to the 
WSJT-X UDP protocol for the WSJT-X v2.0.0 GA release but to make use of 
it the cooperating applications will also have to extract the new fields 
and allocate them to their logs and data feeds.


73
Bill
G4WJS.



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

[wsjt-devel] Contest Log Window- Autoscroll

[oe9kfv]

Hello from Austria,

RC5 737d2f, Windows 10 Pro, Version 1809 (Build 17763.134)

looking at the Contest Log Windows - is there a "trick" to make it scroll
down automatically
all the way to the LAST entry?

Regardless of the window position/size it always shows the last but one log
line.

Thanks.

73, Frank
OE9KFV






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