QSX RX slice not being reported to software in 1.4.16

  • 1
  • Problem
  • Updated 3 years ago
Perhaps this is just my particular case since I haven't heard anyone else discuss it as a problem.  With earlier version of 1,4, using Kenwood TS2000 linkage to DX4WIN, SSDR or CAT would correctly provide both receive and transmit frequency correctly (noticed when cluster spotting mostly).   Ever since I installed 1.4.16 it has failed to do this (leading to a couple of my spots inadvertently causing stations to QRM the DX.)  If this has not been previously reported, I'm surely seeing it.  Anyone else?  

   73, Duane  AC5AA
Photo of Duane, AC5AA

Duane, AC5AA

  • 358 Posts
  • 77 Reply Likes

Posted 3 years ago

  • 1
Photo of Neal - K3NC

Neal - K3NC, Elmer

  • 427 Posts
  • 128 Reply Likes
Duane

I continue to see incidents where CAT just seems to stop providing information to programs even though the program does not receive a port error. Kill CAT and restarting it will solve the problem.

But, why do we have CAT just going  into a coma?
Photo of Burt Fisher

Burt Fisher

  • 1000 Posts
  • 365 Reply Likes
To get CAT to work I have to force it to stop then restart it
Photo of Duane, AC5AA

Duane, AC5AA

  • 358 Posts
  • 77 Reply Likes
I think I've already tried that - I did have CAT stop working a couple of times, but this problem seems to transcend those issues because it happens all the time in this level.  I also stated it incorrectly and no matter how many times I hit "Edit" it will not allow me to change it.  It is the TX split slice/VFO which is not being reported. 
Photo of Neal - K3NC

Neal - K3NC, Elmer

  • 427 Posts
  • 128 Reply Likes
Did you have both a Slice A and B defined when it started acting up?
Photo of George Molnar, KF2T

George Molnar, KF2T, Elmer

  • 1508 Posts
  • 532 Reply Likes
Reports correctly to MacLoggerDX.
Photo of Duane, AC5AA

Duane, AC5AA

  • 358 Posts
  • 77 Reply Likes
Yes.  I just confirmed that no amount of killing and restarting CAT caused it to start working correctly.  This has been a consistent problem in 1.4.16, and I don't remember seeing it in earlier 1.4 levels.  Now, guessing where you're going with the question, Neal, I just killed both slices and restarted them - viola - now it works.  So, something is getting a hitch in its getalong on linking slices to software.  Thanks for the pointer, but I hope they can find the problem to correct since it worked fine prior.

  73, Duane
(Edited)
Photo of Tim - W4TME

Tim - W4TME, Customer Experience Manager

  • 8640 Posts
  • 3238 Reply Likes
Can you provide the data coming from CAT using port monitoring software?  

There are two things involved here and we have to eliminate one; CAT or DX4WIN.  If you can capture the CAT commands off the virtual com port compared to your slice A/B configuration, then you can determine if CAT is sending valid data or not.  If it is, then the issue is how DX4WIN is using the valid data.  This will require com port monitoring software or knowing what commands DX4WIN is sending to the radio query the RX and TX frequencies, in which you can use the Test feature in CAT to validate the data,
Photo of Duane, AC5AA

Duane, AC5AA

  • 358 Posts
  • 77 Reply Likes
If someone can give me a 1-2-3 on how to do that (capture the DX4WIN command/response) I'd be glad to give it a try.
Photo of Duane, AC5AA

Duane, AC5AA

  • 358 Posts
  • 77 Reply Likes
I fired up the Flex this morning, DX4WIN has been running all night (as I always do to catch spots), and found that the fix (restart the slices) still was working. from last night.  However, a moment later, CAT died and I had to restart it.  After restart, all is working again.  I have not noticed any pattern yet to this, but will keep watch for it.