Date   

Re: New computer - Launcher starts but does not display

Dave AA6YQ
 

+ AA6YQ comments below

Thank-you for your reply and suggestions.

I rebooted into "safe mode with networking" and the Launcher started up as expected. I am not running any third party anti virus or anti malware software - just what comes with Windows 10.

What is my next step?

+ Update Windows Defender to its latest malware definitions in

https://www.microsoft.com/en-us/wdsi/definitions

+ and configure it to consider the DXLabLauncher.exe (in your Launcher folder) to be "safe".

73,

Dave, AA6YQ


Re: ADIF Import and DUPES

Dave AA6YQ
 

+ AA6YQ comments below

I guess the only thing in my log file Id still like to get cleaned up is the "R" Requested calls. Ive got 535 of them remaining and I'm not sure how to clear those up.

+ What's an "R" Requested call?

73,

Dave, AA6YQ


Databases not upgrading

Ted Boerkamp
 

Hello all…I have just started to notice for a week now that when I try to upgrade

the LOTW and eQSL AG databases, nothing happens. My cursor has a swirling circle

on it but nothing happens. If I perform an upgrade on a part of the program ie. Commander

then it updates it no problem. I have never had this issue before and wondered if

someone can help me get the upgrades working again??

Thanks

 

Ted VE3SS


Re: New computer - Launcher starts but does not display

sheldon.page@...
 

HI Dave.

Some additional info:

1. I just noticed that the Launcher eventually displays - after about 5 minutes. It runs very slowly and freezes. This is not the case in safe mode with networking - it runs as expected.

2. Launcher is the only application that I have noticed that is having this trouble. Everything else runs as expected.

Sheldon


Re: New computer - Launcher starts but does not display

sheldon.page@...
 

Hi Dave.

Thank-you for your reply and suggestions.

I rebooted into "safe mode with networking" and the Launcher started up as expected. I am not running any third party anti virus or anti malware software - just what comes with Windows 10.

What is my next step?

Your help is greatly appreciated. DxLabs is the hub for all my operating - from controlling my Flex 6400 to working FT8, logging. etc. The new laptop is what I plan to do all my operating on.

Sheldon - VE1SJP


Re: ADIF Import and DUPES

Kirk, N0KK
 

Thank you for the tips.

In my situation, I'm running multiple versions of WSJTX on multiple radios/SDR receivers at the same time. Also on 2 pcs.

Some have JTDX running as well. At times I'll even have a writelog program logging stations. Not all of them work/log automatically with DX Labs simultaneously. I should say, Ive not found a way to do so perhaps.

I did have import setting as you've suggested here. I decreased the time to 30 minutes.
Latest attempt at bringing in a file worked as it should and has been. Why last week a couple files leaked past dupe checking Ive no clue. Ive since removed all dupes from the log of over 50k qsos

I guess the only thing in my log file Id still like to get cleaned up is the "R" Requested calls. Ive got 535 of them remaining and I'm not sure how to clear those up.
If anyone can lend suggestions Id sure appreciate that.


Re: Commander and Flex frequency changing

Dave AA6YQ
 

Tim, I received the errorlog you sent me, analyzed it, and sent you a response -- but my message was rejected as undeliverable.

You had reported that "If I click on Panadapter B to move frequency, and couple of seconds later it shifts Panadapter to the new frequency also.....a few minutes ago, without any intervention by me, Panadapter A changed to the frequency on Panadapter B This only occurs when commander is active"

The errorlog you captured of this happening shows that Commander sent no frequency change commands to your transceiver.

       73,

               Dave, AA6YQ

 



On Wed, Mar 24, 2021 at 03:18 PM, Dave AA6YQ wrote:

+ AA6YQ comments below

I have a Flex 6700. Sometimes.....when I have more than two Panadapters open, for example, 3.525 and 7.025, If I click on Panadapter B to move frequency, and couple of seconds later it shifts Panadapter to the new frequency also.....a few minutes ago, without any intervention by me, Panadapter A changed to the frequency on Panadapter B This only occurs when commander is active.

+ In FlexRadio's SmartSDR, panadaptors are not named. In a 6700, there are 8 slices named A though H, each of which function as a VFO. DXLab treats slices A and B as VFOs A and B in a traditional transceiver; it ignores the other slices.

+ So that I can see what's going on, please do the following:

1. configure SmartSDR to display two panadaptors, one showing Slice A (VFO A) at 3.525, and the other showing Slice B (VFO B) at 7.025

2. on the General tab of Commander's Configuration window, check the "Log debugging info" box

3. terminate Commander

4. start Commander, and wait for Commander to fully initialize

5. replicate the behavior in which clicking on Slice B to move its frequency causes Slice A's frequency to change; when you've replicated this behavior, please make no further changes to either Slice A or Slice B's frequencies.

6. on the General tab of Commander's Configuration window, uncheck the "Log debugging info" box

7. attach the errorlog.txt file from your Commander folder to an email message, and send the email message to me via

