If you select PTT for spacebar and enable RX2, after startup, no ptt but open setup and hit ok - ptt works until you close rx2 and start over with setup form. This is the case with "-autostart" as well.

Describe the bug
When changing modes from SSB to CW VAC1 and VAC2 don't change with the mode. In the CW GUI there is no profile selection box to select the CW profile. I have to change the mode to SSB and then select the CW profile from the profile selection box to get the proper VAC selection.

To Reproduce
Setup a CW transmit profile using VAC1. (for CW Skimmer)
Setup a SSB transmit profile using VAC2. (for USB audio interface)
Set radio in SSB mode in SSB portion of the band. Audio interface works FB.
Change to CW portion of the band. Profile doesn't change to the CW profile. if SSB mode is selected while still in CW portion of the band SSB profile is selected. Have to change profile to CW while in SSB mode in CW portion of band. There are a couple of other work arounds.

Expected behaviour
Would like VAC to change when going from SSB portion of the band to the CW profile. If not possible have the transmit profile box be visible in CW mode so it is easier to the CW profile.

This is also a problem when going from CW to SSB. Mode will remain as CW and have to select SSB mode from the transmit profile box when in SSB portion of the band.

In both CW and SSB there are seperate profiles and the bandstack has been used to memorize parameters. The Bandstack parameters are locked after they are memorized

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):
Win 10

Additional context
73, George
W2GS
[email protected]

When going from one mode to another SSB to CW if I have NR2 select in SSB it no longer selected in CW. Profiles have been previously setup for SSB and CW both in the Band Stack and transmit profiles. I always operate with NR2 turned on and would like it to stay on.

Setup radio in SSB with Proflies and Bandstack saved with NR2 saved on. Do the same for CW. Go from CW to SSB and most of the time NR2 will be turned off.

Expected behaviour
If I save a profile or bandstack frequecny I would like the NR2 setting to be saved in that Profile or Bandstack setting

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):
Win10

Additional context
Thetis has worked great in all modes, contesting and DXing. Best radio/software I have ever used in 50 years of hamming. Many thanks.
73, George
W2GS
[email protected]

Describe the bug

Under certain conditions, including in this example split op's with the VFO-A RX frequency out of band limits, at the cessation of a TX cycle (PTT deasserted) the S-ATT is set to 31dB.

To Reproduce

• Set mode to USB or LSB.
• Activate split.
• Set VFO-A to RX and place the frequency outside of an amateur band (US limit example 7457KHz).
• Set VFO-B to TX and place frequency inside of an amateur band (US limit example 7220KHz).
• Make a transmission. Method does not matter: MOX, PTT and VOX all produce the same results.
• Observe S-ATT change to 31dB from its previous setting.
• Reset S-ATT to desired level.
• Transmit again and observe it change again.

Expected behaviour

After a TX cycle the S-ATT should return to the value set by the operator prior to the TX cycle.

Desktop (please complete the following information):

Win 10 Pro, Thetis 2.9.0.6, firmware 2.1.18, ANAN-8000.

Additional context

There have been reports of improper S-ATT settings after TX cycles under other conditions.

TCI is in its infancy, as such many features are missing, including xit/rit, sensors, audio/iq over the stream, and others

b) I can not increase the band width with the mouse wheel, if the "Low"-value is greater 0. Btw I am using this function in CW-mode starting with a filter width of 400 Hz.

Describe the bug

When transmitting, signal amplitude levels shown on the panadapter in DUP mode are incorrect.

To Reproduce

Consider the following example:

• Two-tone waveform at 1600W total RF power out. 1600W = 62dBm.
• Each individual tone is 6dB below that total RF power level, or 56dBm.
• Coupling factor is 50dB, so rear panel input level for each tone is +6dBm.
• PureSignal drives the attenuator to 19dB, this is exactly as expected for the PS algorithm at that feedback power level.
• Under these conditions the DUP display shows each tone at -20dBm.

Expected behaviour

DUP display should show +6dBm. On receive everything is referenced to the input level at the rear panel connector. During transmit this does not appear to be the case, but it ought to be.

Desktop (please complete the following information):

