"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
- 21 Posts
- 1 Reply Like
Posted 9 months ago
Michael Walker, Employee
- 547 Posts
- 141 Reply Likes
- 21 Posts
- 1 Reply Like
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
- 16 Posts
- 1 Reply Like
Ian VA3QT
- 21 Posts
- 1 Reply Like
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
- 1 Post
- 0 Reply Likes
- 21 Posts
- 1 Reply Like
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
- 21 Posts
- 1 Reply Like
Installed SSDR v2.3.7 today and opened N1MM Logger + to try out the "spots" feature (which works great!). I then found that the same thing happens with N1MM that occured with Logger32, discussed above. To summarise: when I edit the COM port, which communicates the frequency of the selected slice to N1MM, the 'Client COM' is dropped and an error message appears from the N1MM application.
So with N1MM Logger + and Logger32 both behaving in the same way when trying to change slice on the COM port is there something that I have not got set correctly with SmartSDR CAT (which is not on v2.3.7).
73 John, G3WKL
Tim - W4TME, Customer Experience Manager
- 9153 Posts
- 3496 Reply Likes
You have to shut down the spot communication socket in the application before changing the port number.
- 21 Posts
- 1 Reply Like
Tim - W4TME, Customer Experience Manager
- 9153 Posts
- 3496 Reply Likes
I have entered this into our bug tracker as issue #6447. Thanks for the bug report.
Eric - KE5DTO, Official Rep
- 719 Posts
- 211 Reply Likes
- 21 Posts
- 1 Reply Like
Sure will do what I can on Monday. It's very repeatable.
My feeling is that the VSP got corrupted during the Win 10 1803 update, as the issue post-dates that update. But will document the exception before doing anything as drastic as uninstalling and reinstalling the software.
BTW there is a typo in my 'update' posting 4 hours ago. The final phrase should have read 'which is now on v2.3.7'
I'll get back to you next week with some further info
73 John, G3WKL
- 21 Posts
- 1 Reply Like
Here's some detail of the exception for #6447. This was done yesterday and today, although the issue with Logger32 occured with the previous version of SmartSDR (N1MM+ was untested on that version)
PC – Intel Core i7-4790 CPU @3.6GHz, RAM 16GB DDR3
OS - Win10 v1803 from 1st May 2018, with recent updates up-to-date
SmartSDR v2.3.7 along with Flex 6700
Select View|Show hidden devices

Issue as related to N1MM Logger +
CAT9 assigned to N1MM+ (v1.0.7208.0)
Double clicked on it to change slice association from slice A to B
A second or so after opening the ‘Client COM’ drop down went blank
Editing the ‘VFO A Slice’ to B
and clicking Save one gets the following error message from N1MM+

Moments later an error message from Flex

Issue as related to Logger32
COM8 assigned to Logger32 (v30.50.357)
Double clicked on COM8 to change slice association from slice A to B - it worked (this time!)

The ‘Client COM assignment didn’t disappear, and I was able to change slice to B

and save it. Logger32 of course then shows the frequency associated with Slice B.
I would say that the issue occurs with Logger32 roughly 80% of the time. The consistent way to avoid the issue is to close the port (in Logger32), re-assign the COM port and then open the port.
Below is an example of SSDR/Logger32 COM port dropping out during edit:
First the ‘Client COM’ is dropped
Then the error messages from Logger32

and from SSDR

73 John, G3WKL
Eric - KE5DTO, Official Rep
- 719 Posts
- 211 Reply Likes
- 21 Posts
- 1 Reply Like
73 John, G3WKL
Related Categories
-
FLEX-6700 Signature Series SDR
- 2845 Conversations
- 590 Followers
-
SmartSDR CAT
- 899 Conversations
- 387 Followers
-
Third Party Applications and Products
- 860 Conversations
- 236 Followers