Date   

Re: Spot source

Dave AA6YQ
 

+ AA6YQ comments below
Sorry for my lack of clarity; it works fine when I am using a browser remotely; I would prefer it if I could use SpotCollector remotely, using the output from SC at home.
 
In other words, if I cannot do this, I understand I can always resort to using a browser, but I would like to use the web output from SC at home somehow as a source For SC running remote.
 
I know I could forward the telnet port to the correct machine, but it would end there I think.
 
I suspect it is not possible, since I cannot telnet into the home machine and get at the right info; just wondering…

+ If SpotCollector and DXKeeper are running on machine A and you want access to that instance of SpotCollector from machine B, your choices are

1. run a web browser on machine B and connect it to the web server built in to the instance of SpotCollector running on machine A

2. install TeamViewer (or equivalent) on machine's A and B, and use TeamViewer on machine B to access the applications on machine A (including SpotCollector)


       73,

                Dave, AA6YQ


 


Re: Spot source

David Reed
 

Sorry for my lack of clarity; it works fine when I am using a browser remotely; I would prefer it if I could use SpotCollector remotely, using the output from SC at home.

In other words, if I cannot do this, I understand I can always resort to using a browser, but I would like to use the web output from SC at home somehow as a source For SC running remote.

I know I could forward the telnet port to the correct machine, but it would end there I think.

I suspect it is not possible, since I cannot telnet into the home machine and get at the right info; just wondering…

Thanks!
 
73 de W5SV - David F. Reed

On Apr 19, 2021, at 00:08, iain macdonnell - N6ML <ar@...> wrote:

On Sun, Apr 18, 2021 at 9:21 PM David Reed <w5sv.dave@...> wrote:

When I operate portable, I would like to see spots from SpotCollector
running on my home station; easy to see in my browser:
http/w5sv.ddns,net:8080/spots

I can't seem to configure spot collector on my portable setup to see
that ; the problem seems to be in the "/spots" not accepted.

It's not really clear what you're trying to do. Are you trying to use
a browser on your remote setup to access your home SpotCollector
instance's web server? Or are you trying to configure SpotCollector to
somehow see the home instance through its web server? The latter isn't
possible.

There are several typos in your URL above - it should be:

http://w5sv.ddns.net:8080/spots

73,

   ~iain / N6ML







Re: DXKeeper: How to log azimuth? ANT_AZ not populating in log

Dave AA6YQ
 

+ AA6YQ comments below
Another thought;   I assume if I want to save debug info for one or two real QSO's, that it would be
OK to perform your steps below, but;

Step 4.   IGNORE
Step 5.   Make a couple of real QSO's using WSJT-X

Then study the errorlog.txt  text file?

+ Does the new QSO you described in your previous message specify a "myQTH ID"?

   de AA6YQ


Re: DXKeeper: How to log azimuth? ANT_AZ not populating in log

Neal Pollack
 


Hi Dave:

Another thought;   I assume if I want to save debug info for one or two real QSO's, that it would be
OK to perform your steps below, but;

Step 4.   IGNORE
Step 5.   Make a couple of real QSO's using WSJT-X

Then study the errorlog.txt  text file?

Neal


On Sun, Apr 18, 2021 at 06:19 PM, Dave AA6YQ wrote:

+ All of the required settings are described in

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

+ If a careful review of this article doesn't get you going, please do the following:

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

2. terminate DXKeeper

3. start DXKeeper

4. temporarily disable any automatic uploading of QSOs to Club Log, eQSL.cc, and LoTW

5. log a test QSO with AA6YQ with its grid square populated

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

7. re-enable the automatic uploading of QSOs to Club Log, eQSL.cc, and LoTW that you disabled in step 4

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

aa6yq (at) ambersoft.com


Re: Spot source

Dave AA6YQ
 

+ AA6YQ comments below

On Sun, Apr 18, 2021 at 9:21 PM David Reed <w5sv.dave@gmail.com> wrote:

When I operate portable, I would like to see spots from SpotCollector
running on my home station; easy to see in my browser:
http/w5sv.ddns,net:8080/spots

I can't seem to configure spot collector on my portable setup to see
that ; the problem seems to be in the "/spots" not accepted.
It's not really clear what you're trying to do. Are you trying to use a browser on your remote setup to access your home SpotCollector instance's web server? Or are you trying to configure SpotCollector to somehow see the home instance through its web server? The latter isn't possible.

There are several typos in your URL above - it should be:

http://w5sv.ddns.net:8080/spots

+ which works, as I can see if from here.

+ Thanks Iain!

73,

Dave, AA6YQ


Re: Spot source

Dave AA6YQ
 

+ AA6YQ comments below

When I operate portable, I would like to see spots from SpotCollector running on my home station; easy to see in my browser:
http/w5sv.ddns,net:8080/spots

