¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
Date

Re: cba and qrz

 

Is this happening on every callsign or is it possible that the callsign you are trying to lookup really isn't in the QRZ.com database? All US and Canadian calls are in the QRZ.com database because they are copied from the FCC and RAC databases. However, calls for the rest of the world are entered by the callsign holders themselves so obviously they are not all there.

73, Rich - W3ZJ

hambeamtower wrote:

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


Re: The IC-9100 at Tokyo HamFair 2009

 

On Sun, Sep 6, 2009 at 21:17, aa6yq<aa6yq@...> wrote:
Thanks to Adam VA7OJ/AB4OJ and Oba-san JA7UDE:

<>

This is Icom's third transceiver with a direct USB interface for transceiver control and audio.

I've not seen a manual, but I suspect this transceiver's CI-V instruction set is identical to that of the IC-7600. So if one appears on your doorstep, use Notepad to open the radios.txt file in your Commander folder, insert this line:

radio=IIC-9100, Address=XX, DualWatch=T, VFOSel=F, VFOEqual=F, VFOExchange=F, MainSubSel=T, MainSubEqual=T, MainSubExchange=T, Filter0=T, PTT=T, CW-R=T, RTTY-R=T, Smeter=T, PBT=T

How do we do that, Dave? I mean, get one to show up on our doorstep. :-)

Two receivers, it seems. Hmmm. And 70 cm. Might make a nice
replacement for my IC746Pro ... or maybe an addition .. :-)



--
Peter Laws | N5UWY | plaws plaws net | Travel by Train!


The IC-9100 at Tokyo HamFair 2009

 

Thanks to Adam VA7OJ/AB4OJ and Oba-san JA7UDE:

<>

This is Icom's third transceiver with a direct USB interface for transceiver control and audio.

I've not seen a manual, but I suspect this transceiver's CI-V instruction set is identical to that of the IC-7600. So if one appears on your doorstep, use Notepad to open the radios.txt file in your Commander folder, insert this line:

radio=IIC-9100, Address=XX, DualWatch=T, VFOSel=F, VFOEqual=F, VFOExchange=F, MainSubSel=T, MainSubEqual=T, MainSubExchange=T, Filter0=T, PTT=T, CW-R=T, RTTY-R=T, Smeter=T, PBT=T