aa6yq (at) ambersoft.com


Re: Spot collector not showing spots

Dave AA6YQ
 

+ AA6YQ comments below
Suddenly on it's own the spots are not showing at all. I am connected to the cluster but the collector is not showing spots. It's the strangest deal
+ see

https://www.dxlabsuite.com/dxlabwiki/EmptyDatabase

+ If that doesn't get you going, Sean, please let me know.

      73,

             Dave, AA6YQ


Spot collector not showing spots

Sean D. Fleming (K8KHZ)
 

Suddenly on it's own the spots are not showing at all. I am connected to the cluster but the collector is not showing spots. It's the strangest deal


Re: Club Log Upload Status

w6de
 

Most of the time when I have a questionable contact and I intentionally again work that station for an "insurance" contact, and I feel better about the insurance contact, I will go back and mark the first contact N. Both contacts will usually appear sequentially in my log. So I can easily find and go back and submit the first contact if I don't get a confirmation. This is a semi-regular occurrence when I'm chasing weak DX stations I need for a DX Award. For this reason I don't select "Auto upload" in the DXKeeper, QSL Configuration file for ClubLog. I usually upload to Club Log after each operating session unless I've done an intentional duplicate QSO.

Most DX stations I still need are the result of DXpeditions that upload to ClubLog during or after the operating event. After their DXpedition is done, I check their ClubLog uploads and I'll go back and clear or set my DXKeeper logbook as appropriate.

73,
Dave, w6de

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ via groups.io
Sent: Thursday, March 25, 2021 00:28
To: DXLab@groups.io
Subject: Re: [DXLab] Club Log Upload Status

+ AA6YQ comments below

While reading up on Clublog Uploads I seen there is a status item that can be Y, N and M. I understand Y and M but don't get the notion of N.

+ 'N' means "this QSO will not be uploaded to ClubLog by the ClubLog Update function"

What would cause N to be set?

+ User action, e.g. for a QSO whose callsign of which you are unsure. None of DXKeeper's automation sets a QSO's "Club Log Status" item to 'N'.

73,

Dave, AA6YQ


Re: Alternate feed to SpotCollector

Dick Grote
 

Dave, thanks for your reply and explanation.  Forwarding spots to the cluster network is in the medium turn plans of the POTA developers I understand.  I'll sit tight until then.  

73,
--
Dick
K6PBF


Re: Alternate feed to SpotCollector

Dave AA6YQ
 

