DXLab Does Not Support SmartSDR v 3

  • 1
  • Problem
  • Updated 1 month ago
     On Apr 2 Dave, AA6YQ,reported that DXLab does not support SmartSDR v3. This is of great concern for those of us who use DXLab and would otherwise wish to upgrade to SmartSDR v3.

Larry, K4KGG
Photo of Lawrence Libsch

Lawrence Libsch

  • 22 Posts
  • 5 Reply Likes
  • disappointed

Posted 4 months ago

  • 1
Photo of Jon - KF2E

Jon - KF2E

  • 677 Posts
  • 222 Reply Likes
Maybe V4's main feature is going to be repairing the API so we can use third party apps again?

Photo of Mack McCormick

Mack McCormick, Elmer

  • 453 Posts
  • 156 Reply Likes
As an Alpha tester currently using V3 of SmartSDR I'd like to offer that DXLabs is working perfectly well in my environment. In fact, for my use cases I can tell no difference from the behavior I see in SSDR version 2.4.9. I am able to run two Maestro's one two separate bands and one shows up in VFO A and the other in VFO B in DXLabs. I am not questioning Dave's position just informing you that all is well here with version 3.0. I recommend you give it a try when 3.0 is released.

73,

Mack
W4AX
Alpha Team
Photo of Dave AA6YQ

Dave AA6YQ

  • 196 Posts
  • 225 Reply Likes
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.
Photo of David Decoons wo2x

David Decoons wo2x, Elmer

  • 1401 Posts
  • 306 Reply Likes
Hi Dave,

Yes there are changes in these areas. Most functionality works and if you do not use spots on the display the Kenwood CAT interface works fine connected to a local client via SmartSDR CAT.

For how I use DX Labs, (Commander, Keeper, Spot Collector) send spots to radio, click on spot in panadapter or cluster to tune radio, logging, it works fine in V3 via TCP API and Kenwood CAT. (no spots on panadapter when using Kenwood CAT).

Please let me know any functions you specifically want tested for compatibility.

