Thetis Development Build 2.10.3.6 dev_5 available

[ramdor]

Hi folks,

I have just released dev_5 and it has already been updated to dev_5b. Not much testing for these new features so I am expecting a few things to drop out of the woodwork. Change log below.

Link here : https://github.com/ramdor/Thetis/releas ... .3.6-dev_5

Note. although mentioned in the change log, the colour picker didn't make it through as yet for the tx-att combo box.

Cheers. Richie.

## v2.10.3.6 Change Log - WIP dev_5b
- [fix] small change to auto start exe code to fix issue with command line args

##v2.10.3.6 Change Log - WIP dev_5a
- [add] support for command line arguments in the auto launch settings. It should now do something !
- [add] warning message shown when the bypass of BPFs is ignored for PureSignal transmissions
- [changed] forced the bpfs bypass check to be on as default

## v2.10.3.6 Change Log - WIP dev_5
- [add] output AI (kenwwood broadcast info) over cat1/2/3/4/tcpipcat options. (included in dev_4 but here for completeness)
- [add] option in setup for S9 @ -73 or -93 for 30MHz and 144MHz (github #418)
- [add] options added for SWR protection. Swr limits, and tune power (github #221)
- [add] zzoa and zzoc cat commands have been added. zzoa - get/set the rx antenna based on rx1 band. zzoc - get/set the tx antenna based on tx band (github #385)
- [add] rx antenna port selection option for XVTR. It should also revert any changes if you leave an xvtr band. Only applies to RX1 currently (github #424)
- [add] 8 diversity memories. shift click to store, ctrl click to clear (github #263)
- [add] zzxa cat command to get/set audio amplifier (rear speaker sockets). zzxa1; to enable, zzxa0; to disable (github #308)
- [add] midi button command to toggle audio amplifier (rear speaker sockets) (github #308)
- [add] notes field in multimeter container. They are also used in the titlebar of the containers (github #104)
- [add] new start up options tab in setup. Now includes options to open specific forms at start up, and programs/exes (GitHub #286)
- [add] option to prevent ps from bypassing the bpfs (GitHub #413)
- [fix] decouple of the rx1/rx2 attenuator preamp/s-att boxes from tx-att. New tx-att control, and bg colour settings in appearance (github #399)
- [fix] multimeters would sometimes not bottom to low values out when power off, and other rare occurrences. Now resolved
- [change] simplification improvements to db import

[Tony EI7BMB]

Thanks Richie. Edit: Just tested the start up feature and Thetis fires up JTDX no problem at all . Very useful feature

[W4WMT]

- [add] option to prevent ps from bypassing the bpfs (GitHub #413)

Hi All,

Did we ever figure out whether there was a good reason for that "ps bypass" behavior being there in the first place?
It was obviously coded that way on purpose (not a bug).

73,
Bryan W4WMT

[ramdor]

@Bryan W4WMT

nope, I dont think so. I just coded around the option for disabling it if people wanted to test. The default is where it was originally, bypassing the bpf if PS is used.

[ramdor]

@Tony , ah cool! yes I started implementing it earlier today. Seems to work ok.

[W1AEX]

Nicely done Richie! I did a number of Thetis startups and shutdowns until I got all my auto-start "stuff" positioned just how I wanted it. Everything comes up perfectly including my memory positioning of the Diversity phase and gain settings. Everything new to the Dev 5 release that I have messed around with is working perfectly.

Regarding the Bypass of HPF on TX (when PS is enabled) I believe this dates back to the early ANAN radios that came before the REV24 PA boards. There was serious crosstalk during TX in the HPF of REV15 and REV16 boards that made operation with PS on bands above 40 meters very unpredictable and usually very messy. Unless you did the internal cable re-routing documented by Bill Diaz (KC9XG) and used an external relay to change the path of the PS sample to go directly into the mainboard RX port (physically bypassing the HPF) the correction with PS on the upper bands was poor as the internal crosstalk drowned out the RF sample from the external sampler: http://www.w1aex.com/anan/anan.html#relay

I think the HPF Bypass on TX was an attempt to allow cleaner PS operation on the upper bands but I never noticed much improvement with PS using that setting with my ANAN-100 REV16 model.

73, Rob W1AEX

[Warren_NR0V]

Reason for bypassing BPF for PS transmit: We run a high feedback level to use basically the full dynamic range of the ADC. This high signal level can produce passive Inter-Modulation Distortion in the inductors of the bandpass filters. This distorted feedback then degrades PS performance. This is more pronounced in some radios than others. Note that you will NOT be able to observe the degraded performance on the panadapter because PS is correcting to the distorted feedback and the panadapter is "seeing" that same distorted feedback. It can only be observed with an external spectrum analyzer.

73,
Warren NR0V

[ramdor]

@warren

the following will be shown if the bypass system for PS is disabled. The message added in next release. Default is to have the bpfs bypassed with PS.

no-bpf-ps.png (25.58 KiB) Viewed 18108 times

[NC3Z]

Using the new new start up options works fine except for programs I need to start with a command line switch, such as Log4OM where you identify the config file. If I use the command switch then the program does not open, if I remove the switch syntax the program loads.

Start.jpg (123.56 KiB) Viewed 18103 times

[ramdor]

i will look at improving it Gary. At the moment it essentially ignores command line arguments. I might do an update to _5 later this morning, or release a quick _6 with the small change.

[Warren_NR0V]

Richie,

I think the PS BPF warning is a good idea. Thanks for planning that.

BTW, thanks for all the continuing work and dev_5.

Warren NR0V

[NJ2US]

Alright, help a brotha out. When I installed Dev 5, I noticed that "BPF Bypass on PS" is UNCHECKED by default.
In order to avoid the problems described, should not this option be CHECKED by default?

Jeff NJ2US

[ramdor]

I quickly released dev_5a. Changes for the command lines though not much testing. A couple of other timely changes

This is what I see on mine regarding the bpf. If you were running dev_5 before dev_5a, install dev_5a and check that you have that BPF bypass enabled. It should be as default if you have the necessary radio model.

Note. dev_5 has been dropped, replaced with dev_5a

R.

[ramdor]

Updated again.... dev_5b

Cheers. R.

[Trucker]

Ritchie,
Just downloaded and installed dev_5B everything seems to be working fine. I don't use any external programs with Thetis so, I have not tested the auto launch feature.
Thank you for your continued improvements to Thetis. It is greatly appreciated.
James
WD5GWY

[ginger]

thanks Richie

[ramdor]

Using the new new start up options works fine except for programs I need to start with a command line switch, such as Log4OM where you identify the config file. If I use the command switch then the program does not open, if I remove the switch syntax the program loads.

Have you had a chance to try dev_5b yet Gary? I wonder if you have had any luck with the command arguments?

It finds the first locations of .cmd and/or .exe in the text box string, works out which one is left most, and passes everything after the .exe or .cmd as an argument. It doesn't do anything clever with " or things like that so you have to be wary with those.

[NC3Z]

Yes Richie, putting it through it's paces and 5b does allow command line arguments to work! Brilliant!

[ramdor]

@Gary nice!! That is great to know. I did get it working with a text file into notepad, so I was hoping it would.

[w3ub]

5b working well here ... we're going to need more option tabs!
Thanks for the hard work.
Doug

[KC2QMA]

I know I sound redundant but...
Thank You Richie!!!

[N4XD]

Richie thanks for all the updates!!

Ron
N4XD

[Tony EI7BMB]

Gary I wonder if you have tried JTalert by any chance. I managed to wreck the first dev 5 by trying to be too clever and pasting in

"C:\Program Files (x86)\HamApps\JTAlert\JTAlertV2.exe" /jtdx

which I got from the JTalert shortcut properties dialogue

[NC3Z]

Tony, I found if you use " it will prevent Thetis from opening. In that case you simply edit the db and remove those ""

So try it without the " "

e.g. C:\Program Files (x86)\HamApps\JTAlert\JTAlertV2.exe /jtdx

[Tony EI7BMB]

Thanks Gary, yeah I found that out the hard way that it would not start. Luckily I had a back up database so just started over with a new database and re imported.
The " " were the offending characters as you rightly pointed out so working great now.

[W1AEX]

phasing control press m3.jpg (33.74 KiB) Viewed 17666 times

phasing control press m1.jpg (34.08 KiB) Viewed 17666 times

Installed 2.10.3.6 dev_5b and so far all the features I use are working fine with one exception. One display error has showed up with the Diversity interface. I find that when I start Thetis the Diversity "Phasing Control" comes back in the state it was in and the settings appear to be correct but the Phasing Control does not reliably display the correct point of adjustment. If I exit the Diversity GUI and then restart it, the GUI Phasing Control displays the memory point correctly and all is fine. So, the memory of the gain and phase adjustment function is fine, just the reported GUI setting is sitting at the center of the adjustment circle or at a random point instead of on the actual point of adjustment. Switching between Diversity M1 - M8 memories can also cause the adjustment point to remain in the middle of the circle or at another random point rather than on the actual adjustment point. It has been repeatable here with several Thetis shutdowns and restarts.

Rob W1AEX

[ramdor]

hmm. diversity configs are stored per band. Which has always been the case. If you use a memory recall button to load one of these 8 additional, then it will overwrite the settings for the current band. Consequently if you change band, then come back it will look like that memory config is now in use.

The M[1-8] buttons are essentially like favourites than you can store away, and recall at any time, whatever band you are on. Those settings from that mem button will be used for that band.

Edit: it does look like something odd is going on. I just started up and was 'stuck' in the centre. Will look into it Rob. Cheers.

[W9BHI]

I am trying to get the Auto launch at start up to work with my 3rd party software. it is the W1T1 program for the Palstar HF-Auto tuner.
I can get DDUtil to auto start but that is a .exe file.
The target for DDUtil looks like this: C:\DDUtil_V3\DDUtil_V3.exe.
The target for the HF-AUTO program looks like this: C:\Apps\TGG_Systems\HFAUTO\
It does not work in the Auto launch at startup.
How do I get this to work in the Auto launch at startup?
Thanks,
Don W9BHI

[NC3Z]

How about a screenshot of how you have it set. Autostart works fine, here is how mine looks:

Screenshot 2024-07-11 201631.jpg (121.05 KiB) Viewed 17537 times

[K1LSB]

Don,

Your target for the HF-AUTO program is just a folder, with no executable app specified.

C:\Apps\TGG_Systems\HFAUTO\

Mark