For those, who like me, have had issues with Windows 'messing' with the USB/audio there is a very interesting article that explains whats going on. Its called USB soundcards and is in the Data section of RSGB magazine - Feb 2021. Basically, it explains that every time a USB device is plugged in a 'note' is made This record is added to each time another/same device is plugged in. This can lead devices not being registered correctly in favour of the 'default' devices. Hope this is useful. Regards - Phil (G0DOR)

Since installing 2.3.0 rc3, I no longer see my radio being automatically turned on by WSJT-X - how do I make that happen again? -- 73, Patrick, W6AJR

When my PC turns the screen off (not sleep mode), and then wakes up again, WSJT receives OK. But when I try to transmit, the CAT/PTT stuff works OK, but no audio is sent to the rig. I have to restart WSJT to actually transmit a signal. I just changes PCs, and this didn't happen with my previous PC. Both were running Win10 through a microKeyerIII to a Yaesu FTDX101. This may be more of a PC question... I just don't know where to look... Thanks, Frank W2YK

Hello everyone, After 30 years without a mac - my last and only one was the Mac SE - I took the leap and bought the Mac M1 Mini. I am proficient at running wsjt-x on Windows and Linux. I cannot get Wsjt-x to even run. This is the error messages I get before it crashes. I have run the apple diagnostic program and it found no errors. Help would be appreciated. Ken w6bzy

Hi all, the free plan Groups.io option allows up to 1 Gbyte for files, attachments, and photos in total. The usage Today reached 80% of that limit, mainly because of a few rather selfish individuals who have attached very large images or other files to their posts, and often not helped by others replying and quoting the whole of the original post including the images. In order to avoid automatic deletion of older attachments, or bouncing of all posts with attachments (the two automatic options offered by Groups.io), I have taken the arbitrary decision to delete all message attachments contributing more than 1 Mbyte per post. This took me a long time as each post has to be edited to achieve that, and I would rather no one has to do that again too often. In order to try and control the plan storage usage, for now, I have set all posts to be moderated if they have attachments and will ask moderators to reject posts with more than 1 Mbyte of attachments with a message to the poster that they consider re-posting with smaller attachments. Moderating all posts with attachments is a lot to ask of group moderators so I would rather that option is only used temporarily to ensure regular posters understand the need to keep attachment sizes to a reasonable size. This action has only reduced plan storage usage from 80% to 35%, so it it cannot be a permanent fix, and users must try and help here. Please do not post screen captures of whole desktops, particularly from Mac systems, although the same applies for all systems with high resolution monitors. Screen capture tools allow portions or single windows to be captured. If you really feel that large files or images are needed to augment your posts then please do so by posting links where the content can be downloaded rather than using up storage allocation shared by all group members. Do not post photographs as attachments, so many users who post photos seem to do so without any attempt to resize the images to reasonable file sizes. Even a smartphone camera these days creates images of many Mbytes size. This is not an attempt to stop posters using images to explain or reply to issues, as we all know a picture can be worth a thousand words, but please be considerate and remember that we are sharing a free to use resource here. Apologies to those that have their old posts arbitrarily edited to remove large attachments, I am sure that some may contain useful information for the group, but there is just not time to review each post in detail and make such decisions. 73 Bill G4WJS.

This document was originally posted by Bill, G4WJS as part of a long thread. Assuming you are running on MS Windows and have installed WSJT-X, this explains how to set Tx audio levels correctly: The issue you may have with Windows WSJT-X Tx audio levels is due to the "Pwr" slider in WSJT-X no longer being linked to the Windows mixer control for the Tx audio device. This means that you must set the mixer slider manually, this should be a one-time operation. Setting the mixer control is a two step operation. Firstly you must set the mixer control to maximum. The mixer control is only visible when transmitting so use the "Tune" button in WSJT-X. It is advisable to reduce the "Pwr" slider in WSJT-X to minimum while doing this to limit the output power, or do this part with the rig switched off. The mixer slider will look something like this: Once the mixer is set to maximum the second step is very important. You must now adjust the master level for your Tx audio device to 0dB. The level control for that is in the audio playback device properties for the Tx audio device which looks like this: If your slider scale is not in decibels then right-click the slider and select decibels. Your audio device may not have gain, in which case 0 dB will be fully to the right. Some devices do have gain, *in those cases it is critical that the gain be reduced to 0 dB* otherwise a severely distorted transmit signal will be produced. Once you have completed this one time setup you can increase the "Pwr" slider back to maximum for full level audio output from WSJT-X. I recommend rechecking your Tx levels elsewhere, e.g. data modulation level adjustments on your rig, audio interface level controls etc. to ensure that you are not over-driving the audio input of your rig. A good method is to use a 1,500 Hz Tx audio offset "Tune" tone with the " ;Pwr" slider at maximum and your rig at maximum power into a good dummy load. With that arrangement reducing the interface or rig's data modulation input level until little or no ALC is indicated on the rig is about right and should give around 90% of the maximum output of your rig. If your interface and rig do not have any Tx audio level controls then it is OK to use the operating system audio device master level control as shown above to reduce the audio level to a correct amount *so long as the critical 0 dB level is never exceeded*. Once this setup is complete you can make routine Tx power adjustments using power control on the rig or the "Pwr" slider in WSJT-X. Bill G4WJS. It is also advisable to prevent windows USB interfaces from being place into power save mode. The instructions are here. Don't forget to include HDMI interface as they also utilize audio. http://www.dxlabsuite.com/dxlabwiki/PreventUSBPortPowerDown

