w4mmp / mscc-pw Goto Github PK

Describe the bug
Fan never seems to come on though so far have only operated on CW

**MSCC-PW current release

Desktop (please complete the following information):

• OS: Windows 10

Describe the bug
MSCC-PW will allow transmitting CW on frequencies outside the FCC allocated US amateur radio bands. Please review the possible transmit frequency ranges to prevent possible illegal transmissions.

To Reproduce
Steps to reproduce the behavior:

1. Attach a transmitter dummy load and RF output meter to the transceiver. Adjust the HAM band to 160m and vary the MAIN tab frequency across the 1790 kHz to 1800 kHz range.
2. Select CW mode and momentarily select PTT and note RF output exists on 1792 through 1800 kHz frequencies.
3. Perform a second test while adjusting the MAIN tab frequency across the 2000 to 2025 kHz range.
4. Select CW mode and momentarily select PTT and note RF output exists on 2000 through 2022 kHz frequencies.
5. Note that US Amateur Radio Band frequency allocations for 160 meters are 1800 to 2000 kHz per chart at https://www.arrl.org/files/file/Regulatory/Band%20Chart/Band%20Chart%208_5%20X%2011%20Color.pdf
6. A similar condition exists below and above the 80 meter HAM band frequency allocation.
7. Note that the small red square that appears between the 10 kHz and 1 kHz digits in the VFO window of the MAIN tab in MSCC-PW does NOT indicate that transmit output is enabled or disabled. The red square does appear when frequencies outside the allocated ham band are tuned however the radio still produces transmit RF output until the tuning is adjusted significantly MORE outside the ham band range.
8. Please check all ham bands for these or similar symptoms.

Expected behavior
Transmit RF output should be disabled when selected frequency is NOT within US Amateur Radio frequency allocation.

I expected the red square in the VFO window on the main tab to indicate when a non-ham frequency was tuned AND the transmit function was disabled.

MSCC-PW release date (please complete the following information):
MSCC-PW-Install-20221124.exe

Desktop (please complete the following information):

• OS: Windows 10

Additional context
These symptoms exist without BETA TEST or TRANSVERTER boxes checked on the SYSTEM tab. I understand the TRANSVERTER function will allow transmit above 29.7 MHz up to 30 MHz for use with transverters.

Thank you!

Installed latest release of MSCC 20230307 on my Ultimus only to find that the first dit of a transmission was dropped. Sending at 25 wpm my W9BF call would come back as M9BR. Changing Lag Time made no difference using reception of local's receiver.

The DEFAULT FILTERS on the Rx/Tx tab of MSCC-PW and the User Filter settings for VFO B on the Main tab are not stored upon program exit and restored upon program re-start.

To duplicate symptoms:

1. Run MSCC-PW and click Tx/Rx tab. Select DEFAULT FILTERS LOW to 300Hz, TX to 2.4KHz, HIGH to 2.4KHz and CW to 400Hz.
2. Return to MAIN tab and click EXT and then click YES to stop MSCC-PW.
3. Run MSCC-PW and click Tx/Rx tab. Observe the DEFAULT FILTERS TX has changed to 2.7KHz and CW has changed to 200Hz.

To duplicate symptoms for VFO B:

1. Run MSCC-PW, click System, click Beta Test & click OK to approve operating in Beta Test mode so that VFO B functions are available.
2. Set VFO A and VFO B User Filter settings on MAIN tab just below the frequency display to CW BANDWIDTH 400Hz, LO CUT filter to 300Hz and HI CUT filter to 2.4Khz.
3. Change ham band by clicking a different BAND SELECTION button on Main tab. Observe that the USER Filter settings revert to CW BANDWIDTH 200Hz, LO CUT to 75Hz and HI CUT to 300Hz.
4. The above conditions occur even if I set the DEFAULT and USER FILTER settings for both VFO A and VFO B on each of the ten bands - - Once I exit MSCC-PW and re-start it, my desired settings of CW BANDWIDTH 400Hz, LO CUT filter to 300Hz and HI CUT filter to 2.4Khz are lost particularly for VFO B.

The two symptoms above are likely related however I've been unable to understand or correct this response.

MSCC-PW version in use 01/02/2023, MS-sdr 2022.1202, SDRcore-recv 2022.1205, SDRcore-trans 2022.1109 and TRANSCEIVER 122.1.

Windows 10 Pro Version 22H2 with latest Windows updates in use.

Thank you for your diligence in correcting issues and adding features.
Bob, AF5Z

