Date   
Smart SDR 3.0.1.9 loaded but not working corrected with DX Commander and WSJT-X

K4PX K4PX
 

So Flex 6400+Maestro/WSJT-X/DX Labs-Commander worked great 100% of the time with Smart SDR V2.X.  Loaded Smart SDR V3 and now a major problem.  Once I initiate a transmission in WSJT-X, the Flex gets "stuck in transmit" and I have to press MOX button on Maestro two times to get it to release transmit more and return to receive.  Seems like a communications/setup issue between DX Commanded and WSJT-X now with SMartSDR V3??  Any help would be appreciated.  I have no RF issues and never have.  As I said everything worked fine together until I loaded SmartSDR V3.  Flex folks no help so far but they have tried.  Thanks.
Joe

Re: Win 10 ?????

Peter Laws
 

On Fri, Apr 19, 2019 at 2:17 PM Jim Miller, AB3CV <jtmiller47@...> wrote:

My opinion is that the Win10 wailing is wayyyyy overblown. I've updated or clean installed a half dozen machines to Win10 with no big issues. Occasionally need to reset a com port. Updates have never been a problem.

I have no idea why others seem so beset.
My opinion as well. And I say that as someone who has never been a
Microsoft fan (I run OS X and Linux IRL). Now, I will say, that
UPGRADING is something I've never done,with Windows (or Solaris!).
Always a clean install. OS X upgrades have been fine and point
upgrades on Linux (say, CentOS 7.5 to 7.6 but not 6.x to 7.x) have
been fine but I've never trusted MS to do it correctly. But a clean
install of 7 or 10 has never given me issues. XP SP2 and later,
either, for that matter, and I've run all those on my PC at N5UWY.

I must say MS broke their interface with W8/8.1/10 and Classic Shell
fixed that for me. Control of multiple sound cards is another nagging
point with W10 (can be done, but not easily or intuitively). I do my
patch updates myself and wouldn't let any OS handle that chore for me.
Other than those things, no issues with W10 here.


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

Re: Win 10 ?????

Jamie WW3S
 

I resisted.....forever.....but needed a new pc and my only option was win10....it wasn’t that bad, I now have fresh installs on all my programs, only loaded what I needed, new ssd drive blows the doors off my old pc.....Dave’s work with dxlab makes it easy to backup all your settings/files ( I used external hard drive) and then just import them to the new pc.....like I said I was one of the guys, but now don’t know what all the wailing and gnashing of teeth was about....

On Apr 19, 2019, at 4:21 PM, Peter Laws <plaws0@...> wrote:

On Fri, Apr 19, 2019 at 2:17 PM Jim Miller, AB3CV <jtmiller47@...> wrote:

My opinion is that the Win10 wailing is wayyyyy overblown. I've updated or clean installed a half dozen machines to Win10 with no big issues. Occasionally need to reset a com port. Updates have never been a problem.

I have no idea why others seem so beset.
My opinion as well. And I say that as someone who has never been a
Microsoft fan (I run OS X and Linux IRL). Now, I will say, that
UPGRADING is something I've never done,with Windows (or Solaris!).
Always a clean install. OS X upgrades have been fine and point
upgrades on Linux (say, CentOS 7.5 to 7.6 but not 6.x to 7.x) have
been fine but I've never trusted MS to do it correctly. But a clean
install of 7 or 10 has never given me issues. XP SP2 and later,
either, for that matter, and I've run all those on my PC at N5UWY.

I must say MS broke their interface with W8/8.1/10 and Classic Shell
fixed that for me. Control of multiple sound cards is another nagging
point with W10 (can be done, but not easily or intuitively). I do my
patch updates myself and wouldn't let any OS handle that chore for me.
Other than those things, no issues with W10 here.


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


Re: Win 10 ?????

Dave AA6YQ
 

It's fair to say that Windows 10 works well for many amateur radio. However, it has not yet attained "works well for all amateur radio users".

Hopefully it will get there before Microsoft's scheduled end-of-support date for Windows 7.

I'm still using Windows 7 for DXing and DXLab development.

73,

Dave, AA6YQ

Re: DXLab Suite - SmartSDR help needed

Dave AA6YQ
 

+ AA6YQ comments below

