3.10.10 update

knewberry · September 3

I updated to 3.10.10 as soon as it came out. All went OK. No problem yet. Thanks. Ken K5GI

VE7ATJ_Don · September 3

In my case, I had to do some 'jiggery-pokery' with help from Tim to get the update to work. I have my radio directly connected to my PC via a cable — no router in between. After the update was installed, I was getting 'License Purchase required' messages.

Apparently, this release requires connection back to the 'home base' to verify license levels, etc. so it was necessary to temporarily a) power off the radio; b) disconnect it from my PC; c) connect it to a LAN port nearby; d) power the radio back on and leave it on for a few minutes to let it communicate with the license server.

Then, I was able to reconnect it back to my PC directly and everything was good. I reloaded my profiles and all is well.

Again, thanks to Tim and the Flex team for their quick response and diagnosis.

Alex - IK5PWJ · September 3

Hello, unfortunately, with the new 3.1.10 update, there are some problems with the Slice-master.v0.11.0g software.
The problem I'm experiencing with the Slice Master program is this:

During handling of the above exception, another exception occurred:

Traceback (most recent call last):

File:"flex\flexpy!,line 1309,in publish_updates

and other error etc.

And it won't open any WSJTX program, JTDX is all blocked.
How do I fix this?
I'm forced to revert to SmartSDR v3.09.19.
73 Alex ik5pwj

Mike-VA3MW · September 3

Alex,

It sounds like your windows firewall is preventing some communication. Can you turn it off and see if that issue?

mike

LZ2BE · September 3

Hello,

SDC skimmer is not working with v.3.10.10. I have to revert to 3.9.19.

73 Boyan

F4BPO · September 3

Hello,

Same here SDC not working anymore (the skimmer) on SmartSDR API…

