开云体育

In Pathfinder's Config window, Vlad, did you update the QRZ.com URL to

{TargetCallsign}

73,

Dave, AA6YQ

--- In dxlab@..., Vlad_UA6JD <ua6jw@...> wrote:

Dave-
just test and same problem - if I push CBA in DXK "No Call Found" and
PF windows :

Ooops... That page wasn't found on QRZ

callsign of call from DXK is on PF window OK!
then I push QRZ on PF and it work OK -
I think a problem with data transmission from DXK to PF
because PF separately works well

Using - PF v 4.5.7 , DXK v 8.1.6
--
73 Vlad UA6JD

gadgets to your www.qrz.com
examples www.qrz.com/db/ua6jd
just double-click and install

You wrote :

AA6YQ comments below

--- In dxlab@..., Tom Roberts <ac5rd@> wrote:

Your Call, comes up with out error on both the QRZ and Buck,
however when the calls are entered through the DXKeeper it states "No Call Found".
???
Sorry I did not give you all the information you required and be
more specific in regards to my problem.
???
I am certain it is due to the new QRZ Software in place. It occurred at that time.

I disagree, Tom. Pathfinder is working correctly here. Furthermore, a change in the QRZ web site would not cause your Buckmaster Hamcall search to suddenly stop working. My suspicion is that your Firewall (or some other anti-malware application) is preventing Pathfinder from accessing the internet.

73,

Dave, AA6YQ

Dave-
just test and same problem - if I push CBA in DXK "No Call Found" and
PF windows :

Ooops... That page wasn't found on QRZ

callsign of call from DXK is on PF window OK!
then I push QRZ on PF and it work OK -
I think a problem with data transmission from DXK to PF
because PF separately works well

Using - PF v 4.5.7 , DXK v 8.1.6
--
73 Vlad UA6JD

gadgets to your www.qrz.com
examples www.qrz.com/db/ua6jd
just double-click and install

You wrote :

AA6YQ comments below

--- In dxlab@..., Tom Roberts <ac5rd@> wrote:

Your Call, comes up with out error on both the QRZ and Buck,
however when the calls are entered through the DXKeeper it states "No Call Found".
?
Sorry I did not give you all the information you required and be
more specific in regards to my problem.
?
I am certain it is due to the new QRZ Software in place. It occurred at that time.

I disagree, Tom. Pathfinder is working correctly here. Furthermore, a change in the QRZ web site would not cause your Buckmaster Hamcall search to suddenly stop working. My suspicion is that your Firewall (or some other anti-malware application) is preventing Pathfinder from accessing the internet.

73,

Dave, AA6YQ

AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
k7eg
Sent: Tuesday, September 08, 2009 12:11 AM
To: dxlab@...
Subject: [dxlab] DXCC Submission Report Issue


Question - When a DX credit is confirmed by LOTW doesn't a QSL held for
credit get removed from the submission list? If not, it should.

I was holding two entity QSLs for submission to DXCC. I indicated they
should be added to the submission list when I received the cards.
Subsequently, those were confirmed via LOTW. Today, I prepared a submission
report to send cards to DXCC desk. The report indicated I still needed to
submit these two entity cards even though I now had LOTW credit.

Hopefully this is an anomaly and not a bug.

It is neither.

A "submission" is a set of QSOs whose "QSL_RCVD" or "LotW_QSL_RCVD" items

are set to 'S'. These items may have been set to 'S' by you manually, or
they may have been set to 'S' by DXKeeper's Submission generator. Initially,
the set of QSOs so marked is a set you intend to send to the ARRL's DXCC
desk; then they become a set that you have conveyed to the DXCC desk, and
finally a set that the DXCC desk has reviewed and acted upon prior to your
seeing the results of their action.

If during this process, a member of the submission initially confirmed by

QSL card is confirmed via LotW, what should DXKeeper do? For all it knows,
the QSO in question could have already been conveyed to the DXCC desk, or
even verified by that organization. For DXKeeper to unilaterally demote the
QSO's "QSL_RCVD" from 'S' to 'Y' would be incorrect; that would produce an
incorrect result were you to invoke the "Verify Submission" operation after
receiving notice that your submission had been entirely approved.

What DXKeeper should do in this circumstance is include in its summary of

the "Sync LotW QSLs" operation's results an indication that a QSO marked
"submitted" has been newly confirmed via LotW; you can then decide what
action is appropriate given the actual state of the submission. I'll ensure
that the next version of DXKeeper does this.

73,

Dave, AA6YQ

Your initial report stated that at some point, "Commander did not 'follow'
the radio". This is the time to enable "log debugging info" for a minute or
two, then disable it and send me the resulting errorlog.txt file. I just
need to see what commands are being sent to your K3, and how your K3 is
responding to those commands.

73,

Dave, AA6YQ

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of
aburkefl
Sent: Monday, September 07, 2009 8:00 AM
To: dxlab@...
Subject: [dxlab] Re: Losing Contact With Commander


Not exactly certain how to engage this scenario. If I turn on "log
debugging" and don't lose control, you'll learn nothing. If I work for a
while and then discover I've lost contact with Commander, that won't help
either, will it?

How large can the file get before it will give you problems? I could turn
debugging on first thing and then run as normal as possible (at least as
normally as I've been running!), but the debugging file might get kind of
large.

Art - N4PJ

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

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

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

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

aburkefl wrote:

What are the names of some of the popular (and successful!) programs that will disable anything running in the background that doesn't need to be running when running amateur applications (like DXKeeper or other parts of the DXLab suite)?

Thanks.

Art - N4PJ

I use Game Booster. While this little program was designed for serious
game players, it will do what you are asking. Freeware. Works for me,
but there may be other, better programs that I don't know about.

73,

--
Ken K4XL
k4xl@...

*** BoatAnchor Manual Archive ***
On the web at and
FTP site info: bama.sbc.edu login: anonymous p/w: youremailadr

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

If you want your RST items initialized to but don't want the QSO's start

Note that if you log a QSO without having clicked the Begin button,

AA6YQ comments below

By default, a QSO's start time is set when you click the Main window's

On the Config window's Log tab, enabling the "set QSO start when RST

On the Config window's Log tab, there is also an "initialize RST items to

If you want your RST items initialized to but don't want the QSO's start

Note that if you log a QSO without having clicked the Begin button,

Not at all, Jim. Providing answers to questions is one of the fundamental