Win 10 Pro, Thetis 2.9.0.6, firmware 2.1.18, ANAN-8000DLE, PureSignal ON.

Not sure what others think, but I would like the Tune Step setting to be part of the Band Stacking. For example, I use one Band Stack for CW, one for phone, ect. But the Tune Step is independent of this currently, and it would be much more convenient for it to be set per Band Stack.

/Doug

Sometimes the green thumb is not redrawn then user right clicks on the AGC slider. The state changes, but the graphics are not updated on occasions.

If you use increased font size for accessibility reasons or a theme with larger fonts, VFOA/B may be obscured by the menu bar (very old issue)

Describe the bug
Triggered by Tune, Thetis enters a strange xmit-only state when the VFO line on panadapter is outside the band edge but CW offset would put the actual transmitted signal inside.

To Reproduce
Steps to reproduce the behaviour:

1. Start in CWU mode near a lower band edge.
2. Position the VFO cursor below the band edge but the VFO dial display frequency above it, i.e. the CW offset would put a CW signal just inside the band and the dial indicates you're within the band since it takes the CW offset into account. Example: VFO A says 14.0003 and offset is 600Hz but the red VFO line is just below the band edge in the panadapter.
3. Hit Tune (TUN button). An out-of-band warning window pops up.
4. Click OK and now Thetis is in a weird TX-only mode. You can recover normal operation by re-starting Thetis or by cycling the MOX button or doing the same thing by hitting the CW key in Semi mode. There may be other recoveries but I haven't searched for more.

Expected behaviour
The OOB warning properly takes into account the CW offset - i.e. in the above procedure, Tune would cause a carrier on the red-line VFO position, which is OOB, but in CWU it still lets you transmit a CW signal - all is well. But it should not enter this weird transmit-only state after the OOB warning caused by the Tune button (step 3).

Screenshots
A screenshot wouldn't show anything additionally helpful.

Desktop (please complete the following information):

• OS: Windows 10 Pro, version 22H2, build 19045.2364

Additional context
ANAN-8000DLE, dedicated Ethernet connection, static IP addr, Thetis 2.9.0.7 x64 Protocol 2 v2.1.18 MM0LGE pre-release, compiled by me after cloning the current repo.

On a DB update, there are instances reported where data is not being migrated. Such as the bandstack2 overlay check box. Investigate.

Audio from VFO B signals is down >13 dB compared to VFO A in split mode. Problem is independent of Master/RX1 volume, left/right audio pan and MultiRX settings. (This was a also problem with several Flex Radio versions of PowerSDR and SmartSDR)

If you use the MultiRX mode, and want to TX on the MultiRX VFO B frequency, you can, but after you release the PTT the MultiRX mode closes.

In my case, set VFO A to say 3.770, enable MultiRX, set VFOB to say 3.900. You can RX on both frequencies now.

Now change the TX to VFO B using the TX button in the VFO B area at the top. Hit PTT. You are TXing on the correct VFO B frequency, but afterwards the RX from the MultiRX VFO B just turns off and disappears, leaving the RX set to VFO A.

https://apache-labs.com/community/viewtopic.php?f=9&t=4178&p=20155#p20155

Initial investigations and I could not replicate it.

https://apache-labs.com/community/viewtopic.php?f=9&t=4132#p19295

When operating weak signal CW, often with narrow to very narrow passband (50 - 80Hz) I will go to SPECTRUM mode to best center the signal in the passband (using 1Hz step). Also there are times when there's an interfering signal that is slightly off frequency to the DX station. In this case it is extremely useful (WONDERFUL radio/software that this is :) to go to a narrow passband and then tune such that the offending station just falls off the cliff of the passband leaving the DX in the clear - this works marvelously. It would be nice to
A) have a small inset spectrum window to do this or
B) have a mode, maybe PANSPECTRUM where the top is panadapter and the bottom is spectrum.

Is your feature request related to a problem? Please describe.
The Spotting function works great. It would be great to be able to click on a spot in the panadapter and have it output to a logging program.

