Thetis v2.8.11 - UPDATES and current issues

[Joe]

Thanks for everything! Many great updates.

Joe
WD5Y

[NC3Z]

I just can't explain the agc rc2 problem...
RIchie.

Ritchie, I run split sample rates, 192K on RX1 and 1536K on RX2. I stated to note that in my explanation and neglected to note my sample rate on RX2. Although both use the same Bin Width.

It is not an issue now that I understand that it changed. I can set the values to work the way I run my station, it was just different in this version and wanted to report my findings.

I set my Auto AGC offset by ear anyways.

[ramdor]

Since the upgrade I can no longer change the RX2 VFO via the client 2. If I manually change the VFO B that is reported by the client.
If I TX the via RX2 client output is displayed on RX2 window - as expected.

Hi Nigel,

I have fixed this in rc3, it should be out sometime in the coming week before the weekend.

A vid to show it in operation : https://youtu.be/l-8ttd_4_u0

Richie.

[DF2LH]

Does the PA implement multiple TCI client connections? So able to connect to Thetis + EESDR3 at the same time? If not I don't quite understand how it can work with two TCI servers at the same time (Thetis + EESDR3).

Thetis sends out ping frame every 20 seconds (websocket spec), and does not need a reply. However, it will reply with a pong frame if it receives a ping frame. If the frame send fails due to loss of connection for example, Thetis will close the connection.

Edit: I will be adding log windows for both TCI + CATtcpip next week so you can see inbound and outbound messages.

R.

Hi Richie
no, the RF-Kit is not multi TCI capable. I have changed in the PA from the IP:Port of the PC with EESDR to the IP:Port of the PC with Thetis.
Thetis answers every ping of the RF-Kit with a pong and also immediately displays 'TCI Server 1 client connected' when I activate TCI in the PA.
A log window will certainly be a great help to address such problems.
I will report my observation to the OM at RF-Kit about the unsuccessful connection here.

73, Thomas

[Chiron]

@ramdor Richie

PureSignal usage is great.
For the anan with 16 bit ADC is the default value for SetPk = 0.4072

When switching over to hermesLite2 with has a 12 bit ADC the SetPk = 0.4072 is not the propper value. It must be something like 0.238

In order to get 'PureSignal correction' to work the SetPk needs to be set to a value like 0.23. After doing this manualy all works fine. But after starting Thetis again, the default value is 0.4072. Thats perfect for the Anan. But not working for HermesLite2.

Is it possible to save the SetPk value together with the IP address of the radio. And at starting Thetis, recalling the SetPk value corresponding to the IP address of the selected radio?

Chiron

[rdscuba]

I am attempting to do the latest update to Thetis. I am getting the attached error after copy/pasting the newly downloaded Thetis2_8_11_MW0LGE_21k8_64bit files inot the Thetis install folder as per the video at the top of this thread. Any help is appreciated.

thetis error.JPG (32.54 KiB) Viewed 21698 times

[ramdor]

@rdscuba hi, follow the instructions in post1 and it will work. You need to hold CTRL down as you run up the patched version for the first time, this will update your database. Ensure you take a backup first.

You will be presented with the following :

updateDB.png (11.73 KiB) Viewed 21690 times

Follow the on screen instructions.

Cheers, Richie.

[Tony EI7BMB]

Has anyone else noticed any change to VAC stability ? I find I have to reset VAC way more often lately.

[w-u-2-o]

Perfectly stable here. Never have to do anything to it.

[Tony EI7BMB]

Thanks Scott. I'll do some digging to try see what's going on.

[DH1KLM]

VAC also stable here. No difference to prior Versions.

[ULTIMAX]

Just curious, on something I notice after I install the latest 21K (rc2-b) I notice an increase in CPU at system not Thetis when I open any other window, most of the time before the download was between 13-18% , now is 26-60% , DELL intel core i7 @4.00GHz 16 GB 64-bit windows 10
even while making this post while listening in the bands the CPU climbs to 59%, everything works fine, I don't run any logging software or do any digital stuff, just simple SSB. any ideas ???? thank you
73's

[W1JA]

change: rework of cursors

Hi RIchie. If this change was intended to help with my disappearing-cursor issue, I'm sad to report that with k9rc2-b the issue is still present, same as before.

73, John

[ramdor]

change: rework of cursors

Hi RIchie. If this change was intended to help with my disappearing-cursor issue, I'm sad to report that with k9rc2-b the issue is still present, same as before.

73, John

No John, it was just a tidy up of the cursor stuff. I have spent quite a while looking into your issue. The only work around will be to add an option to disable the new DirectX approach. It is very odd, and unfortunately I can not find a solution at this time. I will include the option in rc3, it will require a restart to take effect.

R.

[va7qi]

I see that the latest versions are no longer listed on the first part of this discussion.
Where are the latest RC versions posted now?

73 de va7qi, ....Erik.

[ramdor]

.

[Alexander UC]

rc2-b AGC works strangely, it looks like at that time - the decline is fixed. And it doesn't depend on settings.

[oe3ide]

rc2-b AGC works strangely, it looks like at that time - the decline is fixed. And it doesn't depend on settings.

yepp, will be fixed in rc3

