apache-labs.com

Start the radio with vfo sync. Go to whatever band you like and open the setup screen. You will see the second receiver filter that is selected with the dot inside the circle. If it is in the correct band change band to see if it is following the frequency. Mine is not following the frequency change. If I press the RX2 button next to POWER and then depressed it everything works fine.

Thanks Richie

Mike SV1JSO

Is the correct radio model selected in Setup->General and Alex is checked in Setup->General (it is in the Hardware Options combo box)

Richie.

Hello Richie,
like Jörg DD8JM, I would like to ask again about the fixed band edges in CTUN mode. (TODO 24) Limit tune to viewed spectral area). I know it's not a major priority. Is there anything new in this direction?

Yes everything is correct. Radio is 7000dle and Alex is checked.
If yours is working ok I'll do a database reset and try again.

I 'll report back later.

Thanks Richie.

Mike SV1JSO

DH1KLM wrote:Hello Richie,
like Jörg DD8JM, I would like to ask again about the fixed band edges in CTUN mode. (TODO 24) Limit tune to viewed spectral area). I know it's not a major priority. Is there anything new in this direction?

No Sigi, I have not look at it yet. If you want to limit up to the edge of the spectral area, what happens if something (cat/midi/split/etc) wants to go beyond? It is not quite as simple as it seems. If it is only a mouse drag limit than that is ok and can be done easily enough.

R.

It is not quite as simple as it seems. If it is only a mouse drag limit than that is ok and can be done easily enough.

Perhaps a switch CTUN Lock could be introduced under Miscellaneous to fix the band limits or not.

Have a nice evening!

Greeting Jörg, DD8JM

I am using Version 21k8 and P2.
Radio is an ANAN 7000

In CW when QSK is set and NB2 is on, I get two signals on the monitor display.
One at the VFO freq and one at the true CW freq.

Also when doing a Calibration, if the mode is set to CW then the results of the calibration is off by
the CW offset. Up for CWU , down for CWL

Thanks
Tom AA4VV

Frequency calibration should be done in SSB mode. Adding the ability to do this in CW mode doesn't seem like a worthwhile pursuit.

w-u-2-o wrote:Frequency calibration should be done in SSB mode. Adding the ability to do this in CW mode doesn't seem like a worthwhile pursuit.

You may be right. It seems to me that the Calibration shouldn't work in CW mode. It will give an incorrect calibration when in CW mode.

Thanks for your great support in all the forums.

73 Tom AA4VV

ramdor wrote:No Sigi, I have not look at it yet. If you want to limit up to the edge of the spectral area, what happens if something (cat/midi/split/etc) wants to go beyond? It is not quite as simple as it seems. If it is only a mouse drag limit than that is ok and can be done easily enough.
R.

I will be reviewing PowerSDR on this subject in the next few days.
I don't expect any difficulties in connection with CTUN and MIDI etc.
I might also take a look at the PowerSDR source code.

DH1KLM wrote:I will be reviewing PowerSDR on this subject in the next few days.
I don't expect any difficulties in connection with CTUN and MIDI etc.
I might also take a look at the PowerSDR source code.

https://youtu.be/c_mSDVFArSA

Richie.

This was very fast. Great work as always. I like this very much.

Back then, Chris / W2PA implemented the corresponding changes in PowerSDR 3.4.4.
http://w2pa.net/SDR/2017/09/09/addition ... ancements/

https://youtu.be/c_mSDVFArSA

Hi Richie,

great solution, this is exactly how I imagined CTUN, thanks.
Super fast implementation.
I am already looking forward to the 21L8.

With kind regards

Jörg, DD8JM

Hello Richie! I'd like you to ask pay attention to one annoying Thetis bug My friend send me a link to YouTube video, where he show this problem.
[youtube]https://www.youtube.com/watch?v=YLzaqCe40EI[/youtube]

Hi Rich
Sorry its taken me so long to report this issue - but I wanted to confirm my suspicions that it wasnt firmware/hardware or database issue at my end. I'm now running on a new build, first installed 2.8.11 then went direct to K6 then K7, 8

On my old PC issues started at much earlier update - essentially fromwhen you were working on MultiRX issues.

Now if you do not close the program with MultiRX off, it is not possible to get or restart an audio output on MultiRX via VAC1.

Work around is to deselect MultiRX, close the program and open the program again. Then select MultRX and voila there is auio output again via VAC1.

I can confirm this issue wasn' t present in release 2.8.11 and is independent of firmware (currently using 2.1.18).

Many thanks for your labours of love with Thetis - much appreciated

Hello
Please help
Installation 21a, 21b, 21с goes well, without errors.
As soon as I reach 21d, this is the picture.