Describe the solution you'd like
I use DXLabs as my logging program. It would be great if clicking on a spot in the panadapter would output that to DXLabs capture window or DXKeeper. Programs like CW Skimmer, N1MM and others have this capability. It would be a nice feature in Thetis.

Describe alternatives you've considered

Additional context
73, George
W2GS

all sorts of attenuation display offset issues exist for RX1/RX2 if the DDCs are configured to share the same ADC's

Reset of bandstack is annoying when the region/extended is changed.

• tag system default entries as system
• tag user entries as user
• modify DB to take this new flag
• reset only removes system entries leaving user entries available and then re-adds region defaults as system

show XV if an xvtr band is mapped to a band with xvtr checked (through the IF)

https://apache-labs.com/community/viewtopic.php?f=9&t=4132&p=19585#p19576
https://apache-labs.com/community/viewtopic.php?f=9&t=4132&p=19585#p19585

The PureSignal2 option PS-RX/PS-TX causes VAC underflow/overflow (linearity form)

https://apache-labs.com/community/viewtopic.php?f=20&t=4120

Some radios/protocols have a subset of sample rates.

Investigate chkIncludeOtherSampleRates_CheckedChanged and how that feature can be enabled again.

Defaults for the US region need adding

https://apache-labs.com/community/viewtopic.php?f=9&t=4132#p19301
https://apache-labs.com/community/viewtopic.php?f=9&t=4132#p19306

It would be very nice if there were an option to display RXB only.
User case: I have a broadband "magnetic" loop antenna on the second ADC and I my main (TX) antenna is switched between the Andromeda and another rig. I can then monitor any band while using the main antenna on another rig.

While I can still use RXB with two receivers displayed it gets a little cramped on Andromeda. Hence the desire to remove the RXA panafall.

73 de va7qi, ....Erik.

If RX2 is enabled at start up, the RX1 signal strength display locks up, showing -399.9dbm

If you disable RX2, then shutdown Thetis and restart, when you manually enable RX2, all is well with signal strength display.
Bill KC9XG

Sometimes the filter drags in the reverse direction

Rear speaker sockets are sometimes muted until a frequency/mode/band change is made. Always on start-up from a few users that seemingly own 8000's. Is there a firmware correlation?

Copied over from ApacheLabs forums. Add anything new as a comment below. Cheers. Richie.

On the TODO list (in no specific order)

1. pan adaptor blobs become markers, and have management facility and features from spec analysers such as find -3dB either side of marker, next high to the right, next high to the left, delta dBm, etc
2. split up the receivers, starting with display engine, and then moving to the internals of the console (lots of work, probably weeks and weeks if not months)
3. redo all control panels to be movable, and move away from forced spread out structure of UI especially problematic on large displays
4. json or some such output feed for things like streamdecks
5. Spot colours and improvements to the lines, perhaps with blobs etc, overhaul essentially
6. IF view much like SDR console
7. New modern VFO control + skin-able
8. Setup tidy up
9. Drive power link to TX profile option
10. Insert manual notch from autonotch data. Is this data available - need to investigate
11. timer start on first PTT, and align to interval
12. Path Illustrator - someone will have to take that on. Not for me guv.
13. New updated recording system
14. Wideband update
15. DRM filter extension - investigate
16. Customisable stack grids, where filters can be applied to buttons
17. MON on/off for recording playback
18. VFO acceleration, much like the 'icom' solution. Rate over time config and speed jumps or linear?
19. RX2 rx audio into VAC1
20. Cat? macro button panel
21. dragging splitter of panafall left and right will act the same as if dragging the top numbers
22. enable multi RX option for split mode
23. delta sync drag of rx1/rx2 min/max
24. improved grid spacing to make it more readable
25. Copy VFO-A => VFO-B (and B > A, and A <> B) include mode, rx-filter,etc.... enable/disable via setup
26. Count down timers
27. return cw delay to semi break in, remove when qsk, or add two options
28. waterfall palette to use gradient bar so can be configured
29. zoom/pan on gradient control
30. 5 second tune/tone ?
31. freeze display for screenshot
32. rit/xit overlay and mouse drag/tune
33. unlock gain if value entered into gain multi diversity
34. woodpecker tune tone? investigate

