Date   
Re: Commander and N1MM

Dave AA6YQ
 

+ AA6YQ comments below

Yes - works just fine. It would be perfect if Commander would only pass the RIT reset command through to the connected transceiver via the secondary CAT port. Any chance of that?

+ That's a slippery slope. The purpose of Commander Secondary CAT port is to support frequency and mode tracking. If I extend this to better support N1MM for one transceiver model, I'll eventually have to extend it to support every transceiver model.

+ How would your needs not be satisfied by using the N1MM-DXKeeper bridge and letting N1MM exclusively control the transceiver?

<https://www.dxlabsuite.com/N1MM-DXKeeper/index.htm>

73,

Dave, AA6YQ

Re: Win 10 free upgrade

Phil Cooper
 

Stan,

I believe there is a way to do the clean install with the ISO and the Win7 key. Can't recall the steps right now.

73 de Phil GU0SUP

-----Original Message-----
From: "Stan Gammons" <sg063015@...>
Sent: Sunday, 21 April, 2019 01:21
To: DXLab@groups.io
Subject: Re: [DXLab] RE Win 10 free upgrade

After downloading the ISO from MS a few weeks back and using a Win 7
key, it worked for me.  I did the upgrade though, not a clean install. 
Probably should have done a clean install.


73

Stan
KM4HQE

Re: PropView band selection

Andy k3wyc <a.durbin@...>
 

On Fri, Apr 19, 2019 at 01:56 PM, Dave AA6YQ wrote:
+ Before generating a "To the DX Station" prediction, specify the appropriate Takeoff angle and Power in the "Your Station" panel on the Main window's Parameters tab.
Seems a bit clumsy but, yes, that does work.  Wouldn't a Freq selection under the mode selection of Parameters/Conditions be more convenient?  The available choices would be Rig and all the bands that are populated in "frequency dependent settings".   Setting would default to Rig at program start.

However. given the number of replies to my original post,  I doubt there is enough interest to justify the effort.

73,
Andy, k3wyc

Re: Win 10 free upgrade

Danny Douglas
 

Wish I could remember what I did with the W7 number issued 10 years ago. sigh


N7DC@...
Ex WN5QMX,WA5UKR,ET2US,ET3USA,SV0WPP,VS6DD,N7DC/YV5/G5CTB
QSL Bureau, DIRECT, LOTW Preferred, eQSL used but upload at a courtesy only, as do not use the system for awards.

On April 21, 2019 at 3:21 AM "Phil Cooper via Groups.Io" <pcooper=suremail.gg@groups.io> wrote:


Stan,

I believe there is a way to do the clean install with the ISO and the Win7 key. Can't recall the steps right now.

73 de Phil GU0SUP

-----Original Message-----
From: "Stan Gammons" <sg063015@...>
Sent: Sunday, 21 April, 2019 01:21
To: DXLab@groups.io
Subject: Re: [DXLab] RE Win 10 free upgrade

After downloading the ISO from MS a few weeks back and using a Win 7
key, it worked for me.  I did the upgrade though, not a clean install. 
Probably should have done a clean install.


73

Stan
KM4HQE






Re: PropView band selection

Dave AA6YQ
 

* AA6YQ comments below

+ Before generating a "To the DX Station" prediction, specify the appropriate Takeoff angle and Power in the "Your Station" panel on the Main window's Parameters tab.

Seems a bit clumsy but, yes, that does work. Wouldn't a Freq selection under the mode selection of Parameters/Conditions be more convenient? The available choices would be Rig and all the bands that are populated in "frequency dependent settings". Setting would default to Rig at program start.

However. given the number of replies to my original post, I doubt there is enough interest to justify the effort.

* Better automation for the "generate a propagation prediction for Band A while the radio is on Band B" scenario is certainly possible, but my suspicion is that its use would be so infrequent that few would remember how to employ it. Typing in a take-off angle and power output isn't that clumsy...

73,

Dave, AA6YQ

Re: [FlexRadio Systems] Re: MOX/Transmit not stopping/releasing after WSJT-X transmits

davidg7hjx@...
 

Similar issue here, all was working perfectly with previous version, WSJT, FLDigi and MRP40 all playing nicely with Commander. After updating SmartSDR anything triggering the PTT via Commander made it stay on until MOX was pressed. Even using Commander itself had the same effect. Only workaround I have found is to set the radio in Commander to Kenwood, only issue is mode switching doesn’t work as Kenwood don’t have a DIGI-U mode.

Hope this helps till a new version of Commander comes out.

de Dave G7HJX 

Re: [FlexRadio Systems] Re: MOX/Transmit not stopping/releasing after WSJT-X transmits

Dave AA6YQ
 

+ AA6YQ comments below