@YL2GVC should be resolved in 21l

@Nigel should be resolved in 21l

@Yevgeni it looks like you may not have the regular style of Calibri, or Calibri installed. It should be part of Windows.

Hi Richie
Thanks for the answer. You're right. There is no font.

Installed the font.
The launch was perfect !!!
Thank you!!!

This is relatively minor but easily repeatable. On my 8000DLE running Protocol 2, if I power down the radio before stopping Thetis (usually inadvertently), Thetis then hangs, unresponsive, requiring its process to be killed to stop it.

W2PA wrote:This is relatively minor but easily repeatable. On my 8000DLE running Protocol 2, if I power down the radio before stopping Thetis (usually inadvertently), Thetis then hangs, unresponsive, requiring its process to be killed to stop it.

Do you have network watchdog timer (WDT) turned off Chris? network.c has some issues when this is turned off. Mainly due to the fact that it waits for winsock events indefinitely. It does need to be re-worked at some point, but not something I want to get involved with really.

Richie.

ramdor wrote:
Do you have network watchdog timer (WDT) turned off Chris? network.c has some issues when this is turned off. Mainly due to the fact that it waits for winsock events indefinitely. It does need to be re-worked at some point, but not something I want to get involved with really.

Richie.

Richie,

Yes, that was the problem, of course. I don't know how it got set that way - maybe some long forgotten experimenting. Now I'm wondering if there is still a reason for this setting to exist. It's a part of the code I haven't ever dived into.

W2PA wrote:Yes, that was the problem, of course. I don't know how it got set that way - maybe some long forgotten experimenting. Now I'm wondering if there is still a reason for this setting to exist. It's a part of the code I haven't ever dived into.

During the beta in which the watchdog timer was introduced, some users were having big problems with it turned on. So that's why the switch was left in there. That said, it's been a long time since I've heard any mention of trouble with the timer.

73 de W4WMT (Bryan)

When ever clicking or off VAC2 ONLY WHEN RX2 is enabled, for what ever reason it ALWAYS goes to 40 meters no matter what band I am on. As you can imagine, its extremely annoying.

Not sure if this is reproducible for all of you!.

wa2cop wrote:When ever clicking or off VAC2 ONLY WHEN RX2 is enabled, for what ever reason it ALWAYS goes to 40 meters no matter what band I am on. As you can imagine, its extremely annoying.

Not sure if this is reproducible for all of you!.

Can not reproduce this.

wa2cop wrote:When ever clicking or off VAC2 ONLY WHEN RX2 is enabled, for what ever reason it ALWAYS goes to 40 meters no matter what band I am on. As you can imagine, its extremely annoying.

Not sure if this is reproducible for all of you!.

Please attach your database.xml file here.

Thanks, Richie.

Thanks for looking into this!

ramdor wrote:

wa2cop wrote:When ever clicking or off VAC2 ONLY WHEN RX2 is enabled, for what ever reason it ALWAYS goes to 40 meters no matter what band I am on. As you can imagine, its extremely annoying.

Not sure if this is reproducible for all of you!.

Please attach your database.xml file here.

Thanks, Richie.

wa2cop wrote:When ever clicking or off VAC2 ONLY WHEN RX2 is enabled, for what ever reason it ALWAYS goes to 40 meters no matter what band I am on. As you can imagine, its extremely annoying.

Not sure if this is reproducible for all of you!.

ok there is an issue when SD (stereo diversity) is enabled at the same time as VFOSync. If you are using SD keep the VFOSync disabled. I will look at fixing this for next release.

R.

Thanks! The workaround worked!

ramdor wrote:

wa2cop wrote:When ever clicking or off VAC2 ONLY WHEN RX2 is enabled, for what ever reason it ALWAYS goes to 40 meters no matter what band I am on. As you can imagine, its extremely annoying.

Not sure if this is reproducible for all of you!.

ok there is an issue when SD (stereo diversity) is enabled at the same time as VFOSync. If you are using SD keep the VFOSync disabled. I will look at fixing this for next release.

R.

Hi Richie,

today I used cw split (VFO B 1 kHz above VFO A) to call a dx stn and saw that my tx signal appearing spot on the dx stn tx frequency. I used my 2nd radio to check the frequency, but my tx freq was indeed 1 kHz above. Than I saw the frequency scale shifting up and down by 1 kHz with every ptt change.

That is kind of annoying and does not happen with CTUN activated. I am sure that this behaviour came with one the updates.

Please, please make it so that the panadater frequency scale does never change with ptt in split mode and the tx signal appears where I think it should be, and without CTUN!

Thank you!