version 2.0.974

[ahop...@googlemail.com]

Hi All,

there is a new version here

https://www.sparksdr.com/download/SparkSDR.2.0.974.win64.zip
https://www.sparksdr.com/download/SparkSDR.2.0.974.win32.zip
https://www.sparksdr.com/download/SparkSDR.2.0.974.linux-x64.deb
https://www.sparksdr.com/download/SparkSDR.2.0.974.linux-x64.rpm
https://www.sparksdr.com/download/SparkSDR.2.0.974.linux-arm.deb
https://www.sparksdr.com/download/SparkSDR.2.0.974.linux-arm64.deb
https://www.sparksdr.com/download/SparkSDR.2.0.974.osx.zip

This fixes an issue with profiles using rigcntrl cat and has fixes for all platforms for gateware upload and HPSDR protocol 2 radios.

73 Alan M0NNB

[Steven Sostrom]

When I try to download https://www.sparksdr.com/download/SparkSDR.2.0.974.linux-arm64.deb, it results in a file of 0 bytes on length.

https://www.sparksdr.com/download/SparkSDR.2.0.974.linux-arm.deb is successful.

----Steve

[ahop...@googlemail.com]

Hi Steve,

thanks for reporting that, the build machine had run out of disk space. I've replaced the file so it should be ok now.

73 Alan M0NNB

[Steven Sostrom]

Got it, thanks!

[Thomas Beiderwieden]

Hi Alan,

thanks for the new version. As you may remember, I am doing a lot with the websocket interface of SparkSDR. With the new version you are sending 

# {"cmd":"ReceiverResponse","ID":0,"Mode":"FT8","Frequency":24915000,"FilterLow":100,"FilterHigh":5000} instead of

# {"cmd":"ReceiverResponse","ID":0,"Mode":"FT8","Frequency":24915000.0,"FilterLow":100.0,"FilterHigh":5000.0}
the ".0" in the numbers is missing.

As that (the .0) was not really useful, may I assume, that this change was intentionally? If yes, I would change my script, otherwise wait...

vy 73 de Thomas, DL3EL

[Thomas Beiderwieden]

Hi Alan, again me,

next thing I have tested is the logging. When I save a log entry something like an empty frames is send via WebSocket. My receiver is triggered, but nothing seems to be there. Could you please check?

vy 73 de Thomas, DL3EL

[ahop...@googlemail.com]

Hi Thomas,

the last couple of releases swapped the library used to generate and parse json with something faster. This affected both settings and the websocket stuff, the loss of the '.0' was a side effect I had not noticed and to be honest I'd never noticed it was there to begin with.  I believe the json spec does not require the '.0' .  Just saw the logging message, I shall look into that and see how easy it is to convince the new library to put the .0 back on.

73 Alan M0NNB

[Thomas Beiderwieden]

Hi Alan,

thanks for the quick answer. But don't get me wrong, I do not need the .0. I had explicitly added code to remove it, so it would be ok for me if it stays as it is. For now I have reverted to .966, as logging doesn't work anymore.

vy 73 de Thomas, DL3EL

[ahop...@googlemail.com]

Hi Thomas,

I've found the logging bug, remind me what your preferred platform is and I'll post a test version when fixed.  I converted the websocket stuff first and then did the settings in a slightly better way, I shall take this opportunity to unify them which should also prevent any other messages being missed in future.

73 Alan M0NNB

[Thomas Beiderwieden]

Hi Alan,

my preferred system currently is the Raspberry 4 with 32bit Buster.

vy 73 de Thomas, DL3EL

[ahop...@googlemail.com]

Hi Thomas,

hopefully this https://www.sparksdr.com/download/SparkSDR.2.0.975.linux-arm.deb will work.

73 Alan M0NNB

[Thomas Beiderwieden]

Hi Alan,

yes it does. I have quickly repeated the test from yesterday (qsy & log) and it works. For qsy I have adapted my script to the new format. fb

Thanks

vy 73 de Thomas, DL3EL