开云体育

What is the procedure to print mailing labels - specifically, labels for all of the QSOs on my VUCC progress report. Since the ARRL does not _yet_ offer VUCC via LotW, I need to print them all regardless of whether they have been confirmed via LotW.

Thanks and 73,

--
Tad Danley, K3TD
EM10dq

You could filter the Spot Database Display to include only local spots and
then click SpotCollector's Report button (just below the "Spot source
status" panel on SpotCollector's Main window).

73,

Dave, AA6YQ

This release

- when synchronizing QSOs or QSLs with LotW, QSOs reported by LotW whose Mode is DATA are considered to match a logged QSO whose mode "counts" as RTTY for ARRL awards (tnx to Bob WU9Q)

- updates the AwardInfo.htm, index.htm, Log.htm, LogCompletedMain.htm, LogNewCapture.htm, LogNewMain.htm, ModifyLog.htm, Progress.htm, QSL.htm, Scripts.htm, and ViewEditLog.htm documentation files

If your are uploading digital mode QSOs to LotW where the digital mode is not yet supported by LotW (e.g. JT65A), configure TQSL to "map" these unsupported digital modes to DATA. The above enhancement allows DXKeeper to locate these QSOs in your log when directed to synchronize with LotW; previously, DXKeeper would report such QSOs as not matching any logged QSO because of the change in mode introduced by TQSL.

DXKeeper 8.1.6 is available via the DXLab Launcher and via

<>

73,

Dave, AA6YQ

I have forgotten how to save the Winwarbler Stations Heard information
to a txt file. I know it can be done, done it before. Perhaps
related to "local" spots in Spotcollector?
Andy K3UK

Updated LotW and eQSL AG databases are available via the Databases tab of
DXView's Config window.

Thanks, Renzo!

73,

Dave, AA6YQ

When was the last time the CBA button worked correctly, Bruce?

After you click the CBA button, what appears in Pathfinder's Main window?

In Pathfinder's Config window, is the QRZ.com URL set to

{TargetCallsign}

?

73,

Dave, AA6YQ

Hello
I just started getting an error message "callsign was not found" when pressing the cba button. I use pathfinder and qrz to normally look it up and it has worked fine before. Anyone have any ideas?
Bruce VE7BSM

AA6YQ comments below

--- In dxlab@..., "aburkefl" <aburkefl@...> wrote:

At times, I've changed bands on my K3 and then discovered that Commander did not "follow" the radio. Terminating and restarting Commander generally "cures" the problem - for a while. I'm using a microHAM USB interface and when Commander loses contact with the K3, I can see that the Router still maintains contact with the K3 (patched).

At this point, I can only assume that some other program running in the background is creating some kind of conflict.

Windows won't let more than one application open the same serial port.

The next time this happens, please enable "log debugging info" on the Config window's General tab, wait a minute, disable "log debugging info", and then attach the errorlog.txt file from your Commander folder to an email message to me at aa6yq@... . The errorlog will include Commander's directives to your K3 and the K3's responses, so I'll be able to see what's going on.

I can't remember the name or source of one of those programs that will stop all unnecessary applications and let only the minimum of programs.

Dave, right off the top of your head, is the OCX a potential problem?
Once I tried to start something running involving the MARAC Logger while DXLabs was also running. Could there be a potential conflict if the two are battling for the OCX?

There are many .ocx modules; to which one(s) are you referring?

73,

Dave, AA6YQ

At times, I've changed bands on my K3 and then discovered that Commander did not "follow" the radio. Terminating and restarting Commander generally "cures" the problem - for a while. I'm using a microHAM USB interface and when Commander loses contact with the K3, I can see that the Router still maintains contact with the K3 (patched).

At this point, I can only assume that some other program running in the background is creating some kind of conflict. I can't remember the name or source of one of those programs that will stop all unnecessary applications and let only the minimum of programs.

Dave, right off the top of your head, is the OCX a potential problem? Once I tried to start something running involving the MARAC Logger while DXLabs was also running. Could there be a potential conflict if the two are battling for the OCX?

Art - N4PJ

Hi Dave,
I have just uploaded an updated LoTW user list database, now it is at
06/09/2009.

73,

Renzo I6KZR


MITTO TIBI NAVEM PRORA PUPPIQUE CARENTEM
----------