Similar issue here, all was working perfectly with previous version, WSJT, FLDigi and MRP40 all playing nicely with Commander. After updating SmartSDR anything triggering the PTT via Commander made it stay on until MOX was pressed. Even using Commander itself had the same effect. Only workaround I have found is to set the radio in Commander to Kenwood, only issue is mode switching doesn’t work as Kenwood don’t have a DIGI-U mode.

Hope this helps till a new version of Commander comes out.

+ Yesterday, I "upgraded" my 6500 to SmartSDR v3, did some testing, and sent my observations to the Flex engineers with whom I am working.

73,

Dave, AA6YQ

Re: [FlexRadio Systems] Re: MOX/Transmit not stopping/releasing after WSJT-X transmits

K4PX K4PX
 

Hello Dave,
Thanks for your input from across the pond.  I have been in touch with DX Labs Dave and Eric at Flex and they are aware of the issue and close to an update to Commander.  Apparently Flex changed code that affected DX Labs and DX Labs was not informed.  I went back to V2.49 on SmartSDR today until it is all sorted.
73,
Joe
K4PX

On Sun, Apr 21, 2019 at 8:08 PM davidg7hjx via Groups.Io <davidg7hjx=tiscali.co.uk@groups.io> wrote:
Similar issue here, all was working perfectly with previous version, WSJT, FLDigi and MRP40 all playing nicely with Commander. After updating SmartSDR anything triggering the PTT via Commander made it stay on until MOX was pressed. Even using Commander itself had the same effect. Only workaround I have found is to set the radio in Commander to Kenwood, only issue is mode switching doesn’t work as Kenwood don’t have a DIGI-U mode.

Hope this helps till a new version of Commander comes out.

de Dave G7HJX 

Re: [FlexRadio Systems] Re: MOX/Transmit not stopping/releasing after WSJT-X transmits

Jeffrey griffin
 

I also went back to ver 2.49 till this gets fixed….

 

73 Jeff kb2m

 

From: DXLab@groups.io <DXLab@groups.io> On Behalf Of K4PX K4PX
Sent: Sunday, April 21, 2019 8:34 PM
To: DXLab@groups.io
Subject: Re: [DXLab] [FlexRadio Systems] Re: MOX/Transmit not stopping/releasing after WSJT-X transmits

 

Hello Dave,

Thanks for your input from across the pond.  I have been in touch with DX Labs Dave and Eric at Flex and they are aware of the issue and close to an update to Commander.  Apparently Flex changed code that affected DX Labs and DX Labs was not informed.  I went back to V2.49 on SmartSDR today until it is all sorted.

73,

Joe

K4PX

 

On Sun, Apr 21, 2019 at 8:08 PM davidg7hjx via Groups.Io <davidg7hjx=tiscali.co.uk@groups.io> wrote:

Similar issue here, all was working perfectly with previous version, WSJT, FLDigi and MRP40 all playing nicely with Commander. After updating SmartSDR anything triggering the PTT via Commander made it stay on until MOX was pressed. Even using Commander itself had the same effect. Only workaround I have found is to set the radio in Commander to Kenwood, only issue is mode switching doesn’t work as Kenwood don’t have a DIGI-U mode.

Hope this helps till a new version of Commander comes out.

de Dave G7HJX 

Re: [FlexRadio Systems] Re: MOX/Transmit not stopping/releasing after WSJT-X transmits

Dave AA6YQ
 

+ AA6YQ comments below

Thanks for your input from across the pond. I have been in touch with DX Labs Dave and Eric at Flex and they are aware of the issue and close to an update to Commander. Apparently Flex changed code that affected DX Labs and DX Labs was not informed. I went back to V2.49 on SmartSDR today until it is all sorted.

1. There is only one DXLab.

2. There is no way to predict whether or not we are "close" to an update to Commander. This being a holiday weekend, it is unreasonable to expect activity from Flex engineers.

3. Flex informed me back in November that there would be a SmartSDR v3, but did not mention that it would not be upward compatible with SmartSDR v2. Since its primary new feature - multiFlex - is primarily aimed at contesters, I ignored the "v3 migration guide" Flex sent me, assuming that SmartSDR v3 would "just work" with the current version of Commander.

73,

Dave, AA6YQ

Re: [FlexRadio Systems] Re: MOX/Transmit not stopping/releasing after WSJT-X transmits

K4PX K4PX
 

Thanks Dave.  I stand corrected.
73
Joe

On Sun, Apr 21, 2019, 8:46 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

Thanks for your input from across the pond.  I have been in touch with DX Labs Dave and Eric at Flex and they are aware of the issue and close to an update to Commander.  Apparently Flex changed code that affected DX Labs and DX Labs was not informed.  I went back to V2.49 on SmartSDR today until it is all sorted.

1. There is only one DXLab.

2. There is no way to predict whether or not we are "close" to an update to Commander. This being a holiday weekend, it is unreasonable to expect activity from Flex engineers.

