Apache Labs Community Forum

Mike wrote:Hi Rich

"Unfortunately I don't agree with the change 'add: RX1 + RX2 mute button now mutes audio over VAC'.
Using the MUT button to turn off the FT8 noise in the Powerspeakers while WSJT continued to run was a big advantage.
Maybe it's just me, but for me it's a step backwards to have to push the master volume slider to get rid of the annoying sounds because I don't have another volume control within reach Is it possible to change this behaviour via a switch in the setup?"

I agree with Thomas

Mike G8ALS

Yep, will add option to exclude vacs from mutes. Probably be an update later tonight or tomorrow.

R.

Hi Ritchie,

I think I found a litte Bug: If I go to Setup, Display, RX1/RX2 and select in Spectrum Grid Step 1, I see 2 db in the Spectrum, will say the steps
are doubled.
(Panafall selected) the middle Line between Spectrum and Waterfall is centerd by right Mouseclick.
If I grab the Line and bring it a little bit down, the correct Step-Size is shown on the Spec-Display.
If centered again i see again 2 db.
Display 3840x2160 Pix, Thetis is running here with 3185x1988 Pixel, but with another Monitor with 1920x1080 it is the same

Just Cosmetic??

Also many thanks again for your hard work!

73 Erwin

Richie,
Just viewed your video, all looks great, Thanks very much for the OC control section!

73’s
Joe
WD5Y

DO2ZA Erwin wrote:Hi Ritchie,

I think I found a litte Bug: If I go to Setup, Display, RX1/RX2 and select in Spectrum Grid Step 1, I see 2 db in the Spectrum, will say the steps
are doubled.
(Panafall selected) the middle Line between Spectrum and Waterfall is centerd by right Mouseclick.
If I grab the Line and bring it a little bit down, the correct Step-Size is shown on the Spec-Display.
If centered again i see again 2 db.
Display 3840x2160 Pix, Thetis is running here with 3185x1988 Pixel, but with another Monitor with 1920x1080 it is the same

Just Cosmetic??

Also many thanks again for your hard work!

73 Erwin

yes, has always been like that, when top half of panafall < half height, then every other is shown. It needs re-working, to work out how many numbers can actually fit in the screen area at a given font size. On the list, but, seemingly not making much headway through it tbh.

R.

This is going to be an issue Ernst, unless you can think of a way around it.

The midi knob values being used range from 0-127. The min/max has a range of +-200dBm. 400dBm / 128 = 3.125, which is why it steps in what looks like 3 db. The value being assigned to gridmin/max is actually (midi knob value - 63 ) * 3.125. It is not acting like an increment step, but as an actual value.

Richie.

ramdor wrote:

DO2ZA Erwin wrote:Hi Ritchie,

I think I found a litte Bug: If I go to Setup, Display, RX1/RX2 and select in Spectrum Grid Step 1, I see 2 db in the Spectrum, will say the steps
are doubled.
(Panafall selected) the middle Line between Spectrum and Waterfall is centerd by right Mouseclick.
If I grab the Line and bring it a little bit down, the correct Step-Size is shown on the Spec-Display.
If centered again i see again 2 db.
Display 3840x2160 Pix, Thetis is running here with 3185x1988 Pixel, but with another Monitor with 1920x1080 it is the same

Just Cosmetic??

Also many thanks again for your hard work!

73 Erwin

yes, has always been like that, when top half of panafall < half height, then every other is shown. It needs re-working, to work out how many numbers can actually fit in the screen area at a given font size. On the list, but, seemingly not making much headway through it tbh.

R.

Yes, no Problem. I will use the workaround and place the Mid Line a bit down.

Thanks an 73 Erwin

DO2ZA Erwin wrote:
Yes, no Problem. I will use the workaround and place the Mid Line a bit down.

Thanks an 73 Erwin

exactly what I do Erwin

R.

ramdor wrote:The midi knob values being used range from 0-127. The min/max has a range of +-200dBm. 400dBm / 128 = 3.125, which is why it steps in what looks like 3 db. The value being assigned to gridmin/max is actually (midi knob value - 63 ) * 3.125. It is not acting like an increment step, but as an actual value.

