Date   

Re: "LoTW Member"

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Monday, September 18, 2017 1:03 AM
To: DXLab forum
Subject: Re: [dxlab] "LoTW Member"

I should had mentioned he was listed in previous versions of the data base and that my earlier confirmations by him are from months ago.
Could there be a bug at ARRL and more stations missing?

The URL for obtaining a list of all LoTW callsigns and "last download" dates is documented here:
<https://lotw.arrl.org/lotw-help/developer-query-lotw-users/>

It's currently returning 0-length file, so I can't debug it. I have notified LoTW staff...
73,

Dave, AA6YQ


Re: "LoTW Member"

Björn SM7IUN
 

Dave,

I should had mentioned he was listed in previous versions of the data base and that my earlier confirmations by him are from months ago.
Could there be a bug at ARRL and more stations missing?

73,

Björn 


2017-09-18 0:14 GMT+02:00 'Dave AA6YQ' aa6yq@... [dxlab] <dxlab@...>:

 

>>>AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Sunday, September 17, 2017 5:23 PM
To: DXLab forum
Subject: [dxlab] "LoTW Member"

What is the mechanics for creating the LOTW database? ARRL or some indirect method?

>>>A file containing callsigns and "dates of last update" is downloaded from the ARRL.

I just worked VK5PO on 80m and DXView tells me he is not a LOTW user but I still have recent LOTW confirmations from him on other bands and when I check him on the LOTW web site his last upload was a week ago.

>>>Using the "Find Call" tab in your LoTW Web Account

<https://lotw.arrl.org/lotwuser/act?awg_id=&ac_acct=>

>>>shows that VK5PO last uploaded to LoTW on 2017-09-12, which was after the date that the last LoTW database was created (2017-09-03). Presumably VK5PO will appear in the next LoTW Database.

73,

Dave, AA6YQ



Re: "LoTW Member"

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Sunday, September 17, 2017 5:23 PM
To: DXLab forum
Subject: [dxlab] "LoTW Member"

What is the mechanics for creating the LOTW database? ARRL or some indirect method?

A file containing callsigns and "dates of last update" is downloaded from the ARRL.
I just worked VK5PO on 80m and DXView tells me he is not a LOTW user but I still have recent LOTW confirmations from him on other bands and when I check him on the LOTW web site his last upload was a week ago.

Using the "Find Call" tab in your LoTW Web Account
<https://lotw.arrl.org/lotwuser/act?awg_id=&ac_acct=>

shows that VK5PO last uploaded to LoTW on 2017-09-12, which was after the date that the last LoTW database was created (2017-09-03). Presumably VK5PO will appear in the next LoTW Database.
73,

Dave, AA6YQ


"LoTW Member"

Björn SM7IUN
 

What is the mechanics for creating the LOTW database? ARRL or some indirect method?

I just worked VK5PO on 80m and DXView tells me he is not a LOTW user
but I still have recent LOTW confirmations from him on other bands and when I check
him on the LOTW web site his last upload was a week ago.

Thanks,

Björn SM7IUN




Re: Mouse wheel

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Sunday, September 17, 2017 5:43 AM
To: YahooGroup DXLabs
Subject: [dxlab] Mouse wheel

When the SC-window is active, the mouse wheel scrolls vertical through the shown incoming spots.
I don’t know what i did, but once it happened that the wheel scrolled horizontally, showing all of the columns from left to right, as far as it goes in SC.
I do not find any explanation in the Help files.

If you depress the CTRL key while moving the mouse wheel, the Spot Database Display will be scrolled horizontally.
73,

Dave, AA6YQ


Re: need volunteers for to test a new version of SpotCollector

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Sunday, September 17, 2017 8:47 AM
To: dxlab@...
Subject: Re: [dxlab] need volunteers for to test a new version of SpotCollector

I start/stop SpotCollector daily (full shutdown and restart) but I have never seen the issue you describe. Could the issue be with those who are using hibernate/sleep rather than doing a proper shutdown?

Yes, that's possible, Joe. The issue could also be caused by a Microsoft defect, but I'd like to be sure that SpotCollector is not at fault.
73,

