Date   

Re: GrayLine

Hasan Schiers N0AN
 

The SR/SS tables are particularly valuable to me in that they come into play every day, with the pre and post dawn enhancement on 160/80/40 meters. (I don't operated in the evenings)

Grayline is more limited by season, but perhaps more spectacularly revealing if one pays attention.

I am very pleased with the tables, as they are easy to follow and I can set an alarm on my phone to go check the bands of interest at the right times. I do have DXAtlas, etc, but I don't use it much. The vast  majority of what I want to know is already provided by DXView and DXK, and Propview if needed. I tend to get overwhelmed by too much graphical presentation. 

The Sun tables are outstanding. Comparing them to PSKReporter overnight (late afternoon to post sunrise next day) is most interesting. I usually let my two radios (TS-590sg and an SDR) sit on 80 and 160 or 160 and 40 overnight and look to see what has been spotted  when I come down in the morning. 

73, N0AN
Hasan


On Mon, Nov 9, 2020 at 2:00 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

Regarding the display of grid squares in DXAtlas.
I wondered why under Map/Grid, Bearing/Distance and Grid Squares were greyed out. Turns out I was using the "Globe" display. I found this in DXAtlas "Help":

+ I've updated step 1 in

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

+ to make it explicit that the Rectangular map style must be selected.

Latitude/Longitude, Bearing/Distance and Grid Squares options select the grid that will be displayed on the map.
Note that the Bearing/Distance grid is available only in the Azimuthal projection while Grid Squares is displayed only in the Rectangular projection.

+ In DX Atlas version 2.3, the latitude, longitude, bearing, and distance are all displayed in the lower left corner for all three available map styles (Rectangular, Azimuthal, Globe).

        73,

               Dave, AA6YQ








Importing an ADIF file

Knut Meland
 

Why does not DXLab follow the ADIF standard?
According to this standard SSB is a mode and USB and LSB submodes. See:
http://www.adif.org.uk/311/ADIF_311.html
I encountered problems with this when handling a file export. I edited it in LogConverter (shareware) and had all my LSB and USB QSOs listed in the error file when I tried to save under a new file name. Frankly, I did not know that USB and LSB are just submodes in the ADIF standard. But they are. The mode is SSB!
If we get an update of DXKeeper on this, I hope we will have a script file to help us update our log files.
73 de LA9RY Knut 


Re: IOTA handling

Dave AA6YQ
 

% More AA6YQ comments below

Dave, thank you for the reply.

> Only if IOTA-World considers that activation valid.

of course, I'm already aware of this.

> You can add a QSO to your IOTA submission by setting > its "IOTA VFY" item to 'S'.

yes, but it would be a very tedious and time consuming job that would imply a great waste of time, as I'm doing now, to find some
confirmed by LotW QSOs which are not recognized by IOTA-World and on which they are still investigating.

I suppose that to add a QSO like you suggest, I must:

1. Generate a submission with DXKeeper
2. Transform it into a csv file to import into Excel (already tedious) 3. Download my "Pending QSOs" from IOTA-World 4. Load #3 into
Excel (luckily, it's already a csv file) 5. Chech the QSOs, one by one, to find the QSO to add

Or is there a faster method? Please, notice that I'm not ready to submit to IOTA-World yet, I only want to identify QSOs to be
periodically loaded into my "Pending QSOs".

> There is now an API that DXKeeper could invoke to obtain > the list of valid activations

I hope that it will be activated very soon.

% There was a time when RSGB accepted an IOTA award submission file in a specified format, which DXKeeper could automatically
generate. However, IOTA-World has removed that capability.

% I have yet to find a clear online explanation of the procedure for submitting an IOTA award application. The IOTA-World team is
responsive to my questions, but several of those questions have prompted policy discussions.

% Given the instability, my inclination is to wait awhile for IOTA to "settle down". They'll get there...

73,

Dave, AA6YQ


Re: GrayLine

Dave AA6YQ
 

+ AA6YQ comments below

Regarding the display of grid squares in DXAtlas.
I wondered why under Map/Grid, Bearing/Distance and Grid Squares were greyed out. Turns out I was using the "Globe" display. I found this in DXAtlas "Help":

+ I've updated step 1 in

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

+ to make it explicit that the Rectangular map style must be selected.

Latitude/Longitude, Bearing/Distance and Grid Squares options select the grid that will be displayed on the map.
Note that the Bearing/Distance grid is available only in the Azimuthal projection while Grid Squares is displayed only in the Rectangular projection.

+ In DX Atlas version 2.3, the latitude, longitude, bearing, and distance are all displayed in the lower left corner for all three available map styles (Rectangular, Azimuthal, Globe).

73,

Dave, AA6YQ


Re: GrayLine

Jim McPhee
 

Regarding the display of grid squares in DXAtlas.
I wondered why under Map/Grid, Bearing/Distance and Grid Squares were greyed out. Turns out I was using the "Globe" display. I found this in DXAtlas "Help":

Latitude/Longitude, Bearing/Distance and Grid Squares options select the grid that will be displayed on the map.
Note that the Bearing/Distance grid is available only in the Azimuthal projection while Grid Squares is displayed only in the Rectangular projection.

73,

--
Jim McPhee
Placitas, NM
W5ABA


Re: DXLabs Install Corrupted??

Dave AA6YQ
 

+ AA6YQ comments below
I have looked for the file mentioned in the location listed but can’t find it. So it appears that somehow, my DXLabs install has gotten corrupted by this file.
+ To what file are you referring?
I did download that program a few months back but have not used it since. I am tempted to just uninstall the Ultrascope program but thought I’d wait and see if that is the correct way to proceed.

+ What is "the Ultrascope program"?

+ Screenshots are not conveyed here, as they consume storage, and we have only a modest storage allocation. Please attach the screenshot to an email message, and send the message to me via

aa6yq (at) ambersoft.com

         73,

               Dave, AA6YQ

 


Re: Flaky behavior since last Windows update

Dave AA6YQ
 

+ AA6YQ comments below
I have some interesting results to report. First, rebooting into "Safe Mode with Networking" did indeed make Launcher start in a normal amount of time (i.e. a couple of seconds). An explicit exception for DXLabLauncher.exe did not remedy the problem. I started suspecting some other "Startup" program could be interfering, so I disabled all Startup applications, and sure enough, Launcher started in a normal amount of time. I have concluded that the Adobe Creative Cloud Suite is the culprit. Adobe has 5 startup applications: AcroTray, "Adobe GC Invoker Utility", "Adobe Updater Startup Utility", CCXProcess.exe (had to Google that one) and "Creative Cloud Desktop". With those 5 applications disabled, and everything else enabled, Launcher starts normally. Unfortunately, I need the Adobe suite for work, so I can't just uninstall it. I am going to try and determine if perhaps just one of these 5 is at the root of the issue, and maybe I do not need it to auto-start.

+ Thanks for the report, Matt! I have added "Adobe Creative Cloud Suite" to 

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

        73,

            Dave, AA6YQ

 


DXLabs Install Corrupted??

w2eck
 

Was away over the weekend and when I started up my  Win 10 PC, then Started DXLabLauncher, experienced a  very strange event.  Instead of Launcher opening I get a brief windows Installer window and then the another windows installer msg saying "the feature you are trying to use can't be found". I have a screen shot of the msg , but don't see how to attach to this post. Then found out, if I try to launch any other DXLabs program I get the same window. I have looked for the file mentioned in the location listed but can’t find it. So it appears that somehow, my DXLabs install has gotten corrupted by this file. I did download that program a few months back but have not used it since. I am tempted to just uninstall the Ultrascope program but thought I’d wait and see if that is the correct way to proceed.

73 Paul w2eck


Re: AJA and JCC Award tracking

Bart AA7VA
 

Tim -
Be sure to check more than just the default QRZ lookup - often others will show more detail to figure out the Prefectures and Cities/Guns.  And If that fails, a bit of research on your web search engine will often result in more info.  On some, I have had to resort to maps to find out what Prefecture the city or Gun is located in.  I find it very interesting to do, but others do not. 
Whatever, I do it for my own satisfaction, it is too messy to try to get the actual award.
Bart  aa7va


Re: Flaky behavior since last Windows update

Matt Foster
 

I have some interesting results to report. First, rebooting into "Safe Mode with Networking" did indeed make Launcher start in a normal amount of time (i.e. a couple of seconds). An explicit exception for DXLabLauncher.exe did not remedy the problem. I started suspecting some other "Startup" program could be interfering, so I disabled all Startup applications, and sure enough, Launcher started in a normal amount of time. I have concluded that the Adobe Creative Cloud Suite is the culprit. Adobe has 5 startup applications: AcroTray, "Adobe GC Invoker Utility", "Adobe Updater Startup Utility", CCXProcess.exe (had to Google that one) and "Creative Cloud Desktop". With those 5 applications disabled, and everything else enabled, Launcher starts normally. Unfortunately, I need the Adobe suite for work, so I can't just uninstall it. I am going to try and determine if perhaps just one of these 5 is at the root of the issue, and maybe I do not need it to auto-start.

Thank you to everyone who offered advice, and a HUGE thanks to Dave for having such great online troubleshooting documentation that helped me ferret out the issue!

--
73, Matt, N0EYE


Re: IOTA handling

Salvatore Besso
 

hello,

Dave, thank you for the reply.

Only if IOTA-World considers that activation valid.
of course, I'm already aware of this.

You can add a QSO to your IOTA submission by setting
its "IOTA VFY" item to 'S'.
yes, but it would be a very tedious and time consuming job that would imply a great waste of time, as I'm doing now, to find some confirmed by LotW QSOs which are not recognized by IOTA-World and on which they are still investigating.

I suppose that to add a QSO like you suggest, I must:

1. Generate a submission with DXKeeper
2. Transform it into a csv file to import into Excel (already tedious)
3. Download my "Pending QSOs" from IOTA-World
4. Load #3 into Excel (luckily, it's already a csv file)
5. Chech the QSOs, one by one, to find the QSO to add

Or is there a faster method? Please, notice that I'm not ready to submit to IOTA-World yet, I only want to identify QSOs to be periodically loaded into my "Pending QSOs".

There is now an API that DXKeeper could invoke to obtain
the list of valid activations
I hope that it will be activated very soon.

Thank you.

73 de
Salvatore (I4FYV)


Re: eQSL Auto send

Dave AA6YQ
 

+ AA6YQ comments below

Hi, Looking for some beginner help for an OM who has been off since 1980.

+ Welcome to DXLab!

have been using DXKeeper for about a month now and changed from HRD because it appeared to offer exactly the same product for my needs.

Its called Amateur Radio for a reason ...... not Professional Radio and in saying, would like to thank K0PIR for the comprehensive videos.

+ K0PIR's videos are nice, but they cover less than 1% of DXLab's functionality. I strongly suggest that you start here:

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


I went to eQSL site and looked in my unconfirmed and blow me down there was about every QSO I had done.

So I looked at what I was doing wrong.

Q1, is it eQSL that requires a "third party password for my account"

+ You need an eQSL username and password, and you must accurately specify those on the eQSL tab of DXKeeper's "QSL Configuration" window.


I read the documentation on QSLing and it appears I have to do something for each contact to get it over to the queue and then process the queue.

+ That's incorrect:

1. properly configured, the "Add Requested" function will populate the QSL Queue with every QSO not already submitted to eQSL

or

2. you can filter the Log Page Display to contain all of your QSOs or any subset of your QSOs, and then add them to the QSL Queue by invoking the "Add All" function.

+ Since they can be used with QSL cards, eQSL, and LoTW, both of these functions are described in

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


+ eQSL-specific details are described here:

<https://www.dxlabsuite.com/dxkeeper/Help/QSL.htm#QSLing%20via%20eQSL.cc>



(Thats where I got the bad password message from) I am using the same password that I log in to eQSL with.

+ I suggest that you re-enter your username and password on the eQSL tab of DXKeeper's "QSL Configuration" window.


Now also reading the documentation, I cannot find a way to get the QSO from my log to the queue in a batch.

+ Make sure that you have the current version of DXKeeper (15.8.9) installed; if not, direct the Launcher to upgrade DXKeeper). Then review the two sections of the reference documentation cited above. The Task-oriented documentation provides step-by-step instructions for configuring and using DXKeeper with eQSL:

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


When the help file was written, it appears we were all using 2400 baud modems to get on the internet and this is the reason for not sending QSOs individually BUT Lotw and clublog do.

+ DXKeeper has provided the ability to automatically submit QSOs to eQSL as they are logged for more than a decade. See

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

73,

Dave, AA6YQ


Re: WSJT & Commander & KW TS-850

Dave AA6YQ
 

+ AA6YQ comments below

WSJT & Commander & TS-850 (using ‘Commander’ as RIG setting in WSJT) = “Fake It” mode in WSJT does not work (does not change frequency but audio changes thinking it changed).
+ Please do the following:

1. Configure WSJT-X to use Commander to control your TS-850, with "Fake it" enabled

2. Direct WSJT-X to QSY to a band other than the current band (e.g. if the current band is 20m, QSY to 40m)

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

4. Configure WSJT-X to transmit on a clear frequency

5. Direct WSJT-X to call CQ

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 message to me via

aa6yq (at) ambersoft.com

       73,

              Dave, AA6YQ


eQSL Auto send

VK5OM@...
 

Hi, Looking for some beginner help for an OM who has been off since 1980.

have been using DXKeeper for about a month now and changed from HRD because it appeared to offer exactly the same product for my needs.

Its called Amateur Radio for a reason ...... not Professional Radio and in saying, would like to thank K0PIR for the comprehensive videos.

I went to eQSL site and looked in my unconfirmed and blow me down there was about  every QSO I had done. 

So I looked at what I was doing wrong. 

Q1, is it eQSL that requires a "third party password for my account"

I read the documentation on QSLing and it appears I have to do something for each contact to get it over to the queue and then process the queue. (Thats where I got the bad password message from) I am using the same password that I log in to eQSL with.

Now also reading the documentation, I cannot find a way to get the QSO from my log to the queue in a batch. 

When the help file was written, it appears we were all using 2400 baud modems to get on the internet and this is the reason for not sending QSOs individually BUT Lotw and clublog do.

Now I am nowhere near perfect and have more than likely read it all wrong and (Q2) there must be an easier way to deal with this. I use LOTW eQSL and Clublog. Thats it.

BTU.

 


WSJT & Commander & KW TS-850

Daniel Violette
 

Minor issue.  Maybe someone with the combination in the subject can comment:

 

WSJT & TS-805 ONLY (using ‘Kenwood TS-850’ as RIG setting in WSJT) = “Fake It” mode in WSJT would change the active VFO if needed with one beep.  Example: 1200 Hz tone would drop frequency 0.5 kHz to keep audio in the 1500-2000 Hz range and then move back at receive-one beep each way.

 

WSJT & Commander & TS-850 (using ‘Commander’ as RIG setting in WSJT) = “Fake It” mode in WSJT does not work (does not change frequency but audio changes thinking it changed).

 

Reason I used ‘Fake It’ with WSJT directly is the TS-850 takes time to change and beeps a lot if using ‘Rig’ or split radio mode and would take nearly 3 seconds to start transmitting.  But, ‘Rig’ mode seems to work faster through Commander and I do not think I have a delayed or limited delayed transmit start.  Still have a bunch of beeps though (telling me mode in CW, change to ‘B’ VFO, etc.).

 

Anyone using ‘Fake It’ properly with the subject combination?

 

73, Dan KI6X

 


Re: GrayLine

Joe Subich, W4TV
 

+ I know one way to answer this question: plot the solar terminator
from my QTH every minute over the course of 365 days, and see what's
left uncolored, but I haven't gotten around to doing so.
You probably don't need to plot every minute ... 60 minutes each side
of sunrise and sunset should be more than enough. I'd run the boundary
cases at +/- 30 or +/- 60 minutes and look at anything between the two.

You can also simplify further by not running every day particularly in
December/June as SR/SS does not change that quickly around the solstice.

73,

... Joe, W4TV


On 2020-11-08 1:54 PM, Dave AA6YQ wrote:
+ AA6YQ comments below
I found it, it's in the docs:
http://www.dxlabsuite.com/dxlabwiki/IdentifyGrayLineOpenings
<http://www.dxlabsuite.com/dxlabwiki/IdentifyGrayLineOpenings>
+ Writing this article led me to  ask the question "what would the plot of all locations with which there's never a grayline opening from my QTH look like?"
+ I know one way to answer this question: plot the solar terminator from my QTH every minute over the course of 365 days, and see what's left uncolored, but I haven't gotten around to doing so.
+ Anyone know a more direct way to answer this question?
         73,
               Dave, AA6YQ


Re: GrayLine

Dave AA6YQ
 

+ AA6YQ comments below

Hassan, DXAtlas is an alternate map in DXView.  I use DXAtlas in the AZIMUTHAL view with my QTH at the center of the map and Grey line turned on.  Not only does that view show the Correct pointing angle (Azimuth) for my antenna, it shows the daylight and sunlit areas of the world.  DXAtlas has on the bottom of the display arrows for advancing and retarding the time in: minutes, hours and days and days, weeks and months.  This does not build a table of common gray line visibility, but you can sure figure it out quickly. 

 

In Azimuthal view you can see, in a straight line, the areas your beam is covering.  Which also shows the areas between you and the station you may be trying to work, And thus the potential QRM areas you are working over/through.

+ DXView can also plot worked and confirmed grid squares on the DX Atlas world map; see

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

    73,

             Dave, AA6YQ


Re: GrayLine

w6de
 

Hassan, DXAtlas is an alternate map in DXView.  I use DXAtlas in the AZIMUTHAL view with my QTH at the center of the map and Grey line turned on.  Not only does that view show the Correct pointing angle (Azimuth) for my antenna, it shows the daylight and sunlit areas of the world.  DXAtlas has on the bottom of the display arrows for advancing and retarding the time in: minutes, hours and days and days, weeks and months.  This does not build a table of common gray line visibility, but you can sure figure it out quickly. 

 

In Azimuthal view you can see, in a straight line, the areas your beam is covering.  Which also shows the areas between you and the station you may be trying to work, And thus the potential QRM areas you are working over/through.

 

It is not free but has a free 30 day trial period.  I find it an indispensable tool for my low band operations.

 

73,

Dave, w6de

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Hasan Schiers N0AN
Sent: Sunday, November 08, 2020 13:50
To: DXLab@groups.io
Subject: Re: [DXLab] GrayLine

 

I found it, it's in the docs:

 

 

Hasan

 

 

On Sun, Nov 8, 2020 at 7:34 AM Hasan Schiers N0AN via groups.io <hbasri.schiers6=gmail.com@groups.io> wrote:

Certainly, but while playing around with the feature, how do I test it. I can't sit around entering 300 different countries hoping one will show Grayline. 

 

I was looking for something more efficient to examine potential grayline passes, as it were.

 

There must be a better way .   :-)

 

