Date   

Re: Windows 10 Power Toys

Gilbert Baron W0MN
 

I fail to see how this is a gain over workspaces for DXLABS?

 

Outlook Laptop Gil W0MN

Hierro Candente Batir de Repente

44.08226N 92.51265 W en34rb

 

From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Steve Sacco via Groups.Io
Sent: Tuesday, October 1, 2019 08:13
To: DXLab@groups.io
Subject: [DXLab] Windows 10 Power Toys

 

I've been reading an article on Windows 10 Power Toys this morning: https://www.techrepublic.com/article/windows-10-powertoys-a-cheat-sheet/?

One feature caught my attention:

FancyZones

FancyZones allows users to manage where and how each separate application window open on a Windows 10 desktop will display.

For example, you could use FancyZones to set up a Windows 10 desktop where Outlook always displays on the right-hand side of the desktop, Twitter or other social media always displays on the left-hand side of the desktop, and Word or Excel always displays in the middle between the other two. There would be three distinct and perpetual zones displayed at all times. Figure B shows how you select that configuration.

It struck me that it might be a great tool for managing our DXLab (and other) applications.

Is anyone using Windows 10 Power Toys?  If so, I'd appreciate any feedback.

Thanks/73,
Steve
NN4X


--

W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop


Windows 10 Power Toys

Steve Sacco
 

I've been reading an article on Windows 10 Power Toys this morning: https://www.techrepublic.com/article/windows-10-powertoys-a-cheat-sheet/?

One feature caught my attention:

FancyZones

FancyZones allows users to manage where and how each separate application window open on a Windows 10 desktop will display.

For example, you could use FancyZones to set up a Windows 10 desktop where Outlook always displays on the right-hand side of the desktop, Twitter or other social media always displays on the left-hand side of the desktop, and Word or Excel always displays in the middle between the other two. There would be three distinct and perpetual zones displayed at all times. Figure B shows how you select that configuration.

It struck me that it might be a great tool for managing our DXLab (and other) applications.

Is anyone using Windows 10 Power Toys?  If so, I'd appreciate any feedback.

Thanks/73,
Steve
NN4X


Re: using dx commander with satpc32 questions

Bill Pence
 

I'll try that. The satpc32 com port I did not see a change, so its not configured.

Thanks!


On Mon, Sep 30, 2019, 8:07 PM Joe Subich, W4TV <lists@...> wrote:

Bill,

You likely have an error on the "Multi-Radio" tab ...

Make sure the COM port # for the SatPC32 port is set to '-'
(the last entry, below COM64) so that Commander releases
the CAT port when SatPC32 is selected.

Note: you must also select SatPC32 as the radio before you
start SatPC32 (if Commander has been running in "direct"
- HF mode).

73,

    ... Joe, W4TV


On 2019-09-30 5:26 PM, Bill Pence wrote:
> 1st and most importantly, THANKS!! the capture window populates
> well.
>
> I seem to have a couple of odd things with the serial port
> controlling the radio.
>
> if I open satpc32, and get it connected to the radio, then open
> commander (last commander mode was satpc32...) commander complains
> that it cannot open serial port.  I think I configured the multi
> radio interface configuration correctly, and commander has satpc32
> selected when it starts. but commander still seems to try to capture
> the CAT com port? (I get error pop up "unable to open com3"  2x when
> commander starts.)
>
> also if i have commander open and in "direct" mode (not saptc32...)
> then select satpc32 mode, the  open satpc32, satpc32 cannot connect
> to the radio serial port.  I need to close commander, the open
> satpc32, then open commander. so commander might not be freeing the
> cat com port?
>
> did I miss some config to allow easy switching? I am running windows
> 7 pro SP1, 64 bit. satpc32 V.12.8d (registered version) commander
> version 14.2.6 my radio is FT-847 with FTDI USB serial interface
> COM3
>
> I'll try to gather any debug info to help...
> thanks. > KI4US> bill pence
>




Re: using dx commander with satpc32 questions

Dave AA6YQ
 

+ AA6YQ comments below

You likely have an error on the "Multi-Radio" tab ...

Make sure the COM port # for the SatPC32 port is set to '-'
(the last entry, below COM64) so that Commander releases the CAT port when SatPC32 is selected.

+ That requirement is illustrated in the screen shot in

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

+ but was not explicitly mentioned until a edited the page a few minutes ago. Bill, please let me know if this doesn't enable you to smoothly switch Commander between interoperating directly with SatPC32 and directly controlling your transceiver.

Note: you must also select SatPC32 as the radio before you start SatPC32 (if Commander has been running in "direct"- HF mode).

+ Correct; otherwise, SatPC32 won't be able to connect to your radio.

73,

Dave, AA6YQ


Re: using dx commander with satpc32 questions

Joe Subich, W4TV
 

Bill,