Nessun virus nel messaggio in uscita.
Controllato da AVG - www.avg.com
Versione: 8.5.409 / Database dei virus: 270.13.80/2349 - Data di rilascio: 09/06/09 05:51:00

AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of John
Bastin
Sent: Sunday, September 06, 2009 2:38 PM
To: dxlab@...
Subject: Re: [dxlab] SC and WW Questions



On Sep 6, 2009, at 14:18:06, Jim Besancon wrote:

One WW Question:

1- My radio (FT1000D) has two memories per band for the main VFO. I
generally keep one memory in the CW portion and the other in the RTTY
portion of any given band. Now using 20M as an example, one memory is
14025 CW and the other is 14085 FSK RTTY. The question/problem is
when I see
a RTTY spot, I switch to the RTTY memory and listen for the
station. If
the station is heard, I set the mode on the radio to LSB (AFSK
RTTY) and
then click the RTTY mode button in WW. At this point, WW sets both
memories
to the RTTY LSB frequency, there by destroying my ability to quickly
go back
to CW. Is there a set up or button pushing sequence that will just
set
WW to RTTY, open up the RTTY screen and do nothing with the memories
on the
radio?

My experience with my FT1000MP (same setup, two memories per band) is
that computer frequency control pretty much hoses any attempt to use
the buttons for specific band areas (CW - RTTY, CW - SSB, etc.). When
you set the radio frequency with the computer, it seems to set all the
information on the current button selection, messing up your choices
for using the button to change portions of the band, mode, etc.

I've pretty much given up using the buttons in any meaningful way to
do something like this to save permanent settings. I just use the
computer, click on spots and work the stations using whichever VFO
button selection I happen to be on at the time.

Commander provides 10 banks of 10 memories, so you can set up permanent

settings in a transceiver-independent fashion that will not be modified when
you double-click a spot database entry or bandspread entry.

73,

Dave, AA6YQ

AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of Jim
Besancon
Sent: Sunday, September 06, 2009 2:18 PM
To: dxlab@...
Subject: [dxlab] SC and WW Questions


Good Afternoon

Two SC Questions:

1-Can SC be configured to save the last filter I was using? I have
SC set so the filter buttons are off the screen, so at every startup I
need to move things around to activate 'my' filter.

No. I was concerned that carrying over a filter from the previous

operating session might cause a user to miss needed DX.

2-Eliminating Beacon '/B' stations. I know this has been covered and
I have set /B as an invalid call sign, but they just keep on coming.
Any information would be appreciated.

Add B (with no slash) to the Special Callsign list with no tag.

One WW Question:

1- My radio (FT1000D) has two memories per band for the main VFO. I
generally keep one memory in the CW portion and the other in the RTTY
portion of any given band. Now using 20M as an example, one memory is
14025 CW and the other is 14085 FSK RTTY. The question/problem is when I see
a RTTY spot, I switch to the RTTY memory and listen for the station. If
the station is heard, I set the mode on the radio to LSB (AFSK RTTY) and
then click the RTTY mode button in WW. At this point, WW sets both memories
to the RTTY LSB frequency, there by destroying my ability to quickly go back
to CW. Is there a set up or button pushing sequence that will just set
WW to RTTY, open up the RTTY screen and do nothing with the memories on the
radio?

DXLab does not explicitly set the memories of any transceiver; whatever

changes to your FT1000D's memories are occuring are the transceiver's
response to being instructed to QSY to a particular frequency an mode.

You can configure SpotCollector so that when you see CW, phone, PSK, or