Dave, AA6YQ


Re: need volunteers for to test a new version of SpotCollector

Joe Subich, W4TV
 

Dave,

I start/stop SpotCollector daily (full shutdown and restart) but I
have never seen the issue you describe. Could the issue be with
those who are using hibernate/sleep rather than doing a proper
shutdown?

73,

... Joe, W4TV

On 9/16/2017 6:00 PM, 'Dave AA6YQ' aa6yq@... [dxlab] wrote:
For many years, there has been a low rate of incidence of reports that when SpotCollector starts, an errorlog.txt file is created and the Spot Database Display remains empty. The Spot Database Display contains an entry indicating that the Spot Database cannot be
opened. I have never seen this behavior here. The workaround has been
to delete the Spot Database (Spots.mdb) and restart SpotCollector,
which creates an empty new Spot Database and then proceeds to
populate it with information extracted from incoming DX spots. >
My several attempts to identify the defect responsible for this behavior have so far been unsuccessful. Recently, it occurred to me that the defect may be the result of not properly handling the case where SpotCollector is directed to terminate while it's in the middle
of updating a database table. If this were the case, users who frequently terminate SpotCollector would be more likely to encounter the behavior than those users who, like me, leave it running 7x24 between Windows shutdowns. I have added code to the next version of SpotCollector that delays termination if a database table update is in progress. To test this new version, I'm seeking 5 volunteers to whose usage of SpotCollector involves starting and stopping it
daily. If you're willing, please send email to me via
aa6yq (at) ambersoft.com
The first five qualifying volunteers will be chosen.
The next version of SpotCollector also includes two enhancements suggested by Björn SM7IUN: on startup, it will within a few seconds populate DXView's World Map window with active DX stations (assuming you have DXView configured to display active DX stations), and when you delete a Spot Database Entry, the callsign associated with that Entry will disappear from Commander's Bandspread window. >
73,
Dave, AA6YQ
------------------------------------
Posted by: "Dave AA6YQ" <aa6yq@...>
------------------------------------
------------------------------------
Yahoo Groups Links


Mouse wheel

eddy on5jk
 

Dave,
When the SC-window is active, the mouse wheel scrolls vertical through the shown incoming spots.
I don’t know what i did, but once it happened that the wheel scrolled horizontally, showing all of the columns from left to right, as far as it goes in SC.
I do not find any explanation in the Help files.
Where do i have to seek for this info?
Thanks
Eddy ON5JK

Virusvrij. www.avg.com


Re: need volunteers for to test a new version of SpotCollector

eddy on5jk
 

Dave i start and terminate the whole DXLabsuite dayly.
I hope my English will be good enough.
Eddy ON5JK
 
From: 'Dave AA6YQ' aa6yq@... [dxlab]
Sent: Sunday, September 17, 2017 12:00 AM
To: dxlab@...
Subject: [dxlab] need volunteers for to test a new version of SpotCollector
 
 

For many years, there has been a low rate of incidence of reports that when SpotCollector starts, an errorlog.txt file is created
and the Spot Database Display remains empty. The Spot Database Display contains an entry indicating that the Spot Database cannot be
opened. I have never seen this behavior here. The workaround has been to delete the Spot Database (Spots.mdb) and restart
SpotCollector, which creates an empty new Spot Database and then proceeds to populate it with information extracted from incoming DX
spots.

My several attempts to identify the defect responsible for this behavior have so far been unsuccessful. Recently, it occurred to me
that the defect may be the result of not properly handling the case where SpotCollector is directed to terminate while it's in the
middle of updating a database table. If this were the case, users who frequently terminate SpotCollector would be more likely to
encounter the behavior than those users who, like me, leave it running 7x24 between Windows shutdowns. I have added code to the next
version of SpotCollector that delays termination if a database table update is in progress. To test this new version, I'm seeking 5
volunteers to whose usage of SpotCollector involves starting and stopping it daily. If you're willing, please send email to me via

aa6yq (at) ambersoft.com

The first five qualifying volunteers will be chosen.

