Apache Labs Community Forum

If I zoom way in so that my receive bandwidth fills most of the panadapter width, the cursor of course changes to the <o> cursor inside the bandwidth shading. This cursor never disappears when I move it within this bandwidth. A clue, perhaps?

@W1JA, Hi John , then it is something else that is causing flickering and the pointer vanishing.

Can you please make me a video, so I can visually see what is happening. A video will show me if you are crossing some things that might be causing the issue.

Thanks, Richie.

ramdor wrote:

vk6cpu wrote: 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.

Thanks Richie
All working as expected in RC3. The release was perfectly timed for the best TEP opening from VK to JA (HL & BA) that I have seen in decades on 6m yesterday.

It was so efficient being able to run two instances of JTDX FT8 on RX1 and WSPR/FT4 on RX2. Prior to this changeing modes/swapping instances resulted in lost time and when you have a good opening thats not good for the nerves

I feel a bit like a mean Oliver Twist asking the Benign Beagle for more ....... But.
From your comments about RX/RX2 VFOA/B nomenclature/confusion etc, I gether you'll be looking at this in the future.
It would be really great to have the option of selecting the subreciever for RX/TX rather than RX2.

What you have done with TCI is great. Many thanks again.

ramdor wrote:@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.

Thank you Richie! Yes it is working fine now.

I do have a question regarding the TCI, I am using LOG4OM logging software and have configured the TCI to synch with Thetis. Changing the mode under Thetis from USB/LSB and vice versa is absolutely synching fine with LOG4OM. However, from LSB/USB to CWL/CWU doesn't do anything. Just remains either in LSB/USB. I am not sure if anyone else is also facing this with TCI.

Thanks, Siddhu VU2YYF

Siddhu wrote: I do have a question regarding the TCI, I am using LOG4OM logging software and have configured the TCI to synch with Thetis. Changing the mode under Thetis from USB/LSB and vice versa is absolutely synching fine with LOG4OM. However, from LSB/USB to CWL/CWU doesn't do anything. Just remains either in LSB/USB. I am not sure if anyone else is also facing this with TCI.

Thanks, Siddhu VU2YYF

Same here Siddhu. I expect Log4om is not matching CWL or CWU to CW. I will add an option to have the output mode changed to CW instead of CWL / CWU.

In other news this will also be rc4, hopefully tomorrow :
Cheers, Richie.

Is anyone else seeing this message on Thetis startup?

might be firewall or might be that port is in use by something else (which is most likely reason)

EA1DAV noticed that 50001 clashed with icom rsba, and anydesk.

Richiie.

Hi Richie

I’ve been looking through some of the filter settings today and noticed this error, I’ve never noticed it before. Just wondering if I’ve got them set right cheers mate.

Thanks Richie,it does not happen on every start up and re starting Thetis fixes it. Only program I have that uses TCI is JTDX and that is not running when this happens. I've checked the windows firewall and Thetis is an allowed App. I'll un install anydesk as a test in case its doing stuff without being run.

ramdor wrote:might be firewall or might be that port is in use by something else (which is most likely reason)

EA1DAV noticed that 50001 clashed with icom rsba, and anydesk.

Richiie.

try...

netstat -o | find "50001"

Richie.

@m0cpy ok.. have woken up now. My last two replies were complete bogus.. lol

You have a different FM buffer size to the other modes, so it will take additional time to rebuild this when you switch into and out of FM from any other mode.

R.

That command (with JTDX running) shows
C:\Users\ei7bm>netstat -o | find "50001"
TCP 127.0.0.1:50001 DESKTOP-3B6ADBP:50734 ESTABLISHED 18484
TCP 127.0.0.1:50734 DESKTOP-3B6ADBP:50001 ESTABLISHED 9948

Tony EI7BMB wrote:That command (with JTDX running) shows
C:\Users\ei7bm>netstat -o | find "50001"
TCP 127.0.0.1:50001 DESKTOP-3B6ADBP:50734 ESTABLISHED 18484
TCP 127.0.0.1:50734 DESKTOP-3B6ADBP:50001 ESTABLISHED 9948

I assume it is running ok atm? hmm.. let me see if i can find the flag to get the exe names

Richie.

ok...

tasklist /fi "pid eq 18484"

Will give you the exe name, where the number matches the number at the end of the line when you run

netstat -o | find "50001"

Yeah running fine ATM, just needed one re start of Thetis. Guess I need to run the commands again next time the error shows up. Thanks so much for the help

C:\Users\ei7bm>tasklist /fi "pid eq 18484"

Image Name PID Session Name Session# Mem Usage
========================= ======== ================ =========== ============
Thetis.exe 18484 Console 1 281,948 K

ramdor wrote:

Tony EI7BMB wrote:That command (with JTDX running) shows
C:\Users\ei7bm>netstat -o | find "50001"
TCP 127.0.0.1:50001 DESKTOP-3B6ADBP:50734 ESTABLISHED 18484
TCP 127.0.0.1:50734 DESKTOP-3B6ADBP:50001 ESTABLISHED 9948

I assume it is running ok atm? hmm.. let me see if i can find the flag to get the exe names

Richie.

Hi Richie,

Sorry for the confusion mate... I was referring to if my buffer size filters are correct as there is exclamation mark at the bottom which I haven't noticed before

Try setting all the buffer sizes to the same value and message should disappear.

m0cpy wrote:Hi Richie,

Sorry for the confusion mate... I was referring to if my buffer size filters are correct as there is exclamation mark at the bottom which I haven't noticed before

ramdor wrote:@W1JA, Hi John , then it is something else that is causing flickering and the pointer vanishing. Can you please make me a video, so I can visually see what is happening. A video will show me if you are crossing some things that might be causing the issue.

I used the recorder in Windows Game Bar (ctrl-G). (I never made a video in Windows before. And ignore the audio; obviously it's not working right.) At the beginning of the 21-second video I move around in the receive bandwidth area to demonstrate that the <o> cursor never disappears. Then I move outside the bandwidth, first to the left, then to the right of the bandwidth. When I stop moving the mouse, the + cursor disappears about half the time.

Except in the recording, the + cursor is black, not white. And the black + never disappears. When I made this recording, the corusor was white and it did its normal disappearing act. The playback is different.

I tried it with the Legacy DX Buffers checkbox checked and unchecked. No difference.

Edit: I'm not allowed to attach a .mp4 file. I'll email it to you.

IS all the downloads disabled ?
cant download any of the updates
br Geir/LA5SJA

geireri@online.no wrote:IS all the downloads disabled ?
cant download any of the updates
br Geir/LA5SJA

https://apache-labs.com/community/viewt ... 410#p18467

take note of the NOTE: at the top of the post

R.

m0cpy wrote:Hi Richie,

Sorry for the confusion mate... I was referring to if my buffer size filters are correct as there is exclamation mark at the bottom which I haven't noticed before

I have the same thing. If I change both values to 64, then Thetis goes haywire when I select FM mode.
I opted to leave it like that, it works.

rc4 will see the following if you have under/overflows with vac.

Left column, is for VAC out (red), right is in (green). Upper row is overflow, lower is underflow. Easy way to see if you audio is going wrong when you are transmitting etc.
Also, you will be able to click on the new info bar to cycle through pages of info (currently only 2), with the second page now showing display RBW (display resolution bandwidth) which is a new feature added by Warren in the new wdsp version.

eta, sometime over the weekend.

R.

Richie,

My windows computer died and I had to reload Winblows 10 and I was on 21k6. Can I get a link to download 21k6?

Thank you.

Mike WA3O

Group,

Someone emailed me a copy of 21k6...

Thank you

73's
Mike WA3O

@WA3O and others

Old versions are not available anymore, as there is no benefit to the community in running them. The latest rc3 build includes a new version of the wdsp dll and other such things. The rc3 version is above in the thread. rc4 will be out sometime this weekend.

Also, consider that the release version via TAPR will no doubt take latest changes based on either rc4 or what comes after that.

By all means, run an old version, but it is sad to read especially after all the effort I have put in, that you would want to run an old version. Especially considering this is entirely a test procedure to get to a build that is ok to release through TAPR. So, that being said I would much prefer if you and everyone used the most recent, and where possible I will try resolve any issues there might be.

//contemplates what can be added to make it irresistible to stay on an old version

Richie.

Hi,

Is this redrawing behavior normal with TCI spots?

https://www.youtube.com/watch?v=tc0jNEZN3DM

It is really anoying...

ea3aqr wrote:Hi,

Is this redrawing behavior normal with TCI spots?

https://www.youtube.com/watch?v=tc0jNEZN3DM

It is really anoying...

hah no, that is not normal !!!! what external software is providing them?

EDIT: increase max number of spots that can be handled. That may solve it. I will look into something to help with this.

Richie.

ramdor wrote:

ea3aqr wrote:Hi,

Is this redrawing behavior normal with TCI spots?

https://www.youtube.com/watch?v=tc0jNEZN3DM

It is really anoying...

hah no, that is not normal !!!! what external software is providing them?

Richie.

Swisslog
https://www.swisslogforwindows.com/

try increasing max number of spots that can be handled to 1000, may solve it. I'll look into possible work around if it does.

R.

where does one set swisslog to send spots via tci Jordi?
EDIT: ok bandmap needs showing for spots to be sent over.. somewhat random

R.