I purchased a Visalia promotion Flex 6600 and Maestro and took delivery on it this past Wed. It came with SmartSDR v 3.0.x which is
of course not fully compatible with DXLab Suite.

+ I use SmartSDR 2.4.9 with my Flex 6500; I do not have a Maestro, but I'm not aware of any reported problems using the current
public version of Commander with any Flex configuration.

+ See

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

73,

Dave, AA6YQ

Re: DXLab Suite - SmartSDR help needed

Dave AA6YQ
 

As has been reported here several times over the past weeks, the current version of Commander cannot reliably switch SmartSDR version 3 between TX and RX. Jamie WW3S and I are working with Flex personnel to determine why this is happening.

I've already updated the next version of Commander to handle a change in API command syntax in SmartSDR v3 that prevents the current version of Commander from muting a VFO. After we've resolved the "TX-RX" issue and Jamie confirms correct operation, I will make the new version of Commander publicly available.

73,

Dave, AA6YQ

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Jeff Schwartz via Groups.Io
Sent: Friday, April 19, 2019 10:27 AM
To: DXLab@groups.io
Subject: Re: [DXLab] DXLab Suite - SmartSDR help needed

Gary,
Congrats on your 6600 purchase. It’s an amazing rig. Version 3.0.19 actually seems to continue to work well with most DX Labs applications as far as I can tell EXCEPT for the biggie TX /RX control. This has only affected WSJT-X and WinWarbler for me. Flex PTT, however, is easily control by creating an SDR CAT port for WSJT-X and an SDR CAT PTT port for WinWarbler. Both WSJT-X and WinWarbler need to be reconfigured to make that work but it is a simple process once you create the two ports mentioned in SDR CAT. WSJT-X needs to be configured for control by Flex instead of controlled by DX. lab Suites. As for CW and SSB PTT WinWarbler did not require any changes for me if I’m sending CW from WinWarbler or using my PTT hand switch plugged into the Flex.

You our are welcome to contact me at ki0kb@... and I can send you pictures on how to set this up.

Jeff Schwartz

Re: WSJT-X version 2.0.1 is available

Dave AA6YQ
 

+ AA6YQ comments below

New issue with SmartSDR v3.0.1.9 as follows. When I call a station on FT8 using WSJT-X of course and DX COmmander, when the 6400/Maestro MOX red light on Maestro and the red on/off 6400 button get "stuck on"...in other words they do not release and return to receive. I have to press the MOX button on the Maestro a couple of times to stop the transmit mode. HELP!

+ See

<https://groups.io/g/DXLab/message/185291.

73,

Dave, AA6YQ

Re: PropView band selection

Dave AA6YQ
 

+ AA6YQ comments below

PropView can be be configured to have band specific parameters but it appears that these band specific parameters can only be invoked by setting the transceiver to the band of interest. The user can select (in Parameters/Conditions) the mode to be evaluated and that mode is not constrained to be the mode currently in use. I would find it useful to be able to specify the band in Parameters/Conditions, or elsewhere, so I can check conditions on another band without leaving the band I'm currently working.

How do other users review propagation for one band while working another?

+ On the Configuration window's Prediction tab, uncheck the "Frequency-dependent Settings" panel's Enable box.

+ 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.

73,

Dave, AA6YQ

Re: Win 10 ?????

n4qwf .
 

Thanks for all the comments. Sounds like a clean install would be the way to go. I will still likely wait until I have no choice but move to Win 10. When Dave says he is still holding on to Win 7 that sure impresses me.

When I got the Flex Radio I set it up using a computer that was built especially for the system. It has always preformed excellently. It has handled PowerSDR, DXLab, WSJT-X, N1MM all running at the same time without issue. I do not use it for email and other internet chores even though it is connected to my in house network and the internet.

I guess for now I will follow the advise "if it ain't broke don't fix it".

Thanks <<John N4QWF

Re: Win 10 ?????

KA9JAC
 

A clean install is the best thing to do.
When doing it as an update, you bring along all the garbage that has been collected over the years.
Even when not changing from 7 or whatever to 10, it is a good plan to occasionally do a clean install
just to clean out the trash.



On 4/19/2019 4:15 PM, n4qwf . wrote:
Thanks for all the comments. Sounds like a clean install would be the way to go. I will still likely wait until I have no choice but move to Win 10. When Dave says he is still holding on to Win 7 that sure impresses me.