It could be changed to a wheel type control instead of knob type control. However that poses it's own set of issue for those who do not have a lot of wheels type controls available on their MIDI controller.

However, perhaps a better approach is to limit the range over which changes are possible to a more realistic range. This is similar to the color gradient issue. While it's nice that the code allows such a comprehensive range of values, the actual ranges over which these values might be changed are actually quite a bit smaller.

73,

Scott

UPDATED to 21j2

You can now prevent the vacs from muting.

R.

21j2
add: options to include VACs when MUTE is enabled, for both vac1 and vac2 (Setup->Audio->VAC1/2->[Mute will mute VAC] )
change: removed the 1db midi waterfall step option

Hi Richie,

Just tested xPA. Works ok, nice implementation!

But please disable chkExternalPA during transmit !
Using this button during transmission will lead to dangerous hot switching the PA.

73 Walter

w-u-2-o wrote:

ramdor wrote:The midi knob values being used range from 0-127. The min/max has a range of +-200dBm. 400dBm / 128 = 3.125, which is why it steps in what looks like 3 db. The value being assigned to gridmin/max is actually (midi knob value - 63 ) * 3.125. It is not acting like an increment step, but as an actual value.

It could be changed to a wheel type control instead of knob type control. However that poses it's own set of issue for those who do not have a lot of wheels type controls available on their MIDI controller.

However, perhaps a better approach is to limit the range over which changes are possible to a more realistic range. This is similar to the color gradient issue. While it's nice that the code allows such a comprehensive range of values, the actual ranges over which these values might be changed are actually quite a bit smaller.

73,

Scott

Limit range - 100% agree.
I just played with the values. This should give enough space up/down:
low level:
-72
-200

high level:
+28
-100

Not a high priority, because it currently works "as designed"

73 Ernst

DL2XY wrote:Hi Richie,

Just tested xPA. Works ok, nice implementation!

But please disable chkExternalPA during transmit !
Using this button during transmission will lead to dangerous hot switching the PA.

73 Walter

and disable every clickable tx pin in the OC section when TX/TUN/2TON?

I can change it so that it can only be turned off during a transmission if that is what people want, and disable the entire OC grid when transmitting I guess. Also add an option to allow it (which would not be default) in the event that someone knows what they are doing

R.

The advanced VAC settings are reset to defaults on 21j & 21j2 after restart

ramdor wrote:

DL2XY wrote:Hi Richie,

Just tested xPA. Works ok, nice implementation!

But please disable chkExternalPA during transmit !
Using this button during transmission will lead to dangerous hot switching the PA.

73 Walter

and disable every clickable tx pin in the OC section when TX/TUN/2TON?

I can change it so that it can only be turned off during a transmission if that is what people want, and disable the entire OC grid when transmitting I guess. Also add an option to allow it (which would not be default) in the event that someone knows what they are doing

R.

Turning the PA-PTT off during transmission ist the most dangerous situation. It wears out the TX/RX relays by arcing and stresses the LD-MOS/Valves by seeing indefinitely SWR for a short period of time, maybe under full power. Turning it on should only be a risk to the tranceiver, but at 100W how knows ?

The option to allow seems to be a good compromise (use it on your own risk ). Maybe you can include some of the other tx-blocked controls on the way. I was annoyed of several times for myself...

greets Walter

ramdor wrote:
add: xPA button appears on main console if you have any OC TX pin set as an externalPA control in OC control. This button acts as a master control for any pin assigned as an externalPA pin. When the button is off the pin will always be 0.

What do we need to rename this button to so it displays properly?

NC3Z wrote:

ramdor wrote:
add: xPA button appears on main console if you have any OC TX pin set as an externalPA control in OC control. This button acts as a master control for any pin assigned as an externalPA pin. When the button is off the pin will always be 0.

What do we need to rename this button to so it displays properly?

Details are in post1

