Date   

locked No audio input selection available

Jay Lijoi
 

Good morning,

I have wsjtx installed on my raspberry PI 4. Everything seems to work, however I get an two errors at startup:

"Error in sound output Requested input audio format is not supported on device"
"Error in sound input Requested input audio format is not supported on device"

In the audio settings I select  in the soundcard output Plughw:CARD=b1.DEV=0 and the output error is resolved.

The problem is that the Soundcard Intput does not present any options when clicked on. It's blank.

Please help,
Jay wb2qqj


locked Re: logging to HRD issue

Jay - AE1J
 

I have the same configuration: QSO Forwarding from WSTY-X to HRD logger. Working perfectly here. I've seen no problems with QSOs being missed.

Jay - AE1J


locked Re: FT8 receiving DX the long way

Lawrence Godek
 

You bet.
Larry/w0ogh 

-------- Original message --------
From: Ray <nacray10@...>
Date: 7/11/20 5:24 AM (GMT-07:00)
To: main@WSJTX.groups.io
Subject: [WSJTX] FT8 receiving DX the long way

Not about WSJT-X directly. I have noticed that occasionally a station, say in Japan for instance, seems to be traveling the long way (20 meters FT8). I'm in EM21, so I mean the path may be to my East rather than West. Antenna is hexbeam, usually pointed 30-40 degrees.

Can this be? Anyone else see this?


locked Re: Loss of sound output in 2.2.2

R SCHMAHL
 

Thanks Roger.
Ron K2PSD

On Jul 11, 2020, at 8:50 AM, groups@thebluecastle.org.uk wrote:

On 11/07/2020 00:55, R SCHMAHL wrote:
The other day using ver 2.2.2 my power output was only 5 watts. A little trouble shooting revealed that the system level control was only about 20%. I did not put it at that level. I had just come off a Zoom session. I suspect Zoom lowered the speaker output but did not put it back to normal when you close the AP. Ver 2.2.2 was working just fine before the Zoom meeting. If this is going to be the case perhaps the WSJTX AP should set the system level to max or some other fixed level on start-up.
Ron K2PSD
Ron

Zoom has automatic volume controls which can be deselected.

Roger
G4HZA


locked Re: FT8 receiving DX the long way

Bill Somerville
 

On 11/07/2020 13:24, Ray wrote:
Not about WSJT-X directly. I have noticed that occasionally a station, say in Japan for instance, seems to be traveling the long way (20 meters FT8). I'm in EM21, so I mean the path may be to my East rather than West. Antenna is hexbeam, usually pointed 30-40 degrees.

Can this be? Anyone else see this?
Hi Ray,

nothing unusual about occasional long path openings, particularly during the summer months with stations in the same hemisphere. The paths near the poles are quite reliable at the moment due to the very low solar activity. Look on a Great Circle map for you location (an application that plots Great Circle paths on other map projections is equally good) that shows the terminator between night and day and look for all daylight paths to interesting places. Those could open on bands just below the F2 MUF, which is most likely 20m, again due to the very low Solar activity in this Sun Spot minimum.

73
Bill
G4WJS.


locked Re: FT8 receiving DX the long way

Ronnie Hull
 

I work long path on 20M and 17M a LOT! And good thing too or my rotator would really be getting a workout!!

W5SUM EM32CJ

On Jul 11, 2020, at 7:24 AM, Ray <nacray10@gmail.com> wrote:

Not about WSJT-X directly. I have noticed that occasionally a station, say in Japan for instance, seems to be traveling the long way (20 meters FT8). I'm in EM21, so I mean the path may be to my East rather than West. Antenna is hexbeam, usually pointed 30-40 degrees.

Can this be? Anyone else see this?


locked Re: FT8 Operating Frequency

Ted
 

Another possibility, I just recently had an issue and had a local ham do some testing with me. He was seeing me on different Freqs every time I transmitted. After some experimentation we discovered, I using HRD to control the IC-7300 had a problem where HRD sometimes put radio in USB-D, and other times put the radio in USB. When transmitting in USB, my microphone was open and changed my tx freq all over the place. After correcting the program, my tx freq was very stable. 

