DXLab Does Not Support SmartSDR v 3

K3DCW

Dave AA6YQ

My understanding from Flex personnel is that even if v3's multiFlex capability is not used, changes are required in the area of audio muting and RX/TX switching.

And v3 users will rightfully expect the ability to use multiFlex.

David Decoons, wo2x

David Decoons, wo2x

For single client use most functions including spots on display, click/tune on spots, and logging interface all work fine in version 3. As Dave pointed out there is some functionality that does not work because now the program needs to be able to identify which client it is to "talk to". For those that use Kenwood CAT to SmartSDR CAT interfacing there is no change in functionality. Dave wo2x

Andy - KU7T

Exactly.

Basically, if a program uses the "legacy" CAT protocol, all is fine (DXlab with CAT instead of Flex protocol, N1MM+, spots, most other logging programs). 

On the other hand, if a program uses the Flex or .NET API, it may or may not work as those are affected (DXLab with Flex protocol, SliceMaster).

So, DXLab does work FINE if you do not use the FlexApi, but the CAT port. I am not sure what functionality does not work with CAT, but you can control your rig, key it, read frequency, etc. Pretty much everything you do with any other rig. 

73
Andy
KU7T

David Decoons, wo2x

Most functions work using the TCP API connection. There are some functions, two of which Dave has mentioned, that do not work currently in SSDR V3. I personally do not use those functions so it does not impact how I use DX Labs.

Dave wo2x

KY6LA_Howard

ctate243

Agreed.  As far as I can see most everything works that I use of this very comprehensive suite. I do use commander, but mostly to key macros for my winkeyer..  I would expect a good number of the API programmers to update their applications.  Looking forward to testing SDR bridge v3 tonight.. 

I dont devalue Daves concern,  Your package is great, I have used it for years,  but this all mostly works ok for me... and the tools I need are there or are on the way...  lets try and stay positive and enjoy the expanded capabilities v3 offers if you choose.

Pat N6PAT

Bill -VA3WTB

Pat N6PAT

ctate243

It mostly all still works fine.  This is not a holy war.. its a computer logger. 

Id like to see offline dialogue by all parties here..  and not hold a trial of public opinion prior to the actual release of the software. 

KY6LA_Howard

@Pat  While we will all agree that Bill easily wins the award of Captain of the Flex Cheerleading squad, I do have actual hands on experience with V3 and DXLab.. at least for my purposes, DXLAB and V3 seem compatible enough and there are sufficient work arounds even at this early date that even a sophisticated and discerning user such as yourself will be able to use it


FYI - Looks CWSkimmer will be able to work thru V3 via SDRBridge



Bottom Line:  looks like almost every 3rd part program will migrate to V3


BTW... Your request for APPs known to fail is a rather negative approach as it would include irrelevancies such as Facebook..... how about a list of APPs that work or will soon work with V3 as there are already many and likely even Dave, as brilliant as he is,  will figure something out.


Personally - having played with V3 alpha since the new year, I keep on finding all sorts of non contest uses which makes it perhaps one of the most exciting developments in Ham Radio in a long time...

Pat N6PAT

When did I request a list of Apps that fail?

Perhaps your testing works for what you use it for doesn't necessarily mean it will work for what I use it for. Hence my suggestion that Flex allows a trial period as most software development teams allow.

Then each op can determine for themselves if it works for what they want and not have to rely on your testing.

KY6LA_Howard

That boat has sailed long time ago as it would require a huge investment for little return.....

David Decoons, wo2x

@Pat, I am uploading a video to YouTube showing DX Labs Commander and Spot Collector working with SmartSDR version 3. I will post the link in a new thread in a few minutes when the upload finishes. 

Yes, there are some features that have been identified that do not work in 3.0 but functionality to allow Spot Collector to send spots to the radio, clicking on spots on the panadapter or in Spot Collector, and logging the contacts to Keeper all work.

The RX button in Commander does not work. How many people use that? Or even keep Commander visible when using DX Labs? Also Mute from DX Labs does not work. I do not use these functions so until this thread started I never noticed that items did not work.

Please watch the video and if there are specific functions that concern you I'd be happy to test.

Dave wo2x

Pat N6PAT

No, that's ok. I am not asking you to test anything for me.

I've been developing computer systems for 35 years and I've learned that one testers success can be another testers failures.

I maintain the trial period method is the way to go.

Steve K9ZW

I haven’t found anything broken using v3 in test other than things in SmartSDR itself, though I am clear that their is something to be gained my v3-optimization. YMMV as I am a fairly routine user, and I limited my tests to my usual suite of programs. Not a statement from Optimism or Pessimism, just the facts. Stuff is working. I have some plans that will need to wait for a couple releases of v3 and for a few third party program to catch up. I’ll be writing about this at my blog shortly. While reading of more tension than it seems it is worth, I’m appreciate of this discussion - looks like their has been more results than bantering in the end. And I’ll revisit DXLab in the process. 73 Steve K9ZW

David Decoons, wo2x

Pat,

I am just trying to show that the core functionality of DX Labs works with 3.0. Hopefully Dave, AA6YQ integrates full functionality for SmartSDR 3.0 but my point is unless someone told me something in DX Labs didn't work I would not have noticed it.

An updated video of my testing is here
https://www.youtube.com/watch?v=bgw2Mr6eLjA&t=11s 

Dave wo2x

Pat N6PAT

David Decoons, wo2x

Pat, I am NOT going to get into a flame war with you. When you decide for yourself that version 3.0 works the way you want then buy it. If you feel uncomfortable then sit back and let others share their experiences first.

I shared a video showing how I use DX Labs to chase DX. That is my contribution. Others will post their comments and the you can decide.

I'm done replying. 

Dave wo2x

Dave AA6YQ

Howard, if you do not use Commander, you are not using the component of the DXLab Suite that controls the 6XXX.

I assure you that the current version of Commander will not work correctly with multiFlex enabled, and based on comments further down, RX/TX switching is also non-functional.

Dave AA6YQ

David Decoons, wo2x

Yes, you are correct Dave, MultiFlex is an issue with your software currently. But for those running a single client chasing DX it works 99%. I do not use the few features that you have identified that do not work. (Mute or TX/RX from Commander)

Again, you are correct, for remote access and MultiFlex (where there are multiple clients connected) the SSDR-6xxx connections using the API do not currently function correctly. 

The Kenwood CAT connection does work for single operator when remote using SmartLink but no spots to the panadapter.

73
Dave wo2x

David Decoons, wo2x

Thanks for the clarification Dave. This makes sense. 

Since I use WSJT-X through JTAlert-X for logging I never noticed the problem.

Dave wo2x

Dave AA6YQ

When I extended Commander to support the SmartSDR API, I removed the CAT support. Yes, you can set Commander's Radio Model selector to "Kenwood" and it will sort of work via CAT, but that's not a supported configuration.

Burt Fisher

Asher - K0AU

Mack

It's been supported for some time now. I use it daily.

73,

Mack
W4AX
Alpha Team

RFord

It's been supported for about 1 month...use it every day...

Regards, 
Ronald