I can't seem to configure spot collector on my portable setup to see that ; the problem seems to be in the "/spots" not accepted.

Any ideas on workarounds on either end to fix this?

+ As a first step, enter this URL on a web browser running on the same computer that is hosting SpotCollector:

127.0.0.1/spots

+ If that works, replace the 127.0.0.1 with the machines actual address on your network, e.g.

192.168.1.114/spots

+ If that works, the try that same URL in the web browser on another computer connected to your home network.

+ If that works, then you either the dynamic IP service you setup to allow access from beyond your home network is not properly configured, or your router is blocking remote access.

73,

Dave, AA6YQ


Re: Spot source

iain macdonnell - N6ML
 

On Sun, Apr 18, 2021 at 9:21 PM David Reed <w5sv.dave@gmail.com> wrote:

When I operate portable, I would like to see spots from SpotCollector
running on my home station; easy to see in my browser:
http/w5sv.ddns,net:8080/spots

I can't seem to configure spot collector on my portable setup to see
that ; the problem seems to be in the "/spots" not accepted.
It's not really clear what you're trying to do. Are you trying to use
a browser on your remote setup to access your home SpotCollector
instance's web server? Or are you trying to configure SpotCollector to
somehow see the home instance through its web server? The latter isn't
possible.

There are several typos in your URL above - it should be:

http://w5sv.ddns.net:8080/spots

73,

~iain / N6ML


Re: DXKeeper: How to log azimuth? ANT_AZ not populating in log

Dave AA6YQ
 

+ AA6YQ comments below

I do have exactly one "MyQTH" filled in, on the my QTHs tab.   It has my LAT, LONG, GRID, etc.

I added the column for ANT_PATH to my log display, and made sure all of those were showing "S".
Once I did that, I could manually update so that every QSO in my log shows a bearing now.

However, I just did a new QSO, and it does not populate ANT_AZ (bearing).
For this new QSO, I confirmed the following:

1.   The new QSO, according to the award sub-display on the log page, does have a GRID1.  
       So we know his location.

2.   The new QSO has an "S" in the PATH column, so we know that is in the QSO.

3.    ??   We have my info in my one "my QTH" tab entry, with grid and LAT and LONG.
        We also have my LAT, LONG, and Short Path settings in the CONFIG, DEFAULTS tab

+ Does this new QSO specify a "myQTH ID"?

       73,

            Dave, AA6YQ


Re: DXKeeper: How to log azimuth? ANT_AZ not populating in log

Neal Pollack
 

Hi Dave:

I do have exactly one "MyQTH" filled in, on the my QTHs tab.   It has my LAT, LONG, GRID, etc.

I added the column for ANT_PATH to my log display, and made sure all of those were showing "S".
Once I did that, I could manually update so that every QSO in my log shows a bearing now.

However, I just did a new QSO, and it does not populate ANT_AZ (bearing).
For this new QSO, I confirmed the following:

1.   The new QSO, according to the award sub-display on the log page, does have a GRID1.  
       So we know his location.

2.   The new QSO has an "S" in the PATH column, so we know that is in the QSO.

3.    ??   We have my info in my one "my QTH" tab entry, with grid and LAT and LONG.
        We also have my LAT, LONG, and Short Path settings in the CONFIG, DEFAULTS tab.

What next?

Cheers,

Neal
N6YFM


Spot source

David Reed
 

When I operate portable, I would like to see spots from SpotCollector running on my home station; easy to see in my browser: http/w5sv.ddns,net:8080/spots

I can't seem to configure spot collector on my portable setup to see that ; the problem seems to be in the "/spots" not accepted.

Any ideas on workarounds on either end to fix this?

Thanks & 73 de Dave, W5SV


Re: DXKeeper: How to log azimuth? ANT_AZ not populating in log

Dave AA6YQ
 

+ AA6YQ comments below

I also tried the option on this page:
https://www.dxlabsuite.com/dxlabwiki/QSODistance
called "Updating Already Logged QSOs", and that updates some of them in the Bearing column
but others remain blank. When I click a line in the log display that has no bearing, the DXView
window DOES show the bearing/heading for both long and short path.

So I have two point of confusion:

A. Why does DXKeeper not populate the bearing (ANT_AZ) field when logging a QSO?

+ Three possibilities:

1. your location cannot be determined

2. the location of the worked station is not specified in the QSO

3. the antenna path (short or long) is not specified in the QSO


B. Why does the manual update method only update some QSO records in the log display,
when DXView does indeed have the heading(s) for that QSO record?

+ If you're referring to the use of the "Modify QSOs" function, it too requires the three items of information specified above to be present in a QSO in order to compute its azimuth.


+ Do you have one or more "myQTHs" specified on the Main window's "my QTHs" tab?