All the above comments are probably correct but there may be other reasons why an FT8 tx freq isn’t as stable as it should be. 

Let me apologize to each and every ham that I may have caused qrm to without knowing I was doing it. Problem is fixed and is now
 history. 

Ted W4YJC

On Fri, Jul 10, 2020 at 01:07 Jim Shorney <jshorney@...> wrote:

Pick any random station on PSK Reporter with lots of report blobs and they will be all over the place in frequency, sometimes even on the wrong band or no band. This is a problem at the receivers. The digital equivalent of the guys in tho old curmudgeon's net arguing about who's digital readout is correct (mine of course, all you other guys are wrong!). I consider PSKR a non-calibrated frequency reference. It can get you in the ballpark and that is about the best you can hope for.

73

-Jim
NU0C

On Thu, 9 Jul 2020 19:51:22 -0700
"Jim Brown" <k9yc@...> wrote:

> There seems to be a fundamental misunderstanding about how WSJT modes
> like FT8 are transmitted. They are NOT on the dial frequency, they are
> on the dial frequency PLUS the audio frequency. For example, if the
> audio frequency is 1500 Hz, the signal is at 14075.5 kHz. If the audio
> frequency is 1600 Hz, the signal is at 14075.6 kHz. And so on.
>
> WSJT modes are transmitted as upper sideband modulation, and the
> computer generates the modulated tone stream. If, for example, you were
> to listen to the FT8 window in CW mode with a relatively narrow IF, you
> would hear multiple modulated tone streams as you tuned across the
> "window." Each signal occupies a small part of the "window," which is
> really the width of a sideband TX filter.
>
> 73, Jim K9YC
>
> On 7/9/2020 1:43 PM, Kai-KE4PT wrote:
> > Hi Michael,
> > Those differences may be due to the various stations, including yours,
> > being slightly off frequencies, perhaps due to local oscillator (LO)
> > errors or drift (yours too), or the operators set the dial frequency off
> > (like for the 14.077.269). This has NO effect on the decoding, as long
> > as the short term stability of your LO is okay.
> > Kai, KE4PT
> >
> > On 7/9/2020 15:04, Michael WA7SKG wrote: 
> >> I would have expected 14.075.175, but I see everything all over like
> >> 14.075.169, 14.077.269, 14.075.172, 14.075.126, etc. 
> >
> >
> >
> >   
>


--
Ted Wirick  
zebra30@...


locked Re: Loss of sound output in 2.2.2

Roger
 

On 11/07/2020 00:55, R SCHMAHL wrote:
The other day using ver 2.2.2 my power output was only 5 watts. A little trouble shooting revealed that the system level control was only about 20%. I did not put it at that level. I had just come off a Zoom session. I suspect Zoom lowered the speaker output but did not put it back to normal when you close the AP. Ver 2.2.2 was working just fine before the Zoom meeting. If this is going to be the case perhaps the WSJTX AP should set the system level to max or some other fixed level on start-up.
Ron K2PSD
Ron

Zoom has automatic volume controls which can be deselected.

Roger
G4HZA


locked Re: logging to HRD issue

Loren McCullough - WA3WZR
 

I am not using JTAlert.  This is WSJTX using QSO forwarding to HRDLog (latest v6).  I have been doing it for years, but now it only seems to occasionally forward the QSOs.

73, Loren WA3WZR


locked Re: Frequency error IC 706MK2

OZ9AU Allan
 

Hi Bill

Thanks for your answer. V2.2.2. worked fine, especialy the fast decode.

73
Allan OZ9AU

Den 11. jul. 2020 kl. 14.06 skrev Bill Somerville <g4wjs@classdesign.com>:

On 11/07/2020 00:23, OZ9AU Allan wrote:

Hi
I update wsjt-x to v2.2.2 from v2.1.2. All worked fine until I changed frequency to 144.174 MHz in FT8. The display on the radio shows 44.174, missing the 1.

I tried delete the post in “Frequencies” and retype the frequency (144.174.000). I checked CAT settings. But the problem is the same.

Reinstalled v2.1.2 and all is OK again. Anyone else discovered this?

Radio Icom 706MK2, Win 10, USB CAT with FTDI FT232 chip.

73 Allan, OZ9AU
Hi Allan,

thanks for the issue report, it is a known issue with the version of Hamlib used in WSJT-X v2.2.x. It has been fixed for the next release of WSJT-X.

73
Bill
G4WJS.


locked Re: Frequency error IC 706MK2

Joe Subich, W4TV
 

With v 2.2.2 (or probably hamlib <again>), there is a problem
moving across any 100 MHz "barrier."

If the IC-706mkIIg is operating below 100 MHz and one selects
a frequency/band above 100MHz, the rig will go to a frequency
below 100 MHz (missing the first digit, i.e., 144.170 -> 44.174
or 432.065 -> 32.065).

If one is operating on two meters and selects a frequency on
432, the rig will go to 1xx MHz (e.g. 432.065 -> 132.065).

If one is operating on 432 and selects a frequency on 144, the
rig will go to 4xx MHz (e.g. 144.170 -> 444.170).

If one is operating on 432 and selects a frequency on HF/6M,
the rig will go to 4xx MHz (e.g. 14.074 -> 414.074)

The issue is not resent with 2.1.2 (presumably the version of
hamlib included therein).

73,

... Joe, W4TV

On 2020-07-10 7:23 PM, OZ9AU Allan wrote:
Hi
I update wsjt-x to v2.2.2 from v2.1.2. All worked fine until I changed frequency to 144.174 MHz in FT8. The display on the radio shows 44.174, missing the 1.
I tried delete the post in “Frequencies” and retype the frequency (144.174.000). I checked CAT settings. But the problem is the same.
Reinstalled v2.1.2 and all is OK again. Anyone else discovered this?
Radio Icom 706MK2, Win 10, USB CAT with FTDI FT232 chip.
73 Allan, OZ9AU


locked FT8 receiving DX the long way

Ray
 

Not about WSJT-X directly. I have noticed that occasionally a station, say in Japan for instance, seems to be traveling the long way (20 meters FT8). I'm in EM21, so I mean the path may be to my East rather than West. Antenna is hexbeam, usually pointed 30-40 degrees.

Can this be? Anyone else see this?


locked Re: Frequency error IC 706MK2

Bill Somerville
 

On 11/07/2020 00:23, OZ9AU Allan wrote:

Hi
I update wsjt-x to v2.2.2 from v2.1.2. All worked fine until I changed frequency to 144.174 MHz in FT8. The display on the radio shows 44.174, missing the 1.

I tried delete the post in “Frequencies” and retype the frequency (144.174.000). I checked CAT settings. But the problem is the same.

Reinstalled v2.1.2 and all is OK again. Anyone else discovered this?

Radio Icom 706MK2, Win 10, USB CAT with FTDI FT232 chip.

73 Allan, OZ9AU
Hi Allan,

thanks for the issue report, it is a known issue with the version of Hamlib used in WSJT-X v2.2.x. It has been fixed for the next release of WSJT-X.

73
Bill
G4WJS.


locked Setting Windows WSJT-X Tx audio levels #txaudio

Roger
 
Edited

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

 


locked Frequency error IC 706MK2

OZ9AU Allan
 

Hi
I update wsjt-x to v2.2.2 from v2.1.2. All worked fine until I changed frequency to 144.174 MHz in FT8. The display on the radio shows 44.174, missing the 1.

I tried delete the post in “Frequencies” and retype the frequency (144.174.000). I checked CAT settings. But the problem is the same. 

Reinstalled v2.1.2 and all is OK again. Anyone else discovered this?

 

Radio Icom 706MK2, Win 10, USB CAT with FTDI FT232 chip.

 