Done
20) Calibration Offset store for EXT/INT osc, so that if your ext ref is off you can select the value you stored for that situation.
25) passband SNR calculation (peak power in PB? or using dsp signal power?)
26) auto agc set min of grid, however this causes jumps if step size is set, needs investigation (noise floor comp can control this)
29) PA profiles
30) Drive slider limit (done with right click on drive bar)
38) Midi command to swap vfo wheels
5) Multi-meter 'a better meter'
23) Quick auto split, +/- 5Khz, tx to vfoB, RX left ear, TX (split rx) to right ear
17) FM adjustable RX filters - investigate

Describe the bug
A clear and concise description of what the bug is.
Thetis 2.9.0 22a

Thetis imported my previous database and appeared to work as intended.
However, I soon discovered, if I have DUPE active and I hit the TUNE
button the radio is modulated with TWO TONE. Deactivate DUPE and TUNE
button works as intended.

I reset the database to see if my imported database was causing the above
issue. After reset, I selected ANAN-100D. I then hit the Thetis power
button the radio began keying up and down continuously. If I power down
with the Thetis power button and change the modulation from the default
CW setting to USB, then power up again all is well at power up.

Bill KC9XG

The Cat Command Tester does not display CAT command info. You can test commands successfully, just can't view CAT Command info.
Bill KC9XG

As described by IW7DMH with reference to TCIServer.cs https://community.apache-labs.com/viewtopic.php?f=9&t=4383&p=22227&hilit=sdc#p22227

Fixing this would make SDC http://lw-sdc.com more usable with Thetis.

73 de LB2EG Richard

(edit: Fixed links)

Describe the bug
When XIT is active, going into transmit (MOX) causes the panadapter scale to shift by the XIT value. This occurs on CW and SSB, and probably other modes I didn't test. It occurs regardless of whether CTUN is on or off. The transmitter is operating as it should but the display scale is wrong.

Thanks to Juha, NI2M, for noticing this.

To Reproduce
Steps to reproduce the behavior:

1. Tune to 28.010 in mode CWU, with DUP on, panafall view active, split off, MRx off, RIT off.
2. Zoom in such that individual 1 kHz labels are visible, to easily see the effect
3. In main console, check both check boxes for "Show TX CW Freq" and "Show CW Zero Line
4. Turn on XIT and set its value to 1000 (1kHz)
5. Note the CW frequency line is on 28.010 and the CW Zero Line is on 28.011 (because of XIT), as they should be.
6. Hold key (or paddle) down in Semi mode
7. Transmitted signal appears on the display where it should, but the scale shifts, showing it at 28.012 instead of 28.011
8. Turn on QSK
9. Hit the key and confirm the actual transmitted signal is on 28.011 (this is also confirmed using a separate receiver)

To reproduce on USB, same procedure except:

1. 28.310 in USB
2. Skip this step
3. Skip
4. Click MOX or activate PTT
5. Note that the VFO line now appears on 28.312 instead of 28.311
6. Skip
7. Can confirm signal is actually on 28.311 using external receiver.