When I got the Flex Radio I set it up using a computer that was built especially for the system. It has always preformed excellently. It has handled PowerSDR, DXLab, WSJT-X, N1MM all running at the same time without issue. I do not use it for email and other internet chores even though it is connected to my in house network and the internet.

I guess for now I will follow the advise "if it ain't broke don't fix it".

Thanks <<John N4QWF


Virus-free. www.avg.com

DXKeeper Error

Robie
 

Dave,

I just completed:

 SYNC LOTW QSOs
SYNC LOTW QSLs

I noticed that DXKeeper indicated there was an error log. I found the following as the latest entry in the error log:

19-Apr-2019 23:25:49 > program error 5 in module ADIF.Parse: Invalid procedure call or argument

What actions should I take,


Robie - AJ4F


Re: DXKeeper Error

Dave AA6YQ
 

+ AA6YQ comments below

On Fri, Apr 19, 2019 at 04:35 PM, Robie wrote:

I just completed:
 
 SYNC LOTW QSOs
SYNC LOTW QSLs
 
I noticed that DXKeeper indicated there was an error log. I found the following as the latest entry in the error log:
 
19-Apr-2019 23:25:49 > program error 5 in module ADIF.Parse: Invalid procedure call or argument
 
What actions should I take,

+ Please attach the errorlog.txt file to an email message, and send the message to me via aa6yq (at) ambersoft.com

      73,

           Dave, AA6YQ

Re: DXKeeper Error

Robie
 

Dave,

I e-mailed the file a few minutes ago.

Robie - AJ4F

On Fri, Apr 19, 2019 at 11:48 PM Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below

On Fri, Apr 19, 2019 at 04:35 PM, Robie wrote:

I just completed:
 
 SYNC LOTW QSOs
SYNC LOTW QSLs
 
I noticed that DXKeeper indicated there was an error log. I found the following as the latest entry in the error log:
 
19-Apr-2019 23:25:49 > program error 5 in module ADIF.Parse: Invalid procedure call or argument
 
What actions should I take,

+ Please attach the errorlog.txt file to an email message, and send the message to me via aa6yq (at) ambersoft.com

      73,

           Dave, AA6YQ

Re: WSJT-X version 2.0.1 is available

K4PX K4PX
 

Hi Dave:

Thanks for your efforts.  I am totally committed to your fine software.  DX Labs is the last thing that would go from my shack.  I am totally disgusted with Flex Radio/SmartSDR and will most likely revert back to V2.4X.  If that fails, I will sell all my Flex equipment and go back to Icom where I probably should have stayed.  Thanks again.

Best,
Joe
K4PX

On Fri, Apr 19, 2019 at 4:50 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

New issue with SmartSDR v3.0.1.9 as follows.  When I call a station on FT8 using WSJT-X of course and DX COmmander, when the 6400/Maestro MOX red light on Maestro and the red on/off 6400 button get "stuck on"...in other words they do not release and return to receive.  I have to press the MOX button on the Maestro a couple of times to stop the transmit mode.  HELP! 

+ See

<https://groups.io/g/DXLab/message/185291.

     73,

           Dave, AA6YQ




Re: WSJT-X version 2.0.1 is available

Dave AA6YQ
 

+ AA6YQ comments below

Thanks for your efforts. I am totally committed to your fine software. DX Labs is the last thing that would go from my shack. I am totally disgusted with Flex Radio/SmartSDR and will most likely revert back to V2.4X. If that fails, I will sell all my Flex equipment and go back to Icom where I probably should have stayed. Thanks again.

+ I suggest that you revert to v2 until we can determine why Commander isn't working correctly with v3 (without multiFlex). In my experience, making decisions while frustrated or angry is not a recipe for a good outcome.

+ My understanding is that reverting from SmartSDR v3 to v2 requires saving your settings, performing a factory reset, starting SmartSDR v2, and restoring your saved settings - but I'll defer to Eric KE5DTO of Flex.

73,

Dave, AA6YQ

Re: DXLab Suite - SmartSDR help needed

K4PX K4PX
 

Please let me know when the new version is available so I can try it on my Flex thank you very much hopefully it will fix my problem