(where XX is the IC-9100's default CI-V address)

save your changes, fire up Commander, set the Radio selector on the Config window's General tab to IC-9100, and you should be good to go.

73,

Dave, AA6YQ


Re: printing mailing labels

 

+++ More AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Tad Danley
Sent: Sunday, September 06, 2009 7:01 PM
To: dxlab@...
Subject: Re: [dxlab] printing mailing labels


Dave AA6YQ wrote:

Tad Danley wrote:

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.

Do you only need address labels, or do you also need QSL labels that
can
be affixed to an outgoing QSL card?
Thanks Dave - I need both!

+++ OK. The basic procedure is

1. set the "QSL Via" panel on the Main window's QSL tab to either 2-column
labels or 3-column labels, as desired

2. populate the QSL Queue with QSOs for which labels are to be generated

3. invoke the Address Editor to specify an address for each QSL Queue entry
rendered in red font (double-click the entry)

4. create an Address File and review it to ensure that all addresses are
correctly formatted

4. print QSL labels from the QSL Queue

5. print address labels from the QSL Queue

+++Regarding step 2, DXKeeper can at present automatically populate the QSL
Queue with QSOs needed for the ARRL DXCC family or awards, and for the CQ
WAZ family of awards; for other awards, you must manually add needed QSOs to
the QSL queue. I'd been thinking about providing the option to automatically
populate the QSL Queue with needed QSOs when generating a progress report
for the other awards supported by DXKeeper; each of these reports lists
"counters" for which there's a worked-but-unconfirmed QSO, so it would be
straightforward to insert each worked-but-unconfirmed QSO into the QSL Queue
rather than require the user to manually locate and add each unconfirmed QSO
to the QSL Queue. The challenge is providing a way to let the user specify
whether or not the QSL Queue should be populated with unconfirmed QSOs when
generating a progress report -- without displaying an annoying prompt each
time a progress report is generated, and without having the QSL Queue be
unintentionally populated by subsequent progress reports because the user
forgot to disable the option. Your request prompted me to think harder about
this, and I came up with the idea of adding an "Add Unconfirmed to QSL
Queue" checkbox in the lower-left corner of the Main window's "Check
Progress" tab, as shown here:

<>

+++When you start DXKeeper, this box will be unchecked. If you check this
box before initiating a progress report, then any QSOs identified as needed
but unconfirmed in this report will be added to the QSL Queue -- and the box
will automatically be unchecked after the report is generated. Thus anyone
not interested in generating outgoing QSLs when running a progress report
won't be bothered by this new capability; if you do want to generated needed
QSLs, check the box before clicking the button to generate the progress
report.

+++I have constructed a new version of DXKeeper that implements this
capability, but only for the VUCC progress report. I'll email it to you
shortly, so you can give it a try. If it works out, I'll extend this
capability to all the other progress reports that DXKeeper generates (except
DXCC and WAZ). If anyone else would like to try this new version of
DXKeeper, send email to me at aa6yq@... from an email account that
will accept a zip archive containing an executable file as an attachment
(e.g. not gmail).

+++If you haven't generated labels before, Tad, you'll need to configure
DXKeeper to correctly print the labels of your choice using the "QSL Labels"
and "Envelopes" tabs on the "QSL Config" window. I suggest loading your
printer with inexpensive paper while you do this. The procedure is described
in < with Paper>, but
don't hesitate to post any questions or concerns here.

73,

Dave, AA6YQ


Re: Commander install fail

 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
frank.fahrlander
Sent: Sunday, September 06, 2009 8:28 PM
To: dxlab@...
Subject: [dxlab] Commander install fail


Hi,

I'm posting this to help a fellow who just tried to install Commander and
got the following message:

"unable to download file from
http:www.iv3yer.com/Dxlab/Commander587Archive.exe
aborting installation"

He is using the launcher. Any ideas how this happened and howto proceed?

The DXLab distribution portion of Luigi IV3YER's site appears to be down.
On the Launcher's Config window, choose a different distribution site and
try again. If this doesn't allow your friend to install Commander, please
let me know. Thanks...

73,

Dave, AA6YQ


Commander install fail

frank.fahrlander
 

Hi,

I'm posting this to help a fellow who just tried to install Commander and got the following message:

"unable to download file from
http:www.iv3yer.com/Dxlab/Commander587Archive.exe
aborting installation"

He is using the launcher. Any ideas how this happened and howto proceed?

Frank, N7FF


Re: cba and qrz

 

--- In dxlab@..., "Dave AA6YQ" <aa6yq@...> wrote:

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
Hi Dave
Got it okay now. It was missing the {TargetCallsign).
Thanks
Bruce VE7BSM


Re: printing mailing labels

Tad Danley
 

Dave AA6YQ wrote:

Tad Danley wrote:
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.

Do you only need address labels, or do you also need QSL labels that can
be affixed to an outgoing QSL card?
Thanks Dave - I need both!

73,

--
Tad Danley, K3TD
EM10dq


Re: printing mailing labels

 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
Tad Danley
Sent: Sunday, September 06, 2009 6:00 PM
To: dxlab@...
Subject: [dxlab] printing mailing labels


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.

Do you only need address labels, or do you also need QSL labels that can
be affixed to an outgoing QSL card?

73,

Dave, AA6YQ


printing mailing labels

Tad Danley
 

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


Re: Subject: Save Stations Heard to txt file?

 

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

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
obrienaj
Sent: Sunday, September 06, 2009 5:46 PM
To: dxlab@...
Subject: [dxlab] Subject: Save Stations Heard to txt file?



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



------------------------------------

Yahoo! Groups Links



No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.339 / Virus Database: 270.13.74/2339 - Release Date: 09/06/09
05:51:00


DXKeeper 8.1.6 is available

 

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


Subject: Save Stations Heard to txt file?

obrienaj
 

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


Re: LoTW user list 06/09/2009

 

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

Thanks, Renzo!

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of I6KZR
Sent: Sunday, September 06, 2009 3:26 PM
To: Lista Dxlab
Subject: [dxlab] LoTW user list 06/09/2009


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

73,

Renzo I6KZR


Re: cba and qrz

 

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


cba and qrz

 

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


Re: Losing Contact With Commander

 

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


Losing Contact With Commander

aburkefl
 

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


LoTW user list 06/09/2009

I6KZR
 

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


Re: SC and WW Questions

 

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