Date   
Re: DXLab Suite - SmartSDR help needed

CSM\(r\) Gary Huber - AB9M
 

Thanks Jeff.  I have been having the WXJT-X and Winwarbler issues you stated below.  I just downloaded SmartSDR 2.4.9 and will give it a go shortly. I am mostly interested in DX and do contesting mostly as exercise for getting through pile-ups so I don't loose much using the earlier versions of SmartSDR since I'm not a SO2R guy.

Thanks for the insights on configuring the apps for Version 3.0.19, I'll be trying that a bit later after I'm a bit more used to the new 6600 and Maestro.

73 & DX,
Gary ~ AB9M


From: DXLab@groups.io <DXLab@groups.io> on behalf of Jeff Schwartz via Groups.Io <ki0kb@...>
Sent: Friday, April 19, 2019 9:26 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: Sound Card Issue?

John Plaster
 

Dave,

Thank you for following up.
Whenever WinWarbler or WSJT-X FT-8 is launched I get the message "unable to start sound card - Unknown Error (33)". I only get that message when the digital apps are started. I checked and made sure the audio output from the radio is not the problem and all is good. I am at a loss with this problem.
John
K1VOI

Win 10 ?????

n4qwf .
 

I have a Flex 5000 radio running on a Win7 computer. Due to the many post about Win 10 update issues I have been adamant about not allowing that computer to update to Win10. Now that the dust has settled I wonder if there are any on going issues. Things are working so nicely with PowerSDR and Dxlab and WSJT-X and N1MM and other software I sure would hate to create myself a mess.

Any reports are very appreciated.

73<<John

Re: DXLab Suite - SmartSDR help needed

Jeff Schwartz
 

Sounds like a good plan Gary. I have been back and forth between v 2.49 and v 3.0.19 a few times myself. I suspect Flex will correct the monitor bug in v 3 and who knows what else. I ended up setting up a workspace in DX Labs for both software versions should I switch again. Dave’s DX Labs program is so robust it seems to allow workarounds when programmers decide to go rouge. 

Jeff Schwartz

Re: Win 10 ?????

Jim Miller, AB3CV
 

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.

73

jim ab3cv

On Fri, Apr 19, 2019 at 2:50 PM n4qwf . <N4QWF@...> wrote:
I have a Flex 5000 radio running on a Win7 computer. Due to the many post about Win 10 update issues I have been adamant about not allowing that computer to update to Win10. Now that the dust has settled I wonder if there are any on going issues. Things are working so nicely with PowerSDR and Dxlab and WSJT-X and N1MM and other software I sure would hate to create myself a mess.

Any reports are very appreciated.

73<<John

Re: Win 10 ?????

Phil & Anne Irons
 

Hi John...

I don't have a FLEX radio, but I have been running DXLab Suite on WIN 10 for a couple of years, with no problems (fingers crossed!).  However, I have seen several notices, some I believe here on the DXLab reflector, concerning the upcoming withdrawal of support for WIN 7 early next year.  This, of course means no more updates with patches for loopholes in the code, which means that if you are connected to the Internet, your computer will be vulnerable to online trespassers.  It might be 8 months until support disappears, but that gives you some time to convert to Win 10 and fix any problems you might find with it concerning your radio.

73 & GL,

Phil/VE1BVD
Sydney, NS

On Fri, Apr 19, 2019 at 3:50 PM n4qwf . <N4QWF@...> wrote:
I have a Flex 5000 radio running on a Win7 computer. Due to the many post about Win 10 update issues I have been adamant about not allowing that computer to update to Win10. Now that the dust has settled I wonder if there are any on going issues. Things are working so nicely with PowerSDR and Dxlab and WSJT-X and N1MM and other software I sure would hate to create myself a mess.

Any reports are very appreciated.

73<<John



--
Phil & Anne Irons
Sydney, Nova Scotia

Re: Sound Card Issue?

Dave AA6YQ
 

+ AA6YQ comments below

Thank you for following up.
Whenever WinWarbler or WSJT-X FT-8 is launched I get the message "unable to start sound card - Unknown Error (33)". I only get that message when the digital apps are started. I checked and made sure the audio output from the radio is not the problem and all is good. I am at a loss with this problem.

+ If you're getting the same error message from two entirely different applications, then likely the source of the error message is the soundcard driver. I suggest that you engage with the soundcard manufacturer.

73,

Dave, AA6YQ

Re: WSJT-X version 2.0.1 is available

K4PX K4PX
 

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!  
Thanks,
Joe
K4PX


On Mon, Feb 25, 2019 at 12:48 PM Dave AA6YQ <aa6yq@...> wrote:
Release Notes:

http://physics.princeton.edu/pulsar/k1jt/Release_Notes.txt


Windows Installer:

http://physics.princeton.edu/pulsar/k1jt/wsjtx-2.0.1-win32.exe

      73,

            Dave, AA6YQ




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