Related display scale behavior: If you turn on RIT alone (or with XIT - doesn't matter) with 1kHz setting, the wrong frequency (28.012 - should be 28.011) appears in receive mode, without transmitting.

Expected behavior
Transmitted signal should appear at 28.011 (or 28.311 for the USB example above).

Screenshots
None necessary

Desktop (please complete the following information):

• OS: Windows 10 Pro, version 22H2, build 19045.2364

Additional context
ANAN-8000DLE, dedicated Ethernet connection, static IP addr, Thetis 2.9.0.7 x64 Protocol 2 v2.1.18 MM0LGE pre-release, compiled by me after cloning the current repo.

Note a bug per se - just a change request: When using SPECTRUM change the display such that it is always centered on the passband and the frequency readout is relative ... i.e. 0 at the center and going up , +, and down, - from there. This makes the SPECTRUM view independent of the CW PITCH.

When in expanded mode and with band controls selected, if you select either SWL or VHF+, the band selection at the bottom of the screen disappears.
If you collapse the display and then expand it, the band selection comes back.
It works fine when you select WWV.

https://apache-labs.com/community/viewtopic.php?f=9&t=4132&start=90#p19563

mon & mon volume over vac does not work when vfob TX on a single rx

Newer 7000 MKII radios do not accurately display current draw and voltage. This occurred when Apache Labs made component changes due to part obsolesce or supply chain issues and did not adequately test the hardware to ensure compatibility with Thetis and/or Protocol 2 firmware.

The Andromeda has a programable multi-use rotary encoder. A very useful addition to the list functions for this decoder would be the ability to move the first manual notch filter. Very useful!

73 de va7qi, ....Erik.

A process filtered PerformanceCounter leaks memory over time, and uses a large amount each time NextValue() is called. Tagged as MEMORYLEAK in source.

Richie -- there is a minor nit with the Linearization menu. Whenever I open that menu, it opens fully, as if I have clicked the Advanced button. If you can replicate this then I'd suggest it be recoded to open as just the row of buttons, with the advanced controls only exposed if the Advanced button is clicked. It would be really sexy if it remembered its last state.

Hey Richie

Running 2.9.06 Windows 10 x64
Audio is all VAC here RX and TX and using ASIO for the devices.

When doing a record and playback, SDR Quick Audio follows the volume level seemingly based on the RX1 AF level, at least with VAC audio which is what I run. So the level of the wav file is variable depending on how loud I'm listening at the time.

Upon playback the Wave menu TX level needs to be compensated and if the RX1 level is changed around, that playback gain has to also be compensated.

Is there any way to set a fixed capture level and in turn a fixed playback level to target 0db as a fixed level?

Issue is that a lot of people have crazy levels either low or too high because of the variability, unsure if there is a way to "insert" the record/play at a place where some sort of a 0db reference level can be made?

An "easy way out" may be for the Wave playback TX level to automatically normalize to a 0db target?

Hope all is well with you - de KC2RGW Chris

Width and shift sliders do not work well with mouse wheel

I would like you to consider a change to the CW Auto Mode Switch operation. Right now, you could be in another mode, say LSB, and if you have this enabled and hit the paddles you do indeed switch to CW. But you remain there in CW mode.

I would like the operation to change such that after you send some CW you revert back to the mode you were in. Some of us, when operating phone, like to send some CW to the group we are talking with. But we want to return back to the mode we are in. I know that some other manufactures have this feature, such as Yaesu.

I don't see the value in this option currently without such a change, but perhaps I am missing something.

/Doug

-Puresignal (sometimes) locks off after having used SPLIT (already discussed previously where you were able to see it happen)
-MON is left on sometimes after using SPLIT/CW and then, having turned SPLIT off, going to SSB on that same band
-Possibly eliminate issues related to the use of SPLIT by being sure IF it is inadvertently left on when changing a band that it is the first thing that happens in that band change - check to see if SPLIT is on and if it is turn it off? Perhaps that will circumvent the above issues.

Is your feature request related to a problem? Please describe.
Doesn't fix a problem but enhances panadapter zoom to make it more useful.

Describe the solution you'd like
There are several reasons one might want to zoom-in or zoom-out the display. Today one can only zoom using the zoom slider which zooms in or out centered on the center of the display. This is somewhat useful but could be enhanced to make it much more so.

For me, and I suspect for many, a primary reason for zooming-in is to get more detail around the particular frequency on which I'm operating, or to get a closer look at something elsewhere on the band that has caught my attention within view of the panadapter. This type of zooming-in is often temporary - I want to see some detail then go back to my previous view. The same is true for a temporary zoom-out to briefly see more of the band and then return.

One good way of doing this is to add two features to zooming in Thetis: (1) targeted zooming, i.e. aiming the mouse at something in the display and zoom in (or out) focused on that particular location, and (2) returning to the previous view after doing a targeted zoom.

The targeted zoom (#1) could work much like zooming does today in on-line maps, such as Google Maps. On such a map, you zoom in/out targeted on where you position the mouse, as opposed to the center-oriented zoom provided by the +/- clickable controls. In our case, you'd hover the mouse over a place of interest on the panadapter (or panafall) and zoom in or out focused on that location (which, in our case, is a frequency). The zoom action itself could be via the mouse wheel combined with a shift key (e.g. ctrl or alt).

An alternative to using a shift key would be to repurpose the right-click mode (in which the crosshairs appear) to mean zoom mode instead of its current, rather redundant mode of tuning the VFO.

Zoom reset (#2) could be done in a number of ways. Maybe the most intuitive way would be to remember the zoom level associated with the currently selected band stack entry and offer the user a clickable control to immediately return to that view after zooming. It could also be a different shift-click operation with the mouse.

Describe alternatives you've considered
Additional context
All covered in the above description

Saved memories (via the Memory menu item) are currently only loaded to RXA - even when in RXB mode on Andromeda. It would be very nice to have the selected memory sent to RXB when that receiver is selected.

73 de va7qi, ....Erik.

Describe the bug

This is not a bug per se but perhaps it is best categorized that way.

The problem is that issuing CAT TX commands of the form ZZTX1; or TX; toggle MOX on but do not allow the operator to toggle MOX off from the UI. This situation persists even through a cycle of the "POWER" button in the UI.

This situation is dangerous as it does not allow the operator to easily recover from or override misbehaving rig control software.

To Reproduce
Steps to reproduce the behaviour:

1. Issue one of the above referenced CAT TX commands.
2. Attempt to put the radio back in a receive state by clicking on the MOX button in the UI.
3. Attempt to put the radio back in a receive state by clicking the POWER button and then clicking it again.
4. Note that both of the above actions will not terminate a TX state, it requires the issuance of a CAT RX command, either ZZTX0; or RX;.

Expected behaviour
A CAT instantiated TX state should be able to be manually overridden by using the MOX button in the main UI, or by using the POWER button to put the radio in a reset state.

Describe the bug
ANAN 7000DLE MKII (latest serial number) S-Meter calibration is lost on Thetis close. It looses the calibration and reverts to default as soon as the Thetis is closed. It defaults to show the reset status values (Typically an S-Unit more than what really is)

To Reproduce
Steps to reproduce the behavior:

1. Under Setup > Calibrate
2. Click on Calibrate on selected frequency while injecting a known reference signal level such as -73dBm. (I use an ELECRAFT XG2 RF signal generator)
3. After It successfully completes the calibration routine, the signal meter shows -73dBM (or S-9)
4. See error next time you reboot or restart Thetis. It will revert back to -67dBm (S9+5) while using the same RF signal source.
5. It makes no difference if database was reset to default or newly created.

Expected behavior
The S-Meter on Thetis will revert to default settings: -67dBm (S9+5) using the same reference signal level at the chosen calibration frequency. Just as if RESET was pressed
(I use an ELECRAFT XG2 signal generator on ANAN 7000DLE MKII - latest serial numbers)

Expected Behavior:
The S-Meter on Thetis is expected to keep the calibrated parameters after PC reboot or Thetis restart and to show on the S-meter display the same signal level that it was used for its prior calibration when the reference signal is reapplied to the antenna port with no attenuation present. A typical signal reference of -73dBm (or S-9) is commonly used.

Desktop (please complete the following information):

• OS: [Windows 10 x64]
• Software: Thetis v2.9.0.6 x64 (4/23/22)

Download fresh git repo.
Open Thetis_VS2022.sln
Thetis installer upgrade fails (all other upgrades are OK)
Thetis-Installer\Thetis-Installer.wixproj: The application which this project type is based on was not found. Please try this link for further information: 930c7802-8a8c-48f9-8165-68863bccd9dd
I do have the latest build.386 4.0 WIX toolset installed
But can't quite figure out how to do the dotnet command to try and fix this.
dotnet add PROJECT package WixToolset.UI.wixext --version 4.0.0-preview.1-build.384

When doing SPLIT on CW the TX signal should not shift to the center - it should be over the frequency where TX is. This serves two purposes: the obvious one of showing where I am in the pileup and IF I happen to miss turning SPLIT on, which can happen to us all occasionally, I can immediately tell this fact instead of transmitting and interfering with the DX station. I believe it is correct on SSB (my radio currently off due to storms).