73,

Dave, AA6YQ


Re: DXKeeper: How to log azimuth? ANT_AZ not populating in log

Neal Pollack
 

I also tried the option on this page:
https://www.dxlabsuite.com/dxlabwiki/QSODistance
called "Updating Already Logged QSOs", and that updates some of them in the Bearing column
but others remain blank.   When I click a line in the log display that has no bearing, the DXView
window DOES show the bearing/heading for both long and short path.

So I have two point of confusion:

A.  Why does DXKeeper not populate the bearing (ANT_AZ) field when logging a QSO?

B.  Why does the manual update method only update some QSO records in the log display,
      when DXView does indeed have the heading(s) for that QSO record?

Cheers,

Neal Pollack,  N6YFM


updated eQSL AG and LoTW databases are available...

Dave AA6YQ
 

...via the Databases tab on DXView's Configuration window.

73,

Dave, AA6YQ


Re: DXKeeper: How to log azimuth? ANT_AZ not populating in log

Dave AA6YQ
 

+ AA6YQ comments below

I tried running DXView along side DXKeeper, and have the option clicked on the Rotor Tab, since I don't use rotor control.
When I tried making two QSOs, I noticed that DXView does indeed show short and long path headings to the remote station.
But the column in DXKeeper for ANT_AZ is not populating.

Is there some additional setting that needs to be made?

+ All of the required settings are described in

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

+ If a careful review of this article doesn't get you going, please do the following:

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

2. terminate DXKeeper

3. start DXKeeper

4. temporarily disable any automatic uploading of QSOs to Club Log, eQSL.cc, and LoTW

5. log a test QSO with AA6YQ with its grid square populated

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

7. re-enable the automatic uploading of QSOs to Club Log, eQSL.cc, and LoTW that you disabled in step 4

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

aa6yq (at) ambersoft.com

        73,

              Dave, AA6YQ

 


Re: DXKeeper: How to log azimuth? ANT_AZ not populating in log

Neal Pollack
 

Hi Dave:

I tried running DXView along side DXKeeper, and have the option clicked on the Rotor Tab, since I don't use rotor control.
When I tried making two QSOs, I noticed that DXView does indeed show short and long path headings to the remote station.
But the column in DXKeeper for ANT_AZ is not populating.

Is there some additional setting that needs to be made?

Cheers,

Neal
N6YFM


Re: Issue with uploading to LoTW

Dave AA6YQ
 

+ AA6YQ comments below

I took part in the Michigan QSO Party this last Saturday. I live in Michigan but, thinking my W5DT call sign might confuse people, especially those out of state, I used W5DT/8 for the period of the contest. The pass through of my contacts from N1MM to DXKeeper worked fine but the contacts did not upload to LoTW and I assume that is because I used the /8 on my call sign. A group upload didn't work either. Would the correct thing to do be to get another LoTW certificate for W5DT/8 or is there something else I should do? There are over 200 contacts.

+ If a logged QSO's "Station Callsign" is W5DT/8, DXKeeper's "Upload to LoTW" function will skip it if you specified a "Callsign Certificate" of W5DT. This prevents inadvertently submitting QSOs with the wrong "Callsign Certificate".

+ If you used W5DT/8 over the air, then your QSO partners will submit QSOs with W5DT/8 - which would only match QSOs submitted with a W5DT/8 "Callsign Certificate".

+ So yes, you must request a W5DT/8 "Callsign Certificate", and use it to submit the QSOs you made as W5DT/8.

+ Instructions are here:

https://lotw.arrl.org/lotw-help/addcertreq/

+ You should receive your new "Callsign Certificate" within a few days of requesting it.

73,

Dave, AA6YQ


Issue with uploading to LoTW

Marv Stasak
 

Dave,

I took part in the Michigan QSO Party this last Saturday.  I live in Michigan but, thinking my W5DT call sign might confuse people, especially those out of state,  I used W5DT/8 for the period of the contest.  The pass through of my contacts from N1MM to DXKeeper worked fine but the contacts did not upload to LoTW and I assume that is because I used the /8 on my call sign. A group  upload didn't work either.  Would the correct thing to do be to get another LoTW certificate for W5DT/8 or is there something else I should do?  There are over 200 contacts.

73,
Marv, W5DT


67 new modes!

Dave AA6YQ
 

ADIF 3.1.2 was approved yesterday. It defines the 67 new sub-modes listed below, most of them supported by FLDigi.

In ADIF, modes and submodes are unique. DXKeeper exploits this by treating submodes as if they were modes. For example, ADIF
represents FT8 as

<MODE:4>MFSK <SUBMODE:3>FT8