73 Ernst

[ramdor]

All links to existing downloads have been made unavailable at this time, including rc2-

21k9rc3 will arrive in the next couple of days hopefully.

Richie.

[G3ZQH]

DirectX error message
Thetis 21k9RC2-b has been running fine for a couple of days but this came up this morning after leaving it running overnight. The panadapter and waterfall are blank but otherwise Thetis seems active. Screenshots of DirectX error attached. I had to use Task Manager to shut down Thetis and after this it re-started with full functions restored. I've not seen this before.

73 Dave G3ZQH

[ramdor]

I've not seen this before.
73 Dave G3ZQH

neither have I Dave, could be ...

a) auto update
b) gpu driver crash
c) sleep/awake issue
d) device resolution changes
e) device driver bugs (are you updated to latest)
f) issue in code related to create bitmap (I will have a check later today)

Richie.

[G3ZQH]

Richie, I'll monitor for now and report if it re-occurs.
73 Dave

G3ZQH wrote:
I've not seen this before.
73 Dave G3ZQH


neither have I Dave, could be ...

a) auto update
b) gpu driver crash
c) sleep/awake issue
d) device resolution changes
e) device driver bugs (are you updated to latest)
f) issue in code related to create bitmap (I will have a check later today)

Richie.

[ramdor]

*** hopefully last before it hits post 1, test release 21k9rc3 (I keep saying that)

NOTE: ISSUE WITH THIS BUILD, Turn off N1MM UDP spectrums if you use that before patching, and hold off using them until fixed in rc4 (argghhh)

Please try :

Download x64 [md5: D5200DE4DDC05B820F1B758FD15BE664] - https://bit.ly/3Hw8bwM

and please keep it civil regarding the changes I decided to include regarding the nightmare in Ukraine. Remember, you do not have to use this modified version.

If you use TCI spots, additional info is now shown as follows :

tciSPOT.png (7.9 KiB) Viewed 20904 times

Cheers, Richie.

[21k9rc3]
add: directX legacy buffer option added
add: Thetis version timeout added (this version times out on 1st June 2022)
change: Use Peak Meter Readings for TX COMP and ALC check box moved into ALC section of DSP tab
change: second wdsp update - (1) minor changes to ease builds for non-Windows platforms, and (2) changes to improve display frequency accuracy for high zoom situations
#Stand up for Ukraine#
If you do not agree with the following changes, then feel free not to use this software. (apologies for any false positives)
From 21k9rc3 onwards :
change: if region is Russia, language installed on PC is Russian, along with a host of other checks, you will be reminded about Ukraine
change: all spot systems will ignore any Russian DX stations, or spotting stations

[ea3aqr]

Thanks Ritchie!

Agree with "Russian mods", those days I don't answer or call to russian stations...

EDIT: TCI spots, additional info is just showing "SWL", nothing else... I don't know if it is an issue with Swisslog.

[oe3ide]

Thanks Ritchie!

Agree with "Russian mods", those days I don't answer or call russian stations...

EDIT: TCI spots, additional info is just showing "SWL", nothing else... I don't know if it is an issue with Swisslog.

Yes, swisslog sends only "swl" as text:
SPOT:6W1TG,USB,14222000,16776960,Swl;
SPOT:WB9ONU,FT8,14074000,16776960,Swl;
SPOT:6W1TG,USB,14222000,16776960,Swl;
SPOT:6W1TG,SSB,14222000,16776960,Swl;
SPOT:6W1TG,USB,14222000,16776960,Swl;

73 Ernst

[ea3aqr]

Thanks Ritchie!

Agree with "Russian mods", those days I don't answer or call russian stations...

EDIT: TCI spots, additional info is just showing "SWL", nothing else... I don't know if it is an issue with Swisslog.

Yes, swisslog sends only "swl" as text:
SPOT:6W1TG,USB,14222000,16776960,Swl;
SPOT:WB9ONU,FT8,14074000,16776960,Swl;
SPOT:6W1TG,USB,14222000,16776960,Swl;
SPOT:6W1TG,SSB,14222000,16776960,Swl;
SPOT:6W1TG,USB,14222000,16776960,Swl;

73 Ernst

Tomorrow I will talk with Swisslog developer...

[Siddhu]

I just patched with release 21k9rc3 and performed a database update as well. I'm getting this error while opening Thetis

Error.jpg (55.7 KiB) Viewed 20819 times

[ramdor]

@Siddhu Yes that is an rc3 introduced bug by the looks of it. I will get a version out tomorrow to fix that. It is caused by having N1MM spectrum turned on.

You can edit the database.xml file to get around it for now, located here : C:\Users\<user>\AppData\Roaming\OpenHPSDR\Thetis-x64

<Options>
<Key>chkN1MMEnableRX1</Key>
<Value>False</Value>
</Options>
<Options>
<Key>chkN1MMEnableRX2</Key>
<Value>False</Value>
</Options>

R.

[Tony EI7BMB]

Thanks Richie, just installed.

[W1JA]

add: directX legacy buffer option added

Richie, I checked the checkbox, restarted Thetis, confirmed the checkbox was still checked, but the disappearing + cursor problem is still there, same as before.

Sri es 73, John W1JA