Date   
Re: Manually Entering Satellite Contacts to Catch Up?

Hasan Schiers N0AN
 

Thanks Joe, I have an "unusual" setup here that is not what anyone would typically do.

My SAT setup is on a separate computer, which also does my computer controlled AZ/EL (well, my EL is fixed at 15 deg).
It uses a FunCube Dongle Pro+ fed by an ARR GasFET. The antenna is an interlaced vertically polarized yagi. 5 EL on 2m and 8 EL on 70cm. It is fed thru a duplexer in the shack with 1/2" hardline up the tower. The software controlling it all is SDR Console v3. It controls my TS-2000 for uplink only as an "external" radio. 

The DXLab Suites Computer has a TS-590sg on it for HF and 6 meters.
That computer is 99% WSJT-X with 6m meteor scatter (MSK144), and FT8 and FT4 on HF in general.

So for sat purposes there is no "radio" to read freq from, as the radio connected to DXKeeper/Commander is a TS-590sg, which is obviously not a SAT radio! 

When entering sat data in non-real time or even real time, into DXKeeper, I have to override the freq in the log form, because it is getting that freq from TS-590sg. So ,each time, I put in 435 tx and 145 rx manually, along with the call, as well as the SAT Name and the SAT Xponder mode (B for example). Then when I hit LOG , it goes into the log and automagically up to LoTW.

If I forget to manually change the TX and RX freq in the log form b4 saving it, then it gets uploaded to LoTW with whatever freq my TS-590sg was already on. I have a recent LoTW entry showing I worked KB7IJ on XW-2B with an uplink and downlink freq of 5.357 (60 meters)....I bet that opened some eyes!

Thanks for the info. 73
N0AN
Hasan


On Thu, Dec 26, 2019 at 3:32 PM Joe Subich, W4TV <lists@...> wrote:
Hasan,

If your SDR satellite system is supported by SatPC32 you can configure
Commander to support a second "SATPC32" radio and log those satellite
QSOs in real time.

Just another advance capability of DXLab Suite that you might find
interesting to explore as you become more experienced with the
software.

73,

    ... Joe, W4TV