73,

Hasan

 

 

On Sun, Nov 8, 2020 at 6:40 AM Julio Peralta via groups.io <jperalta4=verizon.net@groups.io> wrote:

Could it be that the country you have selected doesn’t have grey line propagation useful for your location?

 

Julio, W4HY

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Hasan Schiers N0AN
Sent: Sunday, November 08, 2020 6:07 AM
To: DXLab@groups.io
Subject: [DXLab] GrayLine

 

I've been playing with DXView's Sunrise/Sunset table which is wonderful for looking at potential 160m openings (and 80/40) and I saw the choice available for Grayline...but every time I choose it, after having input a callsign that shows Sunrise/Sunset, the list of SR/SS goes away (as it should) but the Grayline is blank.

 

How do I make use of the Grayline feature in non-realtime? 

(or even real time for that matter)

73, N0AN

Hasan


Re: AJA and JCC Award tracking

Ellam, Timothy St. J.
 

Joe

I understand. As you probably know only the land border is closed and you can still fly between the US and Canada (albeit with a 14 day quarantine at our end). However, there is a pilot program with expedited testing at YYC (test on arrival, a quarantine plan and then if the arrival test is negative a second test 48 hours later which, if also negative, frees you from quarantine) that should be expanding to other major airports in Canada before year end. Light at the end of the tunnel.

73

Tim VE6SH


Re: Flaky behavior since last Windows update

Joe Subich, W4TV
 

if you are auto starting Commander using Launcher then this
behaviour could also be due to the Windows updates resetting you
serial port assignments, i.e. the COM port Commander talks to you rig
on may now not be the one configured in Commander.
It can also be explained by the Windows Update replacing the Icom OEM
serial driver with a not quite compatible version from Microsoft.

73,

... Joe, W4TV


On 2020-11-08 2:49 PM, g4wjs wrote:
On 08/11/2020 19:41, Dave AA6YQ wrote:

+ AA6YQ comments below

On Sun, Nov 8, 2020 at 11:00 AM, Matt Foster wrote:

Any suggestions would be appreciated!

+ See this article:

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

+ The usual culprit is a misconfigured or incompetent anti-malware application.

       73,

             Dave, AA6YQ
Hi Matt and Dave,
if you are auto starting Commander using Launcher then this behaviour could also be due to the Windows updates resetting you serial port assignments, i.e. the COM port Commander talks to you rig on may now not be the one configured in Commander.
--
73
Bill
G4WJS.

10941 - 10960 of 208159