Thetis v2.8.11 - UPDATES and current issues

[W1AEX]

Hi Richie,

I still have the earlier 2.8.11 64-bit version installed and when compared on the desktop to the new 32-bit version (both opened up but not running) the difference in the GUI size with the same resolution setting was easily seen. I confirmed with my screen capture software that something was off with the new release. Hope you can avoid installing the dreaded Paint program!

73, Rob

[ramdor]

Hi Richie,

I still have the earlier 2.8.11 64-bit version installed and when compared on the desktop to the new 32-bit version (both opened up but not running) the difference in the GUI size with the same resolution setting was easily seen. I confirmed with my screen capture software that something was off with the new release. Hope you can avoid installing the dreaded Paint program!

73, Rob

yeah it is very odd. I have even started an empty test bed project with the same results. Setting client area works as expected, but not the external form size. Even with some jiggery-pokery using border widths and title bar height the numbers are still off. Will take a look tomorrow

[I2NOY]

So I also throw in one wish Autostart of dx spotting (maybe selectible via setup) would be really great (just using the last settings from the dx-spotting screen and start spotting (ok its not spotting, its "connect to dx-cluster").

And the blue text in the dark menu-strip (if spotting is enabled) is hard to see, maybe light green/light blue would be better.

Thanks!

I quote totally.
For us in Europe, I wish I have a check box to select spots coming from Europe only.

[I2NOY]

@Richie
I am an old IT manager and not a coder but I wonder if the code is compiled with options to use relatively new cpu instructions (AVX, AVX2, etc.) and new hardware.

[ramdor]

@Richie
I am an old IT manager and not a coder but I wonder if the code is compiled with options to use relatively new cpu instructions (AVX, AVX2, etc.) and new hardware.

lots of people probably use cpus without avx. Iirc a release was made with avx compiler options but it was subsequently turned off afaik due to the number of people without support. I've not looked into it, it is something Doug looks at afaik.

Richie.

[ramdor]

An interesting metric.

74 copies of the x64 downloaded so far
12 copies of the x86 downloaded so far

Richie.

[w-u-2-o]

Yep I am not sure if we can set a bit to stop the rear PTT output. I checked the code quickly and all that seem to be available is TXRX relay, and the PA. I'll poke Doug to find out more, and if that fails add some checkboxes to OC to bypass when TUN/2TON.

Recommend these be two different checkboxes, because a common use for two-tone is to check amp drive. Hence a typical workflow would be amp standby with TUN, amp operate with two-tone.

[w-u-2-o]

An interesting metric.

74 copies of the x64 downloaded so far
12 copies of the x86 downloaded so far

Richie.

Is there anyone actually running a 32-bit system anymore? I can't imagine it.

It might be time to stop the 32-bit builds just to force that issue and find the one person who still is, and then shame them into upgrading

More seriously, it's a lot of extra work to support both builds and it shouldn't be necessary in this day and age.

[ramdor]

Yep I am not sure if we can set a bit to stop the rear PTT output. I checked the code quickly and all that seem to be available is TXRX relay, and the PA. I'll poke Doug to find out more, and if that fails add some checkboxes to OC to bypass when TUN/2TON.

Recommend these be two different checkboxes, because a common use for two-tone is to check amp drive. Hence a typical workflow would be amp standby with TUN, amp operate with two-tone.

Indeed Scott. Yes I was thinking two vertical rows, one for TUN and the other for 2TON.

Richie.

[ramdor]

Hi Richie,

I still have the earlier 2.8.11 64-bit version installed and when compared on the desktop to the new 32-bit version (both opened up but not running) the difference in the GUI size with the same resolution setting was easily seen. I confirmed with my screen capture software that something was off with the new release. Hope you can avoid installing the dreaded Paint program!

73, Rob

Well Rob, I even had to get my brother involved in this as he has looked at such oddities over the years. It is related to the drop shadow of the form. Short story is that we now calculate the size of the shadow using DwmGetWindowAttribute and some jiggery-pokery related to operating system versions and whatnot. It should now be fixed

Richie.

[Joe]

Richie,
This is a photo of the adjustments of the OC page. It works but I know you could streamline this much better. Thanks for your consideration.

73’s
Joe
WD5Y

[K1LSB]

Yep I am not sure if we can set a bit to stop the rear PTT output. I checked the code quickly and all that seem to be available is TXRX relay, and the PA. I'll poke Doug to find out more, and if that fails add some checkboxes to OC to bypass when TUN/2TON.

Recommend these be two different checkboxes, because a common use for two-tone is to check amp drive. Hence a typical workflow would be amp standby with TUN, amp operate with two-tone.

Maybe I'm misunderstanding, but I would disagree that two-tone is commonly used to check amp drive, as TUN is the intended (and de facto) feature to use for that. In fact, my AL-80B drives much differently using the default two-tone than it does using TUN (though I've never figured out why that is), consequently I never check amp drive with two-tone.