3. Flex informed me back in November that there would be a SmartSDR v3, but did not mention that it would not be upward compatible with SmartSDR v2. Since its primary new feature - multiFlex - is primarily aimed at contesters, I ignored the "v3 migration guide" Flex sent me, assuming that SmartSDR v3 would "just work" with the current version of Commander.

     73,

            Dave, AA6YQ




Presentation and Notes from last week's DXLab Users Forum at the Visalia International DX Convention

Dave AA6YQ
 

The presentation that Björn SM7IUN used to kick off the session is here:

<http://www.dxlabsuite.com/Presentations/DXLab%20Visalia%20User%20Forum%20Presentation.pdf>

Slides 2-7 of this presentation provide an overview of DXLab for attendees who might not yet be familiar with it.

Slide 8 summarizes the four major enhancements made since the 2017 Visalia International DX Convention, and slides 9 through 12
provide a screen shot illustrating each major enhancement.

Slide 13 provides development statistics for each of the 8 DXLab applications over the past 2 years.

Slide 14 was meant to prompt comments from attendees. This sort of "feedback" is always welcome here on the DXLab Discussion Group.

Notes taken during the forum by volunteer scribe Ron KF7XN are here:

<http://www.dxlabsuite.com/Presentations/DXLab%20Visalia%20User%20Forum%20Notes.pdf>

I've heard nothing but positive comments from attendees of this User Forum. Many thanks to Björn SM7IUN, Dave W6DE, and Ron KF7XN
for standing in for me at the last minute and making it work so well!

73,

Dave, AA6YQ

DX Keeper Mouseover Text

Stewart Wilkinson
 

I have noticed a strange feature with DXKeeper and the Mouseover text when used on my Dual Screen Windows 10 system.

If the DXKeeper window is on the Primary (left) screen the Mouseover text when hovering over the log Columns appears as you might expect next to the Columns, but if the DXKeeper window is place on the Secondary (right) screen the mouseove text appears on the right hand side of the left screen.

The only applies only to the Log list section of the Window and not to the Log entry part of the window.

--
Stewart G0LGS

TQSL Update

Arthur Petteway
 

When I try to update TQSL V2.4.5 build v2.4.6-rc1 to the new version 2.4.7 I get and error: 
Can't open TQSL update file C:\TQSL update: no such file or directory.

How do I fix this?

73,
Art WB4MNK

Re: Win 10 free upgrade

Bill Stravinsky
 

If you go to control panel - system, at the bottom of the info is "Windows Activation" which I believe is the key.  That is what I see in Win 7 which is what I have on 4 of my 5
pc's..  I have one laptop with Win 10 which I took the free upgrade from Win 8 which was a horrible OS, imo.  I will be using Win 7 until I am forced to upgrade.

Bill
K3WJV

On Sunday, April 21, 2019, 1:50:04 PM EDT, Danny Douglas <n7dc@...> wrote:


Wish I could remember what I did with the W7 number issued 10 years ago.  sigh


N7DC@...
Ex WN5QMX,WA5UKR,ET2US,ET3USA,SV0WPP,VS6DD,N7DC/YV5/G5CTB
QSL Bureau, DIRECT, LOTW Preferred, eQSL used but upload at a courtesy only, as do not use the system for awards.


> On April 21, 2019 at 3:21 AM "Phil Cooper via Groups.Io" <pcooper=suremail.gg@groups.io> wrote:
>
>
> Stan,
>
> I believe there is a way to do the clean install with the ISO and the Win7 key. Can't recall the steps right now.
>
> 73 de Phil GU0SUP
>
> -----Original Message-----
> From: "Stan Gammons" <sg063015@...>
> Sent: Sunday, 21 April, 2019 01:21
> To: DXLab@groups.io
> Subject: Re: [DXLab] RE Win 10 free upgrade
>
> After downloading the ISO from MS a few weeks back and using a Win 7
> key, it worked for me.  I did the upgrade though, not a clean install. 
> Probably should have done a clean install.
>
>
> 73
>
> Stan
> KM4HQE
>
>
>
>
>
>
>


Re: TQSL Update

Joe Subich, W4TV
 

Update worked just fine for me from within tQSL (release version).

You should probably be able to download the installer directly from
the LotW site and run it manually but I did not need to do that.

73,

... Joe, W4TV

On 2019-04-22 11:34 AM, Arthur Petteway wrote:
When I try to update TQSL V2.4.5 build v2.4.6-rc1 to the new version 2.4.7 I get and error:
Can't open TQSL update file C:\TQSL update: no such file or directory.
How do I fix this?
73,
Art WB4MNK

Re: Win 10 free upgrade

Danny Douglas
 