73 Allan, OZ9AU

 


locked Re: Colour highlighting scheme

vk4aac@...
 

Hi Ken,
Changed it from <eh> to <eoh>, now working ok.

Many thanks

Rob
VK2VH


locked Re: Colour highlighting scheme

Kermit Lehman
 

Use Notepad to edit the adif file (under File -> Open Log Directory) from <eh> to <eoh

73,
Ken, AB1J


-----Original Message-----
To: main@WSJTX.groups.io
Sent: Sat, Jul 11, 2020 1:10 am
Subject: Re: [WSJTX] Colour highlighting scheme

G'day guy's,
Thanks for your replies.
I do have the check boxes for the colours selected.
The first box is "My call in Message", the second box is "New DXCC".

The "New DXCC" is the only colour that appears, other decodes have no colours???

I tried the "Rescan ADIF" and I get a message..."Error Scanning ADIF Log.   Invalid ADIF Header"

Not sure what I need to do next.

Rob
VK2VH


locked Re: Colour highlighting scheme

vk4aac@...
 

G'day guy's,
Thanks for your replies.
I do have the check boxes for the colours selected.
The first box is "My call in Message", the second box is "New DXCC".

The "New DXCC" is the only colour that appears, other decodes have no colours???

I tried the "Rescan ADIF" and I get a message..."Error Scanning ADIF Log.   Invalid ADIF Header"

Not sure what I need to do next.

Rob
VK2VH


locked Re: Loss of sound output in 2.2.2

Bill Somerville
 

Hi Ron,

if Zoom is changing the levels of the audio device you have connected to your rig then you have set something up incorrectly. Usual that happens if you have either the default device set as the one connected to you rig, or you have the default communications device set as the one connected to your rig. Unfortunately just plugging in a headset, a web camera, or even a monitor with an HDMI connection can cause Windows to switch around audio device assignments.

73
Bill
G4WJS.

On 11/07/2020 00:55, R SCHMAHL wrote:
The other day using ver 2.2.2 my power output was only 5 watts. A little trouble shooting revealed that the system level control was only about 20%. I did not put it at that level. I had just come off a Zoom session. I suspect Zoom lowered the speaker output but did not put it back to normal when you close the AP. Ver 2.2.2 was working just fine before the Zoom meeting. If this is going to be the case perhaps the WSJTX AP should set the system level to max or some other fixed level on start-up. 
Ron K2PSD 


On Jul 10, 2020, at 5:41 PM, Bill Somerville <g4wjs@...> wrote:


On 10/07/2020 20:45, AE0DC@... wrote:

Greetings,

 

After installing (Updating) to 2.2.2 my output volume is greatly decreased.

This happens on all of my YAESU radios (FT991a, FTDX3000) , while I could compensate,

It creates a problem that didn’t exist before. Example switching to other modes including voice

The sound is to loud… You can imagine.

 

With no changes, but reinstalling older version. Problem disappears

It is def related to the software update.

 

I told you the radios, The PC is a top end ASUS, and running windows 10 64 bit.

 

SO I will stick with the older version, but I wanted it to be known this problem is out there.

 

Thanks, Doug AE0DC

Hi Doug,

a common cause of low Tx o/p is related to a change in the way that WSJT-X interacts with the system audio mixer per application level sliders. Check through the recipe in this old post for setting Tx audio levels and see it that helps:

https://groups.io/g/WSJTX/message/5077

73
Bill
G4WJS.



locked Re: Skipped decoding cycles....WSJT seems to fall asleep at times

R SCHMAHL
 

Are you using any other APs real time during the decoding? Other APs can max out the CPU if using resources during decoding.
Ron K2PSD

On Jul 9, 2020, at 9:57 AM, AH0U <bruce@croskey.org> wrote:

monitoring the3 CPU usage I see that it never gets above 43 percent and the Physical memory stays at 16 percent so I don't think the CPU usage is the problem.

17521 - 17540 of 31319