The next version of SpotCollector also includes two enhancements suggested by Björn SM7IUN: on startup, it will within a few seconds
populate DXView's World Map window with active DX stations (assuming you have DXView configured to display active DX stations), and
when you delete a Spot Database Entry, the callsign associated with that Entry will disappear from Commander's Bandspread window.

73,

Dave, AA6YQ


Virusvrij. www.avg.com


Re: MMTTY scrteen shot

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Sunday, September 17, 2017 12:44 AM
To: dxlab@...
Subject: [dxlab] RE: MMTTY scrteen shot

That did the trick. Here are the values that I replaced:

WindowTop=-8
WindowLeft=-8
WindowWidthS=1696
WindowHeightR=1026

I suppose it's a fools errand for me to try to figure out how those got into the .ini file.

If you didn't terminate WinWarbler after expanding the MMTTY engine to "full screen", then the fault could lie in your display driver or Windows.
73,

Dave, AA6YQ


Re: MMTTY scrteen shot

Dick Grote
 

Dave,

That did the trick.  Here are the values that I replaced:

WindowTop=-8
WindowLeft=-8
WindowWidthS=1696
WindowHeightR=1026

I suppose it's a fools errand for me to try to figure out how those got into the .ini file.

Thank you for your help.  

73,
Dick
K6PBF


Re: Running WSJT-X (FT 8) via DX Commander

Bill Conkling
 

Look for "multiple" PTT devices. 

...nr4c. bill


On Sep 16, 2017, at 4:15 PM, Sid Frissell sidfrissell@... [dxlab] <dxlab@...> wrote:

 

I have been trying to change my setup to control my K3S via Commander when using FT8 rather than direct to the radio. Everything seems to work. The transmitter comes on just fine. BUT. It won't stop transmitting! Something is not right with Rig Control.(or half of rig control). Anyone have a solution??

Sid Frissell. NZ7M


Re: MMTTY scrteen shot

Dave AA6YQ
 

Thanks, Dick; I understand now.

Please do the following:

1. terminate WinWarbler

2. using Notepad, open the file MMTTY.ini in your WinWarbler folder

3. in the MMTTY.ini file, locate the section that begins with [Window] and modify the WindowTop, WindowLeft, WindowWidthS, and WindowHeightR settings as shown:

WindowTop=50
WindowLeft=50
WindowWidthS=400
WindowHeightR=200

4. direct Notepad to save your changes

5. start WinWarbler, and place it in RTTY mode

A modest-sized "MMTTY Engine" window should appear in the upper-left corner of your screen.

Please let me know how it goes...

73,

Dave, AA6YQ

-----Original Message-----
From: Dick Grote [mailto:dick_grote@...]
Sent: Saturday, September 16, 2017 10:06 PM
To: aa6yq@...
Subject: MMTTY scrteen shot

Dave,

Sorry if I didn't explain this too well in the post. The MMTTY engine display takes over the entire screen and it size can't be reduced. Let me know if this picture isn't clear enough.

Thanks for being always on the job.

Dick
K6PBF

<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>


Re: MMTTY Display always full screen

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Saturday, September 16, 2017 9:11 PM
To: dxlab@...
Subject: [dxlab] MMTTY Display always full screen

I've had this problem for a while and can't find a way around it. When WinWarbler goes into RTTY mode, the MMTTY decode screen is always full screen. I can minimize it, but I can't reduce the screen size. The 2Tone decode screen is still okay. I've tried diddling with MMTTY settings and have even reloaded MMTTY, but nothing works for me. Any suggestions?

I don't know what you mean by "the MMTTY decode screen". Please make a screen shot of the problematic behavior, attach it to an email message, and send it to me via
aa6yq (at) ambersoft.com

73,

Dave, AA6YQ


MMTTY Display always full screen

Dick Grote
 

I've had this problem for a while and can't find a way around it.  When WinWarbler goes into RTTY mode, the MMTTY decode screen is always full screen.  I can minimize it, but I can't reduce the screen size.  The 2Tone decode screen is still okay.  I've tried diddling with MMTTY settings and have even reloaded MMTTY, but nothing works for me.  Any suggestions?


Thanks,

Dick

