SmartSDR CAT v2.2.8 slice re-assignment problem

  • 1
  • Problem
  • Updated 6 days ago
  • (Edited)
The logging program (Logger32 v3.50.356) that I use is linked to SmartSDR through COM4 port. Since using the latest versions of SmartSDR and Logger32, this COM port link crashes when trying to re-assign the slice that is associated with the COM port.  Logger32 closes the COM port and SmartSDR CAT gives the following error message:

"SmartSDR CAT (v2.2.8.190): An unhandled error has occurred: A Task's exception(s) were not observed either by Waiting on the Task or accessing its Exception property.  As a result, the unobserver exception was rethrown by the finalizer thread.  

Inner Exception: Object reference not set to an instance of an object.

[details of the exception]"

Whilst Logger32 closes the COM port I don't know whether or not that is because of it being removed by the slice re-assignment process failing in SmartSDR CAT.  In other words which application is driving the fault condition.

I've been using SmartSDR/CAT/DAX/Logger32/Flex 6700 together for about 2 years without this issue occurring. The PC's running on Win 10 v1803.  Any ideas as to whether this is a CAT or Logger32 issue, or just down to me doing something wrong!

73 John, G3WKL


Photo of John, G3WKL

John, G3WKL

  • 14 Posts
  • 1 Reply Like

Posted 4 weeks ago

  • 1
Photo of Michael Walker

Michael Walker, Official Rep

  • 165 Posts
  • 44 Reply Likes
Hi John

Is there any chance you have 2 Com 4 ports or a Ghosted one?

Mike
Photo of John, G3WKL

John, G3WKL

  • 14 Posts
  • 1 Reply Like
Mike,

Thanks for your suggestion.  COM port assignments look OK to me.   Used KJ3P's batch script to check, see



However ......

The problem seems to have gone away.  Maybe I should have re-booted Win 10 to check if that cleared the problem, as I can re-assign COM4, which links SSDR with L32.

Re-boot, re-boot and re-boot - maybe I will remember next time!

73 John, G3WKL
Photo of Ian VA3QT

Ian VA3QT

  • 11 Posts
  • 0 Reply Likes
I had similar issue trying to interface a 6600 and Winlink Express and default Com4 port. Solution was to go into the CAT menu and crea t a new port and dedicate it solely to the WE app. My summer's advice was to do this with all apps, give each its own port.
Ian VA3QT
Photo of John, G3WKL

John, G3WKL

  • 14 Posts
  • 1 Reply Like
I have not had this issue recently, as when I have operated I have used the Flex/Maestro combination away from the PC, so not had any COM port integration with Logger32 (L32).  However, I have been doing some general admin in the shack this morning so had SSDR and L32 running in the background on the PC and noticed that the COM port issue, reported in my initial post, is still occuring.  Re-booting the PC does seem to clear it for a few changes of slice, but as the error seems to occur randomly this may be unrelated. 

I have tried Ian's suggestion of setting up a dedicated COM port for L32 - I chose COM8 - but straight away the same thing occurred.  L32 dropped COM8 and showed the error message below right, followed by SSDR posting the error message below left.



I don't know if it is related to  SmartSDR CAT v2.2.8 but my setup only started to show this problem since the most recent upgrade

73 John, G3WKL
Photo of EA2CW

EA2CW

  • 1 Post
  • 0 Reply Likes
I think it could be a new version of soft and new windows 10 driver signature policy. Here the same problem. No way to fix the DAX setup. (Win10, SmartSDR ver 2.2.8 and Flex 6300)73, Mikel EA2CW
Photo of John, G3WKL

John, G3WKL

  • 14 Posts
  • 1 Reply Like
Mikel,

Thanks for your comment.  As it turns out the problem is not recurring today (following a PC re-boot as it's been switched off overnight).  

What I have noticed, which is different from yesterday (when the issue occurred), is that the edit window for COM8 (which is used by Logger32) shows COM8 as the 'Client COM'. Yesterday, 'Client COM' initially showed as COM8 but within a second or so went blank.  I don't know if this is SmartCAT dropping COM8, or SmartCAT showing that it has been dropped by Logger32.   

73 John, G3WKL