You likely have an error on the "Multi-Radio" tab ...

Make sure the COM port # for the SatPC32 port is set to '-'
(the last entry, below COM64) so that Commander releases
the CAT port when SatPC32 is selected.

Note: you must also select SatPC32 as the radio before you
start SatPC32 (if Commander has been running in "direct"
- HF mode).

73,

... Joe, W4TV

On 2019-09-30 5:26 PM, Bill Pence wrote:
1st and most importantly, THANKS!! the capture window populates
well.
I seem to have a couple of odd things with the serial port
controlling the radio.
if I open satpc32, and get it connected to the radio, then open
commander (last commander mode was satpc32...) commander complains
that it cannot open serial port. I think I configured the multi
radio interface configuration correctly, and commander has satpc32
selected when it starts. but commander still seems to try to capture
the CAT com port? (I get error pop up "unable to open com3" 2x when
commander starts.)
also if i have commander open and in "direct" mode (not saptc32...)
then select satpc32 mode, the open satpc32, satpc32 cannot connect
to the radio serial port. I need to close commander, the open
satpc32, then open commander. so commander might not be freeing the
cat com port?
did I miss some config to allow easy switching? I am running windows
7 pro SP1, 64 bit. satpc32 V.12.8d (registered version) commander
version 14.2.6 my radio is FT-847 with FTDI USB serial interface
COM3
I'll try to gather any debug info to help... thanks. > KI4US> bill pence


using dx commander with satpc32 questions

Bill Pence
 

 
1st and most importantly, THANKS!! the capture window populates well.  
 
I seem to have a couple of odd things with the serial port controlling the radio.
 
if I open satpc32, and get it connected to the radio, then open commander (last commander mode was satpc32...)
commander complains that it cannot open serial port.  I think I configured the multi radio interface configuration correctly, and commander has
satpc32 selected when it starts. but commander still seems to try to capture the CAT com port?
(I get error pop up "unable to open com3"  2x when commander starts.)

also if i have commander open and in "direct" mode (not saptc32...) then select satpc32 mode, the  open satpc32, satpc32 cannot connect to the radio serial port.  I need to close commander, the open satpc32, then open commander. so commander might not be freeing the cat com port?

did I miss some config to allow easy switching? I am running windows 7 pro SP1, 64 bit. 
satpc32 V.12.8d (registered version)
commander version 14.2.6
my radio is FT-847 with FTDI USB serial interface COM3

I'll try to gather any debug info to help...
thanks.
KI4US
bill pence


Re: USA-CA Counties Report

Dave AA6YQ
 

# more AA6YQ comments below

snip<
*** thanks for the suggestion. However the QSOs I indicated above do not appear in the DxK report (done without any filter and neither if just filtered by eQSL-AG). The QSOs are not confirmed by Card and the calls are eQSL-AG (i.e. W7ZR, NZ4CW,N0AV, etc.)

# W7ZR is not listed in the 2019-09-22 eQSL AG database maintained by DXView. I just downloaded the list of AG users from eQSL, and W7ZR is still not present.

# Examine the QSOs in question in DXKeeper; are their "eQSL Member" items set to A ?


snip<
*** Last request to you: How can I sort ALL my QSOs having the same "secondary_administrative_subdivision" - sec sub - in Award main pane? For example AZ, Mohave? Which SQL?

# Sorting the Log Page Display does not involve the use of SQL. See the 3rd paragraph in

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

# Then sort the Log Page Display by the CNTY field.

73,

Dave, AA6YQ


Re: VE7CC

Paul W5PF
 

Mike, Glad it worked for you!

73, Paul W5PF

On 9/30/2019 12:44 AM, Mike NA5U wrote:

Paul,

Thanks for the input.

Mike

NA5U

 

From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Floyd Sense
Sent: Sunday, September 29, 2019 7:23 PM
To: DXLab@groups.io
Subject: Re: [DXLab] VE7CC

 

Port 7300, that is.,


R: [DXLab] USA-CA Counties Report

Carlo - IK2RPE
 

*** IK2RPE comments/answers below

-----Messaggio originale-----
Da: DXLab@groups.io <DXLab@groups.io> Per conto di Dave AA6YQ
Inviato: domenica 29 settembre 2019 18:35
A: DXLab@groups.io
Oggetto: Re: [DXLab] USA-CA Counties Report

+ AA6YQ comments below

Preparing my submission for the USA-CA counties Award (> 500) I discovered that:

1. few dozen of confirmed (by card) counties do not appear on the DxKeeper report. I realized that because these QSOs were ALSO confirmed with eQSL and included in the eQSL site report.

+ What is an "eQSL site report"?

*** the list sorted in eQSL for USA-CA award

How many others QSOs confirmed only by card have not been taken into consideration in the DxKeeper report?

Did I miss something in the configuration?