RTTY spot database entry of interest, all you need do is double-click that
entry; WinWarbler's QSO Info window will be appropriately initialized with
information from the spot database entry, and WinWarbler will direct
Commander to QSY to the appropriate frequency and mode so that operation can
begin immediately (e.g. if the frequency of a RTTY or PSK spot database
entry is accurate, WinWarbler will immediately begin displaying decoded
characters.

To do this, open the General tab of SpotCollector's Config window and

- in the "Actions with Digital Mode Application connected" panel, check the
Service column's Digital, CW, and SSB boxes

- in the "Digital Mode Application" panel, ensure that the Name is set to
WinWarbler

73,

Dave, AA6YQ

On Sep 6, 2009, at 14:18:06, Jim Besancon wrote:

One WW Question:

1- My radio (FT1000D) has two memories per band for the main VFO. I
generally keep one memory in the CW portion and the other in the RTTY
portion of any given band. Now using 20M as an example, one memory is
14025 CW and the other is 14085 FSK RTTY. The question/problem is when I see
a RTTY spot, I switch to the RTTY memory and listen for the station. If
the station is heard, I set the mode on the radio to LSB (AFSK RTTY) and
then click the RTTY mode button in WW. At this point, WW sets both memories
to the RTTY LSB frequency, there by destroying my ability to quickly go back
to CW. Is there a set up or button pushing sequence that will just set
WW to RTTY, open up the RTTY screen and do nothing with the memories on the
radio?

My experience with my FT1000MP (same setup, two memories per band) is that computer frequency control pretty much hoses any attempt to use the buttons for specific band areas (CW - RTTY, CW - SSB, etc.). When you set the radio frequency with the computer, it seems to set all the information on the current button selection, messing up your choices for using the button to change portions of the band, mode, etc.

I've pretty much given up using the buttons in any meaningful way to do something like this to save permanent settings. I just use the computer, click on spots and work the stations using whichever VFO button selection I happen to be on at the time.

Hope this helps.

John K8AJS
jbastin@...

I suspect that what Dave was getting at is that the State/County etc. may be dependent on the date of the QSO because the person has moved and QRZ.com will only show the present day information. I could have worked you while you were in Maricopa county Arizona but QRZ.com shows you in in McHenry county Illinois.

73, Rich - W3ZJ

Jim N7US wrote:

Just guessing, of course, but I suspect that the state and/or county
information returned by QRZ.com for those specific callsigns contained
subtle mis-spellings. If it should happen again, please note the callsign
and send it my way. Thanks...

73,

Davem AA6YQ

Good Afternoon

Two SC Questions:

1-Can SC be configured to save the last filter I was using? I have
SC set so the filter buttons are off the screen, so at every startup I
need to move things around to activate 'my' filter.

2-Eliminating Beacon '/B' stations. I know this has been covered and
I have set /B as an invalid call sign, but they just keep on coming.
Any information would be appreciated.

One WW Question:

1- My radio (FT1000D) has two memories per band for the main VFO. I
generally keep one memory in the CW portion and the other in the RTTY
portion of any given band. Now using 20M as an example, one memory is
14025 CW and the other is 14085 FSK RTTY. The question/problem is when I see
a RTTY spot, I switch to the RTTY memory and listen for the station. If
the station is heard, I set the mode on the radio to LSB (AFSK RTTY) and
then click the RTTY mode button in WW. At this point, WW sets both memories
to the RTTY LSB frequency, there by destroying my ability to quickly go back
to CW. Is there a set up or button pushing sequence that will just set
WW to RTTY, open up the RTTY screen and do nothing with the memories on the
radio?

73 - Jim - K8SIA

I had the problem with several QSOs I entered. The state in the Award
section wasn't being filled in either. I don't know why that was happening
but it's working OK now. No doubt an operator problem.

Thanks, Dave.

Jim N7US

"AZ,Maricopa" is indeed a valid US county; I just logged a test QSO containing it.

What's the callsign of the station you logged that caused the error message to appear?

73,

Dave, AA6YQ

I'm entering some QSOs from old logs and have a subscription to the QRZ data
lookup.

I'm getting an error message that "County returned by callbook lookup
doesn't match a known US county: AZ,Maricopa" for example. That's my
previous county so I know it's valid. Do I have a configuration option set
incorrectly?

Jim N7US

Up at the top line in SpotCollector, do you see the letters WW between the set of brackets (along with CC, DXV etc)? And in the top line of WinWarbler do you see SC inside the brackets? If either of those do not show, it means that SC and WW are not talking to each other. You might need to close either one of them (or both), and reinitiate to get them talking.
Danny Douglas
N7DC
ex WN5QMX ET2US WA5UKR ET3USA
SV0WPP VS6DD N7DC/YV5 G5CTB

All 2 years or more (except Novice)
Pls QSL direct, buro, or LOTW preferred,
I Do not use, but as a courtesy do upload to eQSL for
those who do.

Moderator
DXandTALK

DXandTALK@...

Moderator
Digital_modes