In fact, I hardly ever use two-tone at all, even for PureSignal - I just start talking into the mic and PS engages immediately using voice alone. I haven't used two-tone more than a handful of times since purchasing the radio.

But that's just me.

Mark

[I2NOY]

Hi, some small cosmetic corrections on GUI.

Immagine 2021-06-30 170922.jpg (9.91 KiB) Viewed 50780 times

On left TX button (VFO A) there is a red frame when it is selected and it changes when you pass the mouse over it.
The same on VFO B, but the frame is yellow.

On other buttons this is not present.



P.S.: I noted that TX buttons at right of frequency display of VFO A and B are probably coded inside the program as I don't see them in skin buttons.

[W1AEX]

Well Rob, I even had to get my brother involved in this as he has looked at such oddities over the years. It is related to the drop shadow of the form. Short story is that we now calculate the size of the shadow using DwmGetWindowAttribute and some jiggery-pokery related to operating system versions and whatnot. It should now be fixed

Richie.

Thank goodness for brothers! Thanks for taking a look at that and figuring it all out. When you first implemented that feature I quickly found that having presets is a great help when setting up a quick screen capture on the fly.

73, Rob

[w-u-2-o]

Maybe I'm misunderstanding, but I would disagree that two-tone is commonly used to check amp drive, as TUN is the intended (and de facto) feature to use for that. In fact, my AL-80B drives much differently using the default two-tone than it does using TUN (though I've never figured out why that is), consequently I never check amp drive with two-tone.

In fact, I hardly ever use two-tone at all, even for PureSignal - I just start talking into the mic and PS engages immediately using voice alone. I haven't used two-tone more than a handful of times since purchasing the radio.

But that's just me.

Mark

Yup, that's just you I don't want to create thread drift, this being Richie's 2.8.11 Current Issues topic, but you can PM me if you'd like to discuss further, or even start a new topic in the Amp & Tuners sub-forum.

[K1LSB]

Understood, I'm good, thanks Scott.

[ramdor]

Well, doing some testing and this one cropped up :

Can currently CTRL right click on a band to add the current frequency to that band stack. So when on 7.150mhz for example, you can ctrl right click 20m band button and 7.150 will appear in the 20m stack.

After that point, if you are on 40m you cant switch to 20m, because the code will find 7.150 in the 20m band stack and set to that.



Richie.

[g4xzl]

Hi Richie,
I have spotted a problem with CTUN and cw modes. In cw mode you get a shift between tx and rx frequencies so that if you tune in to a station at a beat note of 800Hz and you have set the cw pitch frequency setting also to 800Hz, you will transmit with an 800Hz offset so the other station will hear you at 800Hz also, all fine.
If you toggle the CTUN mode on, the tx to rx shift is lost so that the other station will now hear you at zero beat, the qso is then probably lost as you might be out of the rx passband at the other end!
This happened to me the other night and chatting in ssb after the qso they told me I was way off frequency, we all got rather confused until I did some tests on dummy load later!!
I think this problem may have been in the code for a while, I'm not sure, it may be that my regular qso partners may have been very politely using their rit to compensate!!! The work-round it to permanently set the rit to 800Hz, or not use CTUN, neither is very convenient.
If its possible to look into it, it would be much appreciated.
If you need more explanations, don't hesitate to ask.
Thanks,
Andrew
G4XZL

[ramdor]

Hi Richie,
I have spotted a problem with CTUN and cw modes. In cw mode you get a shift between tx and rx frequencies so that if you tune in to a station at a beat note of 800Hz and you have set the cw pitch frequency setting also to 800Hz, you will transmit with an 800Hz offset so the other station will hear you at 800Hz also, all fine.
If you toggle the CTUN mode on, the tx to rx shift is lost so that the other station will now hear you at zero beat, the qso is then probably lost as you might be out of the rx passband at the other end!
This happened to me the other night and chatting in ssb after the qso they told me I was way off frequency, we all got rather confused until I did some tests on dummy load later!!
I think this problem may have been in the code for a while, I'm not sure, it may be that my regular qso partners may have been very politely using their rit to compensate!!! The work-round it to permanently set the rit to 800Hz, or not use CTUN, neither is very convenient.
If its possible to look into it, it would be much appreciated.
If you need more explanations, don't hesitate to ask.
Thanks,
Andrew
G4XZL