+ Your questions imply that submitting QSOs confirmed via eQSL AG is erroneous. Such confirmations are valid for USA-CA.

*** these QSO are accepted in eQSL submission award. They are all AG

+ If for some reason you only want to submit QSOs confirmed via QSL card, then before invoking the USA-CA progress report, filter the Log Page Display with

QSL_RCVD in ('Y','S','V')

+ After you click the USA-CA button, DXKeeper will ask if you want this filter removed; click the No button.

*** thanks for the suggestion. However the QSOs I indicated above do not appear in the DxK report (done without any filter and neither if just filtered by eQSL-AG). The QSOs are not confirmed by Card and the calls are eQSL-AG (i.e. W7ZR, NZ4CW,N0AV, etc.)


2. The Award requests that ALSO the date of the QSO is indicated. (The rule says: Contacts must be arranged alphabetically by state and then alphabetically by county within each state. Information provided for each contact must include call sign, date of contact, band and mode, in that order. Computer-generated lists must be in a tabular format with separate columns for each field listed above). In the DxKeeper report that date does not appear? Did I miss something in the configuration? Can I bypass this missing data/element? How?

+ Either this is a new requirement, or its been ignored for the past 19 years, as no one has ever reported their USA-CA progress report being rejected due to the QSO Date not being present. I have added "QSO Date" to the USA-CA progress report in the next version of DXKeeper, which is imminent.

*** Thanks for the date implementation (just in time!!). It works perfectly. The USA-CA Awards Manager Brian - NX0X has just confirmed me that he needs the date also.
*** Last request to you: How can I sort ALL my QSOs having the same "secondary_administrative_subdivision" - sec sub - in Award main pane? For example AZ, Mohave? Which SQL?

*** Thanks Carlo IK2RPE

73,

Dave, AA6YQ








---
Questa email è stata esaminata alla ricerca di virus da AVG.
http://www.avg.com


Re: VE7CC

Mike NA5U <mike@...>
 

Paul,

Thanks for the input.

Mike

NA5U

 

From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Floyd Sense
Sent: Sunday, September 29, 2019 7:23 PM
To: DXLab@groups.io
Subject: Re: [DXLab] VE7CC

 

Port 7300, that is.,


Re: VE7CC

Mike NA5U <mike@...>
 

Paul,
23 worked!
Thanks,
Mike
NA5U

-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Paul W5PF
Sent: Sunday, September 29, 2019 7:22 PM
To: DXLab@groups.io
Subject: Re: [DXLab] VE7CC


I use 23 as the port.

Paul W5PF

On 9/29/2019 6:57 PM, Mike NA5U wrote:
I have been trying to connect to VE7CC as one of the telnet spotting sites.
I am using dxc.ve7cc.net as the Host Address and 7300 as the Port.
Does someone know if that is correct?
Thanks,
Mike
NA5U





Re: SpotCollector 8.4.4 is available

Dave AA6YQ
 

Apologetic correction: Dave's call is N9FN.

73,

Dave, AA6YQ

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Dave AA6YQ
Sent: Sunday, September 29, 2019 3:00 PM
To: DXLab@groups.io
Subject: [DXLab] SpotCollector 8.4.4 is available

In this release

- improves performance of the Recompute function when processing a Spot Database Entry that doesn't specify a CQ zone (tnx to Dave
K9FN)

- with the "Spot Xcvr split" option enabled when Commander is connected to a satellite tracking application, populates the Main
window's "Outgoing spot" panel with the active satellite name and downlink frequency (tnx to Jeff KB2M)

- updates the ConfigurationGeneral.htm, ConfigurationSpecialCallsigns.htm, SourceConnection.htm, and SpotDatabase.htm documentation
files

Notes:

1. Step-by-step instructions for interoperating with SatPC32 are available here:
<https://www.dxlabsuite.com/dxlabwiki/SatelliteTracking>

2. Update your firewall and anti-malware applications to consider this new version of SpotCollector to be "safe"

3. If this upgrade doesn't work correctly, see the "After an Upgrade" section of
<http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking>

4. After upgrading, to revert to the previous version of SpotCollector, see
<http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion>



SpotCollector 8.4.4 is available via the DXLab Launcher, and via

<http://www.dxlabsuite.com/download.htm>


73,

Dave, AA6YQ


test - please ignore

Joe - W9RF
 

test


Re: VE7CC

Floyd Sense
 

Port 7300, that is.,


Re: VE7CC

Floyd Sense
 

That works for me.

73, Floyd - K8AC


Re: VE7CC

Paul W5PF
 

I use 23 as the port.

Paul W5PF

On 9/29/2019 6:57 PM, Mike NA5U wrote:
I have been trying to connect to VE7CC as one of the telnet spotting sites.
I am using dxc.ve7cc.net as the Host Address and 7300 as the Port. Does
someone know if that is correct?
Thanks,
Mike
NA5U