I am building a Raspberry Pi 4 to serve as a portable data terminal. For more information, see KM4ACK’s YouTube video and his pi-build script on GitHub (www.github.com/km4ack/pi-build). The rig is an Elecraft KX3. The interface is a Timewave Navigator. The Navigator provides multiple FTDI USB/serial ports, one of which provides a CAT interface to the rig. Just to eliminate the Navigator as the problem, I also tried the standard Elecraft KXUSB interface cable, which also provides a FDTI USB serial port. (the Navigator and KXUSB were not connected at the same time). With the interface cable plugged in to the RPi, I did dmesg and saw that the serial ports were correctly associated with the FTDI drivers. I did the “usermod -a -G dialout pi” to add my local user (pi) to the dialout group for access to the serial ports. FLRig is able to access the CAT interface and control the KX3. I exit FLRig and launch WSJT-X. Under rig setup, I specify the correct serial port (/dev/ttyUSB0) and baud rate. I click the Test CAT button and it doesn’t change color – neither red nor green. Sometimes, this disables the Test PTT button, but when it doesn’t toggling the Test PTT button toggles Tx on the KX3. Back on the WSJT-X main screen, the frequency mirrors the KX3’s frequency, changes to frequency on the radio change in WSJT-X and vice versa, but the “fake it” split mode doesn’t work. This is with WSJT-X 2.1.10 which was built from source code. The RPi 4 is running Raspian Buster which has been updated with the latest changes. For comparison, I installed WSJT-X 2.1.12 from the .deb file on the website onto a desktop computer running Linux Mint 19. I saw the same problems. Again FLRig worked fine. I did various things such as changing the owner of the serial ports to the local user and changing the group of the serial ports to the local user – no change. I started WSJT-X using sudo and the Test CAT button worked and turned green, so I think there may still be a permission issue. Thanks for any suggestions, 73, Mark, N8ME

Below is part of the welcome message which is sent to all new members. It is largely unchanged since Bill and I visited it a couple of years ago. I have made minor changes for clarification. The last two "rules" are new. I'm not sure how the penultimate rule was not included but the last one is prevent further discourteous behavior. Members attempting to inject WSJTX forks into the discussion is a particular problem and one member had two messages rejected within a month. Please desist from mentioning WSJT forks. Discussions involving 73, grids, and other operating procedures continue to bring out the worst in members as many have very strong views which are very different from others. Please remember that others are entitled to different opinions. I am aware that some members use email addresses which are not monitored but you should be aware that you will receive the occasional important email. Members should be aware that even if you set "no email" you will still receive occasional email from the group, such as returned messages or messages from a moderator. The moderators do not expect rudeness in return. 73 Roger GW4HZA moderator Group "rules" No personal insults, be polite when expressing opinions that differ from others or expressing disapproval. No crude language or abbreviations. No items "for sale" "items free". Test messages may only be sent with the hashtag #TestMessage No expression of political or religious viewpoints, keep the messages focused on the software. This is a worldwide group made of many different cultures, faiths, values, and ethnic groups. Please exhibit tolerance, respect and kindness. Threads that become expansive or begin to form a circular argument may be moderated or "locked" by moderators after a period of time so that they do not dominate the group. No promoting the use of the WSJTX software in a manner that violates the author's copyright terms. No reference to derivatives or forks of WSJTX software. Moderating staff exercise exclusive discretion over all posted content, Please report any message that you feel moderating staff may have missed and should be reviewed for possible inappropriate content. Please do not respond directly. Members who, in the opinion of the moderators, have ignored these "rules" make have their posting privileges removed until they have confirmed they have re-read these rules. Discussion of electrical and license regulation matters MUST include the administration you are referring to. Good practice under one administration may be dangerous or illegal or both in another. Personal messages must not be re-posted without permission of the originator

Hello all, I just replaced my station computer with another. Both are Dells. I have tried to make the new computer's configuration as close to the old as possible. The reason for the change was to switch to a computer with a solid state drive rather than a rotating disc. Both are running Windows 10-64 Pro ver 21H2. I have been running WSJT-X v2.6.1 on the old computer since its release with no issues. My transceiver is a Kenwood TS-890S. I installed WSJT-X on the new computer and then copied the contents of the old PC's WSJT-X folder to the new PC, launch WSJT-X and I select FT8. Everything is working perfectly on the new PC (including CAT, decoding received signals, tuning and transmitting) EXCEPT for the signal strength bar graph at the lower left corner of the window. The bar graph is "stuck" at about 15 dB and is red. There is no setting on the new PC that I can find that changes this. When I simply move the USB cable (I don't touch anything else), connecting the TS-890S to the old PC, everything is perfect indicating the issue is with the new PC. All of the sound settings (that I can find) that affect line level input are set to 100% (in both computers). Has anyone seen a symptom like? I hope to get is solved before 3Y0J goes live! Thank you for any help that you can offer ... -- 73, Jim W7EED