but to manually log a QSO in FT8, you simply set the Capture window's Mode selector to FT8. When exporting an ADIF file, DXKeeper
automatically emits the correct ADIF mode-and-submode representation for each QSO's Mode item. When importing an ADIF file or an
ADIF QSO record from another application), DXKeeper automatically converts the ADIF mode-and-submode representation to its internal
"mode only" representation. This eliminates the need for users to be aware of ADIF's mode-submode distinction.

The current version of DXKeeper handles Mode items up to 8 characters in length. Several of the new submodes defined in ADIF 3.1.2
are 11 characters in length. Thus the next version of DXKeeper will automatically expand the width of its Mode items to 12 when you
open a log file whose Mode items are limited to 8 characters. This expansion will fail if DXView, JT-Alert, SpotCollector, or
SpotSpy are running, so it will be necessary to terminate these applications before the automatic Mode item expansion can be
completed; DXKeeper will inform you if that's the case.

SpotCollector has long supported a wider Mode field, so it requires no change to handle the new submodes.

The DefaultModes.txt file included with the next version of DXKeeper will include all 67 of the new submodes. If you don't want
these to appear in DXKeeper's mode selectors, you can create a Modes.txt file in DXKeeper's Databases folder that includes the
subset of entries from DefaultModes.txt that you want present in DXKeeper's Mode selectors. If you've already defined a Modes.txt
file in DXKeeper's Databases folder and want DXKeeper's Mode selectors to include one or more of the 67 new modes, copy their
entries from the new DefaultModes.txt file to your Modes.txt file. After making any change to your DefaultModes.txt or Modes.txt
files, terminate and restart DXKeeper after saving those changes.

Why the mode-submode representation in ADIF? The thinking was that new submodes of an existing mode could be quickly added by the
person serving as "Secretary of ADIF", bypassing a multi-week discussion and vote. In practice, disagreements over submode names
have left the Secretary unwilling accept new submode proposals without a vote.

73,

Dave, AA6YQ


DOM-M
DOM4
DOM5
DOM8
DOM11
DOM16
DOM22
DOM44
DOM88
HELLX5
HELLX9
SLOWHELL
FST4W
JTMS
MFSK64L
MFSK128L
Q65
8PSK125
8PSK125F
8PSK125FL
8PSK250
8PSK250F
8PSK250FL
8PSK500
8PSK500F
8PSK1000
8PSK1000F
8PSK1200F
PSK63RC20
PSK63RC32
PSK63RC4
PSK63RC5
PSK63RC10
PSK125RC10
PSK125RC12
PSK125RC16
PSK125RC4
PSK125RC5
PSK250RC2
PSK250RC3
PSK250RC5
PSK250RC6
PSK250RC7
PSK500RC2
PSK500RC3
PSK500RC4
PSK800RC2
PSK1000RC2
THOR-M
THOR4
THOR5
THOR8
THOR11
THOR16
THOR22
THOR25X4
THOR50X1
THOR50X2
THOR100
THRBX1
THRBX2
THRBX4
THROB1
THROB2
THROB4
NAVTEX
SITORB


Re: DXKeeper: How to log azimuth? ANT_AZ not populating in log

Dave AA6YQ
 

+ AA6YQ comments below

I am running the latest DXKeeper, v16.0.7.  I added a new column today for ANT_AZ in my log display.
I am hoping to record/display the bearing to the other station in my log.

I next went to the DXKeeper CONFIG button, DEFAULTS tab, and made sure that "Antenna Path" said "S".
On this DEFAULTS tab, my QTH LAT and LONG are set.  Format is like 33 48' 45" N.
All of my QSO's from today do show a value in the "GRID 1" field on the log award sub-panel.

But, the ANT_AZ column does not populate.    I searched previous topics here and can't find
what I am missing?
Please note I am only using DXKeeper and WSJT-X, and do not have other DXLABs apps open
due to screen real estate.

+ As described in the "Azimuth and Antenna Path" section of

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

+ DXView must also be running. You can keep its windows minimized (off-screen) to conserve screen space.

       73,

               Dave, AA6YQ

 


DXKeeper: How to log azimuth? ANT_AZ not populating in log

Neal Pollack
 

Hi:

I am running the latest DXKeeper, v16.0.7.  I added a new column today for ANT_AZ in my log display.
I am hoping to record/display the bearing to the other station in my log.

I next went to the DXKeeper CONFIG button, DEFAULTS tab, and made sure that "Antenna Path" said "S".
On this DEFAULTS tab, my QTH LAT and LONG are set.  Format is like 33 48' 45" N.
All of my QSO's from today do show a value in the "GRID 1" field on the log award sub-panel.

But, the ANT_AZ column does not populate.    I searched previous topics here and can't find
what I am missing?
Please note I am only using DXKeeper and WSJT-X, and do not have other DXLABs apps open
due to screen real estate.

Thanks,
Neal  N6YFM

1861 - 1880 of 202740