VE7CC

Mike NA5U <mike@...>
 

I have been trying to connect to VE7CC as one of the telnet spotting sites.
I am using dxc.ve7cc.net as the Host Address and 7300 as the Port. Does
someone know if that is correct?
Thanks,
Mike
NA5U


SpotCollector 8.4.4 is available

Dave AA6YQ
 

In this release

- improves performance of the Recompute function when processing a Spot Database Entry that doesn't specify a CQ zone (tnx to Dave
K9FN)

- with the "Spot Xcvr split" option enabled when Commander is connected to a satellite tracking application, populates the Main
window's "Outgoing spot" panel with the active satellite name and downlink frequency (tnx to Jeff KB2M)

- updates the ConfigurationGeneral.htm, ConfigurationSpecialCallsigns.htm, SourceConnection.htm, and SpotDatabase.htm documentation
files

Notes:

1. Step-by-step instructions for interoperating with SatPC32 are available here:
<https://www.dxlabsuite.com/dxlabwiki/SatelliteTracking>

2. Update your firewall and anti-malware applications to consider this new version of SpotCollector to be "safe"

3. If this upgrade doesn't work correctly, see the "After an Upgrade" section of
<http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking>

4. After upgrading, to revert to the previous version of SpotCollector, see
<http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion>



SpotCollector 8.4.4 is available via the DXLab Launcher, and via

<http://www.dxlabsuite.com/download.htm>


73,

Dave, AA6YQ


DXKeeper 15.1.5 is available

Dave AA6YQ
 

This release

- correctly handles a callbook lookup when the logged QSO specifies US state but not a US county (tnx to Frank G4HBI)

- with the "Use multiple monitors" option disabled, ensures that the Main window size is less than the monitor dimensions (tnx to
Raoul IK0RCY)

- responds to expanding the width of the Main window's "my QTHs" tab by expanding the width of the "my QTHs" table shown on that tab
(tnx to Raoul IK0RCY)

- when logging via the Capture window with Commander connected to a satellite tracking application, populates the "Satellite Name"
and "Satellite Mode" items with the information reported by Commander (tnx to Joe W4TV, Dave N9FN, and Jeff KB2M)

- when logging via the Main window's "Log QSOs" tab with "optimize for realtime QSO entry" enabled and with Commander connected to a
satellite tracking application, populates the "Satellite Name" and "Satellite Mode" items with the information being reported by
Commander, and sets the "Prop Mode" item to SAT (tnx to Joe W4TV, Dave N9FN, and Jeff KB2M)

- adds "Date & Time" to the USA-CA award progress report (tnx to Carlo IK2RPE)

- updates the Initialization.htm, LogNewCapture.htm, and QSL.htm documentation files


Notes:

1. Step-by-step instructions for interoperating with SatPC32 are available here:
<https://www.dxlabsuite.com/dxlabwiki/SatelliteTracking>

2. Update your firewall and anti-malware applications to consider this new version of DXKeeper to be "safe"

3. If this upgrade doesn't work correctly, see the "After an Upgrade" section of
<http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking>

4. After upgrading, to revert to the previous version of DXKeeper, see
<http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion>



DXKeeper 15.1.5 is available via the DXLab Launcher and via

<http://www.dxlabsuite.com/download.htm>


Commander 14.2.6 is available

Dave AA6YQ
 

This release

- when controlling a Flex Signature radio, defers the processing of new active callsigns while transmitting

- when controlling an IC-9700 with Satellite Mode enabled, labels the Main window's VFOs as Main and Sub

- can connect to the SatPC32 satellite tracking application, and when connected provide DXKeeper with the active Satellite's Name
and Mode (tnx to Joe W4TV, Dave N9FN, and Jeff KB2M)

- updates the ChangingFrequency.htm, CommandSequences.htm, Configuration.htm, ControllingMultipleRadios.htm, index.htm,
MonitoringMessages.htm, QuickSetup.htm, SMeter.htm, and TXMeter.htm documentation files (tnx to Mike K9UW)

- adds the Satellite Tracking.htm documentation file


Notes

1. Step-by-step instructions for interoperating with SatPC32 are available here:
<https://www.dxlabsuite.com/dxlabwiki/SatelliteTracking>


2. Update your firewall and anti-malware applications to consider this new version of Commander to be "safe"


3. If this upgrade doesn't work correctly, see the "After an Upgrade" section of
<http://www.dxlabsuite.com/dxlabwiki/ApplicationStoppedWorking>


4. After upgrading, to revert to the previous version of Commander, see
<http://www.dxlabsuite.com/dxlabwiki/RevertApplicationVersion>



Commander 14.2.6 is available via the DXLab Launcher and via

<http://www.dxlabsuite.com/download.htm>

73,

Dave, AA6YQ

20301 - 20320 of 208158