On Fri, Apr 19, 2019, 4:46 PM Dave AA6YQ <aa6yq@...> wrote:
As has been reported here several times over the past weeks, the current version of Commander cannot reliably switch SmartSDR version 3 between TX and RX. Jamie WW3S and I are working with Flex personnel to determine why this is happening.

I've already updated the next version of Commander to handle a change in API command syntax in SmartSDR v3 that prevents the current version of Commander from muting a VFO. After we've resolved the "TX-RX" issue and Jamie confirms correct operation, I will make the new version of Commander publicly available.

       73,

             Dave, AA6YQ

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Jeff Schwartz via Groups.Io
Sent: Friday, April 19, 2019 10:27 AM
To: DXLab@groups.io
Subject: Re: [DXLab] DXLab Suite - SmartSDR help needed

Gary,
Congrats on your 6600 purchase. It’s an amazing rig. Version 3.0.19 actually seems to continue to work well with most DX Labs applications as far as I can tell EXCEPT for the biggie TX /RX control. This has only affected WSJT-X and WinWarbler for me. Flex PTT, however, is easily control by creating an SDR CAT port for WSJT-X and an SDR CAT PTT port for WinWarbler. Both WSJT-X and WinWarbler need to be reconfigured to make that work but it is a simple process once you create the two ports mentioned in SDR CAT. WSJT-X needs to be configured for control by Flex instead of controlled by DX. lab Suites. As for CW and SSB PTT WinWarbler did not require any changes for me if I’m sending CW from WinWarbler or using my PTT hand switch plugged into the Flex.

You our are welcome to contact me at ki0kb@... and I can send you pictures on how to set this up.

Jeff Schwartz





Re: DXLab Suite - SmartSDR help needed

Dave AA6YQ
 

+ AA6YQ comments below

Please let me know when the new version is available so I can try it on my Flex thank you very much hopefully it will fix my problem

+ Every public release of every DXLab application is announced here.

73,

Dave, AA6YQ

Re: DXLab Suite - SmartSDR help needed

K4PX K4PX
 

Ok thanks Dave.
Joe

On Fri, Apr 19, 2019, 11:45 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

Please let me know when the new version is available so I can try it on my Flex thank you very much hopefully it will fix my problem

+ Every public release of every DXLab application is announced here.

       73,

               Dave, AA6YQ





Can't Upgrade Most DXLab Suite Apps

KE0CP
 

This may have been covered in a previous thread but I couldn't find it.
When I try to upgrade most apps such as Commander and DXKeeper the downloading window just freezes after downloading the update .exe file. Eventually I have to abort the process. The ErrorLog.txt file shows:
>DXQSLModule.ConfigureQSLTable: Unable to open QSLQueue C:\DXLab\DXKeeper\Databases\KE0CP.mdb<
and the shutsdown.
This seemed to happen after some prior Windows 10 update, as I have not done anything with the DXLab installation. I have removed all of the Suite's components with Windows' Control Panel | Programs and Features function and reinstalled DXLab Suite but when the installer attempts to upgrade each component they still freeze.
Any help would be greatly appreciated.
BTW: I do have the DXLab Suite running on another computer and it upgrades the programs just fine.

Re: Can't Upgrade Most DXLab Suite Apps

Dave AA6YQ
 

+ AA6YQ comments below

This may have been covered in a previous thread but I couldn't find it.
When I try to upgrade most apps such as Commander and DXKeeper the downloading window just freezes after downloading the update .exe file. Eventually I have to abort the process. The ErrorLog.txt file shows:
DXQSLModule.ConfigureQSLTable: Unable to open QSLQueue C:\DXLab\DXKeeper\Databases\KE0CP.mdb<
and the shutsdown.
This seemed to happen after some prior Windows 10 update, as I have not done anything with the DXLab installation. I have removed all of the Suite's components with Windows' Control Panel | Programs and Features function and reinstalled DXLab Suite but when the installer attempts to upgrade each component they still freeze.
Any help would be greatly appreciated.
BTW: I do have the DXLab Suite running on another computer and it upgrades the programs just fine.

+ Please reboot Windows into "Safe Mode with Networking". Then start the Launcher, and attempt to upgrade one of your DXLab applications. Does the upgrade succeed?

73,

Dave, AA6YQ