+ AA6YQ comments below
've found that chasing POTA's to be a lot of fun.  I've created a POTA SQL filter on SpotCollector based on notes in the spots, but I've found that the spots captured in this manner is a small fraction of the spots that are posted on the POTA website (https://pota.us/#/spots).  The question I have is there a way to feed this web based spot source into SpotCollector. I know there are other situations where this could be useful such as special spotting sites for state QSO parties.

I've thought of scraping spots and creating a local cluster feed, but I have not idea whether is possible or practical.  Any thoughts?
+ The spots on that page are dynamically generated, so there is no HTML to scrape. The only way to get that content into SpotCollector is to convince the operators of  https://pota.us/#/spots to forward their spots to the cluster network, as the DX Summit operators did more than a decade ago.

       73,

              Dave, AA6YQ


Re: RF (Power) of the Commander

Carlo - IK2RPE
 

No problem at all. Thank you Dave

 

 

Carlo  IK2RPE

 

 

 

Da: DXLab@groups.io <DXLab@groups.io> Per conto di Dave AA6YQ
Inviato: venerdì 26 marzo 2021 17:34
A: DXLab@groups.io
Oggetto: Re: [DXLab] RF (Power) of the Commander

 

+ AA6YQ comments below

Is it possible to have - when I log a QSO - that in DxKeeper pane Log_QSOs>QSO>Power is reported the actual RF (Power) appearing in Commander when RF is enabled in "Xmit Meter" **instead** of the power set in DxKeeper Config>Defaults>Default_Transmit_Power_by_band?

+ Not at present, That could only be done for the subset of transceivers that can be directed to report their RF output, and the result would be inaccurate if a linear amplifier were in use. Technically straightforward, but a lot of development and remote testing would be required for what seems like relatively low value.

       73,

              Dave, AA6YQ


Mail priva di virus. www.avg.com


Re: WSJT v2.4 rc-4 ADIF

g4wjs
 

On 26/03/2021 17:00, Jim Miller, AB3CV wrote:

[Edited Message Follows]

I see in the release notes they've adopted ADIF recommendation of mode: MFSK, submode:Q65.

Does this mean it's now in the ADIF spec and ready for adoption by loggers like DXlabs?

73

jim ab3cv
Hi Jim,

as far as I know it is still proposed but not yet released in a new ADIF specification. I would expect any competent consumer of ADIF log records to accept MODE="Q65" as well as what will probably become strictly correct, i.e. MODE="MFSK", SUBMODE="Q65".

73
Bill
G4WJS.



--
73

Bill

G4WJS.


WSJT v2.4 rc-4 ADIF

Jim Miller, AB3CV
 
Edited

I see in the release notes they've adopted ADIF recommendation of mode: MFSK, submode:Q65.

Does this mean it's now in the ADIF spec and ready for adoption by loggers like DXlabs?

73

jim ab3cv


Alternate feed to SpotCollector

Dick Grote
 

I've found that chasing POTA's to be a lot of fun.  I've created a POTA SQL filter on SpotCollector based on notes in the spots, but I've found that the spots captured in this manner is a small fraction of the spots that are posted on the POTA website (https://pota.us/#/spots).  The question I have is there a way to feed this web based spot source into SpotCollector. I know there are other situations where this could be useful such as special spotting sites for state QSO parties.

I've thought of scraping spots and creating a local cluster feed, but I have not idea whether is possible or practical.  Any thoughts?

Thanks.
--
Dick
K6PBF


Re: RF (Power) of the Commander

Dave AA6YQ
 

+ AA6YQ comments below
Is it possible to have - when I log a QSO - that in DxKeeper pane Log_QSOs>QSO>Power is reported the actual RF (Power) appearing in Commander when RF is enabled in "Xmit Meter" **instead** of the power set in DxKeeper Config>Defaults>Default_Transmit_Power_by_band?
+ Not at present, That could only be done for the subset of transceivers that can be directed to report their RF output, and the result would be inaccurate if a linear amplifier were in use. Technically straightforward, but a lot of development and remote testing would be required for what seems like relatively low value.

       73,

              Dave, AA6YQ


RF (Power) of the Commander

Carlo - IK2RPE
 

Is it possible to have - when I log a QSO - that in DxKeeper pane Log_QSOs>QSO>Power is reported the actual RF (Power) appearing in Commander when RF is enabled in "Xmit Meter" **instead** of the power set in DxKeeper Config>Defaults>Default_Transmit_Power_by_band?

Many thanks

Carlo  Ik2RPE


Re: Mode not Switching with band change?

Dave AA6YQ
 

+ AA6YQ comments below

I am running an Elecraft K3 and a KPA1500 amplifier. I use the DXLab Suite of programs for logging, rig control and so on.

If I do a manual band change on either the K3 or using the KPA1500 and change back and forth between 15m and 40m, the side band changes appropriately.

If I do it using the Commander Bandspread window buttons and go from 15 to 40, it stays in USB. I can then do a MODE ALT to get the correct mode, but it doesn't stick if I go back and forth.

FWIW, going to 80 has the same issue...

+ "Changing frequency via the Bandspread window"

+ "Commander remembers the last 5 frequencies you visited on each band, and the mode in use for each such visit; this information is stored in a Band Stack associated with each band. If you QSY the radio, and then let it remain on a frequency for longer than the dwell time setting, the new frequency and mode will be saved on the appropriate Band Stack. The Bandspread window's Band panel contains a button for each band between 160m and 33cm. Clicking a band button sets the radio's frequency to the most recent frequency used on that band, sets its mode to the mode in use at that time, and clears Split; the Band Stack is then advanced, so that clicking the same band button a second time sets the frequency/mode to the next-most-recent frequency/mode used on that band. Using this mechanism, you can QSY to the most recent 5 frequencies."

https://www.dxlabsuite.com/commander/Help/ChangingFrequency.htm#Changing%20frequency%20via%20the%20Bandspread%20window

73,

Dave, AA6YQ


Re: DXKeeper Question

Dave AA6YQ
 

+ AA6YQ comments below

You could export a date sorted ADI file from one log and import it into the other log.

It would take some care but you could keep a master log and import in your FT8 QSO's for example. Something to think about.

+ WSJT-X maintains an ADIF file containing every QSO its ever logged. Importing this file into DXKeeper would require enabling "Duplicate detection", which greatly increases the time required to perform the import. operation.

+ This could be avoided if the WSJT-X log file were deleted after being imported into DXKeeper. To begin operating this way, I'd suggest first terminating WSJT-X, importing the WSJT-X log into DXKeeper with duplicate checking enabled (before retiring for the evening, because it will take a long time), and then deleting the WSJT-X log file.

+ From then on, import the WSJT-X log file into DXKeeper at the end of each operating session (without duplicate checking enabled), terminate WSJT-X, and delete the WSJT-X log file.

+ If you're using the direct interoperation between WSJT-X and DXLab, there's an easier solution: configure WSJT-X on computer B to send logging directives to the instance of SpotCollector running on computer A, which will in turn log those directives to the instance of DXKeeper running on computer A. In the "Installing and Configuring WSJT-X" section of " Getting Started with K1JT modes using Direct Interoperation Between DXLab and WSJT-X", see step 6.b.i

https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesDirect

+ This will enable the direct logging of QSOs to the instance of DXKeeper running on computer A and the logging of QSOs from WSJT-X running on computer B to the instance of DXKeeper running on computer A.


73,

Dave, AA6YQ

2881 - 2900 of 203504