I did some testing Andrew. I could not replicate the problem. https://www.youtube.com/watch?v=m-VlJdckID0

May need more info or vid (even if phone recording).

Richie.

[Yevgeni]

Hi
Checked out CW and CTUN. Everything is working correctly.
But there is one mistake that does not affect the QSO.
She is seen in the Richie video.

[ramdor]

Hi
Checked out CW and CTUN. Everything is working correctly.
But there is one mistake that does not affect the QSO.
She is seen in the Richie video.

nice spot !!! thanks

Richie.

[g4xzl]

Hi Yevgeni,
Interesting that you do not see the problem of CTUN and cw mode. May I ask how you checked it please?
I had a second radio and both were connected to dummy loads so that I could transmit one to the other?
Thanks,
Andrew
G4XZL

[ramdor]

Hi Yevgeni,
Interesting that you do not see the problem of CTUN and cw mode. May I ask how you checked it please?
I had a second radio and both were connected to dummy loads so that I could transmit one to the other?
Thanks,
Andrew
G4XZL

I guess you missed my reply Andrew? I made a video for you : https://www.youtube.com/watch?v=m-VlJdckID0

[g4xzl]

The comments from Yevgeni made me have a think....
I have checked further and found that actually it is occurring when using a transverter with details of LO and gain set in the 'XVTR' menu.
I did not mention this in my original post as I did not realise it would make a difference, apologies I should have.
So to clarify:
When using a transverter with CTUN on and cw mode the tx/rx offset is lost as described in my previous posting.
When just on HF, with CTUN on and cw mode the tx/rx offset is working correctly!
This probably explains why it has not been noticed before as I guess most cw will be direct on HF?
Yevgeni, maybe you could double-check if you see the same with a transverter setting?
I am using a 28-144MHz transverter so the LO setting in the 'XVTR' window is 116MHz.
Thanks,
Andrew
G4XZL

[ramdor]

The comments from Yevgeni made me have a think....
I have checked further and found that actually it is occurring when using a transverter with details of LO and gain set in the 'XVTR' menu.
I did not mention this in my original post as I did not realise it would make a difference, apologies I should have.
So to clarify:
When using a transverter with CTUN on and cw mode the tx/rx offset is lost as described in my previous posting.
When just on HF, with CTUN on and cw mode the tx/rx offset is working correctly!
This probably explains why it has not been noticed before as I guess most cw will be direct on HF?
Yevgeni, maybe you could double-check if you see the same with a transverter setting?
I am using a 28-144MHz transverter so the LO setting in the 'XVTR' window is 116MHz.
Thanks,
Andrew
G4XZL

ok that makes more sense. I will investigate.

Richie.

[g4xzl]

Yes, sorry, I missed your video, just watched it now.
Just doing a bit more testing, it seems to transmit on the correct frequency, but not receive. So probably easier to notice if you can transmit between the two radios.
The sdr here is a Hermes board.
Attached a couple of pictures of a second radio transmitting to the Hermes. One if with CTUN off and the other with CTUN on, nothing else changed. I set the Panadpter to peak mode so it was easier to see the signal and take a screenshot.

ctun and cw problem ctun on.png (242.16 KiB) Viewed 50742 times

ctun and cw problem ctun off.png (263.47 KiB) Viewed 50742 times

Transmitting back to the second radio is fine, CTUN on or off has no effect.
If you pretend you have a transverter and transmit on the frequency I used it will really be 28.155 so you can still test with your sunsdr I think?
Thanks,
Andrew

[DL8LAQ]

So to clarify:
When using a transverter with CTUN on and cw mode the tx/rx offset is lost as described in my previous posting.
When just on HF, with CTUN on and cw mode the tx/rx offset is working correctly!

I have tested with and w/o xvtr. I can confirm this ctun misbehaviour with xvtr.

[ramdor]

Fixed I think Andrew. Just tested into 2m on the Sun as you suggested. I have sent you a PM with 21b pre-release test build. Please let me know if issue is resolved.

Richie.

[Yevgeni]

Hi

I also see an error CTUN with XVTRs.
The transmission is correct.
Reception frequency error.

[w3ub]

Thanks for all the work Ritchie and others!

I like the improved P1 roadmap, supporting 384k sample rates. If we had that I would ditch P2 and use P1, as I find P2 works, sort of, most of the time, but the more you stress it (higher sampling, PS, diversity) the more the FW timing starts to break.

/Doug