DXLab Commander and 2.4.9: Commander Rig Control Issue

  • 2
  • Question
  • Updated 1 month ago
When I upgraded to SmartSDR 2.4.9 it fixed the spot/receiver problem, however,   I have now lost reliable frequency control between SmartSDR
2.4.9 and Commander. After a few minutes I lose communications and I have to go into Commanders config and reset the rig interface. I downgraded to SmartSDR 2.3.9 and have regained reliable frequency control. I noticed the same situation with N3FJP's contest logging software. I had issues with 2.4.9 but resolved the issue by down grading to 2.3.9. I may have to go to 2.3.7 as the receiver interruption's are quite annoying, even if I turn off spot settings in SmartSDR. Has anyone else noticed this? or is this unique to my station/computer.

Photo of Rich - N5ZC

Rich - N5ZC

  • 180 Posts
  • 23 Reply Likes

Posted 2 months ago

  • 2
Photo of Jon - KF2E

Jon - KF2E

  • 648 Posts
  • 195 Reply Likes
Rich,

You will probably get more help with this in the groups.io forum for DXLab. Dave the author is very active there and will help you solve your issue.
Photo of Rich - N5ZC

Rich - N5ZC

  • 180 Posts
  • 23 Reply Likes
Hi Jon,

I did post this to DXLab's iogroup yesterday.  Dave responded with the opinion that there is an issue with SmartSDR 2.4.9.  While he did not say he was having Commander issues like I am he's noticing some other significant issues.

Rich - N5ZC
Photo of Jon - KF2E

Jon - KF2E

  • 648 Posts
  • 195 Reply Likes
Hi Rich,

You might want to consider opening a help desk ticket on this. With Flex's diminished presence in this forum I'm not sure the issue will make it to them if you don't.

Jon...kf2e
Photo of Gene - K3GC

Gene - K3GC

  • 228 Posts
  • 38 Reply Likes
I had basically the same problem with 2.4.9.  reverted to 2.3.9 and everything works like a charm.  Help desk is ,IMO, not likely to fix the issue.  I think it is a bug in 2.4.9 and will require an update to SSDR to resolve the issue.
It does look like Flex is paying less attention to the community and that is a shame
Photo of Jon - KF2E

Jon - KF2E

  • 648 Posts
  • 195 Reply Likes
Gene,

My point is that a help desk ticket is the only path we now have to surface issues like this. I agree it was much nicer when Tim was actively monitoring the forum and providing feedback on issues.

Jon...kf2e
Photo of Gene - K3GC

Gene - K3GC

  • 228 Posts
  • 38 Reply Likes
First Dudley, now Tim.  Flex used to stand out for superior customer service. 'tis a shame.
Photo of Rich - N5ZC

Rich - N5ZC

  • 180 Posts
  • 23 Reply Likes
Hi Jon,

I entered a help ticket this morning.  I was trying to determine if this was a unique problem or maybe some sort of bug one way or the other.  Based on Gene's comment above, I may not be the only one.

Thanks for the help.

Rich - N5ZC
Photo of Steven Linley

Steven Linley

  • 248 Posts
  • 27 Reply Likes
Same drops-out with V2.3.9
Photo of Steven Linley

Steven Linley

  • 248 Posts
  • 27 Reply Likes
What I like about version 2.3.9 is that I can see the spots in panafall .
Photo of Rich - N5ZC

Rich - N5ZC

  • 180 Posts
  • 23 Reply Likes
Eric at Flex was able to duplicate the problem and closed my ticket.  Hopefully the fix will be included in the next version we shall see.

I don't have an issue with 2.39 any longer.  The spots work great and I'm not getting any audio interruptions for some reason.

Rich - N5ZC
Photo of Tim Ellam

Tim Ellam

  • 236 Posts
  • 28 Reply Likes
With both 2.39 and 2,49 I an getting screen "freezes" displaying spots on the screen on the 6600M. It seems to be timed whenever new spots appear in Spot Collector (DXLab). Is this a similar issue?

73

Tim VE6SH
Photo of Jay / NO5J

Jay / NO5J

  • 1577 Posts
  • 228 Reply Likes
I'm still seeing/hearing audio dropouts with SSDR v2.4.9in the same manner Tim VE6SH is reporting. It seems like Spot Collectors spot refreshing sort of floods out the rig audio, causing some pops, clicks, and stuttering. I had Spot Collectors spot display settings set to their defaults. I'm now playing around with spot lifetime settings in an effort to reduce the amount of data Spot Collector might be spewing out. The defaults seemed to be retaining spots indefinitely. I don't see any use in displaying any spots older than those spotted today. I'm more interested in right now.

    #FlexRadio IRC chat

For real-time discussions

        SDRgadgets

User created documentation.
           Volunteer!!

         73, Jay - NO5J

Photo of Tim Ellam

Tim Ellam

  • 236 Posts
  • 28 Reply Likes
Thanks Jay

Interestingly I have no issue with SSDR on Windows. The freeze is only occurring on the 6600M display.

I have my Spot Display set to prune anything older than 2 days.

73

Tim
Photo of Denley W3XY

Denley W3XY

  • 21 Posts
  • 5 Reply Likes
I am also having DXlab Commander disconnects with 2.4.9
73,
Denley W3XY
Photo of Pat

Pat

  • 4 Posts
  • 0 Reply Likes
New to Flex with a 6400 a little over a week old.  I have the same problem with Commander.

I can open a ticket with Flex.  Glad to.  

When doing so, is there another ticket number to reference?  Particularly with regard to the comment above "Eric at Flex was able to duplicate the problem and closed my ticket".

Thank you!
Pat NF8H
Photo of Gene - K3GC

Gene - K3GC

  • 228 Posts
  • 38 Reply Likes
Pat,
There have several of us with the same problem.  It would seem that the only real answer is to run SSDR 2.3.9.  It plays nicely with Commander.  Eventually, Flex will come out with a new version fixing the problems with 2.4.9
Photo of Pat

Pat

  • 3 Posts
  • 0 Reply Likes
Thanks for the reply.  I downgraded to 2.3.9.  Given that I'm brand new to Flex, I won't miss the new function in 2.4.9.