That is a pity :(

Mike-VA3MW · September 3

I would like to look into this, but telling me it is broken doesn't help much.

Can you let me know any error messages? Is the IQ stream connecting? Is SDC Skimmer able to do a connection to the radio?

thanks

F4BPO · September 3

SDC connects to the radio as usual no problem, but when the skimmer is started it is like no stream is coming, the screen remain completely black with no signal and no decode.

No error message just everything is like usual except that the skimmer remains completely black with no decode

Mike-VA3MW · September 3

Correction - there is a problem with SDC now

WX7Y · September 4

Remote Hams RCForb server no longer works with 3.10.10 either using a Flex6700, 6400 or 8600, If I change the RCForb Radio driver to a Elecraft K3 it kind of works, the Kenwood drivers kind of work but a lot Errors on RCForb server. Tim told me there have been NO CAT changes but something has defiantly changed the way the Radio handles these 3rd party programs.

I turned off the Windows firewall but that made NO difference so in our cases here it is NOT a firewall issue.

We all went back to 3.9.19 and all is good.

KD0RC · September 4

Hi Bret, I changed my server from Flex SmartSDR to Kenwood Generic and it seems to work. I haven't tested extensively so there may be lurking issues that I haven't encountered yet.

It's funny, because with the Flex SmartSDR setting, it connects to the radio, then gets lost. I wonder if they are not parsing the UDP Discovery packets correctly.

This feels like a similar issue as SliceMaster.

F4BPO · September 4

Hi MIke,

Why problem is from SDC ?

Worked very well then I upgraded SmartSDR and now it does not work anymore.

Could you please elaborate a bit further please ?

Thanks

KD0RC · September 4

I just realized that in one of my experimental programs, I was parsing for 0x0 (hex zero) to terminate the Flex Discovery Packet (i.e. treat it like a string). While this worked in earlier releases of SmartSDR, it is clearly not part of the VITA 49 protocol which specifies the packet length in the header, not a specific value at the end of the packet.

As of 3.10.10, the end of the Discovery packet is no longer delimited by 0x0. My guess is that those apps that parse the discovery packet for a hex zero are now failing - some of my own code (fortunately, just experimental) now fails for that very reason.

Fortunately, Simon, NV0E saw that my method for determining a Flex Discovery Packet was not using the VITA 49 protocol properly, so he fixed the Flex Arduino library. As a result, the TeensyMaestro firmware from V2.001 forward is doing it correctly, and in fact, it works with 3.10.10.

I could easily be wrong in this assessment, but given my own experience, I think it is a likely cause. If anyone has any insight into this, I would be very interested to hear it.

W2PP · September 4

Same here Slicemaster will not launch WSJTX

Hopefully the Firmware can fix fixed. Works fine with 3.9

Peter

Don Pezet · September 4

I just came to report the same. Slice Master 6000 v0.11.0g worked fine under SmartSDR v3.9.19, but throws a whole fleet of errors when using SmartSDR v3.10.10. @Mike-VA3MW I can submit log files if you like, but they contain my radio serial number and other details, so I didn't want to post the full log here. Here is a sampling of the errors that Slice Master throws:

2025-09-04 10:07:02,265 ERROR  flex.flex.Flex6000.publish_updates err=AttributeError('type')

Traceback (most recent call last):

  File "flex\flex.py", line 300, in __getattr__

KeyError: 'type'


During handling of the above exception, another exception occurred:


Traceback (most recent call last):

  File "flex\flex.py", line 1309, in publish_updates

  File "cwskimmer.py", line 628, in slice_cb

  File "cwskimmer.py", line 476, in enabled

  File "cwskimmer.py", line 310, in local_streams

  File "flex\radio.py", line 629, in local_iq_streams

  File "flex\flex.py", line 308, in __getattr__

AttributeError: type

2025-09-04 10:07:02,266 ERROR  flex.flex.Flex6000.publish_updates err=AttributeError('type')

Traceback (most recent call last):

  File "flex\flex.py", line 300, in __getattr__

KeyError: 'type'


During handling of the above exception, another exception occurred:


Traceback (most recent call last):

  File "flex\flex.py", line 1309, in publish_updates

  File "wsjtx.py", line 597, in slice_cb

  File "wsjtx.py", line 524, in enabled

  File "wsjtx.py", line 569, in local_audio_streams

  File "flex\radio.py", line 553, in local_audio_streams

  File "flex\flex.py", line 308, in __getattr__

AttributeError: type

2025-09-04 10:07:03,008 ERROR  flex.flex.Flex6000.publish_updates err=AttributeError('type')

Traceback (most recent call last):

  File "flex\flex.py", line 300, in __getattr__

KeyError: 'type'


2025-09-04 10:07:03,124 DETAIL flex.smartlink.WanServer.parse_reply unknown reply reply='error| invalid command'

There's actually a lot more, but most of it is a repeat of the lines I included above. Just launching Slice Master and closing it again after about a minute generated 1400+ lines of log messages.

Mike-VA3MW · September 4

Please contact Don at SliceMaster with this.

I am not seeing the same issue at all on my station but it seems there are some corner cases regarding this.

WX7Y · September 4

Thanks Len, sounds like you might have a finger on it, So using the Kenwood Generic you don't get the

"info ID911 in AL1 mode, switching to AI2" every 5 seconds ??

WX7Y · September 4

Len and anyone else with the RCForb issue, Roger who writes the Radio Drivers says there is a new installer, probably later today, I have tested this new drive a little bit and it seems to works.

He says, the issue was Flex changed the version format and it broke the driver where it parsed out the version number. Now starting up, there will be an info line just stating the min version will be xxxxxxx

see ya later and thanks

Bret WX7Y

KD0RC · September 4

Hi Bret, well, that lends some credence to my assessment. The Arduino library that I was using was parsing some of the discovery packet items positionally instead of using named parameters. I'll bet that is what RCForb and others were doing.

I'll watch for the new version to come out.

Eric-KE5DTO · September 4

I'm unclear on the other applications, but I can say for sure that there is an issue with IQ Streams in v3.10.10 due to an unintended change in format of the data. This will be corrected in a point release in the near future. This will affect programs like SDC skimmer that utilize the IQ Streams.

If there are issues with other applications unrelated to the IQ Streams, please get with the application developer so we can work with them to investigate and hopefully get fixes into the same point release. Thanks!

3.10.10 update

Comments

Leave a Comment

Categories