On 2019-12-26 2:44 PM, Hasan Schiers N0AN wrote:
> Thanks Dave,
>
> The issue is the main log screen does not have entries for SAT NAME and SAT
> MODE, so when those are automatically uploaded to LoTW, they do not go up
> as SAT qsos.
>
> I have DXK set for auto-upload and it works GREAT for the TS-590sg and
> WSJT-x with Commander. I can't tell you how impressed I am with that combo.
>
> So, what am I missing in terms of being able to manually enter a SAT QSO,
> so that when it is automatically uploaded to LoTW it will have the right
> info?
>
> Sorry to be so thick. But I'll catch on...  :-)
> 73, N0AN
> Hasan
>
>
> On Thu, Dec 26, 2019 at 12:59 PM Dave AA6YQ <aa6yq@...> wrote:
>
>> + AA6YQ comments below
>>
>> New user.
>>
>> + Welcome to DXLab, Hasan!
>>
>>
>> Amazingly good software. I can't find an answer to this situation in all
>> the docs I've searched thru. (Very good docs, btw)
>>
>> I keep a scratch pad of my satellite contacts as I work people. So I might
>> have 10 qsos to add to DXKeeper. The main log form doesn't seem to accept
>> SAT QSOs (need to have Sat Name and Mode (A,B,J, etc).
>>
>> The Capture won't let me enter a date and time....it want's to run in real
>> time.
>>
>> + That's correct. As described in the first sentence of
>>
>> <https://www.dxlabsuite.com/dxlabwiki/QSOCapture>
>>
>> + the Capture window is intended for real-time logging. More detail about
>> the Capture window is provided in the reference documentation:
>>
>> <https://www.dxlabsuite.com/dxkeeper/Help/LogNewCapture.htm>
>>
>>
>> I do not have a satellite radio connected to DXKeeper/Commnader. . I us an
>> SDR on  a different computer altogether. So what I need to do is simple
>> enough, I just don't see a way for it to happen.
>>
>> I want to be able to manually enter a satellite qso, where I specify the
>> date and times and frequencies and the program requests the SAT NAME and
>> MODE (SAT not operating mode) as it does in Capture. Then it should be a
>> simple matter of hitting LOG and two things happen:
>>
>> 1. It logs the qso
>> 2. It sends it to LoTW
>>
>> If I submit the sat qso in real time, it works, because it is setting the
>> time to "now'. This won't work for my paper log.
>>
>> Any ideas?
>>
>> + To record new QSOs after they have already been completed, use
>> DXKeeper's Main window's "Log QSOs" tab, as documented here:
>>
>> <https://www.dxlabsuite.com/dxkeeper/Help/LogNewMain.htm>'
>>
>> + Configuring DXKeeper for interoperation with LoTW is described here:
>>
>> <https://www.dxlabsuite.com/dxlabwiki/QSLingLotW>
>>
>> + If you wish, you can configure DXKeeper to automatically submit each
>> logged QSO to LoTW.
>>
>>         73,
>>
>>              Dave, AA6YQ





Re: Manually Entering Satellite Contacts to Catch Up?

Dave AA6YQ
 

+ AA6YQ comments below

If your SDR satellite system is supported by SatPC32 you can configure Commander to support a second "SATPC32" radio and log those satellite QSOs in real time.

Just another advance capability of DXLab Suite that you might find interesting to explore as you become more experienced with the software.

+ Hasan runs his satellite tracking operation on a separate computer. SatPC32 uses DDE to interoperate with Commander, which requires SatPC32 to run on the same computer that hosts Commander.

73,

Dave, AA6YQ

Re: Limiting submission to ones from single entity

Dave AA6YQ
 

+ AA6YQ comments below

Thanks for the quick response. I'll have to remove all the entries in his log that are made from his Curacao location. Not sure how many there are. I'll create another log just for those. I sure hope they didn't get mixed into his LOTW account somehow.

Just did a quick sql query and got 27900 qsos. I'll export them and import into a separate log. He must have had these mixed in with his others in his old logging software since I've intentionally avoided his DX logs so far.

I assume I should do the same for Costa Rica (TI9) and Hawaii (KH6)?

+ Yes. As stated in the documentation, DXKeeper assumes that all QSOs recorded in a log file were made from within the same DXCC entity:

<https://www.dxlabsuite.com/dxkeeper/Help/Log.htm#Log%20files>

73,

Dave, AA6YQ

Re: TQSL in Admin Mode After Updating via DXKeeper?

Dave AA6YQ
 

+ AA6YQ comments below

It is not checked "Run As Admin"

Neither is Commander
Neither is DX Keeper
Nor is Spot Collector
Nor is TQSL app that I have been running for years

+ Good!


So, I got the error when running the program (DXK) early on. It kept prompting me on every logged qso to fix the Admin issue or let it go this once, or do Admin from now on.

This was when it was trying to automagically upload to LoTW following a logged contact (I have that feature turned on)

I got tired of seeing it, so when prompted I said, from now on. That meant to me, I told it to run in Admin mode forever.

Now I'm really confused, cuz I can't find any setting on any of the Icons that tells me any of the above programs are being run as Admin.

Frm what I'm reporting, I don't have a problem and I should just forget what I told the program about Amin rights yesterday?

+ DXKeeper doesn't know anything about Admin rights. That was TQSL that you configured to stop complaining.


Befuddled!

+ Joe W4TV is correct -- another possible source of TQSL's prior complaint could be that your Windows account gives you Administrative privileges.

73,

Dave, AA6YQ

Re: Manually Entering Satellite Contacts to Catch Up?

Joe Subich, W4TV
 

Hasan,

If your SDR satellite system is supported by SatPC32 you can configure
Commander to support a second "SATPC32" radio and log those satellite
QSOs in real time.

Just another advance capability of DXLab Suite that you might find
interesting to explore as you become more experienced with the
software.

73,

... Joe, W4TV

On 2019-12-26 2:44 PM, Hasan Schiers N0AN wrote:
Thanks Dave,
The issue is the main log screen does not have entries for SAT NAME and SAT
MODE, so when those are automatically uploaded to LoTW, they do not go up
as SAT qsos.
I have DXK set for auto-upload and it works GREAT for the TS-590sg and
WSJT-x with Commander. I can't tell you how impressed I am with that combo.
So, what am I missing in terms of being able to manually enter a SAT QSO,
so that when it is automatically uploaded to LoTW it will have the right
info?
Sorry to be so thick. But I'll catch on... :-)
73, N0AN
Hasan
On Thu, Dec 26, 2019 at 12:59 PM Dave AA6YQ <@AA6YQ> wrote:

+ AA6YQ comments below

New user.

+ Welcome to DXLab, Hasan!


Amazingly good software. I can't find an answer to this situation in all
the docs I've searched thru. (Very good docs, btw)

I keep a scratch pad of my satellite contacts as I work people. So I might
have 10 qsos to add to DXKeeper. The main log form doesn't seem to accept
SAT QSOs (need to have Sat Name and Mode (A,B,J, etc).

The Capture won't let me enter a date and time....it want's to run in real
time.

+ That's correct. As described in the first sentence of

<https://www.dxlabsuite.com/dxlabwiki/QSOCapture>

+ the Capture window is intended for real-time logging. More detail about
the Capture window is provided in the reference documentation:

<https://www.dxlabsuite.com/dxkeeper/Help/LogNewCapture.htm>


I do not have a satellite radio connected to DXKeeper/Commnader. . I us an
SDR on a different computer altogether. So what I need to do is simple
enough, I just don't see a way for it to happen.

I want to be able to manually enter a satellite qso, where I specify the
date and times and frequencies and the program requests the SAT NAME and
MODE (SAT not operating mode) as it does in Capture. Then it should be a
simple matter of hitting LOG and two things happen:

1. It logs the qso
2. It sends it to LoTW

If I submit the sat qso in real time, it works, because it is setting the
time to "now'. This won't work for my paper log.

Any ideas?

+ To record new QSOs after they have already been completed, use
DXKeeper's Main window's "Log QSOs" tab, as documented here:

<https://www.dxlabsuite.com/dxkeeper/Help/LogNewMain.htm>'

+ Configuring DXKeeper for interoperation with LoTW is described here:

<https://www.dxlabsuite.com/dxlabwiki/QSLingLotW>

+ If you wish, you can configure DXKeeper to automatically submit each
logged QSO to LoTW.

73,

Dave, AA6YQ

Re: TQSL in Admin Mode After Updating via DXKeeper?

Joe Subich, W4TV
 

On 2019-12-26 4:02 PM, Hasan Schiers N0AN wrote:> So, I got the error when running the program (DXK) early on. It kept
prompting me on every logged qso to fix the Admin issue or let it go
this once, or do Admin from now on.
Contact Rick Murphy on the ARRL-LotW list. There is a reported issue
of this very error when running tQSL from DXKeeper on systems where
tQSL is installed on a system with a single ADMINISTRATOR account
(and no "user" level accounts).

73,

... Joe, W4TV


On 2019-12-26 4:02 PM, Hasan Schiers N0AN wrote:
It is not checked "Run As Admin"
Neither is Commander
Neither is DX Keeper
Nor is Spot Collector
Nor is TQSL app that I have been running for years
So, I got the error when running the program (DXK) early on. It kept
prompting me on every logged qso to fix the Admin issue or let it go this
once, or do Admin from now on.
This was when it was trying to automagically upload to LoTW following a
logged contact (I have that feature turned on)
I got tired of seeing it, so when prompted I said, from now on. That meant
to me, I told it to run in Admin mode forever.
Now I'm really confused, cuz I can't find any setting on any of the Icons
that tells me any of the above programs are being run as Admin.
Frm what I'm reporting, I don't have a problem and I should just forget
what I told the program about Amin rights yesterday?
Befuddled!
73, N0AN
Hasan
On Thu, Dec 26, 2019 at 2:41 PM Dave AA6YQ <@AA6YQ> wrote:

Thanks, Hasan. This group does not convey screenshots, as they would count
against the storage limits associated with a free Groups.io account, and I
want to maximize the availability of storage for information maintained in
the Groups' Files area.

Base on the information you've provided below, the question is whether the
Launcher is being started with Admin privileges. Since you're running on
Windows 10,

1. right-click the Launcher's desktop icon, and select Properties from the
pop-up menu

2. in the Properties window that appears, select the Shortcut tab

3. on Properties window's Shortcut tab, click the Advanced... button in
the lower-right corner

4. in the "Advanced Properties" window, is the "Run as Administrator" box
checked? If so, then

4a. uncheck the "Run as Administrator" box and click the "Advanced
Properties" window's OK button

4b. click the Properties window's OK button

4c. terminate all DXLab applications

4d. start the Launcher via its desktop icon

4e. direct the Launcher to start DXKeeper

Does TQSL complain about being started with Administrative privileges?

73,

Dave, AA6YQ



Win10 Pro, 8 gB RAM, Core I5


I installed from Launcher, using the defaults as presented.
C:\DXLab\
...all installed under that directory as expected.
At no point did I knowingly install any of DXLabs stuff as Admin. I was
aware how undesirable it was. I can't imagine the Launcher/Configuration
would install as Admin without some sort of warning and certainly not on
its own....so I must have done something stupid.


I started with the Launcher and its configuration setup.

I installed from it, DXK first, then DX Commander, other stuff later, all
from within the launcher.

I then RUN all programs via the Launcher.

I Terminated all DXL programs using the launcher. Now I'm going to start
them with "Start"

CMD went from Red to Yellow (assuming due to in minimized state.)

dsk is green and on screen.

dvc went from Red to Yellow (minimized)

pv is yellow (minimized); sc is yellow (minimized)

...ok, since I had the program create icons during install, I just went to
the Launcher and looked at properties. I have attached a screen capture of
it:

I won't send more info, I await your instructions, and thanks so much for
the help. 73, N0AN Hasan


On Thu, Dec 26, 2019 at 1:08 PM Dave AA6YQ <@AA6YQ> wrote:


+ AA6YQ comments below

When I first ran the program all was well. LoTW proceeded
normally. I've had TQSL installed for a long time and it works perfectly
when I bring it up and create a list to submit.

While running DXKeeper for the second time it came up with a
notice that TQSL could be upgraded. I let it do it. I did nothing special.

The nedxt thing I know every time I try to upload from DXK to
LoTW, I get an error about the Amin issue. Now I have to tell it to run in
Admin privilege or it won't work. I got so tired of this error, that I
finally (when given choice by DXK) told it to aways run in Admin mode.

How do I get out of this ....uhhhh....mess. ?

+ DXKeeper would only start TQSL with Administrative privileges if
DXKeeper were running with Administrative privileges -- an unnecessary and
undesirable situation.

+ Into what folder did you install DXKeeper?

+ How are you starting DXKeeper?

+ If you are starting DXKeeper via the DXLab Launcher, into what
folder did you install the Launcher, and how are you starting it?

+ If you're starting the Launcher from a Windows desktop icon,
please tell me what version of Windows you are running so I can explain how
you can determine if the Launcher's Desktop icon is configured to start the
Launcher with Administrative privileges (which would cause the Launcher to
start DXKeeper with Administrative privileges).

73,

Dave, AA6YQ

Re: Limiting submission to ones from single entity

Joe Subich, W4TV
 

On 2019-12-26 4:06 PM, Jim Miller, AB3CV wrote:

I sure hope they didn't get mixed into his LOTW account somehow.
It depends on which certificate he used to sign the uploads of
those QSOs. If his stateside certificate was used, the PJ4/TI/KH6
QSOs will be "mixed in." If the separate PJ4, TI and/or KH6
certificate (PJ4/CALL, TI/CALL, CALL/KH6) was used for the appropriate
QSOs, they will be found in separate LotW accounts.

73,

... Joe, W4TV


On 2019-12-26 4:06 PM, Jim Miller, AB3CV wrote:
Hi Dave
Thanks for the quick response. I'll have to remove all the entries in his log that are made from his Curacao location. Not sure how many there are. I'll create another log just for those. I sure hope they didn't get mixed into his LOTW account somehow.
Just did a quick sql query and got 27900 qsos. I'll export them and import into a separate log. He must have had these mixed in with his others in his old logging software since I've intentionally avoided his DX logs so far.
I assume I should do the same for Costa Rica (TI9) and Hawaii (KH6)?
Thanks!
Jim
Thanks
Jim ab3cv

Re: Amazing Replacement

Dave AA6YQ
 

+ AA6YQ comments below

I just wanted to quickly share with you my early experience with DXLabSuite

I tried to install it about 3 months ago and got no where. I just could not get a grip on things.

Yesterday I proceeded to download and install and it went pretty much painlessly. I have no idea why. I must have followed the directions by accident. ☺

Prior to your software, I had been using:

Logic9, powerful, confusing and clunky (slow response even on a fast machine) For Logging, Spotting and talking to TRX Manager

TRX Manager for Rig Control


QRZ both lookup and logging

WSJT-X and JTAlert

Manually uploading all SAT qsos via TQSL

Keeping all these things in sync had become a nightmare. I had a full page sheet of reconciliation instructions I wrote to myself !

After 6 hours yesterday, start to finish I had completely converted to DXLabSuite. Now all the functions I was doing piecemeal are unified under DXL!

Absolutely astounding. As my other posts indicate, I have a few things to iron out yet, but I truly regret waiting this long to convert.

Thanks so much for your efforts and let me know where and how to contribute!

73 and really do appreciate your help and the quality of the software.

+ Thanks for the report and kind thoughts, Hasan!

+ However, I must point out that you are at risk of a trap into which some new DXLab users fall: attempting to instantly replicate the functionality they've been using for years in a previous application or set of applications. If you've been using those previous applications for any significant length of time, your interactions are practically automatic, burned in to the layers of your neocortex along with riding a bicycle, walking, and eating; it will take weeks or months to gain this automatic level of facility with DXLab. Attempting to get there too quickly can result in terminal frustration. To avert this risk, please review the first section of

<https://www.dxlabsuite.com/dxlabwiki/GettingStarted>

+ Go slow, and enjoy the process of traversing DXLab's learning curve, which is non-trivial. You already know to post questions here; such questions are always welcome, no matter how many times they've already been asked and answered, or how obvious the answers might be in the documentation.

+ I do not accept contributions. I develop DXLab because I enjoy developing software in direct collaboration with users; many of DXLab's most useful capabilities are the result of interactions in this group. If you absolutely must make a monetary contribution, I recommend St. Jude's Children's Hospital, which does excellent work with modest administrative overhead. A review of your experience in

<https://www.eham.net/reviews/view-product?id=3139>

+ would also be appreciated.

73,

Dave, AA6YQ

Re: Limiting submission to ones from single entity

Jim Miller, AB3CV
 
Edited

Hi Dave

Thanks for the quick response. I'll have to remove all the entries in his log that are made from his Curacao location. Not sure how many there are. I'll create another log just for those. I sure hope they didn't get mixed into his LOTW account somehow.

To be clear contacts made from his USA station are being included in submissions whether Curacao or other. It's just that a station from Paraguay sent him a card for a QSO made when he was in Curacao which he noted in his log in his old software and now shows up as a submission candidate for his USA log. That will go away when I move out the QSOs made from DX locations.

Just did a quick sql query and got 27900 PJ2 based qsos. I'll export them and import into a separate log. He must have had these mixed in with his others in his old logging software since I've intentionally avoided his DX logs so far.

I assume I should do the same for Costa Rica (TI5) and Hawaii (KH6)?

Thanks!

Jim



Thanks

Jim ab3cv

Re: TQSL in Admin Mode After Updating via DXKeeper?

Hasan Schiers N0AN
 

It is not checked "Run As Admin"

Neither is Commander
Neither is DX Keeper
Nor is Spot Collector
Nor is TQSL app that I have been running for years

So, I got the error when running the program (DXK) early on. It kept prompting me on every logged qso to fix the Admin issue or let it go this once, or do Admin from now on.

This was when it was trying to automagically upload to LoTW following a logged contact (I have that feature turned on)

I got tired of seeing it, so when prompted I said, from now on. That meant to me, I told it to run in Admin mode forever.

Now I'm really confused, cuz I can't find any setting on any of the Icons that tells me any of the above programs are being run as Admin. 

Frm what I'm reporting, I don't have a problem and I should just forget what I told the program about Amin rights yesterday?

Befuddled! 

73, N0AN
Hasan


On Thu, Dec 26, 2019 at 2:41 PM Dave AA6YQ <aa6yq@...> wrote:
Thanks, Hasan. This group does not convey screenshots, as they would count against the storage limits associated with a free Groups.io account, and I want to maximize the availability of storage for information maintained in the Groups' Files area.

Base on the information you've provided below, the question is whether the Launcher is being started with Admin privileges. Since you're running on Windows 10,

1. right-click the Launcher's desktop icon, and select Properties from the pop-up menu

2. in the Properties window that appears, select the Shortcut tab

3. on Properties window's Shortcut tab, click the Advanced... button in the lower-right corner

4. in the "Advanced Properties" window, is the "Run as Administrator" box checked? If so, then

4a. uncheck the "Run as Administrator" box and click the "Advanced Properties" window's  OK button

4b. click the Properties window's OK button

4c. terminate all DXLab applications

4d. start the Launcher via its desktop icon

4e. direct the Launcher to start DXKeeper

Does TQSL complain about being started with Administrative privileges?

          73,

                Dave, AA6YQ



Win10 Pro, 8 gB RAM, Core I5


I installed from Launcher, using the defaults as presented.
C:\DXLab\
...all installed under that directory as expected.
At no point did I knowingly install any of DXLabs stuff as Admin. I was aware how undesirable it was. I can't imagine the Launcher/Configuration would install as Admin without some sort of warning and certainly not on its own....so I must have done something stupid.


I started with the Launcher and its configuration setup.

I installed from it, DXK first, then DX Commander, other stuff later, all from within the launcher.

I then RUN all programs via the Launcher.

I Terminated all DXL programs using the launcher. Now I'm going to start them with "Start"

CMD went from Red to Yellow (assuming due to in minimized state.)

dsk is green and on screen.

dvc went from Red to  Yellow (minimized)

pv is yellow (minimized); sc is yellow (minimized)

...ok, since I had the program create icons during install, I just went to the Launcher and looked at properties. I have attached a screen capture of it:

I won't send more info, I await your instructions, and thanks so much for the help. 73, N0AN Hasan


On Thu, Dec 26, 2019 at 1:08 PM Dave AA6YQ <aa6yq@...> wrote:


        + AA6YQ comments below

        When I first ran the program all was well. LoTW proceeded normally. I've had TQSL installed for a long time and it works perfectly when I bring it up and create a list to submit.

        While running DXKeeper for the second time it came up with a notice that TQSL could be upgraded. I let it do it. I did nothing special.

        The nedxt thing I know every time I try to upload from DXK to LoTW, I get an error about the Amin issue. Now I have to tell it to run in Admin privilege or it won't work. I got so tired of this error, that I finally (when given choice by DXK) told it to aways run in Admin mode.

        How do I get out of this ....uhhhh....mess. ?

        + DXKeeper would only start TQSL with Administrative privileges if DXKeeper were running with Administrative privileges -- an unnecessary and undesirable situation.

        + Into what folder did you install DXKeeper?

        + How are you starting DXKeeper?

        + If you are starting DXKeeper via the DXLab Launcher, into what folder did you install the Launcher, and how are you starting it?

        + If you're starting the Launcher from a Windows desktop icon, please tell me what version of Windows you are running so I can explain how you can determine if the Launcher's Desktop icon is configured to start the Launcher with Administrative privileges (which would cause the Launcher to start DXKeeper with Administrative privileges).

                  73,

                        Dave, AA6YQ









 <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: Limiting submission to ones from single entity

Dave AA6YQ
 

+ AA6YQ comments below

I've generated submissions many times before for cards but I've always been a single entity operator. I'm generating a submission from someone who has operated also from Curacao and an entry is showing for that entity as well. He has no need or interest to submit a card for credit from that location.

How do I tell the Submission process to only consider cards that would advance Challenge from the current USA location?

+ Your friend's log should not contain any QSOs made from Curacao; such QSOs should be maintained in a separate Curacao-only log.

+ The fact that your friend has operated from Curacao doesn't invalidate Curacao-bands as points in the DXCC Challenge, thus there is no reason to not include them in a DXCC submission, as DXKeeper's DXCC Submission Generator will automatically do. If your friend really doesn't want to include any QSOs with stations in Curacao in his DXCC applications, set the "QSL Rcvd" item of each such QSO to 'I', meaning "not valid for DXCC"; DXKeeper's DXCC Submission Generator will then ignore them.

73,

Dave, AA6YQ

Re: TQSL in Admin Mode After Updating via DXKeeper?

Dave AA6YQ
 

Thanks, Hasan. This group does not convey screenshots, as they would count against the storage limits associated with a free Groups.io account, and I want to maximize the availability of storage for information maintained in the Groups' Files area.

Base on the information you've provided below, the question is whether the Launcher is being started with Admin privileges. Since you're running on Windows 10,

1. right-click the Launcher's desktop icon, and select Properties from the pop-up menu

2. in the Properties window that appears, select the Shortcut tab

3. on Properties window's Shortcut tab, click the Advanced... button in the lower-right corner

4. in the "Advanced Properties" window, is the "Run as Administrator" box checked? If so, then

4a. uncheck the "Run as Administrator" box and click the "Advanced Properties" window's OK button

4b. click the Properties window's OK button

4c. terminate all DXLab applications

4d. start the Launcher via its desktop icon

4e. direct the Launcher to start DXKeeper

Does TQSL complain about being started with Administrative privileges?

73,

Dave, AA6YQ



Win10 Pro, 8 gB RAM, Core I5


I installed from Launcher, using the defaults as presented.
C:\DXLab\
...all installed under that directory as expected.
At no point did I knowingly install any of DXLabs stuff as Admin. I was aware how undesirable it was. I can't imagine the Launcher/Configuration would install as Admin without some sort of warning and certainly not on its own....so I must have done something stupid.


I started with the Launcher and its configuration setup.

I installed from it, DXK first, then DX Commander, other stuff later, all from within the launcher.

I then RUN all programs via the Launcher.

I Terminated all DXL programs using the launcher. Now I'm going to start them with "Start"

CMD went from Red to Yellow (assuming due to in minimized state.)

dsk is green and on screen.

dvc went from Red to Yellow (minimized)

pv is yellow (minimized); sc is yellow (minimized)

...ok, since I had the program create icons during install, I just went to the Launcher and looked at properties. I have attached a screen capture of it:

I won't send more info, I await your instructions, and thanks so much for the help. 73, N0AN Hasan

On Thu, Dec 26, 2019 at 1:08 PM Dave AA6YQ <@AA6YQ> wrote:


+ AA6YQ comments below

When I first ran the program all was well. LoTW proceeded normally. I've had TQSL installed for a long time and it works perfectly when I bring it up and create a list to submit.

While running DXKeeper for the second time it came up with a notice that TQSL could be upgraded. I let it do it. I did nothing special.

The nedxt thing I know every time I try to upload from DXK to LoTW, I get an error about the Amin issue. Now I have to tell it to run in Admin privilege or it won't work. I got so tired of this error, that I finally (when given choice by DXK) told it to aways run in Admin mode.

How do I get out of this ....uhhhh....mess. ?

+ DXKeeper would only start TQSL with Administrative privileges if DXKeeper were running with Administrative privileges -- an unnecessary and undesirable situation.

+ Into what folder did you install DXKeeper?

+ How are you starting DXKeeper?

+ If you are starting DXKeeper via the DXLab Launcher, into what folder did you install the Launcher, and how are you starting it?

+ If you're starting the Launcher from a Windows desktop icon, please tell me what version of Windows you are running so I can explain how you can determine if the Launcher's Desktop icon is configured to start the Launcher with Administrative privileges (which would cause the Launcher to start DXKeeper with Administrative privileges).

73,

Dave, AA6YQ









<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>

Amazing Replacement

Hasan Schiers N0AN
 

Dave,
I just wanted to quickly share with you my early experience with DXLabSuite

I tried to install it about 3 months ago and got no where. I just could not get a grip on things.

Yesterday I proceeded to download and install and it went pretty much painlessly. I have no idea why. I must have followed the directions by accident. ☺

Prior to your software, I had been using:

Logic9, powerful, confusing and clunky (slow response even on a fast machine) For Logging, Spotting and talking to TRX Manager 

TRX Manager for Rig Control

QRZ both lookup and logging

WSJT-X and JTAlert

Manually uploading all SAT qsos via TQSL

Keeping all these things in sync had become a nightmare. I had a full page sheet of reconciliation instructions I wrote to myself !

After 6 hours yesterday, start to finish I had completely converted to DXLabSuite. Now all the functions I was doing piecemeal are unified under DXL! 

Absolutely astounding. As my other posts indicate, I have a few things to iron out yet, but I truly regret waiting this long to convert.

Thanks so much for your efforts and let me know where and how to contribute!

73 and really do appreciate your help and the quality of the software.
N0AN
Hasan

Re: SpotCollector Font Color for unworked / unconfirmed

Dave AA6YQ
 

+ AA6YQ comments below

When clicking ctrl-need in SC I currently see 3 entities i.e. Sri Lanka, Ukraine and Austria (all in red font). Double Clicking each one followed by clicking DXCC in DXK's Log Page Display shows many previous QSO's that have been completed (including those that are Confirmed, Verified and / or worked) for each.

+ Thanks, Curt. Please do the following:

1. On the Awards tab of DXKeeper's Configuration window, check the "Automatically recompute realtime award tracking" box if it isn't already checked

2. At the bottom of the "Check Progress" tab of DXKeeper's Main window, click the Recompute button; this will rebuild your log's DXCC progress table (to which SpotCollector refers when determining "need") by scanning your logged QSOs

3. When step 3 has completed, on the "Spot Database" tab of SpotCollector's Configuration window, click the Recompute button; this will cause SpotCollector to update the "neededness" of each Spot Database Entry based on the updated DXCC Progress table created by step 2

+ Now depress the CTRL key while clicking the Need button in SpotCollector's Filter panel; do you still see entries for stations in entities that are not ATNOs?

+ Note: Step 1 above will eliminate the need to perform steps 2 and 3 in the future.

73,

Dave, AA6YQ

Limiting submission to ones from single entity

Jim Miller, AB3CV
 

I've generated submissions many times before for cards but I've always been a single entity operator. I'm generating a submission from someone who has operated also from Curacao and an entry is showing for that entity as well. He has no need or interest to submit a card for credit from that location. 

How do I tell the Submission process to only consider cards that would advance Challenge from the current USA location?

Thanks

Jim ab3cv

Re: Manually Entering Satellite Contacts to Catch Up?

Hasan Schiers N0AN
 

Tnx Dave and Bill,
Worked fine by adding Prop, tested, upload is correct to LoTW
73, N0AN
Hasan


On Thu, Dec 26, 2019 at 2:23 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

those fields are on the Propagation panel, you probably have that disabled, check the tick box to the right of the other panels.

+ DXKeeper can record more than 100 items in each QSO, accessible via 9 panels on the Main window's "Log QSOs" tab. Only the panel labeled "QSO" - which contains basic items like callsign, RX and TX frequencies, mode, date, time, and DXCC entity - is permanently visible. The list of all items and the panels in which they are made accessible is here:

<https://www.dxlabsuite.com/dxkeeper/Help/Items.htm>

+ The primary means by which panels on the "Log Page Display" are made visible is the set of checkboxes provided in the "Log Panels" panel on the Configuration window's General tab, as documented here:

<https://www.dxlabsuite.com/dxkeeper/Help/Configuration.htm#Log%20Panels%20Panel>

+ As Bill G4WJS pointed out above, a vertical array of identically-functional checkboxes is for convenience provided to the right of the QSO panel at the top of the Main window's Log Page Display; you may have to expand the horizontal width of the window to see these checkboxes.

       73,

              Dave, AA6YQ




Re: Manually Entering Satellite Contacts to Catch Up?

Dave AA6YQ
 

+ AA6YQ comments below

those fields are on the Propagation panel, you probably have that disabled, check the tick box to the right of the other panels.

+ DXKeeper can record more than 100 items in each QSO, accessible via 9 panels on the Main window's "Log QSOs" tab. Only the panel labeled "QSO" - which contains basic items like callsign, RX and TX frequencies, mode, date, time, and DXCC entity - is permanently visible. The list of all items and the panels in which they are made accessible is here:

<https://www.dxlabsuite.com/dxkeeper/Help/Items.htm>

+ The primary means by which panels on the "Log Page Display" are made visible is the set of checkboxes provided in the "Log Panels" panel on the Configuration window's General tab, as documented here:

<https://www.dxlabsuite.com/dxkeeper/Help/Configuration.htm#Log%20Panels%20Panel>

+ As Bill G4WJS pointed out above, a vertical array of identically-functional checkboxes is for convenience provided to the right of the QSO panel at the top of the Main window's Log Page Display; you may have to expand the horizontal width of the window to see these checkboxes.

73,

Dave, AA6YQ

Re: Manually Entering Satellite Contacts to Catch Up?

Hasan Schiers N0AN
 

Aha! Thanks Bill, as soon as I went to Config  > Log Panel > and checked Propagation, the main log form showed :
Drop down for mode : SAT
Drop down for name : like XW-2B
Drop down for mode (xponder mode, not op mode) liek Mode B or A or J

I assume if I need to enter my paper notes on the log form, it will now include that info in the LoTW submission, is that right?
So when I put a contact in the log form manually, and then right click on it after it has been saved and shows in the log, will allow me to upload directly that qso to LoTW. I'll put a dummy qso in there with KB7IJ ...whom I have worked hundreds of times on the sats.

73, N0AN

73, N0AN

Hasan


On Thu, Dec 26, 2019 at 1:59 PM g4wjs <bill.8@...> wrote:
On 26/12/2019 19:44, Hasan Schiers N0AN wrote:
> The issue is the main log screen does not have entries for SAT NAME
> and SAT MODE

Hi Hasan,

those fields are on the Propagation panel, you probably have that
disabled, check the tick box to the right of the other panels.



--
73

Bill

G4WJS.



Re: TQSL in Admin Mode After Updating via DXKeeper?

Hasan Schiers N0AN
 

Win10 Pro, 8 gB RAM, Core I5


I installed from Launcher, using the defaults as presented.
C:\DXLab\
...all installed under that directory as expected.
At no point did I knowingly install any of DXLabs stuff as Admin. I was aware how undesirable it was. I can't imagine the Launcher/Configuration would install as Admin without some sort of warning and certainly not on its own....so I must have done something stupid.


I started with the Launcher and its configuration setup.

I installed from it, DXK first, then DX Commander, other stuff later, all from within the launcher.

I then RUN all programs via the Launcher.

I Terminated all DXL programs using the launcher. Now I'm going to start them with "Start"

CMD went from Red to Yellow (assuming due to in minimized state.)

dsk is green and on screen.

dvc went from Red to  Yellow (minimized)

pv is yellow (minimized); sc is yellow (minimized)

...ok, since I had the program create icons during install, I just went to the Launcher and looked at properties. I have attached a screen capture of it:

I won't send more info, I await your instructions, and thanks so much for the help. 73, N0AN
Hasan


On Thu, Dec 26, 2019 at 1:08 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

When I first ran the program all was well. LoTW proceeded normally. I've had TQSL installed for a long time and it works perfectly when I bring it up and create a list to submit.

While running DXKeeper for the second time it came up with a notice that TQSL could be upgraded. I let it do it. I did nothing special.

The nedxt thing I know every time I try to upload from DXK to LoTW, I get an error about the Amin issue. Now I have to tell it to run in Admin privilege or it won't work. I got so tired of this error, that I finally (when given choice by DXK) told it to aways run in Admin mode.

How do I get out of this ....uhhhh....mess. ?

+ DXKeeper would only start TQSL with Administrative privileges if DXKeeper were running with Administrative privileges -- an unnecessary and undesirable situation.

+ Into what folder did you install DXKeeper?

+ How are you starting DXKeeper?

+ If you are starting DXKeeper via the DXLab Launcher, into what folder did you install the Launcher, and how are you starting it?

+ If you're starting the Launcher from a Windows desktop icon, please tell me what version of Windows you are running so I can explain how you can determine if the Launcher's Desktop icon is configured to start the Launcher with Administrative privileges (which would cause the Launcher to start DXKeeper with Administrative privileges).

          73,

                Dave, AA6YQ





Re: SpotCollector Font Color for unworked / unconfirmed

Curtis WX4W
 

Dave,  When clicking ctrl-need in SC I currently see 3 entities i.e. Sri Lanka, Ukraine and Austria (all in red font).  Double Clicking each one followed by clicking DXCC in DXK's Log Page Display shows many previous QSO's that have been completed (including those that are Confirmed, Verified and / or worked) for each.