Date   

Re: No one is more deserving ...

Dave AA6YQ
 

+ AA6YQ comments below

Congratulations Dave!

A most deserved recipient, and not just exemplary, outstanding, and continuing service to ARRL and its members", but also to all us DXLab users too.

+ Thanks, Phil!

73,

Dave, AA6YQ


Re: No one is more deserving ...

Dave AA6YQ
 

* more AA6YQ comments below

Let me add my 'AMEN' to that - congratulations Dave !!

* thanks, Russ!

73,

Dave, AA6YQ

On Feb 10, 2020, at 10:42 AM, Dave AA6YQ <aa6yq@ambersoft.com> wrote:

+ AA6YQ comments below

And the multitudes said AMEN!!!

+ Thanks, Dave!

73,

Dave, AA6YQ


Re: beam headings ..

Dave AA6YQ
 

+ AA6YQ comments below

dave, i finally got it to report the AZ, but looks like dxview must be running and , on rotor control tab must check "report short path when disabled "

so dxview must be runnning ???

+ Correct.

+ Note that if you don't have a rotatable antenna, then you don't know what direction your signals are heading to your QSO partner. Even with a rotator, unless you "home in" on the azimuth that yields the strongest signal, you don't know.

+ With DXView running and its Main window visible, selecting a logged QSO in DXKeeper will cause DXView to display the great circle short path and long path headings to the selected QSO. Thus it's not necessary to jump through hoops to record an azimuth with each logged QSO when the azimuth you record is the great circle heading that DXView can compute and display whenever you select the QSO.

+ As for having to run DXView, each application in the DXLab Suite has a set of functions it performs. Replicating functions provided by one DXLab application into another would unnecessarily bloat the recipients, increasing the learning curve for new users and increasing the time required to implement and test new enhancements.

73,

Dave, AA6YQ


Re: No one is more deserving ...

Ted Bauer
 

IMO the ARRL should also recognize Dave's contribution of DXLab Suite to the Amateur Radio community (if they have not done so already). We all owe Dave a great debt of Thanks for his work.
There have been times I have read Dave's posts in response to ur myriad questions and wondered: When does Dave sleep?

73 
---
Ted   WA3AER


On Mon, Feb 10, 2020 at 10:00 AM Peter Laws <plaws0@...> wrote:
http://www.arrl.org/news/view/arrl-board-grants-awards-and-recognitions

``The Board conferred the ARRL President’s Award on David H.
Bernstein, AA6YQ, in recognition of “exemplary, outstanding, and
continuing service” to ARRL and its members as part of the ARRL
Logbook of The World team. Bernstein was a charter member of the ARRL
Logbook Committee and a “founding, influential, and devoted member” of
the Committee on Communication with ARRL Members.''

Sincere congratulations, Dave.

73,
Peter


--
Peter Laws | N5UWY | plaws plaws net | Travel by Train!




--
---
Ted   WA3AER


Re: Complicated (?) problem

g4wjs
 

On 10/02/2020 21:39, Steve - N3SL wrote:
Will try here with a "simple" question to see if I get a hit:

I run the "original" microHam keyer and router software (virtual ports).  Have for years, without problems.  Any Win10 upgrade beyond v1803 has the router software still seeing my radio, but none of the programs using the virtual ports (Commander, WSJT-X, MMTTY) can read radio status, key the rig, etc. and I get error messages that the ports have not been created (while the microHam program communicates with the radio just fine!).

