Apache Labs Community Forum

EA1DAV wrote:May be I am wrong, but this measuremet is dB and not dBm.

Agree with this. Please change to dB.

[Not sure what PBNP is.

That is "passband noise power". It is a real-time estimate of passband noise power based on the power measured in the panadapter RBW (resolution bandwidth) and as displayed by the noise line. This power is scaled/normalized to a 1Hz bandwidth and shown as NPSD--noise power spectral density. That noise power is again scaled/normalized to the passband bandwidth to obtain PBNP.

While PNBP is technically only an estimate, it's pretty accurate. You can adjust it further by going to a quiet part of the band, switching the S-meter to show dBm (Settings > Display > General), then going to Settings > General > Options > Options-2 and adjusting Noise Floor Shift. It shouldn't be more than a couple of dB off.

With PNBP being estimated, that gets you a real-time PBSNR: passband signal-to-noise ratio. SNR is, arguably, a much more useful metric when judging signal power and quality. Not the norm in the CW/phone realm yet, but very familiar to the digi mode folks.

If your PBSNR reading is not updating often enough for you, its update rate, and the update rate of all the rest of the values on the InfoBar (the strip just below the spectral display) is controlled by Setup > Display > General: Refresh Rates CPU Meter. I have mine set to 250ms and that seems to work quite well. If you want to report SNR in S-units, just take the PBSNR value and divide by 6 in your head

These new metrics are wonderful additions, thank you Richie!

73,

Scott

w-u-2-o wrote:If you want to report SNR in S-units, just take the PBSNR value and divide by 6 in your head

or use the option to do it for you, again in options 2

still trying to find this atten bug in the spaghetti

ramdor wrote:@Dick - KA5KKT

1) reboot
2) uninstall
3) check folders
C:\Program Files\OpenHPSDR\Thetis
or
C:\Program Files (x86)\OpenHPSDR\Thetis
have no lingering dlls
4) reinstall
5) run up thetis and leave it start

If it is stuck again, make sure there are no popup windows behind the splash screen, by hovering over Thetis taskbar icon to see if any other windows are there

if nothing and still stuck, check task manager for Thetis.exe. If in list end task

check for Errorlog.txt in C:\Users\<user>\AppData\Roaming\OpenHPSDR\Thetis-x64 or C:\Users\Richie\AppData\Roaming\OpenHPSDR\Thetis

Richie.

Hi Richie,

I had tried as you suggested a time or two before my OP. After your reply, I tried again. It worked...up to the point I imported my latest Settings Database. At that point a restart of Thetis yielded the same as outlined previously. I cleaned it all up again, reinstalled and on this occasion imported a bit earlier database. All seems to be working fine now. I must assume the later Settings Database had some sort of corruption in it.

Thank you kindly for keeping me after it,
Dick - KA5KKT

KA5KKT wrote:
Hi Richie,

I had tried as you suggested a time or two before my OP. After your reply, I tried again. It worked...up to the point I imported my latest Settings Database. At that point a restart of Thetis yielded the same as outlined previously. I cleaned it all up again, reinstalled and on this occasion imported a bit earlier database. All seems to be working fine now. I must assume the later Settings Database had some sort of corruption in it.

Thank you kindly for keeping me after it,
Dick - KA5KKT

can you email the db that goes wrong? email over on qrz, cheers.

ramdor wrote:

w-u-2-o wrote:If you want to report SNR in S-units, just take the PBSNR value and divide by 6 in your head

or use the option to do it for you, again in options 2

Ha! I was not quite yet on the latest beta. But I am now

On that note, playing with the new "Adjust Min to Noise Floor" setting, as you know at lower zoom settings (large panadapter bandwidths) there can be a significant tilt or variation in the average noise floor. In the spirit of Yet Another Option, would it be possible to get an offset adjustment on this setting so that there could be some leeway for this? I think most people would be OK with a little taller "grass" growing at the bottom of the panadapter such that small signals didn't go missing in other places--thanks!

w-u-2-o wrote:.
.
I think most people would be OK with a little taller "grass" growing at the bottom of the panadapter such that small signals didn't go missing in other places--thanks!

I have the same mindset, right now I do it manually by vertically dragging the spectrum display so as to just show a little grass at the bottom.

Mark

Hi Richie,

After installing rev 4 Thetis does not seem to connect to the radio properly. No firmware version is shown and the radio does not seem to be alive. The frequency windows and power button light up.

I was previously using the latest release.

73 de va7qi, ....Erik.

va7qi wrote:Hi Richie,

After installing rev 4 Thetis does not seem to connect to the radio properly. No firmware version is shown and the radio does not seem to be alive. The frequency windows and power button light up.

I was previously using the latest release.

73 de va7qi, ....Erik.

perhaps didn't uninstall the old version? Uninstall, check the install folder for any old dlls (C:\Program Files\OpenHPSDR\Thetis or C:\Program Files (x86)\OpenHPSDR\Thetis), and re-install.

I may give up on this WIX installer for these repeated updates to an existing install.

ramdor wrote:can you send me your db? enjoy the tasting

Done! Sent to qrz.com

DL8LAQ wrote:

ramdor wrote:can you send me your db? enjoy the tasting

Done! Sent to -----

will take a look later this evening, still working through the att problem. Not found the cause yet.

DL8LAQ wrote:

ramdor wrote:can you send me your db? enjoy the tasting

Done! Sent to -------

the reason I tell people to get my email from qrz is that it is somewhat hidden behind a login process

I could post it to public forum here, but I don't.

Thanks for that

Uninstall/re-install worked. TNX de va7qi, ....Erik.

ramdor wrote:

DL8LAQ wrote:

ramdor wrote:can you send me your db? enjoy the tasting

Done! Sent to -------