K6PBF


Re: Running WSJT-X (FT 8) via DX Commander

Sid Frissell <sidfrissell@...>
 

Bill:  I have CAT selected. I didn't change that. Should I?

Sent From Sid Frissell's iPad

On Sep 16, 2017, at 2:26 PM, bill.8@... [dxlab] <dxlab@...> wrote:

 

Hi Sid,

which option do you have selected in the WSJT-X "Settings->Radio->PTT Method" panel?

73
Bill
G4WJS.


need volunteers for to test a new version of SpotCollector

Dave AA6YQ
 

For many years, there has been a low rate of incidence of reports that when SpotCollector starts, an errorlog.txt file is created
and the Spot Database Display remains empty. The Spot Database Display contains an entry indicating that the Spot Database cannot be
opened. I have never seen this behavior here. The workaround has been to delete the Spot Database (Spots.mdb) and restart
SpotCollector, which creates an empty new Spot Database and then proceeds to populate it with information extracted from incoming DX
spots.

My several attempts to identify the defect responsible for this behavior have so far been unsuccessful. Recently, it occurred to me
that the defect may be the result of not properly handling the case where SpotCollector is directed to terminate while it's in the
middle of updating a database table. If this were the case, users who frequently terminate SpotCollector would be more likely to
encounter the behavior than those users who, like me, leave it running 7x24 between Windows shutdowns. I have added code to the next
version of SpotCollector that delays termination if a database table update is in progress. To test this new version, I'm seeking 5
volunteers to whose usage of SpotCollector involves starting and stopping it daily. If you're willing, please send email to me via

aa6yq (at) ambersoft.com

The first five qualifying volunteers will be chosen.

The next version of SpotCollector also includes two enhancements suggested by Björn SM7IUN: on startup, it will within a few seconds
populate DXView's World Map window with active DX stations (assuming you have DXView configured to display active DX stations), and
when you delete a Spot Database Entry, the callsign associated with that Entry will disappear from Commander's Bandspread window.

73,

Dave, AA6YQ


Re: DXKeeper logging band and not frequency

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Saturday, September 16, 2017 5:32 PM
To: dxlab@...
Subject: Re: [dxlab] DXKeeper logging band and not frequency

Ross and Dave, thank you for your replies. All of my frequencies track as they should and for radio contro I use PTT with RTS selected. The problem was solved today when I had one of those "I wonder what would happen if..." moments. It turns out the solution was as simple as defining a space for the frequency in DXKeeper. All I had defined was "Band". As soon as I defined "freq" it started working. Thanks again for your replies.

By "defining a space for the frequency", I assume you mean "adding a column for frequency in the Log Page Display". If so, then all of the FT8 QSOs you logged before adding the frequency column should contain information in that frequency column.
Note that that when you select a QSO in the Log Page Display, that QSO's information is displayed in the panels above the Log Page Display, not matter what columns are or are not present in the Log Page Display. In particular, the QSO's "tx freq" and "rx freq" i0tems are displayed in the 2nd and 3rd rows respectively of the QSO panel, which is always present. You can configure DXKeeper to display additional panels above the Log Page Display; see
<http://www.dxlabsuite.com/dxlabwiki/Logging>

73,

Dave, AA6YQ


Re: DXKeeper logging band and not frequency

patchiles@...
 

Ross and Dave, thank you for your replies.  All of my frequencies track as they should and for radio contro I use PTT with RTS selected.  The problem was solved today when I had one of those "I wonder what would happen if..." moments.  It turns out the solution was as simple as defining a space for the frequency in DXKeeper.  All I had defined was "Band".  As soon as I defined "freq" it started working.  Thanks again for your replies.
Pat, K8PC   


Re: Running WSJT-X (FT 8) via DX Commander

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Saturday, September 16, 2017 5:02 PM
To: dxlab@...; dxlab@...
Subject: Re: [dxlab] Re: Running WSJT-X (FT 8) via DX Commander

Is there any capability in WinWarbler to run FT-8 and other recent Dig modes, in addition to RTTY and PSK?

No. See
<http://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModes>

73,

Dave, AA6YQ