Describe the bug
The on-screen label for the 300Hz and 500Hz LOW CUT FILTER settings shows 300kHZ and 500kHZ.

To Reproduce
Steps to reproduce the behavior:

1. Run MSCC-PW and identify the SET LOW CUT FILTER button just below the 100kHZ digit of the frequency display.
2. Click on the SET LOW CUT FILTER button multiple times to move through all available choices and observe the displayed settings.
3. Note that the 75Hz, 100Hz and 200Hz settings are shown correctly as Hz.
4. Note that the settings show 300kHz and 500kHz when chosen. This should be 300Hz and 500Hz.

Expected behavior
I expected the available LOW CUT FILTER frequency settings to be in the lower range of human hearing. The software provides a range of 75Hz to 500Hz which is good but the label for 300Hz and 500Hz is incorrect. The function of the filters sounds correct.

MSCC-PW release date (please complete the following information):
MSCC 09/01/2022

Desktop (please complete the following information):

• OS: Windows 10 Home

Describe the bug
Unable to ADD or DELETE 12m band FAVORITES. I attempted to add a single favorite on each band 20m, 17m,, 15m, 12m and 10m for the NCDXF International Beacon System (see https://www.ncdxf.org/beacon/beaconlocations.html). I was able to create a favorite named INTL BCN on bands 20m, 17m, 15m and 10m however attempts to create a 12m favorite failed as described below..

To Reproduce
Steps to reproduce the behavior:

1. Tune to a 12m frequency 24.930 MHz. Click on Favs tab in MSCC-PW.
2. Click on Enter Name and type in desired name (I used INTL BCN). Click ADD. Observe that newly created favorite appears in the 10m band favorites area and .NET error occurs. See screen grab below.
3. I tried multiple times to prevent the error but any 12m favorites I create appear in 10m area.
4. Additionally I'm unable to DELETE these 12m frequencies from the 10m favorites area. This action also creates a .NET error (see screen grab).

Expected behavior
I expected to be able to ADD and DELETE favorites in each band as I did on bands other than 12m.

Screenshots

*MSCC-PW release date (please complete the following information):
MSCC 09/02/2022

Desktop (please complete the following information):

• OS: Windows 10 Home

Additional context
I note that the 'b12_favs.ini' file in folder \MSCC-PW\backup is an empty file (0 bytes) while similiarly named files for other bands contain data. This is also true for that file in folder \MSCC-PW\init-files.local\share\mscc and also in path \MSCC-PW\utilities\backup. Perhaps this contributes to this failure.

mirror-and-delay

already is ok !?? But....

Sorry, i have never used GetHub befor today. It is my first contribution.

First and important: Thanks a lot for your mainpower and help, Ron.

I've had the hardware Proficio in operation for weeks. At the beginning with the software "MSCC" under the files "Proficio". Starting problem with driver. Fast and successful help through "MultusSDR". With the appearance of the variant "MSCC-PW" this app is installed.

Working with the "MSCC" app is basically possible,... but 2 phenomena show up here with me.

There is a signal e.g. 3766 kc (CW) from a Hf-Generator at the HF input at "Proficio" Level -60dBm.
appears in the spectrum. e.g. not only the line at 3766 kc, but also another line at about 3752 kc.
If the receiving frequency is changed by the Proficio, the frequency lines in the spectrum change as a mirror image.

This phenomenon also occurs with real received signals. Maybe correctable with RX I/Q ?? But don't know how.
Description is still missing in the manual.

Initial situation: reception 80m band, mode: LSB Commands for transmission and frequency change in the band
are carried out immediately (less than 0.5 seconds). Then... Frequency change to 20m band. Mode: CW: 5 seconds transmission. All subsequent commands such as frequency change (band) as well as changes in small steps or send commands are executed with a delay of up to 4 seconds.

If the "MSCC.PW" app is closed, the main window goes out immediately, but not the two sub-windows of the spectrum and waterfall. The voice information is still audible, even if the main window has already been deleted, but the two sub-windows "Spectrum" and "Waterfall" are still active. Only after about 10 -15 seconds does the "MSCC" report with error messages. Summary: All operations are executed successfully, but always with a delay of 4-5 seconds. Extremely difficult operation !!

Thanks for any help. 73 de HB9SIU, John

System-INFO.txt

mscc.log
MSCC-Spectrum.exe.log
MSCC-Waterfall.exe.log
mscc-pw.exe.log

The size of the windows for the console, spectrum and waterfall should be adjustable to enhance resolution. Bandwidth adjustment of the spectrum/waterfall is a desirable feature.

W4MNp de HB9SIU John.

Hello Ron,
I apologize for addressing my problem again
report to you.

In your mail of 8/21/2022
Re: [w4mmp/MSCC-PW] mirror and delay (Issue #3)
you ask me questions

I tried this question with a number of
Files (images of spectra) and the file: "mirrror" to be answered at GitHub.

So you can see for yourself where I put my pictures and the file on gitHub
Attached is an image copy from my GitHub account.

Question: Does this information appear in the expected place in GitHub?

Do NOT take my message as leverage.
I'm just not sure yet if I can send my reports to the
right place, publish in the right way on github.

My message regarding "mirror" has not changed here for me.

The phenomenon of insufficient image rejection is like me
in the meantime researched and read on the net, a well-known one
and not an easy problem to solve.
Very small errors in magnitude and/or phase
in the processing of the two signals I and Q lead to insufficient
suppression of the image frequency.

Because the phenomenon of insufficient image frequency suppression
under the "MSCC" software, I did not notice it for a short time
installed and activated this older software.
The phenomenon also occurs here.
I didn't notice it at the time.

Now here with me again "MSC-PW" active with the latest firmware.

In the meantime it is clear to me that with the tools (Tab Freq Cal)
"RX I/Q calibration" and (Tab S/F) "TX I/Q calibration" error in signal processing
of I and Q are trying to correct, so that
the image frequency suppression is sufficient for both transmission and reception.

In the older "MSCC Operators Guide" (06/14/20 it is on page 15 ff
described.
These procedures for the new MSCC-PW software are still in the new operating manual.

I tried following the old manual that described
steps to be carried out with the new software as well.
Unfortunately without success.
The sliders for minimizing IQ errors show from -200 to +200 in one step
(increment =1) NO influence on the image display (spectrum)

In the old manual, on page 18 under "Note 3" it says -43 dB or better
spoken. Halleluia.

Question : Am I the only user complaining about this phenomenon

====================================================

Image below: Snipping from GitHub Does content and location make sense?

?

Hi Ron,

It was the intention of the software designer at MSCC to
that the socket "KEY", only exactly in the mode "CW" and at
active software key "PTT" a CW carrier at the RF output
is generated by Proficio.
In all other operating modes or inactive
"PTT" shows the socket "KEY-Input" no reaction.

topic 1
Inquiry , request for modification of the functioning of the "Key" socket

• In the MSCC application, in the operating modes USB, LSB (optional AM), with an active signal on "KEY" input,
  the software button "PTT" is activated. The TX is booted up.
  In "CW" mode, the "KEY" input shows normal (unchanged) behavior.

Reason and intention:

The TX can be activated via KEY input by a hardware switch.
eg. PTT on the microphone, foot switch, VOX control or "CQ speech machine" in contests.

This option should be selectable -active or passive- by querying the program "Initialite.BAT".

topic 2

• Idea and thoughts about fashion "CW":

When the button is first activated (keyer), the TX is activated when the button is pressed, but NO CW carrier is sent out.

When the button is released, the TX remains active for 1-3 seconds with no CW sinal output.
After the above time has elapsed, TX off and RX active.
If the key is pressed a second time within the above time period, the CW carrier is transmitted in the rhythm of the key play, corresponding to the key play of the CW modulated HF carrier.
If the key play is interrupted for 2-n seconds, automatic return from TX to RX
Operation.

best 73 de HB9SIU, John

Describe the bug
in the IQBD settings in MSCC-PW, some of the bands don't display correctly, but the frequency does...see below I clicked band to get 60m...it changed the freq to 5330500, but still says 80m

To Reproduce
Steps to reproduce the behavior:

1. Go to P/M/IQ
2. Click on the box showing current band (e.g. 80m)
3. check top left box witgh frequency displayed.
4. it appears that the first time you clikc on 80m, it still displays 80m, but the frequency changes to an appropriate one for 60m

Expected behavior
each click of the band, should change the text showing the next lowest band, and the frequency should change as well

Screenshots

MSCC-PW release date (please complete the following information):
version 20221227

Desktop (please complete the following information):

• OS: Windows 10

Additional context
Add any other context about the problem here.

Have been using MSCC-PW 20220908 with no startup issues save the "unhandled exception" error on clicking the CW/AUDIO tab. Dismissing the error message resulted in non-problematic function of MSCC-PW ongoing.

However, it has been pointed out that the first "dit" of a cw transmission is fore-shortened, if heard at all. My call of W9BF is oft repeated to me as M9BF. Most operators are too polite to correct or do not respond. But, on air tests with locals sending me recordings show I have a real problem with this issue. QRS operation has no beneficial effect.

Hoping that this can be fixed. I know Flex had this issue with PowerSDR.

Bob W9BF

Describe the bug
The ENHANCED setting of pallette color for the waterfall in the S/W tab is not properly saved and restored when MSCC-PW is exited and then re-started.

To Reproduce
Steps to reproduce the behavior:

1. Run MSCC-PW, click on S/W and then click Enhanced in the waterfall pallette window. Observe the waterfall responds correctly with high-contrast multi-color display of signals.
2. Click S/W to close the spectrum/waterfall settings window. Observe the enhanced color still appears in the waterfall window.
3. Again click S/W to view the spectrum/waterfall settings window. Note that the enhanced color pallette setting for the waterfall is shown to be selected. Note that the waterfall properly shows the enhanced pallette.
4. Click S/W on the MAIN display to close the spectrum/waterfall settings window. Note that the enhanced color mode still displays in the waterfall screen.
5. Click EXT on the MAIN screen and click Yes to stop MSCC-PW and return to the Windows desktop.
6. Run MSCC-PW and observe the waterfall is properly displayed with the enhanced color pallette.
7. Click S/W on the MAIN display to view the spectrum/waterfall settings window. Note that the waterfall display immediately changes back to the default red/yellow color pallette. Additionally on the S/W settings display Red/Yell waterfall color pallette is shown to be selected.
   Expected behavior
   I expected all settings that are in use on the S/W settings display screen to be saved and then restored after MSCC-PW is exited and re-started. I did not expect any settings to be changed when I click S/W on the Main screen. In the numbered paragraphs above - I believe steps 1. through 6. are all normal, expected behavior. Only step 7. above shows unexpected behavior.

MSCC-PW release date (please complete the following information):
MSCC-PW: 09/07/2022

Desktop (please complete the following information):

• OS: Windows 10 Home

Additional context
Add any other context about the problem here.

Describe the bug
The AM Carrier Level setting on the Rx/Tx tab is not saved and restored during MSCC-PW exit/stop and re-start.

To Reproduce
Steps to reproduce the behavior:

1. Run MSCC-PW. Click Rx/Tx tab and observe AM Carrier Level setting is centered at 50%.
2. Click on AM Carrier Level adjustment and change setting to a different setting (25% used in this example).
3. Click on Main tab and then Rx/Tx tab and observe AM Carrier Level adjustment shows chosen previous setting (25% in this example).
4. Click on Main tab and then click on EXT and choose STOP to close MSCC-PW.
5. Run MSCC-PW. Click Rx/Tx tab and observe AM Carrier Level setting is centered at 50%.

Expected behavior
I expected whatever setting I choose for AM Carrier Level would be saved and restored after MSCC-PW was exited/stopped and then re-started.

MSCC-PW release date (please complete the following information):
MSCC 09/07/2022

Desktop (please complete the following information):

• OS: Windows 10 Home

Describe the bug
Changing the PITCH frequency to something other than the default 600Hz has no effect on the pitch of received signals and any changes made are not persistent i.e. when MSCC-PW is restarted, the desired setting is lost and the default 600Hz is shown.

To Reproduce
Steps to reproduce the behavior:

1. Click on CW/AUDIO tab in MSCC-PW console window.
2. Click on the up or down arrow to the right of '600Hz' that appears in the CW Control area of the screen below PITCH. Alternate PITCH frequecies of 400Hz, 500Hz, 700Hz or 800Hz can be selected. I note that the UP and DOWN arrows change the setting the opposite direction than expected, i.e. clicking the UP arrow makes the selection move DOWN in PITCH frequency. Leave the setting on anything other than the default of 600Hz.
3. Click on the MAIN tab to return to the console window. Click on EXT to stop the MSCC-PW program and close all windows.
4. Run MSCC-PW again by double-clicking the icon on the desktop to start the program. Again select CW/AUDIO tab and observe that the previously chosen PITCH frequency in the CW Controls area of the display again reflects 600HZ instead of the previously preferred PITCH frequency choice.

Expected behavior
I can not detect any change in the behavior of the receiver regardless of the chosen PITCH frequency. I expected an 800Hz PITCH when used with 200Hz CW filter bandwidth to allow me to hear audio frequencies from 700Hz to 900Hz as I slowly tune across a signal. I also tried to select a PITCH frequency of 400Hz which in my opinion should allow me to hear audio pitch frequencies of 300Hz to 500Hz when a 200Hz CW filter bandwidth is in use. With either a 400Hz or a 800Hz PITCH setting I hear the same audio pitch frequencies as I tune across a signal with a narrow 200Hz bandwidth CW filter in use.

**MSCC-PW release date **
MSCC-PW was installed with "MSCC-PW-Install-20220829.exe". The SYSTEM tab shows MSCC 08-29-2022.

Desktop (please complete the following information):

• OS: Windows 10 Home Version 21H2 OS Build 19044.1889 with all current windows updates.

Additional context
The PITCH setting also impacts a CW operators ability to correctly SPOT the transceiver so that transmit and receiver frequencies match. Often an operator will set their CW sidetone audio frequency (pitch) to their preference to act as a reference guide to help correctly tune in a signal so that their transmitted frequency will match the frequency of the received signal.

Previous version dated 8-18 had flawless semi-break cw. Lost that function with new update. Also, long-standing issue of meter function (only A and T buttons turn red and only S units displayed on meter).

Thanks, Bob W9BF

ziplog.zip

Ron,

I verified this morning that 20220820 still would not do semi-bread cw. So I reinstalled 20220818 without deleting the firmware files. TUNE would work as always but again semi-break didn't. I shut down and restarted and got an initialization failure message so per the error suggestion I'm attach the logs zip file for a suggestion on how to proceed.

I could always delete everything and start over but that recalibration procedure is something I'd like to avoid.

Many thanks for assistance.
Bob W9BF
ziplog.zip

From: HB9SIU e-mail: [email protected]

Hi Bob, Ron and all

About 1 year ago I bought a Proficio and installed the necessary app "MSCC-PW" (MSCC-WINDOWS_Install-20230224.exe) under "Win 10 pro".

After some initial difficulties, operation was possible.
Operation under GSDR was also OK.

After some experimentation with my PC and a careless operation on the operating system, much of the MSCC and GSDR installation was missing.
Despite intensive work on the PC, I can no longer put both apps "MSCC" and "GSDR" into operation.

1. The two "USB-Multus-Drivers" are installed. V 1.2.7.3 . Visible in Device Manager.

After double-clicking on the MSCC icon, the error message shown in Figure 1 appears.
This error message makes sense because the folders listed in the error message are not available.

The ZIP file that can be created with the app (?? sorry) is empty.
(Zip file is created but without content)

Any idea?

The "GSDR" app gets stuck during the installatiion in the "Initialize Genesis Radio Communication" phase. Stuck app can't with task manager
to be deleted.
Reboot necessary.

Thank you for any idea and help
best regards John

Apparently doesn't seem to find comm port
A clear and concise description of what the bug is.

Expected behavior
When I boot MSCC-PW I told to send in the error report file so I'm attaching that file as I have no idea what the problem actually is. The additional problem is that I have no idea where this logfile is. When I looked for it in the MSCC-PW folder I don't see any such thing.

Rick, W2JAZ

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

MSCC-PW release date (please complete the following information):
[e.q. 20220818]

Desktop (please complete the following information):

• OS: [e.g. Windows 10]

Additional context
Add any other context about the problem here.

I was using a MSCC-PW version that was the latest available before AF5Z's bugs were fixed. I uploaded the 20220903 and found rapid onset latency of spectrum freq changes. In addition when I ran 25-30 wpm cw what appears to be a buffer overload caused failure to revert from tx to rx.

I erased all files/folders and started with a clean install of 0903. Ran FreqCal and QRPCal on 4 bands. No problems with original initialization prior to calibrations. Attempted to exit. Console disappeared but spectrum and waterfall did not. Used Task Manager to delete. Turned off/restarted Ultimus. Got error message in .jpg attached. Also attaching individual log files.

I knew I should have left well enough alone!.... I wish I had the earlier .exe that worked to reinstall.

Mni tks,
Bob W9BF

mscc.log
ms-sdr.log
sdrcore-recv.log
sdrcore-trans.log
spectrum.log
waterfall.log

On occasion I have started MSCC-PW before the Ultimus is powered. The result has been loss of calibration settings. The Restore function under the System tab did not restore the calibrations.

Describe the bug
The little square box to the right of the entered(desired frequency) frequency is missing so manual calibration will not work.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

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

MSCC-PW release date (please complete the following information):
[e.q. 20220906]

Desktop (please complete the following information):

• OS: [e.g. Windows 10]

Additional context
Add any other context about the problem here.

Waterfall and Spectrum are covered (underneath) when the main window is moved.
A clear and concise description of what the bug is.

When moving the main window, the waterfall and spectrum move with it, but at times if other windows are present where the main window is moved to, the waterfall and spectrum fall are covered (go underneath other windows).

Expected behavior
The waterfall and spectrum should stay on top of other windows.

Screenshots

Desktop (please complete the following information):

• Windows 10
• 20220818

When restoring MSCC-PW from a minimized state, the outline box randomly disappears from the Waterfall or Spectrum.
Work around: repetitively click on the MSCC-PW tool bar icon until both the Waterfall and Spectrum have the outline box.

Describe the bug
Rego band switching does not work unless you have MFC or Meter attached. Works great when I connected the MFC and re-ran mscc-pw-cfg.

I have been using the Ultimus for Amplifier testing which has it's own band switching jack but was wanting to try out the Proficio using the Rego Band switching without having to connect everything else up.

I suppose most folks with a Rego would have at least an MFC so my situation might be a rare setup;)
Stew
N8VET

MSCC-PW release date (please complete the following information):
20220903

Desktop (please complete the following information):

• OS: Win 8 It works :)

Describe the bug
Numerous errors reported and install failed. New firmware was first installed in Proficio which went fine. I never got the screen described in the manual that should occur when activating the shortcut to run MSCCPW the first time. I'll attach screen shots of the first errors encountered. I believe I fixed the audio issue reported earlier by changing the default port to the internal computer sound card.

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior
A clear and concise description of what you expected to happen.

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

MSCC-PW release date (please complete the following information):
[e.q. 20220818]

Desktop (please complete the following information):

• OS: Windows 10

Additional context
Add any other context about the problem here.

*Describe the bug
The receiver audio is distorted in AM mode when the Low Cut filter setting is greater than 100Hz.

To Reproduce
Steps to reproduce the behavior:

1. Start MSCC-PW, select AM mode and tune in a strong broadcast station (9.980Mhz or a WWV frequency with good reception).
2. Click on the Low Cut Filter settings and listen to the received audio while each available setting is in use.
3. Note that the received audio is not properly demodulated/detected when the Low Cut filter in use is 200Hz, 300Hz or 500Hz.

Expected behavior
I expected the receiver audio to remain undistorted regardless of what Low Cut Audio filter is in use.

MSCC-PW release date (please complete the following information):
MSCC: 09/07/2022

Desktop (please complete the following information):

• OS: Windows 10 Home

Additional context
Note that the Low Cut filter settings are working properly as far as restricting the low-frequency (bass) range of receiver audio in both AM, LSB and USB modes. Even on a AM broadcast signal, listening with either LSB or USB receiver mode allows the use of all available Low Cut Filter settings with minimal audio distortion. I suspect that the algotithms used for Low Cut audio filtering are removing the carrier signal when 200Hz or greater is selected thereby causing distortion of the received audio in AM mode ONLY.

I installed the 10/14 release. Initially, I had no issues other than restoring my calibration settings from a backup file did not work.

I later experienced issues when restarting. I would get several incomplete loadings of MSSC GUI. After several retries the program would eventually load and the initial screen showing "30.000 000 Khz" and USB would revert to the last band and mode I used and all would be coordinated. After prolonged use I sometimes experienced latency in mouse click responses. Stop and restart would clear that up.

On the second day of using 10/14 MSCC-PW I could not get the GUI to respond. Spectrum and waterfall loaded with sound and signals showing but the GUI did not fully load. I could not produces a ziplog to send as a result. I did attach a .jpg of the error message.

My thanks for fixing the first dropped dit. Works fine when it works...

Bob W9BF

MSCC-PW release date (please complete the following information): 20221014
[e.q. 20220818]

Desktop (please complete the following information):

• OS: [e.g. Windows 10]

Additional context
Add any other context about the problem here.

Using the Beta feature to engage VFO B function has an issue when using a mouse to change frequency. A change in frequency using a mouse produces a change in audio reflecting the change, but the console frequency digits do not.

In Beta mode VFO A does change the digital frequency display when the mouse is used.

I installed the 11/16 .exe and ran MSCC-PW until I got latency and immediately created a backup and ziplog which is attached. When I tried to EXT, the console disappeared but rx remained as did the spectrum and waterfall. A GUI error message came up saying no communication with Console and programmed fully closed.
ziplog.zip

On continued use for making cw contacts I have experienced latency in changing frequency lasting a few seconds. Exiting and restart restored normal operation.