Thanks Bill.  Ill take a look.  I too, intend to wait as long as possible, but frankly, without the security updates, etc, from W7, Ill probably switch over at the last moment.  Was just glad to see it was still available.  I find some things on W10 that I cant do with W7, but have been happy with the latter, for years.  Now that MS has let us delay their mad upgrades for a month or so, I have put that into effect, and hope they dont just ignore it.  Without that, I have no problem with w10.

Danny


N7DC@...
Ex WN5QMX,WA5UKR,ET2US,ET3USA,SV0WPP,VS6DD,N7DC/YV5/G5CTB
QSL Bureau, DIRECT, LOTW Preferred, eQSL used but upload at a courtesy only, as do not use the system for awards.

On April 22, 2019 at 11:39 AM "Bill Stravinsky via Groups.Io" <k3wjv@...> wrote:

 
If you go to control panel - system, at the bottom of the info is "Windows Activation" which I believe is the key.  That is what I see in Win 7 which is what I have on 4 of my 5
pc's..  I have one laptop with Win 10 which I took the free upgrade from Win 8 which was a horrible OS, imo.  I will be using Win 7 until I am forced to upgrade.

Bill
K3WJV

On Sunday, April 21, 2019, 1:50:04 PM EDT, Danny Douglas <n7dc@...> wrote:


Wish I could remember what I did with the W7 number issued 10 years ago.  sigh


N7DC@...
Ex WN5QMX,WA5UKR,ET2US,ET3USA,SV0WPP,VS6DD,N7DC/YV5/G5CTB
QSL Bureau, DIRECT, LOTW Preferred, eQSL used but upload at a courtesy only, as do not use the system for awards.


> On April 21, 2019 at 3:21 AM "Phil Cooper via Groups.Io" <pcooper= suremail.gg@groups.io> wrote:
>
>
> Stan,
>
> I believe there is a way to do the clean install with the ISO and the Win7 key. Can't recall the steps right now.
>
> 73 de Phil GU0SUP
>
> -----Original Message-----
> From: "Stan Gammons" < sg063015@...>
> Sent: Sunday, 21 April, 2019 01:21
> To: DXLab@groups.io
> Subject: Re: [DXLab] RE Win 10 free upgrade
>
> After downloading the ISO from MS a few weeks back and using a Win 7
> key, it worked for me.  I did the upgrade though, not a clean install. 
> Probably should have done a clean install.
>
>
> 73
>
> Stan
> KM4HQE
>
>
>
>
>
>
>



 


 

Re: TQSL Update

Björn Ekelund, SM7IUN
 

I got a similar error message but mine said that "C\tqslupdate.msi" is not availabe.
Which is not very surprising, since it obviously lacks a colon after the C. 
I guess there wasn't enough QA done on this release. Either. 

I updated using the dowloaded file from  http://www.arrl.org/tqsl-download without issues.

73,

Björn SM7IUN


Den mån 22 apr. 2019 kl 17:34 skrev Arthur Petteway <wb4mnk@...>:

When I try to update TQSL V2.4.5 build v2.4.6-rc1 to the new version 2.4.7 I get and error: 
Can't open TQSL update file C:\TQSL update: no such file or directory.

How do I fix this?

73,
Art WB4MNK

Re: TQSL Update

w7psk
 

I wound up downloading it off the ARRL web site also.

73

Scotty W7PSK


On 4/22/2019 11:44 AM, Bjorn SM7IUN wrote:
I got a similar error message but mine said that "C\tqslupdate.msi" is not availabe.
Which is not very surprising, since it obviously lacks a colon after the C. 
I guess there wasn't enough QA done on this release. Either. 

I updated using the dowloaded file from  http://www.arrl.org/tqsl-download without issues.

73,

Björn SM7IUN


Den mån 22 apr. 2019 kl 17:34 skrev Arthur Petteway <wb4mnk@...>:
When I try to update TQSL V2.4.5 build v2.4.6-rc1 to the new version 2.4.7 I get and error: 
Can't open TQSL update file C:\TQSL update: no such file or directory.

How do I fix this?

73,
Art WB4MNK

Re: DX Keeper Mouseover Text

Dave AA6YQ
 

+ AA6YQ comments below

I have noticed a strange feature with DXKeeper and the Mouseover text when used on my Dual Screen Windows 10 system.

If the DXKeeper window is on the Primary (left) screen the Mouseover text when hovering over the log Columns appears as you might expect next to the Columns, but if the DXKeeper window is place on the Secondary (right) screen the mouseove text appears on the right hand side of the left screen.

The only applies only to the Log list section of the Window and not to the Log entry part of the window.

+ That's a defect in the commercial control (Trued DB Grid Pro) used to implement DXKeeper's Spot Database Display, DXView's Override List, SpotCollector's Special Callsign List, and SpotCollector's Spot Database Display. Since it’s the only defect in this control, I continue to defer the acquisition and testing of the latest version.

73,

Dave, AA6YQ