I personally do not use the Mute (don't know where it is) or the TX/RX in Commander so I never would have noticed they do not work.

73
Dave wo2x
(Edited)
Photo of Pat - WH6HI

Pat - WH6HI

  • 380 Posts
  • 77 Reply Likes
Has a list of 3rd party apps been tabulated that are known to fail with V3?
Photo of K3DCW

K3DCW

  • 93 Posts
  • 36 Reply Likes
I presume that when we're talking about the Flex SmartSDR 3 API not working with all of this software, we're talking about communication with the rig directly over the TCP/IP API, correct?

So, I also presume that this doesn't mean that third-party software suddenly won't work with SmartSDR v3 VSP software via the traditional COM ports, right? So, Fldigi/WSJT-X, most loggers, and third-party software that doesn't have to use the TCP/IP API will still work, albeit with some reconfiguration being required and without the ease of the API.

Is that correct or am I missing something? 

(Mac users are likely still out-of-luck due to the need to reconfigure xCAT or other API issues, I'm sure).
(Edited)
Photo of KY6LA - Howard

KY6LA - Howard, Elmer

  • 3755 Posts
  • 1617 Reply Likes
DXLABS - or at least the parts I use- Work OK will V3.0
Did some simple testing of the parts I mainly use - Logbook and Spot Collector with V3.
It seems to work OK for me.   - I do not use commander as I do not see the point with Flex.
I have been using DXLabs as my primary logger for 10+ years.. Dave does superb programming.
I also use HRD logger because its prettier..as a secondary logger which works with V3


So while there may be some obscure functions that don't work, I suspect that this is a huge molehill taking on the guise to seem to be a insurmountable mountain...  YMMV

FRLogger and N4PY work 100% OK already with V3 as do many other programs as well.  I am aware of the fact that DDUTIL and SSSDR/iOS are being upgraded to handle V3.extra clients.

ALSO - WSJT-X and JTDX seem to work OK with V3

So per usual for this forum - a lot of hysteria over very little as most of you would not even eb aware of the effect of the API differences had Dave not mentioned it.







(Edited)
Photo of Chris Tate  - N6WM

Chris Tate - N6WM, Elmer

  • 934 Posts
  • 266 Reply Likes
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.
Photo of Dave AA6YQ

Dave AA6YQ

  • 196 Posts
  • 225 Reply Likes
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.
Photo of David Decoons wo2x

David Decoons wo2x, Elmer

  • 1402 Posts
  • 306 Reply Likes
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
Photo of Pat N6PAT

Pat N6PAT

  • 770 Posts
  • 252 Reply Likes
This type of situation is exactly why I suggested months ago that Flex allow a try-before-you-buy trial period for new releases. Then each op can decide for themselves what works and does not work for them

Almost every software package I've purchased allows for a trial period. Why doesn't Flex?.
(Edited)
Photo of Bill -VA3WTB

Bill -VA3WTB

  • 3849 Posts
  • 929 Reply Likes
There you have it, all you guys that said you would never use V3 because it was beleived it would not work with V3 can now go ahead and get it if you had planned to.
The sky didn't fall and Flex is still in busness, life is good.
Photo of Pat N6PAT

Pat N6PAT

  • 770 Posts
  • 252 Reply Likes
Sorry but I prefer to put my faith with Dave AA6YQ. Who knows more about DX Labs than he does?

Bill, if Flex radios started to burst into flames you'd try to put a positive spin on it and
that type of cheer leading erodes your credibility in my book.

Photo of Chris Tate  - N6WM

Chris Tate - N6WM, Elmer

  • 934 Posts
  • 266 Reply Likes
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. 
Photo of KY6LA - Howard

KY6LA - Howard, Elmer

  • 3755 Posts
  • 1617 Reply Likes
@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...
Photo of Pat N6PAT

Pat N6PAT

  • 770 Posts
  • 252 Reply Likes
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.
Photo of KY6LA - Howard

KY6LA - Howard, Elmer

  • 3755 Posts
  • 1617 Reply Likes
That boat has sailed long time ago as it would require a huge investment for little return.....
Photo of David Decoons wo2x

David Decoons wo2x, Elmer

  • 1402 Posts
  • 306 Reply Likes
@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
Photo of Pat N6PAT

Pat N6PAT

  • 770 Posts
  • 252 Reply Likes
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.
Photo of Steve K9ZW

Steve K9ZW, Elmer

  • 1516 Posts
  • 762 Reply Likes
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
Photo of David Decoons wo2x

David Decoons wo2x, Elmer

  • 1402 Posts
  • 306 Reply Likes
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
Photo of Pat N6PAT

Pat N6PAT

  • 770 Posts
  • 252 Reply Likes
Dave,

Tell you what....if you are so certain all is well then I would be willing to upgrade if .... and here's the big if....you are willing to reimburse me my $199 upgrade cost if it doesn't work as advertised.

How does that sound?
(Edited)
Photo of David Decoons wo2x

David Decoons wo2x, Elmer

  • 1402 Posts
  • 306 Reply Likes
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
Photo of Dave AA6YQ

Dave AA6YQ

  • 196 Posts
  • 225 Reply Likes
Some of you may be satisfied with "it mostly works". For DXLab, that's not remotely acceptable.

If Commander can't switch the transceiver between RX and TX, then apps like WinWarbler and WSJT-X that rely on Commander for RX/TX switching won't work. You'd notice this.

If Mute doesn't work, then you can't quickly switch between exclusively listening to a DX station and to the station and its pileup. You'd notice this.

These are defects. I don't release software containing known defects.
(Edited)
Photo of David Decoons wo2x

David Decoons wo2x, Elmer

  • 1402 Posts
  • 306 Reply Likes
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
Photo of Asher - K0AU

Asher - K0AU

  • 210 Posts
  • 34 Reply Likes
Any progress or resolution for DXLabs V3 support?
Photo of Mack McCormick

Mack McCormick, Elmer

  • 453 Posts
  • 156 Reply Likes
It's been supported for some time now. I use it daily.

73,

Mack
W4AX
Alpha Team
Photo of Ronald / W4RJF

Ronald / W4RJF

  • 53 Posts
  • 3 Reply Likes
It's been supported for about 1 month...use it every day...

Regards, 
Ronald
Photo of Asher - K0AU

Asher - K0AU

  • 210 Posts
  • 34 Reply Likes
Thanks! Must have missed the announcement
Photo of Dave AA6YQ

Dave AA6YQ

  • 196 Posts
  • 225 Reply Likes
Some users -- including me -- report that SmartSDR v3.0.27 occasionally disconnects from Commander, and then automatically re-connects. To rule out SmartSDR's "keepalive" mechanism as the source of these disconnects, I have sent a version of Commander that does not activate this mechanism to 11 Flex users. Some still report seeing disconnects. So far Flex personnel have been unable to determine why this happens with 3.0.27, but never happened with SmartSDR v2.4.9. I haven't used SmartSDR v2.5.1 enough to know whether it too occasionally disconnects.

I have also seen SmartSDR v3.0.27 enter a "mode" in which transmitted audio is badly distorted, a mode that is immediately cured by terminating and restarting it. I've sent a recording of the distorted audio to Flex personnel. They are hopeful that future improvements to DAX will correct this.

I have on several occasions seen SmartSDR v3.0.27 lock up. Termination via Windows Task Manager and a re-start will cure this.

Unless you have need of a feature or defect repair in SmartSdr v3.0.27, my advice is to remain with Smart SDR v2.4.9.

Asher, I've sent you an invitation to join the DXLab Discussion Group so you can keep abreast of new release announcements. I don't routinely post them here.
(Edited)
Photo of Asher - K0AU

Asher - K0AU

  • 210 Posts
  • 34 Reply Likes
Dave,

Thanks so much for the info. I've been seeing the "DAX TX Audio intermittently corrupted" bug since v1.x. I was checking on DXLabs support since I finally cleared the backorder list for a PGXL and didn't want to get stuck with a potential "PGXL requires V3.x, while DXLab requires V2.x" situation."