So without all the gory details, just this:  Anyone using the microHam box/software successfully beyond Win10 v1803?  If so, we can take this "offline" for more discussion. (Yes, I've been to microHam support.)

Otherwise, the current setup works just fine, and I'm done updating Win10!

Thanks,
Steve, N3SL
Hi Steve,

I don't recall having exactly that problem, and I run Windows 8.1, but I have had to delete all the virtual ports  occasionally and recreate them using the urouter Virtual Ports menu items. Make sure to note what port numbers are assigned to what on the various urouter configuration pages.



--
73

Bill

G4WJS.


Re: Complicated (?) problem

Steve - N3SL
 

He suggested a sequence of not starting the router automatically (which wasn't the case anyway), upgrading, then starting the router.  He also pointed me to a version of the software that actually had been released that day (last week).  Unfortunately, no joy.


On Mon, Feb 10, 2020 at 3:58 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comment sbelow

Will try here with a "simple" question to see if I get a hit:

I run the "original" microHam keyer and router software (virtual ports).  Have for years, without problems.  Any Win10 upgrade beyond v1803 has the router software still seeing my radio, but none of the programs using the virtual ports (Commander, WSJT-X, MMTTY) can read radio status, key the rig, etc. and I get error messages that the ports have not been created (while the microHam program communicates with the radio just fine!).

So without all the gory details, just this:  Anyone using the microHam box/software successfully beyond Win10 v1803?  If so, we can take this "offline" for more discussion. (Yes, I've been to microHam support.)

+ Joe W4TV is our resident microHam expert. What was his response when you contacted microHam support?

     73,

           Dave, AA6YQ






Re: No one is more deserving ...

Phil Cooper
 

Congratulations Dave!

A most deserved recipient, and not just “exemplary, outstanding, and continuing service” to ARRL and its members", but also to all us DXLab users too.

73 de Phil GU0SUP

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Peter Laws
Sent: 10 February 2020 15:00
To: DXLab@groups.io
Subject: [DXLab] No one is more deserving ...

http://www.arrl.org/news/view/arrl-board-grants-awards-and-recognitions

``The Board conferred the ARRL President’s Award on David H.
Bernstein, AA6YQ, in recognition of “exemplary, outstanding, and
continuing service” to ARRL and its members as part of the ARRL
Logbook of The World team. Bernstein was a charter member of the ARRL
Logbook Committee and a “founding, influential, and devoted member” of
the Committee on Communication with ARRL Members.''

Sincere congratulations, Dave.

73,
Peter


--
Peter Laws | N5UWY | plaws plaws net | Travel by Train!


Re: Complicated (?) problem

Dave AA6YQ
 

+ AA6YQ comment sbelow

Will try here with a "simple" question to see if I get a hit:

I run the "original" microHam keyer and router software (virtual ports). Have for years, without problems. Any Win10 upgrade beyond v1803 has the router software still seeing my radio, but none of the programs using the virtual ports (Commander, WSJT-X, MMTTY) can read radio status, key the rig, etc. and I get error messages that the ports have not been created (while the microHam program communicates with the radio just fine!).

So without all the gory details, just this: Anyone using the microHam box/software successfully beyond Win10 v1803? If so, we can take this "offline" for more discussion. (Yes, I've been to microHam support.)

+ Joe W4TV is our resident microHam expert. What was his response when you contacted microHam support?

73,

Dave, AA6YQ


Re: Understanding QSL_sent and the QSL Queue

Dave AA6YQ
 

+ AA6YQ comments below

I spent some time yesterday going through the DXKeeper help files trying to determine exactly when the QSL_sent check box is set and
how it is used to create the QSL Queue when Add Requested is pressed. For a long time I have been setting the QSL_sent to 'R' when
I imported QSO's from N1MM+ and SKCCLogger. I now have a lot of QSO's with QSL_sent set to 'R' but the QSO's have been confirmed
via LOTW and I don't want to send cards. I also turned off setting QSL_sent to 'R' when I import QSO's so I can just set it when I
want to request a card.

Recently I worked some DX that I can only confirm via card, i.e. they don't do LOTW. I set the LOTW_sent to 'N' and QSL_sent to 'R'
for those QSO's. When I go to the QSL tab, click on QSL via cards, and click Add Requested, I get all the old QSO's that I don't
want to print cards for.

+ Did you review

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

+ and

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

+ ?

So my question is when does QSL_sent get set to 'R'

+ As described in the "Responding to Your QSO Partner's Request" section of

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

+ you can optionally check the "Preset QSL Request" box on the "QSL Configuration" window's General tab; doing so is equivalent to
checking the Capture window's "QSL Requested" box at the beginning of each QSO. If you don't enable this automation, then a QSO's
"QSL Sent" item would only be set to 'R' by your direct action.


and when does LOTW_sent get set to 'R'

+ The assumption is that if you use LoTW, you will want to upload every logged QSO to LoTW -- either immediately as you log it, or
later in a batch with other QSOs. Thus step 3.b in

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

+ is to check the "Initialize LotW Sent to 'R' for each logged or imported QSO" box on the "QSL Configuration" window's LoTW tab. If
you don't enable this automation, then a QSO's "LoTW QSL Sent" item would only set to 'R' by your direct action.


and what is the best way to handle this situation so I only get QSL_sent set to 'R' for cards when I actually want to get cards. I
worked out a script for turning off the QSL_sent to 'R' on old QSO's confirmed via LOTW but I am concerned about what might happen
if I do that.

+ What criteria motivate you to "get cards"?

- to request a QSL that will confirm a QSO whose confirmation will advance your award progress?

- because during the QSO, your partner asked you to QSL?

- because you received a card confirming a QSO, and the card said "please QSL!", or because you received an Online QSL Request
(Inbound OQRS) from Club Log?

- because you believe that a QSL card is the polite completion of every QSO, and wish to send one without waiting to be asked?

73,

Dave, AA6YQ


Complicated (?) problem

Steve - N3SL
 

Will try here with a "simple" question to see if I get a hit:

I run the "original" microHam keyer and router software (virtual ports).  Have for years, without problems.  Any Win10 upgrade beyond v1803 has the router software still seeing my radio, but none of the programs using the virtual ports (Commander, WSJT-X, MMTTY) can read radio status, key the rig, etc. and I get error messages that the ports have not been created (while the microHam program communicates with the radio just fine!).

So without all the gory details, just this:  Anyone using the microHam box/software successfully beyond Win10 v1803?  If so, we can take this "offline" for more discussion. (Yes, I've been to microHam support.)

Otherwise, the current setup works just fine, and I'm done updating Win10!

Thanks,
Steve, N3SL


Re: No one is more deserving ...

Russ Ravella
 

Let me add my “AMEN” to that - congratulations Dave !!

On Feb 10, 2020, at 10:42 AM, Dave AA6YQ <aa6yq@ambersoft.com> wrote:

+ AA6YQ comments below

And the multitudes said AMEN!!!

+ Thanks, Dave!

73,

Dave, AA6YQ





Re: beam headings ..

bill steffey NY9H
 

dave,  i finally got it to report the AZ,  but looks like dxview must be running   and  , on rotor control tab must check "report short path when disabled "


so dxview must be runnning  ???

tnx  ,               I can minimize

bill

On 2/10/2020 1:07 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

I don't think you can change the layout of the capture window, perhaps someone will correct me if I'm wrong.

+ There is an Az item in the Capture window on the 8th row of controls; if this row isn't visible, drag Capture window's lower border downward until the Az item is visible. See the second and third screen shots in

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

+ If DXView is controlling your rotatable antenna, entering a callsign in the Capture window and striking the Tab or Enter key will populate the Az item with the last heading DXView sent to your rotator.

73,

Dave, AA6YQ



Re: WSJT-X with Spotcollector + Gridtracker possible?

Dave AA6YQ
 

+ AA6YQ comments below

RR, that puts SpotCollector in the same position as JTAlert because both are implemented using tools that do not have out of the box support for joining multicast groups. Either could make the required Windows system calls to join a multicast group, but I understand that may be a low priority given other more pressing enhancements.

Do you use a Winsock1 or Winsock2 control for sockets in SpotCollector?

+ DXLab applications employ MSWINSCK.OCX to send and receive messages via UDP and TCP.

It should only need a couple of Winsock function calls to join and leave a multicast group for receiving UDP traffic from WSJT-X.

+ If you point me at the relevant documentation for these function calls, I'd appreciate it!

73,

Dave, AA6YQ


Re: beam headings ..

Dave AA6YQ
 

+ AA6YQ comments below

I don't think you can change the layout of the capture window, perhaps someone will correct me if I'm wrong.

+ There is an Az item in the Capture window on the 8th row of controls; if this row isn't visible, drag Capture window's lower border downward until the Az item is visible. See the second and third screen shots in

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

+ If DXView is controlling your rotatable antenna, entering a callsign in the Capture window and striking the Tab or Enter key will populate the Az item with the last heading DXView sent to your rotator.

73,

Dave, AA6YQ


Re: WSJT-X with Spotcollector + Gridtracker possible?

g4wjs
 

On 10/02/2020 17:08, Dave AA6YQ wrote:
+ AA6YQ comments below

I do not know if either GridTracker or SpotCollector are able to listen for multicast UDP traffic, but they should do if they have been correctly implemented.

+ SpotCollector is correctly implemented. However, the UDP-supporting Microsoft-provided component used by DXLab applications does not support multicast. I expect to eliminate this limitation over time so that DXLab applications can communicate among themselves using multicast UDP.

73,

Dave, AA6YQ
Hi Dave,

RR, that puts SpotCollector in the same position as JTAlert because both are implemented using tools that do not have out of the box support for joining multicast groups. Either could make the required Windows system calls to join a multicast group, but I understand that may be a low priority given other more pressing enhancements.

Do you use a Winsock1 or Winsock2 control for sockets in SpotCollector? It should only need a couple of Winsock function calls to join and leave a multicast group for receiving UDP traffic from WSJT-X.



--
73

Bill

G4WJS.


Understanding QSL_sent and the QSL Queue

 

I spent some time yesterday going through the DXKeeper help files trying to determine exactly when the QSL_sent check box is set and how it is used to create the QSL Queue when Add Requested is pressed.  For a long time I have been setting the QSL_sent to ‘R’ when I imported QSO’s from N1MM+ and SKCCLogger.  I now have a lot of QSO’s with QSL_sent set to ‘R’ but the QSO’s have been confirmed via LOTW and I don’t want to send cards.  I also turned off setting QSL_sent to ‘R’ when I import QSO’s so I can just set it when I want to request a card. 

 

Recently I worked some DX that I can only confirm via card, i.e. they don’t do LOTW.  I set the LOTW_sent to ‘N’ and QSL_sent to ‘R’ for those QSO’s.  When I go to the QSL tab, click on QSL via cards, and click Add Requested, I get all the old QSO’s that I don’t want to print cards for. 

 

So my question is when does QSL_sent get set to ‘R’ and when does LOTW_sent get set to ‘R’ and what is the best way to handle this situation so I only get QSL_sent set to ‘R’ for cards when I actually want to get cards.  I worked out a script for turning off the QSL_sent to ‘R’ on old QSO’s confirmed via LOTW but I am concerned about what might happen if I do that. 

 

Bob AF9W

 


Re: pending card credit

Dave AA6YQ
 

+ AA6YQ comments below

I have cards from 3 30m countries in my file that will be submitted on my next application. They are marked with a "S" in the QSL rcvd block and the date received is shown in the date rcvd line in DXKeeper QSL window. When I do a check of my progress report for my 30m totals on digital they appear on the report as "C" for 30m and digital.

+ That's correct. The QSOs in your submission are confirmed.

Checking LOTW they are not shown as confirmed there. Since they have not been submitted yet that is expected. JTAlert which scans my DXKeeper log for updates does not show them as confirmed.

+ If JTAlert doesn't consider a logged QSO confirmed when its "QSL Rcvd" item is set to 'S', that's a defect in JTAlert.

73,

Dave, AA6YQ


Re: No one is more deserving ...

Dave AA6YQ
 

+ AA6YQ comments below

And the multitudes said AMEN!!!

+ Thanks, Dave!

73,

Dave, AA6YQ


Re: No one is more deserving ...

Dave AA6YQ
 

+ AA6YQ comments below

``The Board conferred the ARRL President s Award on David H.
Bernstein, AA6YQ, in recognition of exemplary, outstanding, and continuing service to ARRL and its members as part of the ARRL Logbook of The World team. Bernstein was a charter member of the ARRL Logbook Committee and a founding, influential, and devoted member of the Committee on Communication with ARRL Members.''

Sincere congratulations, Dave.

+ Thanks, Peter!

73,

Dave, AA6YQ


Re: DxKeeper display question

Dave AA6YQ
 

+ AA6YQ comments below

everytime I enter a new entry into DxKeeper, or clear the "capture" the "log QSos" display jumps to the beginning of my log ( back in 1973) before displaying the current UTC sorted entries.

is this normal????

+ Yes, if you have the "Chronological Sort Order" panel set to "Descending" in the lower-left corner of the Configuration window's Log tab. It sounds like you'd rather have this set to "Ascending".

73,

Dave, AA6YQ

13661 - 13680 of 204721