the reason I tell people to get my email from qrz is that it is somewhat hidden behind a login process

I could post it to public forum here, but I don't.

Thanks for that

Correction done!

Richie,

I think this was stated as been notice not sure, I install the new beta test and I notice that the ATT which I always keep in -20db , it was on 0 as default and after engaging it back to -20db like always , the receiver got way too quiet, even max out the RF gain , is way too low

I went to 80Meters and is even worst than the higher bands, I'm force to keep the 0, or -10db in the lower bands and the RF gain max out to be able to hear well, I still can hear but is so low is weird.

Albert
N3YV
73'

yes, there are a couple of issues that I am in the middle of looking at.

eta.. a couple of hours

ok, that took far too long. When the code takes different paths depending if the attenuation string is -50dB or -50db you know that it is going to be a struggle. Hopefully that will sort out that attenuation problem. It seems to be working ok on my 7000.

Anyway, please try 2.9.0.4 and like before, uninstall if you are running 2.9.0.4 or 2.9.0 rev4, before re-installing.

https://github.com/ramdor/Thetis-2.9.0/ ... .9.0.4-pre

add: offset to the noise floor GridMin option
fix: rx2 GridMin's will only be updated if RX2 is in use

ramdor wrote:ok, that took far too long. When the code takes different paths depending if the attenuation string is -50dB or -50db you know that it is going to be a struggle. Hopefully that will sort out that attenuation problem. It seems to be working ok on my 7000.

Anyway, please try 2.9.0.4 and like before, uninstall if you are running 2.9.0.4 or 2.9.0 rev4, before re-installing.

https://github.com/ramdor/Thetis-2.9.0/ ... .9.0.4-pre

add: offset to the noise floor GridMin option
fix: rx2 GridMin's will only be updated if RX2 is in use

The ATT bug using ADC0 for RX1 and RX2 seems to be fixed.

Thank you, Richie! Good night...

Richie--would it please be possible to increment the "x" in 2.9.0.x? And to show the entire version number in the title bar? Configuration management is becoming difficult without this.

Thanks,

Scott

w-u-2-o wrote:Richie--would it please be possible to increment the "x" in 2.9.0.x? And to show the entire version number in the title bar? Configuration management is becoming difficult without this.

Thanks,

Scott

I cant include the the changing number in the true version number on the left easily, otherwise a database update will happen every new revision. If we want to change the dB version, then it would become 2.9.1. I have put the 4 from 2.9.0.4 on the end of rev, so rev4. However, as it is a pre-release (as per the tag in github) there may be many .4's before a full release of .4.

I will have a think about it, and probably recode the version detection for dB update.

Ouch! Yes, it would be better if the fourth digit did not kick off a DB reset, while the third one did. That would work fine.

ramdor wrote:ok, that took far too long. When the code takes different paths depending if the attenuation string is -50dB or -50db you know that it is going to be a struggle. Hopefully that will sort out that attenuation problem. It seems to be working ok on my 7000.

Anyway, please try 2.9.0.4 and like before, uninstall if you are running 2.9.0.4 or 2.9.0 rev4, before re-installing.

https://github.com/ramdor/Thetis-2.9.0/ ... .9.0.4-pre

add: offset to the noise floor GridMin option
fix: rx2 GridMin's will only be updated if RX2 is in use

Richie, I click that link for the try out 4-pre and it takes me no where

???

Al
73'

ULTIMAX wrote:

ramdor wrote:ok, that took far too long. When the code takes different paths depending if the attenuation string is -50dB or -50db you know that it is going to be a struggle. Hopefully that will sort out that attenuation problem. It seems to be working ok on my 7000.

Anyway, please try 2.9.0.4 and like before, uninstall if you are running 2.9.0.4 or 2.9.0 rev4, before re-installing.

https://github.com/ramdor/Thetis-2.9.0/ ... .9.0.4-pre

add: offset to the noise floor GridMin option
fix: rx2 GridMin's will only be updated if RX2 is in use

Richie, I click that link for the try out 4-pre and it takes me no where

???

Al
73'

ahah, wrong link... https://github.com/ramdor/Thetis-2.9.0/ ... .9.0.4-pre

ramdor wrote: I will have a think about it, and probably recode the version detection for dB update.

What about a scheme where the 4th segment (2.9.0.x) increments during a string of beta releases. But then, when it goes to the TAPR GitHub repo for release, the 4th segment is dropped and we increment the 3rd segment (e.g. 2.9.1)?

73, Bryan W4WMT

That is what we are doing as we do not show the revision number in the title bar.

2.9.0 was the original release
2.9.0.1 can overwrite 2.9.0
2.9.0.4 can overwrite 2.9.0.1

however, when I am continually working through issues in 2.9.0.4 as it is 'pre-release' then an update will not overwrite 2.9.0.4 automagically.

I do not really want to create potentially hundreds of incrementing revisions. There will be a message eventually, and post 1 will be updated with 2.9.0.4, and perhaps TAPR at the same time.

ramdor wrote:That is what we are doing as we do not show the revision number in the title bar.

2.9.0 was the original release
2.9.0.1 can overwrite 2.9.0
2.9.0.4 can overwrite 2.9.0.1

Right, but what I was thinking is, e.g. last week when 2.9.0.3 went up to github.com/tapr for "official" maintenance release, the 3rd segment would increment to 2.9.1. Then you could start off with subsequent beta drops as 2.9.1.x. FWIW (which is probably nothing )

73!

@everyone,

If you are using 2.9.0.4 (rev4) (pre-release), please let me know what radio model you are using with it, and the protocol.

Cheers.

8000 & P2

7000, P2
Win 10 i9-10900K 32Gb RAM NVIDEA RTX2060

Jeff NJ2US

7000 black case, P2

7000DLE MKII P2- v2.1.18