button name 'chkExternalPA' for skin makers

also included in my buttons that are linked in post #1, and you can also find out using the option Setup->Tests->[Show Control Debug]

R.

Thanks Ritchie, I swear that I did not see that Button name in post 1 when I review the changes.

And thanks for the reminder on that hint to use the Debug to find the name.

>> You can now prevent the vacs from muting.

Great! Thank you Richie

just a heads up, the saving of advanced audio is dead as a dodo in 21j/21j2 . I have resolved it, but working on something else tonight so will attempt to get fixes out tomorrow.

R.

My vac audio has runaway overflows/underflows now on startup in 21J . Previously it was solid. Anyone seeing any issues ?

VAC is stable here with 21j
73 Ernst

Vielen dank Ernst, I will try J2 now

Richie,

As time permits, please have a look at OC Control. Here's a bug I'm seeing:

1) Go to OC Control Menu
2) Engage "Ext Control"
3) Check any box. For example, OC-7 40m Tx and 40m Rx
4) Disengage "Ext Control"
5) Press CTUN

With "Ext Control" disengaged, the OC outputs become active upon pressing CTUN. I've seen other GUI buttons do the same but most noticeably CTUN. Thanks!

Paul, W9AC

w9ac wrote:Richie,

As time permits, please have a look at OC Control. Here's a bug I'm seeing:

1) Go to OC Control Menu
2) Engage "Ext Control"
3) Check any box. For example, OC-7 40m Tx and 40m Rx
4) Disengage "Ext Control"
5) Press CTUN

With "Ext Control" disengaged, the OC outputs become active upon pressing CTUN. I've seen other GUI buttons do the same but most noticeably CTUN. Thanks!

Paul, W9AC

fixed in 21k already, but thanks Will probably be released sometime this evening (uk time)

R.

thanks for the errorlog.txt files. No more needed.

R.

ramdor wrote:Request.

For those that are able, could you check the following file

C:\Users\<user>\AppData\Roaming\OpenHPSDR\Thetis-x64\ErrorLog.txt

for the following :

Index was outside the bounds of the array.

If found, could you email me the txt file.

Thanks, R.

Sent to your email!

I am tempted to move over to version scheme 2.8.11.X. This will result in DB updates each time, which :

a) will iron out any issues with the DB importer
b) potentially clean up DB's that might need it

Perhaps after the 21k (which will be released shortly).

R.

UPDATE 21k

Quick update with some fixes/changes and some experimental noise floor goodies

Cheers, Richie.

PS: not doing anything more this weekend. If something is broken, let me know, and use older version

21k
fix: penny prevented from setting OC pins if [Ext Control] is disabled
add: xPA button can not be switched on during transmission if [allow hot switching] is turned off in OC control setup
add: noise floor is now estimated in pandapter/panafall views. This can be shown as a dotted line (red) on both RX1 and RX2. Can be shown/hidden with option in Setup->Display->RX1/2
add: auto agc options added to AGC/ALC setup tab. This is experimental and relies on panadapter noise floor calcs
change: ocTX pins disable preventing adjustment during transmission if [allow hot switching] is turned off in OC control setup
change: peak blobs show snr (peak against noise floor) in brackets instead of index number if noise floor is shown
change: change to DirectX draw surface resizing. This will now happen before the next frame due to be rendered.

DL2XY wrote: Turning the PA-PTT off during transmission ist the most dangerous situation. It wears out the TX/RX relays by arcing and stresses the LD-MOS/Valves by seeing indefinitely SWR for a short period of time, maybe under full power. Turning it on should only be a risk to the tranceiver, but at 100W how knows ?

The option to allow seems to be a good compromise (use it on your own risk ). Maybe you can include some of the other tx-blocked controls on the way. I was annoyed of several times for myself...

greets Walter

after 21k, i will stop it being turned off, unless [hot switch] is turned on. In 21k it will not permit you turn it back on if in TX, but it does let it turn off.

R.

This auto AGC is very nice, would be great to have a button under the AGC gain control to enable auto AGC.